The Recovery Point Objective (RPO) value you set during replication configuration affects replication scheduling.

The definition of an RPO of x minutes is that 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 replication starts.

For example, if the replication starts at 12:00 and it takes five minutes to transfer to the secondary site, the instance becomes available on the secondary site at 12:05, but reflects the state of the virtual machine at 12:00.

You set the RPO during replication configuration to 15 minutes. You start the replication at 12:00 and expect the replication to take 5 minutes to transfer. The next replication can start no later than 12:10. This replication instance is then available at 12:15 when the first replication instance that started at 12:00 expires.

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. For example, if the replication starts at 12:00 and takes 10 minutes to transfer an instance, the replication finishes at 12:10. You can start another replication immediately, but it finishes at 12:20. During the time interval 12:15-12:20, an RPO violation occurs because the latest available instance started at 12:00 and is too old.

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.