Case study Active –Active DC

EMC VPLEX part of solution Working with a partner Introduction Active-Active DC EMC VPLEX part of solution Working with a partner Agenda

EMC VPLEX part of solution Working with a partner Introduction Active-Active DC EMC VPLEX part of solution Working with a partner Agenda

Active-Passive Data Centers Site A - Active Site B - Passive Active-Passive Site Data on disaster recovery site is used on failure Outage to move applications Traditional two-site data center configurations create an active-passive architecture where the second site sits idle and resources are not used. This is common for traditional disaster recovery solutions today. This topology requires the tedious data movement process to bring systems down, reconcile, and restart them. Problems Site B is idle Process is lengthy Restart is required Active-Passive Data Centers

New Levels of Business Continuity Application continues with no disruption (Zero Downtime) Continuous Availability Active-Active Data Centers High Availability In-data-center Clusters for Application Protection Continuous Data Protection Operational Recovery to Any Point in Time Disaster Recovery Tape Backup and Replication

The “first” drawing

EMC VPLEX part of solution Working with a partner Introduction Active-Active DC EMC VPLEX part of solution Working with a partner Agenda

VPLEX Metro Use Cases AVAILABILITY MOBILITY COLLABORATION Zero RPO/RTO Eliminate storage operations from failover Federated AccessAnywhere Maintain availability and non-stop access by mirroring across locations MOBILITY Active-active data centers Disaster avoidance Data center migration Workload rebalancing Cluster A Cluster B Move and relocate VMs, applications, and data over distance COLLABORATION Instant and simultaneous data access over distance Streamline workflows Enable concurrent read/write access to data across locations Federated AccessAnywhere Federated AccessAnywhere VPLEX Metro Use Cases

VPLEX Active-Active Data Access Location A Location B Stretched Cluster Cluster Servers Cluster Servers Physical volumes are virtualized Virtual volumes are distributed across arrays Hosts access virtual volumes which access both physical arrays simultaneously Creating an Active-Active Environment Active/Active allows you to stretch server clusters over distance VPLEX Distributed Virtual Volume A VPLEX Distributed Virtual Volume B VPLEX VOL A VPLEX VOL B VOL A VOL B VOL A VOL B Active Active Enabled by Distributed Virtual Volumes VPLEX Active-Active Data Access

Bringing Mobility and Availability to VMware Environments Federated AccessAnywhere Witness VM Combining VMware HA / vMotion with VPLEX Metro Note to Presenter: Click now in Slide Show mode for animation. Now let’s take a closer look at how VPLEX works with VMware. Note to Presenter: Click now in Slide Show mode for animation VPLEX works together with VMware to have Virtual Volumes restarted on a secondary site should anything happen to the main site. VPLEX also supports nondisruptive vMotion of Virtual Machines between sites. VPLEX and VMware

VPLEX and Recover point VPLEX Geo Across Data Centers asynchronous (50ms) distances VPLEX Metro Across Data Centers synchronous (5ms) distances VPLEX Local Within a data center RecoverPoint Operational recovery and 3rd site protection for extended distances VPLEX and Recover point

VPLEX Family Product Matrix Local Metro Geo Mobility Within a data center Synchronous: 5 ms round-trip time Asynchronous: 50 ms round-trip time Availability High availability VPLEX Witness support Cross-cluster connected configuration VPLEX offers mobility, availability, and collaboration within and between data centers at synchronous and asynchronous distances. This matrix will help you find the VPLEX family product that is right for you. VPLEX RecoverPoint Splitter Collaboration Between two sites VPLEX Family Product Matrix

Active-Active Failover Bi-directional Failover Active-Passive Failover Active-Active Failover Bi-directional Failover Shared Recovery Sites Production Production Production Recovery Recovery Production Dedicated resources for recovery Leverage recovery infrastructure for test/dev Production applications at both sites Each site acts as the recovery site for the other Many-to-one failover Useful for Remote Office / Branch Office DR Topologies Site Recovery Manager can be used in a number of different failover scenarios: Active-Passive: Site Recovery Manager absolutely supports the traditional active-passive DR scenario, where a production site running applications is recovered at a second site that is idle until failover is required. Although the most common configuration, this scenario also means that you are paying a lot of money for a DR site that is idle most of the time. Active-Active: To make better use of the recovery site, Site Recovery Manager also enables you to leverage your recovery site for other workloads when you aren’t using it for DR. Site Recovery Manager can be configured to automatically shutdown or suspend VMs at the recovery site as part of the failover process so that you can easily free up compute capacity for the workloads being recovered. Bidirectional: Site Recovery Manager can also provide bidirectional failover protection so that you can run active production workloads at both sites and failover to the other site in either direction. The spare capacity at the other site will be used to run the VMs that are failed over. Shared Recovery Sites: Although less common, some of our customers need to be able to failover within a given “site” or campus, for example when a storage array failure occurs or when building maintenance forces you to move workloads to a different campus building. These customers are leveraging Site Recovery Manager to perform these failovers.

EMC VPLEX part of solution Working with a partner Introduction Active-Active DC EMC VPLEX part of solution Working with a partner Agenda

Functional/technical design Hardware/software sizing The design sessions: EMC, Cisco, VMware Functional/technical design Hardware/software sizing Working with a partner

Solving WAN Connection question: Connectivity Latency Applications Working with a partner