How to create a disaster recovery test checklist
| Channel | Publish Date | Thumbnail & View Count | Download Video |
|---|---|---|---|
 | Publish Date not found |  0 Views |
Disaster Recovery Test Checklist
Provide a detailed DR testing plan when attempting to obtain approval and funding to conduct testing.
Clearly identify goals, objectives, procedures and what you are looking for in your post-test analysis.
Assemble a testing team – including subject matter experts – and make sure everyone is available on the scheduled test date.
Specify exactly what needs to be tested, such as backup and recovery, system and network resumption, or the employee notification system.
Carefully document your DR plan and disaster recovery test scripts and be prepared to edit them.
Review and confirm that all code in the test scripts is correct.
Include all relevant technology elements and processes that will be tested in the plan – no matter how insignificant they may seem.
Before starting, ensure that the test environment is ready, available, and does not impact production systems. Ensure that the test does not conflict with other activities or tests.
Schedule a DR test, which may take hours, well in advance; notify and remind other IT managers of the upcoming test.
Conduct a dry run – or hands-on exercise – before the disaster recovery test goes live to uncover and resolve potential issues.
If problems occur, stop the test and review it. Continue if the problem can be worked around. Reschedule the test if necessary.
Assign a timer to record start and end times and a scribe to take notes to prepare the debriefing report, which describes what happened during the test, what worked and what didn't, and what was learned.
Update disaster recovery and business continuity plans (BCP) and other documents based on the findings from the DR test.
Provide a detailed DR testing plan when attempting to obtain approval and funding to conduct testing.
Clearly identify goals, objectives, procedures and what you are looking for in your post-test analysis.
Assemble a testing team – including subject matter experts – and make sure everyone is available on the scheduled test date.
Specify exactly what needs to be tested, such as backup and recovery, system and network resumption, or the employee notification system.
Carefully document your DR plan and disaster recovery test scripts and be prepared to edit them.
Review and confirm that all code in the test scripts is correct.
Include all relevant technology elements and processes that will be tested in the plan – no matter how insignificant they may seem.
Before starting, ensure that the test environment is ready, available, and does not impact production systems. Ensure that the test does not conflict with other activities or tests.
Schedule a DR test, which may take hours, well in advance; notify and remind other IT managers of the upcoming test.
Conduct a dry run – or hands-on exercise – before the disaster recovery test goes live to uncover and resolve potential issues.
If problems occur, stop the test and review it. Continue if the problem can be worked around. Reschedule the test if necessary.
Assign a timer to record start and end times and a scribe to take notes to prepare the debriefing report, which describes what happened during the test, what worked and what didn't, and what was learned.
Update disaster recovery and business continuity plans (BCP) and other documents based on the findings from the DR test.
Please take the opportunity to connect with your friends and family and share this video with them if you find it useful.
