Kemal Balioglu makes some suggestions about ways you can make your DRaaS testing more efficient and productive.
I bet you didn’t know that one simple command line resulted in the full deletion of most of the production files for Pixar’s Toy Story 2 from a studio server back in 1998. The studio ensured it created daily backups of production files, however they didn’t realise until they made an attempt to restore the lost files that the backup solution hadn’t worked.
This event happened when backup solutions were immensely complex and difficult, if not impossible, to ‘test’. According to the story, the studio had seemingly been prepared for this unimaginable situation; however, they ultimately had to rely on blind luck to recover lost files. An employee just happened to have a copy of the movie that she had taken home the week before, and that became the de facto backup file.
Today, cloud-based disaster recovery solutions are quickly gaining enterprise-wide adoption as organizations seek to reduce hardware costs and improve flexibility in responding to unplanned downtime events.
Disaster recovery as a service (DRassS) not only allows organizations to quickly and easily recover data, but more importantly, enables them to resume operations seamlessly during a disaster. Advances in cloud-based disaster recovery solutions allow IT administrators to determine the level of protection at the server level. Mission critical servers can be set to recover instantly while other servers with less critical data might be set to recover at a longer recovery time objective (RTO).
Despite the benefits of cloud-based disaster recovery over traditional solutions, a disaster recovery program can only be successful if it is consistently tested. Regular scheduled testing must include communications, data recovery, and application recovery. DR testing in these areas is required to conduct planned maintenance and train staff in disaster recovery procedures.
Traditionally, disaster recovery tests have been complex, disruptive and consequently unpopular. Too often, testing focuses on backing up instead of recovery. While this approach ensures you have a copy, it does little to make the data, server, or application easy to reinstate. To further complicate efforts, many of the systems used in the testing are needed to run day-to-day operations. To have those systems down during testing is unacceptable.
A hybrid-cloud approach to disaster recovery has changed the testing landscape for the better, combining public cloud and SaaS automation software to make continuity planning easier. Companies gain data backup, fail-over of servers and the ability to have a secondary data centre at a different site to allow for regional disaster recovery.
Here are four suggestions to make your DRaaS testing more efficient and productive.
1. Plan ahead and plan often
The problem with disasters is they aren’t planned and are unexpected. If you’re not testing your disaster recovery strategies frequently, you might find yourself hung out to dry when lightning strikes. DR tests can be done frequently because DRaaS doesn’t have the physical infrastructure and configuration synchronization associated with traditional disaster recovery.
With an automated DRaaS solution, you don’t need to schedule IT personnel to manually check system configurations. Recent innovations make it easy to create an on-demand recovery node that you can test quickly. Unlike a typical backup-only cloud storage solution, hybrid DRaaS solutions can maintain up-to-date, ready-to-run virtual machine clones of your critical systems that can run on an appliance or in the cloud.
2. Test Your DRaaS in a sandbox
With DRaaS solutions, standby-computing capacity is available to recover applications in the event of a disaster. This can be easily tested without impacting your production servers or unsettling the daily business routine. A sandbox copy is created in the cloud, which is only accessible by the system administrator. These copies are created on demand, paid for while being used and deleted once the test is complete. The approach makes testing simple, cost effective and does not disrupt business operations. You can test disaster recovery and applications every day without missing a beat, assuming you have the right DRaaS provider.
Test cases can be performed against the recovery nodes in as little as 15 minutes, depending on the application, often with no incremental costs. Applications and services are immediately available for other uses, enabling businesses to effectively adopt cloud infrastructure or speed tie to production for new applications or initiatives.
3. Take advantage of a sliding scale
There are financial benefits to cloud-based testing. Service providers regularly offer sliding scales for disaster recovery testing. Putting your DR solution in the cloud also means there isn’t a redundant in-house infrastructure that is sitting unused most of the time.
The cloud gives small- to medium-sized businesses the same capabilities as larger organizations. With a level playing field, SMBs have greater access to disaster recovery solutions and the ability to test frequently.
4. Entice regular employee participation
In traditional disaster recovery settings, employees may consider testing to be time consuming and distracting from their already busy schedule. However, according to a survey by market research company, Enterprise Strategy Group, respondents using cloud-based DR services were four times more likely to perform weekly disaster recovery tests than those-hosting their disaster recovery or business continuity solution.
People learn by reputation, so just like fire drills, we have to create and practice disaster recovery drills, which are critical to a disaster recovery plan. Companies that fail to conduct regular drills shouldn’t be shocked when employees panic during a disaster.
Unplanned downtime events, whether caused by a natural disaster, human error, or hardware failure can have immediate and long-term negative impact. Take steps to ensure your business can quickly and easily recover its IT infrastructure and data, and minimise the impact by being prepared. Rather than just relying on luck.
The author
Kemal Balioglu is vice president of product at Quorum.
