Many organizations have annual disaster recovery (DR) test requirements, whether to run production operations from a secondary facility for several days or test the functionality of systems and applications running in a DR facility while production workloads run as usual. Every business should have a disaster recovery plan and perform a DR test, especially with recent virus and ransomware activity.
In the past, disaster recovery was much more complex. However, virtualization and cloud technologies significantly improved DR capabilities and the ability to run workloads in separate or multiple locations. While advantageous, it is crucial to check the functionality of systems, processes, and people resources.
How often should I perform a disaster recovery test?
Your business needs and requirements will determine the testing frequency, but an annual test is usually sufficient for many. It is essential to schedule the test well in advance, especially if it involves a third party. Finding time for all parties as the end of the year approaches will be difficult. If you make significant infrastructure or application changes, it may be worth performing an additional test.
What are the goals of a disaster recovery test?
While you may think the goals of a DR test are obvious, setting objectives helps keep tasks in scope and focused. Implementing a disaster recovery testing plan helps. You want to verify connectivity and application functionality and ensure you have the appropriate users available to assist. Believe it or not, running into problems during your DR test can be a good thing so you can resolve the issues. You do not want to encounter issues during an actual emergency!
Some issues we have discovered while performing DR tests for customers:
- Old, unsupported, or end-of-life operating systems
- Unsupported operating systems that are too new (beta, just released)
- Old versions of virtual machines and hypervisors
- Unpatched servers take a long time to bring up, as they apply patches automatically. (Note: Be sure to follow regular patching practices.)
- Incomplete networking documentation
Disasters can happen at any time. Performing a disaster recovery test allows organizations to prepare ahead of a crisis and remediate issues before a disaster occurs. In addition to applications and systems testing, tests will enable you to fine-tune call trees, identify application owners and stakeholders, and understand the process of turning on DR workloads.
More Disaster Recovery Articles
What is Cloud Disaster Recovery (CDR)?
Your server goes down. Your network won’t work. Or worse…your office suffers a fire, flood, or other natural or man-made catastrophe. Whatever the case, you need to have a disaster recovery plan ready to protect your data as well as your overall business. Cloud...
Fully Managed Backup and Disaster Recovery Solutions
Good technology just works – right? That’s right…until it doesn’t. We all know that even the best managed IT environments require careful attention to be sure that your tools work when you need them. Backup and disaster recovery are particularly critical – these...
Does Your Cloud Disaster Recovery Service Come with Hidden Fees?
When it comes to picking a cloud disaster recovery service provider, you can make an easy choice by simply picking the one with the lowest rates per GB, right? Not so fast. Even if a cloud disaster recovery provider quotes you mere cents on the dollar per GB, the...
What is Cloud Disaster Recovery (Cloud DR)?
What Is Cloud Disaster Recovery? Often shortened to Cloud DR, disaster recovery is a plan put into place in case a disaster hits. Cloud DR refers to the component in your disaster recovery plan that involves the use of a cloud backup environment. The Cloud Component...
0 Comments