Continuous Availability for Business-Critical Data

Transcription

1 Continuous Availability for Business-Critical Data MetroCluster Technical Overview Jean-Philippe Schwartz Storage Systems Specialist - IBM / Gate Informatic jesc@ch.ibm.com

2 Agenda NetApp / IBM Agreement Customer Challenges NetApp Business Continuity Solutions NetApp MetroCluster Overview MetroCluster Failure Scenarios When do I need MetroCluster IBM MetroCluster in SR One Pager 2

3 NetApp / IBM Agreement 3

4 Why NetApp? Mainframe, System i Open Systems Heterogeneous NAS High-end Mid-range DS8000 For clients requiring: One solution for mainframe & open systems platforms Disaster Recovery across 3 sites across 2 sites > 100 km apart Secure encryption Continuous availability, no downtime for upgrades Best-in-class response time Dedicated rack DS4000/5000 For customers requiring: Open systems environment support including IBM i support Cost efficient storage for capacity Modular storage XIV For clients requiring: Open systems environment support Future-proof capacity expansion and management Web 2.0 workloads Dedicated Rack SVC For clients requiring: Virtualization of multiple vendor environments, including IBM, EMC, HP and others V7000 For clients requiring storage virtualization, Thin provisioning, EasyTier, online migration SoNAS For customers with massive IO / backup / restores N series For clients with: Combined NAS (file) and SAN requirements Simple two-site high availability Entry DS3000 For very price-sensitive customers Modular storage Affordable disk shelves behind SVC EE Supercomputing DCS9900 (HPC and Digital Media clients only) 4

5 IBM and Network Appliance Join Forces Previous attempts by IBM to penetrate the NAS market in have shown limited success (NAS100, NAS200, NAS300, NAS300G then later on NAS500G) In April, 2005, IBM and Network Appliance announced a strategic storage relationship to drive information on demand solutions and to expand IBM's portfolio of storage solutions: -IBM sells re-branded Network Appliance storage solutions as N series -Network Appliance extends its market presence with key partner IBM does additional testing on specific solutions to ensure the highest possible Availability, Reliability & Scalability 5

6 IBM N series Offer For Customer NAS only or Unified Storage Requirements Same HW and DOT as NetApp Platforms Full range of NetApp Software Functions Filer and Gateway Models Entry level pricing, Enterprise Class Performance N3000 Series Excellent performance, flexibility and scalability at a lower TCO N6000/Gateway Series Highly-scalable storage systems for large enterprise data centers. N7000/Gateway Series Up to 1176TB Up to 1.2PB Up to 136TB 6

7 Customer Challenges 7

8 Customer Challenges Internal Data Center Failures External Data Center Failures NetApp FAS HA (active-active) MetroCluster Addresses the storage major hardware causes of downtime failures in in the the data data center Source: Forester / Disaster Recovery Journal: Global Disaster Recovery Preparedness Online Survey, Oct,

9 NetApp Business Continuity Solutions 9

10 Availability IBM System Storage N series Unified Storage Solutions NetApp Data Protection and Business Continuity Solutions Block-Level Incremental Backups Asynchronous Replication Synchronous Replication LAN/WAN Clustering Continuous Operations Synchronous Clusters MetroCluster Synchronous SnapMirror and Clusters Data Protection Synchronous SnapMirror and SyncMirror Asynchronous SnapMirror Application Recovery SnapRestore SnapVault Cost Daily Backup Snapshot Copies Local Restore Remote Restore Remote Recovery Low RTO Capability 10

11 The MetroCluster Difference Across Floors, Building, or Campus Within Data Center Across City or Metro Area NetApp MetroCluster provides continuous availability within a single data center and across data centers in adjacent floors, buildings, and metro areas Support for N series N6000 & N7000 MetroCluster MetroCluster Stretch Stretch up to 500 up mto 100 km 11

12 The MetroCluster Difference: Automatic Protection Primary Data Center Alternate Data Center Others Oracle Exchange Oracle Exchange SharePoint SharePoint Home Dirs Create volume New Volume Home Dirs New Volume MetroCluster Oracle Exchange Home Dirs SharePoint New Volume Set up replication Aggregate Mirroring Create destination volume Oracle Exchange Home Dirs SharePoint New Volume Create volume Automatic mirroring 12

13 The MetroCluster Difference: Quick Recovery Time Others Primary Data Center Exchange Oracle SharePoint Home Dirs New Volume Alternate Data Center 1. Break Mirror 2. Bring Online ONLINE 3. Break Mirror ONLINE Exchange 4. Bring Online Oracle 5. Break Mirror ONLINE 6. Bring Online ONLINE SharePoint 7. Break Mirror Home Dirs 8. Bring Online ONLINE 9. Break Mirror New Volume 10. Bring Online MetroCluster Oracle Exchange Home Dirs SharePoint New Volume CF Forcetakeover -d ONLINE ONLINE Oracle Home Dirs ONLINE ONLINE SharePoint Exchange New Volume ONLINE 13

14 NetApp Efficiency Deduplication offers cost savings for MetroCluster Deduplication efficiencies for both the source and mirrored arrays Investment protection and storage efficiency for other vendors storage with V-Series systems PVR no longer required Must be licensed on both nodes Must be running NetApp Data ONTAP or later, or later Subject to the same considerations as non MetroCluster systems 14

15 MetroCluster Overview 15

16 MetroCluster Components Cluster License SyncMirror Cluster Remote FC Interconnect Provides automatic failover capability between sites in case of most hardware failures. Provides an up-to-date copy of data at the remote site; data is ready for access after failover without administrator intervention. Provides a mechanism for the administrator to declare a site disaster and initiate a site failover with a single command. Provides appliance connectivity between sites that are more than 500 meters apart; enables controllers to be located a safe distance away from each other. 16

17 MetroCluster Deployment in a Single Data Center, Across Floors, and So On Node 1 Node 2 Stretch MetroCluster 500m Aggregate X Aggregate Y Aggregate Y Mirror Data Center Aggregate X Mirror 17

18 MetroCluster Deployment Across City or Metro Areas Building A Fabric MetroCluster Building B <=100 km DWDM Dark Fiber DWDM Aggregate X Aggregate Y Mirror No SPOFs redundancy in all components and connectivity Dedicated pairs of FC switches Aggregate Y Aggregate X Mirror 18

19 MetroCluster Component: Cluster Remote License Provides single-command failover. Provides the ability to have one node take over its partner s identity without a quorum of disks. Root volumes of both appliances MUST be synchronously mirrored. By default, all volumes are synchronously mirrored and are available during a site disaster. Requires administrator intervention as a safety precaution against a split brain scenario (cf forcetakeover d) 19

20 MetroCluster Component: SyncMirror Writing to an unmirrored volume Writing to a mirrored volume Two Plexes Created Plex 0 from Pool 0 = Orig Plex 1 from Pool 1 = Mirror Note: Plex # may change over time Volume1 Volume1 A Plex 0 Pool 0 A Plex 0 Pool 0 A Plex 1 Pool 1 20

21 MetroCluster Support Matrix Stretch Fabric FAS/V Model Supported Max. Disks Supported Max. Disks 3070 Yes 504 Yes Yes 420 Yes Yes 840 Yes 840 2, Yes 480 Yes Yes 600 Yes Yes 960 Yes Yes 840 Yes 840 2, Yes 840 Yes 840 2, Yes 1008 Yes 840 2, Yes 1166 Yes 840 2, Yes 1008 Yes 840 2, Yes 1176 Yes 840 2, Yes 1176 Yes 840 2, spindle count requires Data ONTAP or later spindle count requires Data ONTAP to spindle count requires Data ONTAP or later spindle count requires Data ONTAP or later 21

22 Twin MetroCluster Configuration (DOT 7.3.3) 22

23 New in Data ONTAP 7.3.5/8.0.1 FAS 32xx FAS32xx series support FAS62xx series Support Up to 840 spindles on fabric MetroCluster 8Gb cluster interconnect 8Gb FCVI X1927A-R6 23

24 MetroCluster Failure Scenarios 24

25 Host Failure Host 1 Data Center #1 Data Center #2 Host 2 Recovery Automatic Host #2 accesses its data across the data centers FAS 1 FAS 2 DC1 Primary DC2 Mirror DC 1 Primary DC2 Primary DC1 Mirror 25

26 Storage Controller Failure Host 1 Data Center #1 Data Center #2 Host 2 Recovery Automatic FAS 2 provides data services for both data centers. Writes go to both plexes. Reads come from local by default. FAS 1 FAS 2 DC1 Primary DC2 Mirror DC 1 Primary DC2 Primary DC1 Mirror 26

27 Storage Array Failure Host 1 Data Center #1 Data Center #2 Host 2 Recovery Singlecommand failover FAS 1 FAS 2 DC1 Primary DC2 Mirror DC 1 Primary DC2 Primary DC1 Mirror 27

28 Complete Site Failure Host 1 Data Center #1 Data Center #2 Host 2 Recovery Singlecommand failover FAS 1 FAS 2 DC1 Primary DC2 Mirror DC 1 Primary DC2 Primary DC1 Mirror 28

29 Interconnect Failure Host 1 Data Center #1 Data Center #2 Host 2 Recovery No failover; mirroring disabled FAS 1 FAS 2 Both appliance heads continue to run, serving their LUNs/volumes Resyncing happens automatically after interconnect is reestablished DC1 Primary DC2 Mirror DC 1 Primary DC2 Primary DC1 Mirror 29

30 Return to Normal Host 1 Data Center #1 Data Center #2 Host 2 One-step return to normal CF giveback Mirror is rebuilt DC1 primary reverts back to FAS 1 DC1 FAS 2 DC1 Primary DC2 Mirror DC 1 Primary DC2 Primary DC1 Primary Mirror 30

31 When do I need MetroCluster 31

32 MetroCluster Positioning Qualification questions: Is continuous data availability important to one or more of your product applications? Would providing geographic protection be of value? What distance between controllers would provide the best protection (building, floor campus, metro, or regional)? If you are employing an HA solution for a virtualized environment, why not have the same resilience at the storage level? 32

33 SnapMirror Sync Versus MetroCluster Feature SnapMirror Sync MetroCluster Replication network IP or FC FC only Limit on concurrent transfers Yes No limit Distance limitation Up to 200km (latency driven) Replication between HA pairs Yes No Manageability Multi-use replica Deduplication Use of secondary node for async mirroring FilerView, CLI, Operations Manager Yes (FlexClone ) No (dump) Deduplicated volume and sync volume cannot be in the same aggregate Yes 100km CLI Limited (app can read from both plexes) No restrictions No. Async replication has to occur from primary plex 33

34 MetroCluster Best Practices Choose the right controller Based on normal sizing tools and methods Connections are important Calculate distances properly Use the right fiber for the job Verify correct SFPs, cables required, and patch panels Remember that mirroring requires 2x disks Remember MetroCluster spindle maximums 34

35 IBM MetroCluster in SR 35

36 IBM MetroCluster Installations in Suisse Romande Total of 5 IBM MetroCluster Customers in Suisse Romande 3 Stretch Configurations 1 x Across Rooms 1 x Across Floors 1 x Across Roads 2 Fabric Configurations 1 x Owned LW Connections (1.2 km) 1 x External Provider Service (30+ / 50+ km) Extremely High Customer Satisfaction 36

37 One Pager 37

38 Value of MetroCluster Simple Set it once: Easy to deploy, with no scripts or dependencies on the application or operating system Zero change management through automatic mirroring of changes to user, configuration, and application data Continuous availability Zero unplanned downtime through transparent failover with protection for hardware plus network and environmental faults Zero planned downtime through nondisruptive upgrades for storage hardware and software. Cost effective 50% lower cost, no host-based clustering required, added efficiency through data deduplication and server virtualization Data Center MetroCluster 38

39 Thank You 39