Embed Size (px)
Citation preview
1EMC CONFIDENTIAL—INTERNAL USE ONLY
EMC Private Cloud
Site Recovery ManagerDisaster Recovery for ViPR-Managed Storage
2EMC CONFIDENTIAL—INTERNAL USE ONLY
Summary
Use Cases– 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
3EMC CONFIDENTIAL—INTERNAL USE ONLY
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
4EMC CONFIDENTIAL—INTERNAL USE ONLY
Automated Provisioning of DR Resources 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.
1H 2014
VMware
StorageVN
X VMAX ComputeNetwork
Openstack
Tenant A Tenant B Tenant C
Database App Web
Firewall/Security group
Firewall/Security group
VMware
StorageVN
X VMAX ComputeNetwork
Openstack
Tenant A Tenant B Tenant C
Database App Web
Firewall/Security group
Firewall/Security group
Boston
San Francisco
VMware
StorageVN
X VMAX ComputeNetwork
Openstack
Tenant A Tenant B Tenant C
Database App Web
Firewall/Security group
Firewall/Security group
Las Vegas
VMware SRM
+ EMC RecoverPoint
VMware SRM
+ EMC Reco
verPoint
5EMC CONFIDENTIAL—INTERNAL USE ONLY
Automated DR Failover/Failback/Testing
VMware
StorageVN
X VMAX ComputeNetwork
Openstack
Tenant A Tenant B Tenant C
Database App Web
Firewall/Security group
Firewall/Security group
1H 2014
VMware
StorageVN
X VMAX ComputeNetwork
Openstack
Tenant A Tenant B Tenant C
Database App Web
Firewall/Security group
Firewall/Security group
Boston
San Francisco
VMware
StorageVN
X VMAX ComputeNetwork
Openstack
Tenant A Tenant B Tenant C
Database App Web
Firewall/Security group
Firewall/Security group
Las Vegas
VMware SRM
+ EMC RecoverPoint
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– RecoverPoint replication is halted– VM/app restarts at production site– RecoverPoint replication direction is reversed
IT admin must be able to test failover / failback using SRM
Automated storage failover must be supported across Multiple sites
VMware SRM
+ EMC Reco
verPoint
6EMC CONFIDENTIAL—INTERNAL USE ONLY
RecoverPoint VNX VMAX
RecoverPointViPR-managed replication
VNX VMAX
SRM initiates RP failover via RP SRA
• 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
ViPR 1.1 Solution: RP SRA with ViPR cluster managing multiple sites
Software Defined Storage
Software Defined Storage
SRM-initiated failover of ViPR controllers for ViPR DR
Available Feb 7, 2014
7EMC CONFIDENTIAL—INTERNAL USE ONLY
RecoverPoint VNX VMAX
RecoverPointViPR-managed replication
VNX VMAX
Software Defined Storage
Software Defined Storage
SRM initiates RP failover via ViPR SRA
• 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
Preferred future solution: ViPR SRA and Linked ViPR Clusters
Desired Q2 2014
8EMC CONFIDENTIAL—INTERNAL USE ONLY
VNX VMAXRecoverPointViPR-managed replication
VNX VMAX
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
Alternate future solution: ViPR SRA with single ViPR cluster managing multiple sites
Software Defined Storage
Software Defined Storage
SRM-initiated failover of ViPR controllers for ViPR DR
RecoverPoint
