You architect your BC/DR/HA solution around the RPO, build the solution to match the RPO, and then measure the solution’s performance against the RPO. Remember: an RPO is a design spec, not a statistic. If your primary source machine fails, your organization would lose no more than the last 30 seconds of production system updates.Īn RPO is a business decision as to how much current data (orders, invoices, inventory moves) the business is willing to risk if the production source system becomes unavailable. RPO provides a target for designing your BC/DR/HA solution.įor example, if you designate a RPO of 30 seconds, you would design your solution to synchronize data between your production/source and backup/target solution so that at any given moment, the data between the two boxes is no more than 30 seconds out of sync. They all work together in the following ways to define how data is synchronized between your source and target machines and how long it takes to switch production from your source to your target machine.Ī Recovery Point Objective (RPO) is the maximum time frame your organization is willing to lose data for, in the event of a major IT outage. Think of RPO, RTO, and RTA are being three gears in the same machine.Įach gear helps move your BC/DR/HA strategy in the right direction. RPO, RTA, and RTO are the terms management uses to communicate goals for a BC/DR/HA system (click to enlarge)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |