1 / 29

Replicating Microsoft Applications using EMC RecoverPoint

Replicating Microsoft Applications using EMC RecoverPoint. b y. Sharon Almog RecoverPoint Eng. James Baldwin Strategic Solutions. &. Microsoft mSpecialist Summit 2011 – Day #3. Agenda . Introduction to RecoverPoint Data Protection Roadmap RecoverPoint Cluster Enabler (RP/CE)

hawa
Download Presentation

Replicating Microsoft Applications using EMC RecoverPoint

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Replicating Microsoft Applicationsusing EMC RecoverPoint by Sharon AlmogRecoverPoint Eng. James BaldwinStrategic Solutions & Microsoft mSpecialist Summit 2011 – Day #3

  2. Agenda • Introduction to RecoverPoint • Data Protection Roadmap • RecoverPoint Cluster Enabler (RP/CE) • Replicating HyperV applications • Replicating Microsoft SQL Server • EMC RecoverPoint and SQL 2012 “AlwaysOn”

  3. An introduction to RecoverPoint

  4. Bi-directional Local and Remote Replication PRODUCTION SITE DISASTER RECOVERY SITE RecoverPoint bi-directional replication/recovery Application servers Standby servers Local copy Remote copy RecoverPoint appliance RecoverPoint appliance Production and local journals FibreChannel/WAN Remote journal ProdLUNs SAN SAN Storage arrays Storage arrays Host-based write splitter Fabric-based write splitter Symmetrix VMAXe, VNX-, and CLARiiON-based write splitter

  5. / A r A / C r C / B r B Local Protection Process:Continuous Data Protection (CDP) 2a. Host write splitter 1. Data is split and sent to the RecoverPoint appliance in one of three ways 2b. Intelligent-fabric write splitter 3. Writes are acknowledged back from the RecoverPoint appliance 4. The appliance writes data to the journal volume, along with time stamp and application-specific bookmarks 2c. CLARiiON write splitter Production volumes Replica volumes Journal volume 5. Write-order-consistent data is distributed to the replica volumes

  6. r A / A r C / C r B / B Remote Protection Process:Continuous Remote Replication (CRR) 1. Data is split and sent to the RecoverPoint appliance in one of three ways 3. Writes are acknowledged back from the RecoverPoint appliance 6. Data is received, uncompressed, sequenced, and verified 2a. Host write splitter 7. Data is written to the journal volume 2b. Intelligent-fabric write splitter 2c. CLARiiON write splitter 5. Data is sequenced, checked, deduplicated, compressed, and replicated to the remote appliances over IP or SAN • 4. Appliance functions • Fibre Channel-IP conversion • Replication • Data reduction and compression • Monitoring and management Local site Remote site Journal volume 8. Consistent data is distributed to the remote volumes

  7. Components and Topology Application servers • Application servers • Accesses data that needs to be replicated • Heterogeneous storage • Source or target for replicated data • RecoverPoint appliance (RPA) • Connects to LAN and Fibre Channel (FC)/WAN for replication management and replicating data over FC/IP • Connects to Layer 2 FC SAN for storage access • RecoverPoint appliance cluster • A group of inter-linked RPAs, working together closely, to provide replication services • RPAs in a RecoverPoint cluster are called nodes • WAN bandwidth management • Reduce WAN bandwidth by up to 90% through deduplication, compression, and write-folding RecoverPoint appliances FibreChannel/WAN Layer 2 Fibre Channel SAN EMC IBM HDS LSI HP Heterogeneous storage

  8. RecoverPoint Family Details • RecoverPoint/CL • Supports EMC and non-EMC storage environments • Heterogeneous storage array support • Multiple arrays per site, EMC and non-EMC • Supports up to 300 TB of production data RecoverPoint/EX EMC storage environments Multiple EMC arrays per site Array-based splitting only Supports up to 300 TB of production data RecoverPoint/SE Supports VNX and CLARiiON environments Single VNX, CLARiiON, or Celerra unified array per site Supports Microsoft Windows host-based and VNX, CLARiiON array-based splitting only Supports 300 TB of production data Common functionality • One solution for data protection, replication, and disaster recovery • Local replication for LUNs in one SAN • Remote replication between LUNs in two SANs • Concurrent local and remote data protection that combines local and remote replication • Heterogeneous operating system support • Disaster recovery for VNX series file systems • Wizards automate production rebuild/restart • DVR-like recovery and consolidation reduces RPO and RTO • Application integration for Microsoft Exchange and SQL, other applications and databases • Integrated consistency groups support federated servers and storage • Synchronous or asynchronous local and/or remote replication with optional dynamic selection policies

  9. RecoverPoint integration with Cluster Enabler (RP/CE)

  10. Microsoft Failover Cluster A high-availability restart solution Node or resource failure automatically restarts failed nodes on another node where resources are available Node fails Resource Group: Microsoft SQL Resource Group: Microsoft Exchange Resource Group: Oracle Microsoft failover cluster provides high availability; shared-nothing cluster model

  11. RecoverPoint/Cluster Enabler for Microsoft Failover Cluster LAN/WAN Private Interconnect Site A Site B File Share Witness with RecoverPoint/CE installed RecoverPoint Cluster nodes with RecoverPoint/CE installed Failover cluster supports 16 nodes with Windows Server 2003/2008 using Majority Node Set with and without File Share Witness

  12. RP/CE & Hyper-V Overview Cluster Enabler 4 supports Hyper-V with failover clusters • Failover of the virtual machine (VM) resource • RecoverPoint/CE is deployed in the Hyper-V parent partition • Cluster relocation is at the VM level • Hyper-V Live Migration and Quick Migration—between nodes at the same or different sites • Live Migration supported with RecoverPoint CRR/CLR synchronous replication • Quick Migration supported with synchronous and asynchronous replication • Use for planned maintenance, such as VM relocation for hardware upgrades and software upgrades • Use for VM workload redistribution—move VMs between physical hosts

  13. Target 2 Target 1 Prod 1 Prod 2 Disaster Recovery for Hyper-V Automated failover operations for Hyper-V environments LAN/WAN Private Interconnect Site A Site B Majority Node Set with File Share Witness RecoverPoint Cluster nodes with RecoverPoint/CE installed Hyper-V with Failover Clusters supports 16 nodes with Windows 2008 R2

  14. R2 R2 R1 R1 Hyper-V Live Migration Planned hardware maintenance on physical server requires moving virtual machine(s)to another physical server Site A Site B Majority Node Set with File Share Witness RecoverPoint CRR synchronous replication

  15. RP/CE 4.1.2 (new release) • Supported with RP 3.4.2 code • Supports RecoverPoint CLR topology • Failover is still limited to CRR copy (can’t failover to CDP) • New CE Group Policy “Auto Failover” • Provides missing flexibility which was absence in previous “Restricted group” (see next table) • No need to perform “RecoverPoint manual failover” on specific use cases • Supports Windows Server and Server Core for Windows Server 2008 • Up to 8 nodes per site with Windows Server 2003 • Up to 16 nodes per site with Windows Server 2008 and Windows Server 2008 R2 • Up to 16 child partitions with Hyper-V

  16. Using RecoverPoint/Cluster Enabler • Supports Windows 2003 Cluster Services • Supports Windows 2008 Failover Clusters • Supported with Hyper-V • Repurposing does not work • MSCS failover enforces that remote cluster nodes can’t be manipulated • All resources of those nodes are not available outside of nodes • No access, mounting, multi-masking of LUNS to non-clustered hosts • Cluster Enabler 4.1 supports CSV • Requires Windows Server 2008 R2 SP1 • Support Majority Node Set, other quorum modes not supported • Only supports CRR • Toleration of CLR will be added 2H’2011 (addresses repurposing issue)

  17. DEMO:Protecting SQL 2008 using RP/CE (movie)

  18. RecoverPoint integration with MS HyperV

  19. Supported Hyper-V configurations • Clustered HyperV (each VM reside on its own replicated Cluster Disks) • ClusteredHyperV with CSV volume (multiple VMs reside on single replicated CSV volume) • Standalone HyperV host (since CSV is only supported in Cluster, then each VM reside on its own replicated volume)

  20. RecoverPoint integration with SQL Server

  21. DEMO #1: SQL VDI Backup/Restore using Kutils 1) Backup using RP Hot Backup command the entire production database 2) Select RecoverPoint Hot Backup bookmark 3) Mount this Bookmark 4) Restore entire database on DR SQL Server

  22. DEMO #2: SQL VSS Backup/Restore using KVSS 1) Perform SQL VSS bookmark using KVSS utility on production Host 2) VSS bookmark created successfully 3) Mount this Bookmark

  23. 4) Online replica volumes 5) Remove Hidden/Read-Only disk attributes 6) Assign drive letters 7) Attach SQL database using SQL Mgmt. Studio

  24. EMC RecoverPoint and SQL 2012 “AlwaysOn”

  25. Dynamic Business Intelligence and DR with SQL Server 2012 AlwaysOn and EMC RecoverPoint • Local high availability is provided by SQL Server “Denali 2010” AlwaysOn Availability Groups • Local data accessibility for destructive data access to enable Dynamic BI is enabled by RecoverPoint • Remote site crash-consistent database copies are available over extended distances with WAN optimization and no SQL Server overhead with RecoverPoint • Dynamic Business Intelligence is enabled, whereby rapid copies of large OLTP production databases must be available to business intelligence teams; • Within minutes • Must have BI SQL Server Instances fully isolated from production environments and networks • Supports dynamic BI where databases copies need to be writeable to support dynamic BI lookup scenarios • Continue to ensure the production databases copies are intact

  26. SQL Server AlwaysOn and EMC RecoverPoint - The Best of Both Worlds-

More Related