Which of the following is most important to determine the recovery point objective RPO for a critical process in an enterprise?

Planning for disaster recovery means knowing what questions to ask.

After living through the business disruptions of the past few years, companies are re-examining their business continuity plans and evaluating how much they contributed to the agility and resiliency of their businesses. Here we outline some of the questions you should be asking yourself around business continuity and setting your RTO (Recovery Time Objective) and RPO (Recovery Point Objective).

Which is more important: Time to recovery or retrieving data and documents?

Business Continuity and IT Disaster Recovery planning tend to focus first on Recovery Time Objective (RTO) then second on Recovery Point Objective (RPO). RTO includes system and application recovery while RTO is focused on data recovery. But does that really make sense? Customer information, financial data, product specifications, research sets, accounts payable metrics, form transactions… the list could go on and on. Data is the life’s blood of any company.

It’s good to point out that not all company data resides in specialized applications monitored by IT. Businesses tend to have a lot of information stored in PDF-formatted documents or even paper that are critical to their day-to-day business functions. These documents may be stored on local servers, on Microsoft, Google, Dropbox, or in any of a dozen other cloud-based applications. Do businesses define in their plan which documents are critical? Do they define when the documents/data are required to be available, or they can’t function?

Who sets a data recovery strategy, and how? 

That said, every piece of data is not critical to recovery. How do you separate what’s critical from the rest? Who sets the Recovery Point Objective? If IT sets the backup time frame for the data recovery, do they ask the business what their need is? How much data they can the business functions afford to lose? Does the business have a way to recreate any lost data?

Then there is all the data that is still in paper form. What is the plan for data that has come in through the mail or fax machine that has not been entered into any electronic systems yet?

Recovery strategies depend on timing. How long it has been since the last backup will tell us how much data could be lost. Is this amount of loss acceptable? Should the data be backed up more frequently or stored in a safe accessible place? What is the timing of the backups and are they full or incremental?

These are just a few of the questions that need to be asked when setting up your recovery point objectives and data recovery strategies. Other considerations include:

  • Has the data been analyzed and prioritized into what is critical, necessary or optional to support the business recovery?
  • Where is your data? Is it centralized or is it all over the place, on local servers, on SharePoint, in the “cloud”.
  • Can just the critical docs be restored in a timely manner or does the whole storage system have to be restored before the business can get to them?
  • How much data is lost between backups?
  • Can the lost data be recreated?
  • Does your BC/DR tool help you make important data available quickly?

These are some of the questions that need to be answered in order to create a recovery point objective (RPO) that the company can live with without losing too much of its “lifeblood”. Where do you and your company stand? Have you asked all the “right” questions?


Learn about SAI360's solutions for disaster recovery and business continuity management.

Keep Reading

When it comes to data backup and disaster recovery planning your recovery point objective (RPO) is a critical tool. Put simply, your RPO is the metric you set for the amount of data your organization can tolerate losing in a data disaster. Your RPO helps you determine how often you need to back up your data, and the infrastructure you need to have in place to support your backup plan. It's important to note that, despite its title, RPO is less about the actual execution of recovery and more about establishing the framework so that when you do have to recover from a data loss, you'll be able to get all of the data you need back up and available. RPO isn't a tool for measuring or reducing downtime. That's where your recovery point objective (RTO) comes into play. So let’s take a deeper look into determining your RPO.

Thinking Through Your RPO

Which of the following is most important to determine the recovery point objective RPO for a critical process in an enterprise?

Even if your systems are protected by a high availability system, you may lose some data when a disaster strikes. The question you have to ask is, how much data can my organization afford to lose? Unfortunately, that’s a complicated question. Most likely your gut reaction is, “I don’t want to lose any of my data. I need all of it.” There are options for meeting that requirement, including StorageCraft backup and disaster recovery solutions, but there are a number of factors you need to consider—including cost—when determining your RPO. Every backup you take on every system in your environment takes up space, and if you’re taking backups every 15 minutes it can really add up. That’s not to mention the bandwidth each backup takes across your network. Enter RPO. Calculating your RPO helps you set up your backup solution so that it fits both your data and your budget. By realistically assessing the amount of data you can afford to lose, you put yourself in a position to balance those data needs with your current infrastructure and identify areas where you may need to make updates. Say you determine that you can really only afford to lose an hour’s worth of data. It's relatively simple to do the math and figure out how many servers and the amount of bandwidth you need to make that happen. Keep in mind that different systems will have different RPOs. Critical systems, like those in development or accounting (or your CEO’s laptop), may demand more rigorous RPOs because a data loss in those areas could create serious problems for the company.

How Much Data Can You Lose?

So what do we mean by how much data you can “afford to lose”? The answer usually varies. You and your team are the only ones who understand the value of your data, so when you’re determining your RPOs ask yourselves “what will happen after we lose specific data, including applications, structured, and unstructured data?” Will we need to recover all of it or is some of that data more or less expendable? What if it’s not expendable? Then set your RPO and corresponding backup schedule accordingly. Ultimately, determining an RPO for each of your systems is an essential part of your disaster recovery plan. Being prepared for a disaster is really all about understanding and adapting your IT environment to support your organization's objectives. RPO is one great tool to help you do just that.

Which is more important RPO or RTO?

The main difference is in their purposes – being focused on time, RTO is focused on downtime of services, applications, and processes, helping define resources to be allocated to business continuity; while RPO, being focused on amount of data, has as its sole purpose to define backup frequency.

What is the RPO for critical process?

Recovery point objective (RPO) is defined as the maximum amount of data – as measured by time – that can be lost after a recovery from a disaster, failure, or comparable event before data loss will exceed what is acceptable to an organization.

How is recovery point objective determined?

If you want to calculate recovery point objectives for your business or organization, consider following these five steps:.
Look at how often files update. ... .
Review the goals of your BCP. ... .
Consider industry standards. ... .
Establish and approve each RPO. ... .
Analyze your RPO settings consistently..

What does RPO stand for recovery?

Recovery Point Objective (RPO) and Recovery Time Objective (RTO) are two of the most important parameters of a disaster recovery or data protection plan.