Change and Project Management Implications on the DR Plan

implications on the DR plan

Anytime a business changes, tweaks, enhances or makes any major modifications to its current environment, it must look at the implications that this will have on its Disaster Recovery Plan, particularly if the applications are set up at a recovery site. The most effective way to do this is to build in checkpoints along the way and to accommodate for the changes. Ensuring that everything stays in sync between the primary site and a recovery site is essential to guaranteeing seamless implementation of a DR plan.

Examples of changes that will have implications to a DR site include:

  • Switching versions of software
  • Upgrading servers
  • Expanding storage
  • Changing OS

In general, software suppliers usually announce patches on a monthly basis for security purposes, and these patches impact operating systems. While these patches may have been downloaded, tested and applied at the production site, it is important that they are also downloaded, tested and applied at the recovery site as well to ensure that there is congruency between the sites. The goal is to prevent any snags or problems that could delay or prevent recovery at the time of disaster.

Build in checkpoints. It is important to make people aware of the Disaster Recovery implications of what they are doing. Monitor any new developments at various stages of implementation to confirm that they are migrated smoothly and efficiently to the recovery site. This may start  as simply as having a checkbox on a form to fill out. The goal is to be aware of, communicate and prevent potential inconsistencies before they emerge during disaster recovery.

Accommodate changes to DR. There is going to be an impact in the work, activity and costs associated with keeping a disaster recovery site in sync. There is also going to be an impact on the recovery processes functioning while a business goes through a transformation and makes changes to its production systems. It is vital that these impacts are accommodated. Be prepared for the potential loss of IT productivity, so that DR capabilities can absorb the effect that these changes had on the rest of the IT organization.

Develop a mindset. Get everyone on the same page because applying changes to DR is everyone’s responsibility. Make it common practice to monitor and accommodate upgrades. Having prompting fields, questions, and fill-in items on forms that are used in change requests, enhancements and projects makes everyone aware that there are real concerns to worry about, as well as providing information on how in-sync the recovery and production sites are.

Steve Tower

With many years of professional IT experience, and training as a Certified Management Consultant, a Project Management Professional, a Professional Engineer and a Member, Business Continuity Institute, Steve Tower has the skills and abilities required to assist with even the most complex disaster recovery planning initiatives. Below, Steve discusses the necessary tools involved in setting up a disaster recovery plan and program.