2025 01 25 08 24 51

Summary

This transcript discusses the initial kickoff meeting for a Disaster Recovery (DR) test scheduled for the weekend of March 1st and 2nd. The test will focus on failing over the internet from Tarine to West Melbourne, minimizing disruption to the TC's internet. The session also highlights the need for updated contact details for effective communication during the test. Key tasks for DXC include performing health checks before, during, and after the failover. The document also addresses gaps in previous documentation and the importance of confirming team assignments and scope details.

Takeaways

• 😀 The DR test for TAAC and WorkSafe is scheduled for the weekend of March 1st-2nd, 2025, and will involve a failover from Tarine to West Melbourne without impacting TC’s internet.
• 😀 DXC's main role is to perform health checks before, during, and after the failover and failback processes.
• 😀 The DR test is a limited scope test and will only involve internet failover, ensuring no impact on the TC’s network.
• 😀 A document (the 'Rambo') was shared with participants prior to the meeting and updated with contact information for participants.
• 😀 The speaker emphasized the importance of attendees providing their contact phone numbers for better communication during the test, particularly for health checks.
• 😀 Resources have been mostly assigned, with the exception of middleware and 365, which are still pending assignments.
• 😀 The DR document provided by the previous vendor is sparse and lacks detailed information, leaving gaps in knowledge for some processes.
• 😀 Participants are required to perform health checks for the network, firewall, and other infrastructure components during the test.
• 😀 Certain steps within the DR document are marked as 'not applicable' or blacked out, such as line 36, for this particular test.
• 😀 The speaker clarified that steps marked in red or 'TBA' (To Be Announced) in the document are still to be confirmed or assigned.
• 😀 DXC will mainly perform health checks and not manage network configurations during the test, as their primary role is to monitor the environment's stability.

Q & A

What is the main purpose of the DR test discussed in the script?

The main purpose of the DR (Disaster Recovery) test is to perform a limited failover of the internet from Tarine to West Melbourne, without impacting the TC's internet, in order to validate and test the disaster recovery process.

When is the scheduled DR test taking place?

The DR test is scheduled to commence on the weekend of the 1st and 2nd of March.

Why is there uncertainty about the test duration in the document?

The uncertainty is due to the possibility that the failover might extend to Tuesday, the 2nd of March, which is why the exact duration has not been confirmed yet.

What does the term 'TBA' stand for in the document, and why is it used?

'TBA' stands for 'To Be Announced,' and it is used to indicate that certain roles or resources have not yet been assigned, such as for middleware and 365 resources.

What is expected of DXC's resources during the test?

DXC's resources are mainly required to perform health checks on the environment before, during, and after the failover process.

What are the missing or insufficient details in the runbook mentioned in the transcript?

The runbook provided by the previous vendor is very basic and lacks detailed documentation, particularly in sections related to health checks and implementation processes. Some sections, like the 'CIS to tab' section, are also non-existent or not clear.

How does the team handle steps that are not in scope for the current test?

For steps that are not in scope, they are not deleted from the documentation. Instead, they are blacked out, and the step number is crossed out to indicate that it is not applicable for the current test.

What additional action is requested from the participants in the meeting?

Participants are requested to provide their contact details, including phone numbers, to ensure they can be reached in case of any issues during the health checks or test process.

What is the status of resource assignments for the DR test?

Most of the DXC resources have been assigned to the test, with the exception of middleware and 365, which are still pending assignment.

What issue was mentioned about the previous vendor’s documentation?

The issue with the previous vendor’s documentation is that it was very minimal, lacking critical details, and in some cases, it was completely absent, making it difficult to understand the steps and processes needed for the DR test.