1. Site Recovery Manager Disaster Recovery for ViPR-Managed Storage
EMC Private Cloud
Site Recovery Manager
Disaster Recovery for ViPR-Managed Storage

2. Summary Use Cases Proposed solution
Configure vCAC blueprint (single VM or multi-VM app) with RP DR
Provision VM/app with RP DR
Failover VM/app
Failback VM/app
Test Failover / Failback plan
Proposed solution
ViPR 1.1 and EPC 2.x (single ViPR managing storage at both sites)
ViPR protected by VMware SRM
ViPR tolerant of SRM initiated failover/failback
ViPR future and EPC future (multiple linked ViPR instances)
ViPR self protected
ViPR executes SRM initiated failover/failback

3. Summary (continued) Limitations addressed by “future” solution
Linked ViPR instances alleviate latency limitations of managing storage in multiple sites from a single ViPR instance
Use of ViPR SRA makes solution indifferent to underlying DR replication technology being used
Next Steps
Confirm there are no blockers for near term (Q2’14) plan
ViPR Engineering to investigate linked instances architecture
XBU Engineering to investigate developing ViPR SRA

4. Automated Provisioning of DR Resources
1H 2014
Automated Provisioning of DR Resources
Tenant A
Tenant B
Tenant C
Database
App
Web
Security group
Firewall/
IT admin can create blueprints
With RecoverPoint replicated storage
With SRM protected applications
End user provisions VM/Application
VM Datastore provisioned with RP protected storage
Automated RP provisioning must be supported across multiple sites.
VMware
Openstack
Tenant A
Tenant B
Tenant C
Database
App
Web
Security group
Firewall/
Storage
VNX
VMAX
Compute
Network
San Francisco
+ EMC RecoverPoint
VMware SRM
VMware
Openstack
Storage
VNX
VMAX
Compute
Network
Goals
Enable differentiated mobility in the VMware stack
Virtualize Mission critical apps with LDM and HA OD for virtual environments
VMware objectives and value proposition
Value to EMC II
Boston
Tenant A
Tenant B
Tenant C
Database
App
Web
Security group
Firewall/
+ EMC RecoverPoint
VMware SRM
VMware
Openstack
Storage
VNX
VMAX
Compute
Network
Las Vegas

5. Automated DR Failover/Failback/Testing
1H 2014
Automated DR Failover/Failback/Testing
Production site fails / failover triggered
Storage connectivity at remote site is configured
RecoverPoint replication is halted
VM/app restarts at remote site
RecoverPoint replication direction is reversed
IT admin/user triggers failback
Storage connectivity at production site is configured
VM/app restarts at production site
IT admin must be able to test failover / failback using SRM
Automated storage failover must be supported across Multiple sites
Tenant A
Tenant B
Tenant C
Database
App
Web
Security group
Firewall/
VMware
Openstack
Tenant A
Tenant B
Tenant C
Database
App
Web
Security group
Firewall/
Storage
VNX
VMAX
Compute
Network
San Francisco
+ EMC RecoverPoint
VMware SRM
VMware
Openstack
Storage
VNX
VMAX
Compute
Network
Goals
Enable differentiated mobility in the VMware stack
Virtualize Mission critical apps with LDM and HA OD for virtual environments
VMware objectives and value proposition
Value to EMC II
Boston
Tenant A
Tenant B
Tenant C
Database
App
Web
Security group
Firewall/
+ EMC RecoverPoint
VMware SRM
VMware
Openstack
Storage
VNX
VMAX
Compute
Network
Las Vegas

6. ViPR 1.1 Solution: RP SRA with ViPR cluster managing multiple sites
Available Feb 7, 2014
SRM initiates RP failover via RP SRA
VNX VMAX
VNX VMAX
ViPR-managed replication
RecoverPoint
RecoverPoint
Software Defined Storage
SRM-initiated failover of ViPR controllers for ViPR DR
Software Defined Storage
ViPR cluster on protected site provisions volumes and replication on both sites
RP SRA executes SRM-initiated failover
ViPR controller application is protected by SRM and can be failed over to recovery site
Up to 200ms round-trip latency OK for ViPR to manage storage on recovery site

7. Preferred future solution: ViPR SRA and Linked ViPR Clusters
Desired
Q2 2014
SRM initiates RP failover via ViPR SRA
VNX VMAX
VNX VMAX
ViPR-managed replication
RecoverPoint
RecoverPoint
Software Defined Storage
Software Defined Storage
Linked ViPR Clusters made up of controllers on local and remote sites manage provisioning and failover of replicated volumes from either site.
ViPR SRA executes SRM-initiated failover.
ViPR controller application does not need SRM protection and does not failover

8. Alternate future solution: ViPR SRA with single ViPR cluster managing multiple sites
SRM initiates RP failover via ViPR SRA
Protected site ViPR cluster provisions volumes and replication on both sites
SRM calls ViPR directly to manage RP failover.
ViPR controller application is protected by SRM and can be failed over to the other site.
Up to 200ms round-trip latency OK for ViPR to manage storage on remote site
VNX VMAX
VNX VMAX
ViPR-managed replication
RecoverPoint
RecoverPoint
Software Defined Storage
SRM-initiated failover of ViPR controllers for ViPR DR
Software Defined Storage