Don’t Experience Downtime, Have a Plan

Lenny ChesalBy Lenny Chesal, CRRD Chief Evangelist

Part of any Disaster Recovery and Business Continuity (DR/BC) plan, is determining how best and how frequently todisaster-recovery-plan-ts-100662705-primary.idge back up your network and data.  Some companies establish daily back-ups, and others require back-ups on a real-time basis. While no company wants to experience ANY downtime – it all comes down to balancing your specific IT requirements, the amount of downtime that is acceptable, how much data you need to back-up and your budget. Two key elements to consider in DR/BC planning are Recovery Time Objective (RTO) and Recovery Point Objective (RPO).

RTO is the point in the future when you’ll be up and running after an outage. Another way to think of it is, how long can you go without a specific application?

While it sounds similar, RPO is actually quite different. It is essentially the point in time in the past that you will recover to and dictates the allowable data loss. How much data can you afford to lose if your data network goes down? For example, organizations that are highly transaction oriented, such as retail or banks, could loose quite a bit of data during an outage – so their allowable data loss or RPO would be lower than other types of companies.

no_downtimeAs every business is different and the tolerances for downtime can vary significantly, it is important to talk to a DR/BC expert. There is a lot to consider in DR/BC planning, but taking the time to understand what’s at risk and how long it will take to get back up and running after an outage, is well worth the effort. creates customized solutions focused on meeting the specific needs of customers.  Contact us today, to establish or improve your RTO/RPO and develop a DR/BC solution specific to your business.