Written disaster recovery plan with continual updating
This phase seeks to address the following questions: Disaster Recovery as a Reality is when a potential triggering event is recognized and acknowledged, e.g., production server hard disks are encrypted or when the primary datacenter is flooded.This means that the response processes and team are active.You’ll want to determine if your organization plans to have remote storage of its backups or backups that are off-site.Next, you’ll have to decide if you plan to do a full, incremental or differential backup.The details of how to build and execute a complete disaster recovery plan requires resources and time beyond the scope of this article, however, it is important to review the critical phases and how they interrelate.Each phase can be approached by breaking the process down into a set of questions that leadership needs to address, and a set of requirements that need to be defined.Constant feedback from your disaster recovery plan team, as well as employees within your organization, will make your plan even stronger should a disaster take place.
A full test brings day-to-day operations to a stop because it performs a complete recovery.
Written by Peter Shand Chief Technology Officer, Americas Disaster Recovery for information technology assets is uppermost in the minds of many business and technology decision makers.
Whether it is global concern about the possible impact of cybersecurity threats, inevitable breaches, or more location specific concerns related to natural or man-made disasters, the vulnerability is real.
One important decision your disaster recovery plan committee will need to make is backups.
You’ll need to factor backups (tapes, disks, operator manuals and installation software) into your plan.