Assuming a 10GbE LAN connection, other than if you have extreme change rates so your RPO cannot be met, are there any issues using vSphere Replication with large VMs i.e. file servers with 10TB of data or 2TB Exchange servers?
If the change rate is really high, disk consolidation at the recovery site (redo logs merged with the base disks once complete replica instance is available) can take more than 15-20 minutes and failover initiated from VR UI plugin at the Web Client or test cleanup, planned migration or disaster recovery initiated via SRM Recovery Plan can fail. Re-try once the disk consolidation is complete will succeed.
Issue with 20 minute timeout in VR is fixed in 5.5 and next releases.
The default 15 minute timeout in SRM can be increased via the config file (default timeout value of RemoteManager).
Here are some limitations. Are you gone through this.
Will you go through following steps.
Each vSphere Replication management server can manage a maximum of 500 replicated virtual machines.
vSphere Replication supports a maximum disk size of 62TB.
vSphere Replication no longer supports IBM DB2 as the vSphere Replication database, in accordance with the removal of support for DB2 as a supported database for vCenter Server 5.5. If you use DB2 as an external vSphere Replication database, contact VMware support for instructions about how to migrate your data to a supported database.
vSphere Replication does not support upgrading the VMware Tools package in the vSphere Replication appliance.