General discussion


Data and Code Recovery in a Disaster

By WelshBilly ·
I am currently working on a Disaster Recovery Plan specifically for our data and code. I work in a development team, so therefore I only need to worry about that aspect e.g whether the back ups actually work is down to another team, I just need to ensure they are backing up the correct data.

Some of the areas I have been asked to look into are safe storage of code; whether we should ensure that only critical data gets replicated to our off site servers; if applications should be organised into a priority order, so we would immediatly know which applications to work on first in a DR situation; what sort of documentation should we create? How often should the documentation and the plan be revisited?

I was wondering if anyone else had a plan for thier code and data recovery. What do you have set up to ensure business continuity if a disaster occured? What do you recommend?

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Collapse -

Backup Plan

by richard In reply to Data and Code Recovery in ...

Every week we do a full backup of all our code. This is to both onsite and offsite servers. Every night, at midnight, we do an incremental backup, this backs up only the things that have changed since the previous backup. This is a strong recommendation if you are working on important code. It is possible to backup only critical information, remember however that code that you believe is un-critical and is not backup may become critical very quickly when a disaster occurs so it is safter to back everything up.

As for documentation, you need to document every single backup so, in the rare event of a disaster, you can look at your backup documentation and know exactly what each back contains. This will save you having to go through the backups later on.

Collapse -

They are really valid points.....

by WelshBilly In reply to Backup Plan

Hi Richard,

Thank you for your response and I will be checking that code is backed up and double checking what is backed up at the moment. These are important points.

Say I have now ensured that our back-ups are correct, have you organised your applications into some sort of priority order? So if a disaster did happen you would know what applications to restore first.

Also have you looked at different scenarios/disaster types and accounted for each of these. For example your plan would be different if all of a department's laptops were stolen, compared to the building blowing up.

Have you considered that if a disaster does happen, that you may not have time to immediatly restore all of the data for every application. That you may have to work out what is the most crtitical data you would have and restore first so that departments can be up and running quickly but with critical data.

Related Discussions

Related Forums