RecoverPoint 4.1 Product Enhancements
One of the many technologies that I get to work with on a regular basis is EMC RecoverPoint. It has continued to evolve as the years have passed. Code version 4.1 was released a few months ago and I wanted to go over a few of the major new enhancements.
- MetroPoint Support
- Snap-based Replication
- I/O Throttling
- External Storage Support
Before MetroPoint, RecoverPoint was used to protect VPLEX distributed volumes, via replication, to a third site. However, RecoverPoint only protected one site of the Metro for a distributed volume. If the site performing replication to the remote site went down, hosts could access the distributed volumes but continuous data protection wouldn’t happen. MetroPoint, eliminates this problem because replication can switch over to the other site and continue to replicate to the disaster recovery site. When this happens, a source switchover occurs with only a short init phase.
In RecoverPont 4.1, snap-based replication can be used to replicate point-in-time snapshots asynchronously from production to target. Benefits in doing snap-based replication are reduced traffic transmission and lower RTO. This will also provide better journal utilization.
Requirements for Snap-Based Replication
- All RPAs must be 4.1 or higher
- Storage array must be registered the Storage wizard
- VNX OE must be Block 32 or later
- RecoverPoint Splitter
- VNX Snapshot enabler
- VPLEX is supported
I/O throttling regulates I/O during Init/Full sweep initialization to prevent burdening the storage array due to heavy I/O activity by RecoverPoint. I/O throttling support has been extended to support individual storage arrays meaning the throttling value can be different for different storage arrays involved in the replication process.
External Storage Support
You now have the option of provisioning Journal volumes from within the Consistency Group Wizard directly from Storage Pools on the VNX. This can be done once the Storage has been registered in Unisphere for RecoverPoint. This allows for an easier administration of RecoverPoint Journal Volumes. Block 32 or higher is supported
There are few smaller enhancements listed below.
- Policy Templates – This allows for user-defined policies when it comes to the copy or link policy for each CG
- HTTPS is now the default GUI access
- RecoverPoint Check for registered RPAs – Lets you know if an RPA is registered or not
- Logs can be collected form a detached RPA
- More languages have been added
As you can see RecoverPoint continues to get better and makes Disaster Recover more feasible.