When you set a Recovery Point Objective (RPO) value during replication configuration, you determine the maximum data loss that you can tolerate.
How the Recovery Point Objective Affects Replication Scheduling
The RPO value affects replication scheduling, but vSphere Replication does not adhere to a strict replication schedule. For example, when you set the RPO to 15 minutes, you instruct vSphere Replication that you can tolerate losing the data for up to 15 minutes. This does not mean that data is replicated every 15 minutes.
If you set an RPO of x minutes, and the RPO is not violated, the latest available replication instance can never reflect a state that is older than x minutes. A replication instance reflects the state of a virtual machine at the time the synchronization starts.
If you set the RPO to 15 minutes and the replication takes 7.5 minutes to transfer an instance, vSphere Replication transfers an instance all the time. If the replication takes more than 7.5 minutes, the replication encounters periodic RPO violations.
The replication scheduler tries to satisfy these constraints by overlapping replications to optimize bandwidth use and might start replications for some virtual machines earlier than expected.
To determine the replication transfer time, the replication scheduler uses the duration of the last few instances to estimate the next one.
How the 5 Minute Recovery Point Objective Works
If the target and the source sites use VMFS 6.0, VMFS 5.x, NFS 4.1, NFS 3, vVol, or vSAN 6.2 Update 3 storage and later, you can use the 5 minute RPO.
vSphere Replication displays the 5 minute RPO setting when the target and the source site use VMFS 6.0, VMFS 5.x, NFS 4.1, NFS 3, vVol, or vSAN 6.2 Update 3 storage and later.
If you are using different datastore types between the source and the target site, you can use the 5 minute RPO setting .
The 5 minute RPO requires the source host to be ESXi 6.5 or later.