Hi,
The original request was for "hands on experience" with the products. However, the given reply above ignored the case for using SRM w/ vSphere Replication and also gave some incorrect statements.
I hope that the clarifications below might help:
Other limitations
• No failback
Automated failback is available when using SRM + vSphere Replication.
Manual failback is possible, by using the disks of the old source VM as initial copies.
• No swap exclusion
Disks can be individually excluded from replication. vSphere Replication replicates whole disks, not individual files.
• No network customization (network mapping)
• No re-IP upon failover
These features are available when using SRM + vSphere Replication.
• No traffic compression
• No traffic throttling
These features are considered for a future release.
Currently third party tools can be used on the networking layer (source ESXi -> target VR server TCP connections) to provide such functionality.
• Minimum possible RPO is 15 minutes
This feature is considered for a future release.
• Works within single vCenter only
vSphere Replication works in both multiple vCenter Servers and also a single vCenter Server (a.k.a ROBO) topologies.
Regards,
Martin