If your RPO is 4 hours, then you need to perform backup at least every 4 hours; every 24 hours would put you in big danger, but if you did it every hour, it might cost you too much and not bring additional value to the business. Both Recovery Time Objective and Recovery Point Objective are determined during the business impact analysis BIA , and the preparations for achieving them are defined in the business continuity strategy. For example, an e-commerce site may need to be online 4 hours after a disruption, so RTO is 4 hours.
Now, this same e-commerce site has two databases, one for its product catalog, which is updated once a week, and the second to record sales thousands per day. Business continuity and disaster recovery plans are things that organizations need to have and hope not to use, and in such cases, they need to find a balance between investing the minimum amount of resources possible, and having the maximum confidence that the plans will work.
Without determining them properly, you would just be guessing — and guessing is the best way to ensure recovery disaster, instead of recovery from a disaster.
Watch now. You may unsubscribe at any time. For more information, please see our privacy notice. For full functionality of this site it is necessary to enable JavaScript. Here are the instructions how to enable JavaScript in your web browser. Dejan Kosutic. What is the RTO? What is the RPO? The point is, the harder it is to recover or recreate the data, the shorter the RPO needs to be. If during real-life disaster recovery, you go over the given time-frame, you should either reconsider the RTO calculations or update your disaster recovery plan and procedures.
RPO, or Recovery Point Objective , is a measure of the maximum tolerable amount of data that the business can afford to lose during a disaster.
It also helps you measure how long it can take between the last data backup and a disaster without seriously damaging your business. RPO is useful for determining how often to perform data backups. Determining the RPO is important because you will lose at least some data during a disaster, even if your backups are near instant. Most businesses back up their data at fixed intervals -- once an hour, once a day, or perhaps just as rarely as once a week. For example, if you back up your data once a day at midnight and there is a disaster at 8 AM.
In this case, you will lose 8 hours of data. But if your RPO is, say, four hours, you're not. The RPO has yet another layer of depth if we are considering live production datasets. You have the RPO of four hours, hence you can afford to lose four hours' worth of data.
If your backups are done once every two hours, you have to recover the data in two hours, rather than four. RTO, or Recovery Time Objective, is the target time you set for the recovery of your IT and business activities after a disaster has struck. The goal here is to calculate how quickly you need to recover, which can then dictate the type or preparations you need to implement and the overall budget you should assign to business continuity.
If, for example, you find that your RTO is five hours, meaning your business can survive with systems down for this amount of time, then you will need to ensure a high level of preparation and a higher budget to ensure that systems can be recovered quickly. On the other hand, if the RTO is two weeks, then you can probably budget less and invest in less advanced solutions. RPO is determined by looking at the time between data backups and the amount of data that could be lost in between backups.
As part of business continuity planning, you need to figure out how long you can afford to operate without that data before the business suffers. A good example of setting an RPO is to imaging that you are writing an important, yet lengthy, report. Think to yourself that eventually your computer will crash and the content written after your last save will be lost. How much time can you tolerate having to try to recover, or rewrite that missing content?
0コメント