When disaster strikes, the first thing you need is a plan. Ideally you should have the plan BEFORE the disaster hits. What should go into the plan, and what critical information does your staff need to know about? To start, lets cover some of the basics:
O.R.P.I.S. is simply shorthand for "Outage Recovery Plan for Information Systems", some companies call this a Disaster Recovery Plan (DRP). Some companies have a "planned" outage recovery plan and add a P to the front of the acronym. The most important part of this plan is that it is up to date and can be followed by non-technical people if necessary. It should detail steps to be taken before, during and after a disaster occurs. Note that a disaster doesn't necessarily have to mean that your systems were destroyed, depending on the business it can mean a wide range of "outages" that bring key systems offline. So for example a printing company being unable to print could be a disaster!
Goals and Objectives
Before you can write the plan, you need to decide beforehand what the goals are. How much downtime is acceptable, and what extent you are going to go to to bring systems back online. For example will you say that if there is a disaster you will be back online in 24h with 7day old data, or will it say that you will be back online in 1h with 8h old data. These goals must be decided beforehand. This is often called your Recovery Time Objective (RTO) and Recovery Point Objective (RPO).
What goes in the plan?
This is a difficult question to answer, because it depends on many factors. What type of business you are in, your objectives and goals, how you will fail over to another site if you can do that, etc. There is no one-size-fits-all plan, what the plan will look like can depend on many many factors. It is best to ask an expert for help on designing your plan and pushing it through to completion.
You need to do dry-runs or other methods to test your plan before a disaster strikes. This will greatly decrease your downtime! You need to test on a regular basis, at least once a year and you should have a non-technical person follow the documentation so you can be sure that if you have the "hit by a bus" problem you can still recover.
Give RDAIT a call
To learn more about how RDA can help your business with your ORPIS or Disaster Recovery Plan, give us a call or use the contact form on the right.