You might encounter RPO violations even if vSphere Replication is running successfully at the recovery site.
When you replicate virtual machines, you might encounter RPO violations.
RPO violations might occur for one of the following reasons:
- Network connectivity problems between source hosts and vSphere Replication servers at the target site.
- As a result of changing the IP address, the vSphere Replication server has a different IP address.
- The vSphere Replication server cannot access the target datastore.
- Slow bandwidth between the source hosts and the vSphere Replication servers.
To calculate bandwidth requirements, see Calculate Bandwidth for vSphere Replication.
- Search the vmkernel.log at the source host for the vSphere Replication server IP address to see any network connectivity problems.
- Verify that the vSphere Replication server IP address is the same. If it is different, reconfigure all the replications, so that the source hosts use the new IP address.
- Check /var/log/vmware/*hbrsrv* at the vSphere Replication appliance at the target site for problems with the server accessing a target datastore.
- Verify that you have sufficient bandwidth.