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
Why every company needs DRaaS
DRaaS is insurance that you don't know you need--until you need it. If your business relies on any type of data or digital systems - and nowadays what business doesn't - then you are already well aware of the necessity of protecting data from malicious threats and...
What is Data Protection as a Service (DPaaS)?
Data protection as a service is an overarching principle of protecting data no matter where it resides and utilizes tools to protect data from various threats. We often think of backups and disaster recovery when considering data protection, but DPaaS also includes...
The Veeam 2021 Data Protection Report
image credit: Veeam® Software The world faced unique, historical challenges in 2020 due to COVID-19, which introduced economic issues and impacted digital transformation efforts. Veeam® Software’s 2021 Data Protection Report covers how that cataclysmic year affected...
Why BaaS when you can DRaaS?
All images and data sources credit Veeam Software or Jason Buffington Veeam® Software’s live LinkedIn series on Mondays in June discussed Backup as a Service (BaaS) and Disaster Recovery as a Service (DRaaS). Both topics are near and dear to our hearts. Veeam’s Jason...
0 Comments