A target expressing to what point in time data must be recoverable when a failure or disaster occurs. With an RPO of 1 hour, at most the last hour of data may be lost, so backups or copies of the data must be taken at least every hour.
Japanese name: RPO(目標復旧時点)
RPO (recovery point objective) appears in 3 practice questions across 2 topics, including System Architecture and Reliability, IT Service Management and Systems Audit.
The RPO is a target for how far back recovery may go, that is, the amount of data that may be lost expressed in time. The RTO (recovery time objective) is a target for how long resumption may take. For example, with an RPO of 4 hours and an RTO of 2 hours, a failure must not lose data older than 4 hours, and business must resume within 2 hours. They are separate targets, so a scheme that meets both must be chosen.
When protection relies on periodic backups alone, a failure just before the next backup loses data for the whole backup interval. The backup interval is therefore made no longer than the RPO. To bring the RPO down to minutes or near zero, database update logs are sent frequently to another location, or replication copies data to another server.
Synchronous replication completes an update only after confirming that the write has also finished at the replica, so no data is lost on failure (an RPO of zero). In exchange, the round-trip communication time to the replica is added to every update, so responses become slow between distant sites. Asynchronous replication sends copies later, so responses are fast, but data not yet sent may be lost on failure.
Answer: A. A target expressing up to what point in time data must be recoverable when a failure occurs (how far back data loss is tolerated)
The RPO (recovery point objective) is a target expressing to what point in time the data must be restorable when a failure occurs. For example, an RPO of 1 hour means the data must be restorable to a point within the hour before the failure, so backups or copies of the data must be taken at least every hour. The time allowed until business resumes is the RTO (recovery time objective), and the shorter the RPO and RTO, the more the required facilities cost.
Answer: B. Backups are taken every 3 hours, and recovery takes 1.5 hours when a failure occurs
If a failure occurs just before the next backup, data for the whole backup interval is lost, so meeting the RPO requires a backup interval no longer than the RPO. Also, the recovery time must be no longer than the RTO. With backups every 3 hours and recovery in 1.5 hours, at most 3 hours of data is lost (4 hours or less) and recovery takes 1.5 hours (2 hours or less), so both are met. The 1-hour scheme fails the RTO, and the 6-hour scheme fails the RPO.
Shorter ones reduce the impact of failures, but the cost of replication, standby equipment and operational effort grows. It is common to decide them for each business by comparing the losses from stopped business or lost data with the cost of the measures.
With synchronous replication, a configuration that loses no data up to the moment of failure is possible. However, if data is corrupted by a mistaken operation or a software bug, the corrupted state is replicated as well, so backups that can return to past points in time are still needed separately.
The RPO (recovery point objective) is a target expressing to what point in time the data must be restorable when a failure occurs.
In business continuity planning, which describes the RPO (r…If a failure occurs just before the next backup, data for the whole backup interval is lost, so meeting the RPO requires a backup interval no longer than the RPO.
For a system, the RPO (recovery point objective) is set at …First, the impact on the business is analyzed (business impact analysis) to determine the critical activities and their acceptable downtime, and targets such as the recovery time objective (RTO) and recovery point objective (RPO) are set for the systems that support them.
Which of the following is an appropriate way to draw up a b…As an Amazon Associate I earn from qualifying purchases.
RTO (recovery time objective) BCP (business continuity plan) Differential backup Dual system Duplex system Fail-safe Fail-soft Fault tolerance Fool-proof Hot standby