recovery point objective, or “RPO”, is defined by ​​business continuity planning​​. It is the maximum targeted period in which ​​data​​ might be lost from an IT service due to a major incident.​[1]​ The RPO gives systems designers a limit to work to. For instance, if the RPO is set to four hours, then in practice, off-site mirrored backups must be continuously maintained – a daily off-site backup on tape will not suffice. Care must be taken to avoid two common mistakes around the use and definition of RPO. Firstly, business continuity staff use ​​business impact analysis​​ to determine RPO for each service – RPO is not determined by the existent backup regime. Secondly, when any level of preparation of off-site data is required, rather than at the time the backups are offsited, the period during which data is lost very often starts near the time of the beginning of the work to prepare backups which are eventually offsited.



The recovery time objective (RTO) is the targeted duration of time and a service level within which a ​​business process​​ must be restored after a disaster (or disruption) in order to avoid unacceptable consequences associated with a break in ​​business continuity​​.​[1]

It can include the time for trying to fix the problem without a recovery, the recovery itself, testing, and the communication to the users. Decision time for users representative is not included.

The business continuity timeline usually runs parallel with an incident management timeline and may start at the same, or different, points.

In accepted ​​business continuity planning​​ methodology, the RTO is established during the ​​Business Impact Analysis​​ (BIA) by the owner of a process (usually in conjunction with the business continuity planner). The RTOs are then presented to senior management for acceptance.