1. 1© Copyright 2014 EMC Corporation. All rights reserved. ViPR DR Requirement

2. 2© Copyright 2014 EMC Corporation. All rights reserved. Scope of ViPR DR Procedure DR scenarios focused on ViPR App Ability to resume all normal ViPR use cases: – In case of loss of primary ViPR instance – Secondary instance of ViPR needs to be instantiated on different hardware/data center – For arrays/hosts/switches that are still available/accessible to ViPR Ability to simulate and test ViPR DR scenario Unavailability scenarios documented in subsequent slides Not in Scope: – DR of application using storage provisioned by ViPR

3. 3© Copyright 2014 EMC Corporation. All rights reserved. DISTRIBUTED DATABASE Physical Storage Minority node down; less than half ViPR VMs are corrupted/deleted 1a. ViPR Reduced redundancy X Desired State: - ViPR appliance redundancy can be brought back to the original state Documented process? VMware vApp-Shared storage -No doc on repair process -Need investigation on partial data loss VMware vApp - With SRM -NA HyperV-Repair process need to document -Working on minority node repair or recovery VMware No vApp-Same as above

4. 4© Copyright 2014 EMC Corporation. All rights reserved. DISTRIBUTED DATABASE Physical Storage Majority node failure 1. Reduced redundancy X Desired State: - ViPR appliance redundancy can be brought back to the original state Documented process? VMware vApp-No repair process today (future) -Backup and restore process applies. VMware vApp - With SRM -NA HyperV-Backup and restore process applies. VMware No vApp-Same as above X

5. 5© Copyright 2014 EMC Corporation. All rights reserved. DISTRIBUTED DATABASE Physical Storage X 2. All ViPR nodes corrupted/HW unavailable Desired State -ViPR data is recovered. -Provisioning through ViPR can be resumed quickly -Customer should be able to switch ViPR back without losing any new configuration Documented process? VMware vApp-Backup and restore process applies VMware vApp - With SRM -NA HyperV-Backup and restore process applies VMware No vApp-Backup and restore process applies Ability to test this scenario? -Yes. Documentation needed Managed resources are still up and running

6. 6© Copyright 2014 EMC Corporation. All rights reserved. 3a. Disaster at Site 1 hosting ViPR No ViPR managed storage replication between sites (No RP/SRDF/VPLEX) Desired State -ViPR instance on another site can be brought up quickly -Provisioning for site 2…site n can resume through ViPR. -No/Limited loss of ViPR configuration data -Once site 1 is restored, ViPR can be moved back to site 1 Documented process? VMware vApp -With SRM (Jedi) -Use Vmware SRM to bring up ghost instances -Different IP support needed -Need to run test under load -Official doc needed (make sure ports are open) VMware vApp -Without SRM (Jedi) -Backup can be shipped -Different IP support needed -Official doc needed HyperV (Jedi)-Backup option Same as above VMware No vApp Jedi? -Same as above -Separate testing is required Ability to test this scenario -Yes Site 1 Site 2Site n X

7. 7© Copyright 2014 EMC Corporation. All rights reserved. 3b. Disaster at Site 1 hosting ViPR ViPR managed storage replication between sites (RP/SRDF/VPLEX) Desired State -ViPR should be able to perform storage continuity operations through another site -Admin can use ViPR to change state of target devices to source -ViPR understands the change in internal state (Operating in failover mode/metropoint) if Admin changes state outside ViPR -Provisioning for site 2…site n can resume through ViPR. -No/Limited loss of ViPR configuration data -Once site 1 is restored, ViPR can be moved back to site 1 Documented process? VMware vApp w SRM-RPO/RTO objectives can be met -making R2 device available workflow not in ViPR VMware vApp w/o SRMBackup and restore will not meet RPO/RTO requirements HyperV VMware No vApp Ability to test this scenario Site 1 Site 2 RP/SRDF/VPLEX X ViPR interacting with SMI-S on site 1 (SMI-S DR needs to be in place) - Need to identify limitation ( work with Evgeny) - ViPR working with SRDF/RP and SRM

8. 8© Copyright 2014 EMC Corporation. All rights reserved. Other Considerations Customer RTO for ViPR – Depends on how important customer perceives ViPR to be. – For Bank of America – any app that concerns storage management is Tier 1 (out of 6 total). Tiers 0-4 require a DR strategy and a Tape Backup strategy. Tier0 – sub-minute, Tier1 – approx. 10 mins is OK Tier2 – 1 or 2 hrs is OK, etc.

9. 9© Copyright 2014 EMC Corporation. All rights reserved.

10. 10© Copyright 2014 EMC Corporation. All rights reserved. Situation Enterprise customers have a very well established DR strategy which is usually tested a few times every quarter There is a gap in the customer’s DR strategy when they deploy ViPR in their environment Even though ViPR is only a control path product it is still makes for disconnected DR strategy for customers as they would have to fall back to element managers to manage their infrastructure in the eventuality of a DR

11. 11© Copyright 2014 EMC Corporation. All rights reserved. Customer Ask ViPR product team provides a well qualified/validated DR strategy which the customers can incorporate in their overall DR playbooks As most of our customers currently run ViPR as a vAPP, the ask is predominantly from a VMware perspective This has quickly becoming a blocker for every enterprise customer (Bank of America, JPMC etc.) as this puts their Datacenter DR strategy at risk (i.e. incomplete)

12. 12© Copyright 2014 EMC Corporation. All rights reserved. The “right” long term solution ViPR’s DR strategy should be hypervisor agnostic (i.e. VMware, Hyper-v, KVM) as we will have support for all of these by the end of the year One way to accomplish that would be to have a truly federated ViPR solution –Can this potentially be accomplished by the end of the year? Since this is a long term goal which could potentially be a sizeable engineering effort we need to think of a short term solution to address customer concerns

13. 13© Copyright 2014 EMC Corporation. All rights reserved. Requirements Since the short term ask is from a VMware perspective –VMware SRM is a viable option –Need to have a good mix of platforms for the qualification testing (i.e. VMAX, VNX, VPLEX, XtremIO etc.) –We need to fully qualify this offering for all different DR scenarios (common customer DR exercises, losing entire production site etc.) –Identify any gaps –Once qualified, create a white paper articulating ViPR’s DR solution offering and how it fits with customer’s overall DR strategy –PM’s can vet the solution with customers during the qualification stages to identify concerns or just solicit feedback