EMC RecoverPoint
1) Recoverpoint is not capable of restricting overall bandwidth used by
all protection groups. Recoverpoint is capable of restricting
bandwidth used by each protection group individually.
2) The Recoverpoint WAN and LAN networks may not be the same logical
network.
3) Recoverpoint uses MTU on the WAN network. If Recoverpoint's
MTU does not match the actual MTU of your WAN, Recoverpoint won't
communicate successfully with the other side of the WAN.
4) Customer aren't allowed to install RecoverPoint and EMC does not
make it easy to try. The passwords you will need to access
RecoverPoint are in the RecoverPoint Administrator's Guide
300-010-641.pdf
EMC RecoverPoint SRM Failback plugin
The EMC RecoverPoint SRM Failback plugin is nearly useless. These
issues were reported to EMC support and I was told these features are
by design and won't be fixed.
1) When it fails back, it errors out telling you that you must
manually resignature the volumes. This is something SRM does for
you
automatically.
2) When it fails back, it forces every single VMware server (not
just the servers you are protecting with SRM) on the production vCenter
server to scan all their HBAs one at a time, serially. If you
have
dozens or hundreds of other servers that are not running SRM, this
forced rescan can take hours. It should only force those servers on the
SRM cluster in question to rescan.