Written disaster recovery plan with continual updating
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.
Another crucial detail that should be included in your disaster recovery plan is the individuals authorized to declare a disaster, personnel allowed to access the recovery site and where the disaster recovery plan implementation team should meet after a disaster occurs.
Be sure to maintain a list of emergency phone numbers you’ll need when a disaster is declared.
Be sure to consider the configuration of your network, cloud computing, web applications, and software as a service (Saa S) in your overall planning.
If your organization uses Saa S or cloud computing, you’ll certainly want to document these services in your overall disaster recovery plan.
This phase seeks to address the following questions: Disaster Recovery as a Policy/Process is the stage after the strategic plan has been completed where implementation and continuous improvement of the technology or processes occurs.
This medium is widely in use today but is basically becoming obsolete do the decreasing cost of storage.
It’s also important to consider all components of your organization’s infrastructure.
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.