5 things all IT Disaster Recovery Plans need

No one really likes to think the worst. Although if you’re a responsible business owner; it’s not a good practice to ignore the growing possibilities of something going wrong until it actually does. This is why it’s important for an IT disaster recovery plan. It’s not unheard of that a natural disaster, theft or even just an unexpected user error can bring down entire organisations.

An IT disaster recovery scenario - you never know when you'll have one on your hands!

An IT disaster recovery scenario – you never know when you’ll have one on your hands!

To reduce the impact and chance of critical company data being compromised, lost or even unrecoverable – there are five things any good IT disaster recovery plan needs. We outline them below.

1. A Solid Backup Strategy

Developing and maintaining a robust backup strategy is a core component to get through any disaster situation. This would include a combination of the following:

  • permanent on-premise backup
  • an offsite backup (either taken offsite manually or written directly to the cloud)
  • Multiple backup types ranging from file level to complete image backups.

You’re covered for the largest possible number of possible disasters your business may encounter just by ticking off these points within your backup strategy! Or just use the 3-2-1 backup strategy.

2. An Expert Disaster Recovery Team

The execution of every plan is the difference between success and failure. This is no different for an IT disaster recovery plan. Assembling a team of not only IT focused members, but operational members as well is well regarded. In addition to making sure of their understanding of the DR plan and their role within it, include all relevant contact information for these key stakeholders within the plan itself.

3. Detailed Contact List

Apart from the contact details of key internal staff (as mentioned above); a contact list of key external stakeholders should also be included.
This list could include the likes of:

  • Internet Service Providers
  • Data Centers required to take on hosting responsibilities
  • Impacted external users (suppliers and clients)

4. Robust Documentation

Since a disaster recovery plan is most likely going to be used in a disaster situation – it needs to be documented properly. This means that it needs to be easy to follow; but also detailed enough so that it doesn’t leave any ambiguity in the steps and processes.

A good way of doing this is using pictures, diagrams to achieve this (as they say ‘a picture is worth 1000 words’).

A key requirement for the DR team is to know all relevant documentation; before a real emergency ever occurs!

5. Every IT disaster recovery plan is a live document

Just like a business never stands still; the IT disaster recovery plan isn’t a static document. Floor plans change, hardware and software retired, staff move on, etc.
If the DR plan wasn’t to reflect such changes; then systems which no longer exist are being looked for, calls to the wrong ISP occur and the General Manager from 4 years ago is a main contact.

These types of situations are not only embarrassing; but waste valuable time that increases the RTO and RPO. This heightens the impact the disaster ultimately has on the business overall!

Don’t take on a disaster alone – consider a disaster buddy!

Regardless of the scale of the disaster; it’s always good to have some backup in the form of a disaster recovery company.
Test My Backups can help in a variety of ways when it comes to:

Therefore; we’ll be able to answer your questions. Just contact our team for an obligation free chat about your situation!

 

By |2018-09-18T17:56:24+00:00June 7th, 2018|

Leave a Reply