Recovery time objective and recovery point objective in disaster recovery planning

Article

Recovery time objective and recovery point objective in disaster recovery planning

Recovery time objective (RTO) and recovery point objective (RPO) are the key metrics to determine the disaster recovery (DR) level required to recover business processes and applications.

    Requires Free Membership to View

    When you register for SearchDisasterRecovery.com, you’ll also receive targeted emails from my team of award-winning editorial writers. As you know, an interruption can threaten your organization at any time – and it’s our goal to ensure you’re armed with the right tips and information to help you ensure a swift recovery.

    Rich Castagna, Editorial Director

    By submitting your registration information to SearchDisasterRecovery.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchDisasterRecovery.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

They are reciprocally proportional to the cost of disaster recovery: The closer RTO and RPO are to zero, the more expensive DR provisioning will be. If the recovery time takes days or even weeks, costs will likely be significantly less.

More on disaster recovery planning
Array-based data replication: The pros and cons

Using data classification tools to aid in disaster recovery planning

Change management in disaster recovery and business continuity planning

Determining the necessary recovery time objectives and recovery point objectives is the most important exercise a business needs to perform to ensure the cost-effective level of disaster recovery. RTOs and RPOs are derived in two ways: through the analysis of business processes and applications, which determines the value of business processes, and the anticipated financial impact if they become unavailable.

Obviously, this varies greatly by business process and application. "While for just-in-time manufacturing, the critical threshold may be 15 minutes, it could be days for a marketing application," said George Ferguson, worldwide service segment manager for Hewlett-Packard (HP) Co.'s business continuity and recovery services.

Determining recovery time objectives and recovery point objectives can be an iterative process because of two competing forces: available budget and required recovery objectives. "The challenge of contingency services like disaster recovery is to find the right balance between available budget and what's required to sustain the business," said Greg Schulz, founder and senior analyst at StorageIO Group, Stillwater, Minn.

This article originally appeared in Storage magazine.

About this author: Jacob Gsoedl is a frequent contributor to "Storage" magazine.