ES Outlook Weekly Brief
Be first to read the latest tech news, Industry Leader's Insights, and CIO interviews of medium and large enterprises exclusively from ES Outlook
Disasters are unpredictable, and the enterprises should have an effective disaster recovery plan to combat disasters efficiently. Whether the company uses traditional disaster recovery process or uses disaster recovery as a service (DRaaS), they should have an appropriate disaster recovery plan. Here are a few disaster recovery planning methods that might benefit organizations:
Disaster isn’t over until the Recovery: Normalcy doesn’t come just after the disaster; the actual recovery can take weeks or months to accomplish. For example, floods not only wipe out a company’s equipment but it also affects an employee’s home. Supply-chains also get affected during the floods. An effective disaster recovery plan must include the recovery of supply chains and logistics along with other processes.
Testing the disaster recovery plan: Companies should keep in mind that testing a plan or an application provides an opportunity to smooth future disruptions and disasters. Although the disaster recovery testing is not a cost-effective option, companies cannot prove the value of assets and planning without a real drill.
Inter-disciplinary continuity planning: enterprises should allocate tasks in case of a disaster situation. Employees should have an idea of what to do before, during, and after a disaster. Disaster recovery plans should be well documented and distributed across the organization.
Employee Participation: disaster recovery is not just an IT department’s job. If the entire organization is not engaged in disaster recovery plans, then it is destined to fail. All the stakeholders should participate in business continuity efforts.
Synchronization: After every drill, companies should check for synchronization. If the applications are not in sync, then it can prove to be a disaster for the company, as they might lose crucial data. Lack of synchronization can break the IT infrastructure of a company.
Defining dependencies: Understanding and defining the dependencies is a must for organizations. Figuring out dependencies is an arduous task, but it is required for a smooth business process after a disaster.
By Kim Tracy, CIO, Northeastern Illinois University
By William Miller, SVP & CIO, Broadcom, Inc.
By Dr. Cheryl Flink, Chief Strategy Officer, Market Force
By Paul Kent, VP-Big Data, SAS
By Tom Conophy, CIO, Staples Inc.
By Mark Lilien, SVP & CIO, Things Remembered
However, if you would like to share the information in this article, you may use the link below: