EMCRecoverPoint.ppt

Here is a view of RecoverPoint in normal operation. Note to Presenter: Click now in Slide Show mode for animation. First, an initial synchronization sends a full copy of the LUNs to the remote site. Note to Presenter: Click now in Slide Show mode for animation. Then, the clients update the source LUNs. RecoverPoint uses compression of differential snapshots to replicate changes to the production LUNs and sends these to the destination. The update will be prioritized to meet the RPO and bandwidth service levels. Here is a view of a RecoverPoint failover operation. Note to Presenter: Click now in Slide Show mode for animation. First, the production site experiences a disaster and is unavailable. Note to Presenter: Click now in Slide Show mode for animation. Then, the LUNs in each of the consistency groups at the disaster recovery site are changed to read/write and designated as sources. Note to Presenter: Click now in Slide Show mode for animation. Finally, the clients update the source LUNs at the disaster recovery site. Here is a view of a RecoverPoint failback operation. Note to Presenter: Click now in Slide Show mode for animation. First, the production site recovers from the disaster. The LUNs at the production site are changed to read-only and designated as destinations so that no servers on the production site can access them. Note to Presenter: Click now in Slide Show mode for animation. Then, RecoverPoint uses compressed differential snapshots to replicate any changes and sends these to the destination at the production site. Note to Presenter: Click now in Slide Show mode for animation. Finally, after the sites are re-synchronized, a failback reverses the sources and destinations back to their original configuration. Now let’s look at a use case for operational recovery. RecoverPoint uses CDP technologies to capture every change made to a production volume. Additionally, both compression of these changes in the journal as well as consolidation of these chan