HPE 3PAR高可用解决方案

1、HPE 3PAR高可用解决方案HPE 3PAR High Availability SolutionsRemote Copy & Peer Persistence3PAR Remote Copy3PAR Remote Copy (RC) Protect and share dataSmartSimple and intuitive setup in minutes via GUI (SSMC) ore CLI CompleteNative FC SAN and/or IP LAN-based replication Reservation-less No extra copies or inf

2、rastructure neededFully compatible with all 3PAR Data Reduction Technologies Remote Copy configurations from 1:1 up to 4:4Support details are in the “3PAR Remote Copy Software User Guide”VMware vSphere Site Recovery Manager (SRM) certified VMware vSphere Metro Storage Cluster (vMSC) certifiedScalabl

3、eUp to 5 replication links per node up to 40 per array1 RCIP link per node (1GbE or 10GbE)1 to 4 FC and/or FCIP links per node1:1 ConfigurationRC sync, async streaming and periodicSee a demo video here /watch?v=7RVozzXOuRQRead the whitepaper Disaster-tolerant solutions with HPE 3PAR Remote Copy4:4 C

4、onfigurationRC sync, async streaming and periodicPSSP3PAR 3 Data Center Disaster Recovery ConfigurationsSynchronous Long Distance Solution (SLD)Allows volumes in a Remote Copy volume group to be replicated from one primary 3PAR to two different secondary 3PAR arraysCombines the ability to maintain c

5、oncurrent metro-distance synchronous RC (RTO=0) with continental distance async RC for Disaster Tolerance (DT)Find some SLD demo videos here/playlist?list=PL9UfCHCZQuNDmU8WRXT_RU7yG_sL-eweV Secondary SiteSynchronous RCPrimary SiteActive asynchronousPeriodic RCTertiary SiteStandby asynchronousPeriodi

6、c RC3DC Peer Persistence SolutionCombines the metro-distance synchronous Peer Persistence HA solution (RTO=0) with continental distance asynchronous Remote Copies for Disaster Tolerance (DT)New with 3PAR OS 3.3.1Manual Disaster RecoveryManual Disaster RecoveryManual switch-overStretched ClusterPrima

7、ry Site BSynchronous RCPrimary Site AActive asynchronousPeriodic RCTertiary SiteStandby asynchronousPeriodic RCAutonomic switch-over3DC Peer Persistence RC Group SSMC view3DC Peer Persistence SSMC topology view3PAR Remote Copy SynchronousContinuous operation and synchronizationReal-time MirrorHighes

8、t I/O currencyLock-step data consistencySpace EfficientThin provisioning awareTargeted UseCampus-wide business continuityGuaranteed Consistency Enabled by Volume Groups2 : Primary array writes I/O to secondary write cachePS1 : Host server writes I/O to primary write cache23 : Remote array acknowledg

9、es the receipt of the I/O144 : Host I/O acknowledged to host3PrimarySecondaryLocal Snapshots3PAR Remote Copy Asynchronous PeriodicInitial setup and synchronization Efficient even with high latency linksLocal writes acknowledgementBandwidth-friendlyJust delta replicationSpace efficientThin awareGuara

10、nteed Consistency Enabled by Volume GroupsBased on snapshots3Step 2 :Local snapshot createdPrimarySecondaryStep 1 :Secondary volume created2Step 3 :Initial synchronizationPS3PAR Remote Copy Asynchronous PeriodicContinuous operation and periodic resynchronizationIdeal for long-distance implementation

11、sEfficient even with high latency linksLocal write acknowledgementBandwidth-friendlyJust delta replicationSpace efficientThin awareGuaranteed Consistency Enabled by Volume GroupsBased on snapshots42 : Host I/O acknowledged to hostSecondary1 : Host server writes I/O to primary write cacheLocal Snapsh

12、ots12Manual or scheduled resync3 : Create local and remote snapshot4 : Replicate snapshot delta 33RemoteSnapshotPSPrimary3PAR Remote Copy Asynchronous StreamingContinuous operation with RPO close to 0Efficient with higher latency linksLocal write acknowledgement Maintains local server write IO perfo

13、rmance and latency Write IO data is queued in local cache and replicated at max available link speed Guaranteed Consistency Enabled by Volume Groups and Write IO tickets (tags)2 : Host I/O acknowledged to hostPS1 : Host server writes I/O to primary write cache33 : Primary array writes I/O to seconda

14、ry write cache124 : Remote array acknowledges the receipt of the I/O4PrimarySecondary3PAR Remote Copy Volume GroupsAssured Data integritySingle VolumeAll writes to the secondary volume are completed in the same order as they were written on the primary volumeAutonomic Remote Copy Volume GroupVolumes

15、 grouped together to maintain write ordering across sets of volumesUseful for databases or other applications with dependenciesSecondary groups and volumes are autonomically created and credentials inherited RC Volume GroupRC Volume GroupCreate new Source VolumeNew Target Volume created autonomicall

16、yPrimary 3PAR StorageSecondary 3PAR Storage3PAR Remote CopySupported topologies and maximum latencies Remote Copy TypeMax Supported Latency Round Trip Time (RTT )3PAR OS 3.2.13PAR OS 3.2.23PAR OS 3.3.1Synchronous RCFC2.6ms MU1: 5ms - MU2: 10ms10msSynchronous RCIP2.6ms5ms5msSynchronous RC FCIPNA10ms1

17、0msAsynchronous Periodic RCFC2.6ms5ms5msAsynchronous Periodic RCIP150ms150ms150msAsynchronous Periodic RC FCIP120ms120ms120msAsynchronous Streaming RCFCNA5ms30msAsynchronous Streaming RCIPNANA30msAsynchronous Streaming FCIPNA10ms30msOptical Fibre networks typically have a delay of 5 us/km (0.005ms/k

18、m)Thus 2.6ms RTT will allow Fibre link distances of up to 260km, 10ms RTT gives you 1000km 2.6ms : 0.005ms/km = 520km forth and back 260km site to site10.0ms : 0.005ms/km = 2000km forth and back 1000km site to siteGo back to SW and Features3PAR Remote Copy link performance enhancementsDramatically i

19、ncreased performance with 3.3.1 for RCFC and RCIP3PAR 2-node configuration, 8kB, 100% random writeSynchronous Remote Copy FC (4 x 16Gb FC links)3.2.23.3.1 with IRQ map disabled3.3.1 with IRQ map enabledIRQ = Processor Interrupt Request1432765Response time (ms)400006000010000080000120000Host performa

20、nce (IOPS)3PAR 4-node configuration, 8kB, 100% random writeSynchronous Remote Copy IP (4 x 10Gb RCIP links)10000012000016000014000180000Response time (ms)Host performance (IOPS)14327653.2.23.3.1 with IRQ map disabled3.3.1 with IRQ map & jumbo frames enabledIRQ = Processor Interrupt RequestRemote Cop

21、y terminologyPrimary systemTarget systemPPTT Copy pair Copy pairRemote Copy group (RCG)P=Primary volumeT=Target volume14Remote Copy: Failure scenarios15Failure scenario Failures/events preventing replication to the remote site such as: All links go down Target/remote array goes down Target/remote ar

22、ray experiences a hardware failure, preventing remote replication Snapshots at the primary are taken to resynchronize the stale target at the remote site. Writes are allowed for the primary volume.PrimarySecondaryWrites allowed to primary volumesnapPT16PrimaryP=Primary volumeT=Target volumeSecondary

23、New primary (original target) can be exported to the remote site host and the application brought up at remote sitePFailover conceptIn a remote replication context, failover reverses replication direction and volume roles Target RCG member becomes the primary Original primary volumes in RCG become t

24、arget volumesTTP17Remote Copy operations18Create a Remote Copy configuration19Stop replication of Remote Copy groupTo stop/suspend remote replication:stoprcopygroup 20Fail over a Remote Copy groupTo fail over a single Remote Copy group (to be done from the target/remote system): setrcopygroup failov

25、er To fail over all Remote Copy groups for a failed primary array: setrcopygroup failover -t 21Recover a Remote Copy groupTo resume or start replication in the opposite direction after a failover, a recovery must be done on the Remote Copy group setrcopygroup recover -t 22Remote Copy CLI (1 of 2)23C

26、ommandSummaryhistrcvvDisplays histogram data for Remote Copy volumesstatrcvvDisplays statistics for Remote Copy volumesadmitrcopylink Admits a network link for Remote Copy useadmitrcopytargetAdds a target to a Remote Copy volume groupadmitrcopyvvAdmits a virtual volume to a Remote Copy volume groupc

27、heckrclinkPerforms a latency and througHPEut test between two connected HPE 3PAR Storage systemscreatercopygroupCreates a group for Remote CopycreatercopytargetCreates a target for Remote CopydismissrcopylinkDismisses a network link from Remote Copy usedismissrcopytargetDismisses a Remote Copy targe

28、t from a Remote Copy volume groupdismissrcopyvvDismisses a virtual volume from a Remote Copy volume groupremovercopygroupRemoves a group used for Remote CopyRemote Copy CLI (2 of 2)24CommandSummarysetrcopygroupSets the volume group policy for dealing with I/O failure and error handling, or switches

29、the direction of the Remote Copy groupsetrcopytargetSets the Remote Copy target stateshowrcopyDisplays the details of a Remote Copy configurationshowrctransportShows status and information about end-to-end transport for Remote Copy in the systemstartrcopyStarts a Remote Copy systemstartrcopygroupSta

30、rts a Remote Copy volume groupstatrcopyDisplays Remote Copy statisticsstoprcopyStops a Remote Copy subsystemstoprcopygroupStops a Remote Copy volume groupsyncrcopySynchronizes Remote Copy volume groupssrstatrcvvSystem reporter reports on the performance of the Remote Copy volumes srstatrcopySystem r

31、eport performance reports for Remote Copy links Remote Copy: Summary of features and benefitsFeaturesBenefitsHost-independent, array-basedBoosts performance by offloading host servers of replication tasks Modular architecture Allows customer-defined, flexible deployment at all sites Line-trunking to

32、 seamlessly balance load across all available RC links Optimizes performance and prevents bottlenecks; increases availability Multiple modes of operation: Synchronous, asynchronous periodic, asynchronous streaming and synchronous long distance (SLD)Offers choice and flexibility in deploying the appr

33、opriate solution Consistency groups Ensures readily usable, I/O consistent data at remote site Transport agnosticSimplifies connectivity requirementsThin Provisioning/Thin Dedup awareSignificantly reduces cost of deploying remote replicationMany-to-One, One-to-Many, M-to-NProvides a cost-effective d

34、isaster recovery solution for service providers and enterprises with distributed data centers25Disaster Tolerant Solutions- Cluster Extension- Metrocluster - Peer PersistenceNever lose access to your volumesPeer Persistence 3PAR Storage & VMware vSphereWhat does it provide?High Availability across d

35、ata centers Automatic or manual transparent LUN swap Transparent VM vMotion between data centersHow does it work?Based on 3PAR Remote Copy and vSphere ALUAPresents primary LUN as active and secondary as standbyAutomated LUN swap arbitrated by a Quorum Witness (QW Linux ESX VM on 3rd site)Supported e

36、nvironments:ESX vSphere 5.x incl. HA, Failsafe and vSphere Metro Storage ClusterSync Remote Copy Up to Remote Copy sync supported maximum of 10ms RTT (1000km)Requirements:Two 3PAR Disk ArraysTwo RC sync links (RCFC or RCIP*)3PAR Remote Copy and Peer Persistence LicensesAlso see the VMware KB Impleme

37、nting vMSC using 3PAR Peer Persistence and the HP Whitepaper ”Implementing vMSC using HP 3PAR Peer Persistence”* RCFC strongly recommended; VMware vMSC certification is based on RCFCData Center 2Data Center 1Synchronous Remote Copy + Peer PersistencePAActive LUN presentationPassive LUN presentationH

38、P 3PARHP 3PARQW DC 3vSpherevSpherevSpherevSphereUniform vSphere Metro Storage ClustervSphereAPALAN/WANP3PAR Peer PersistenceNever lose access to your data volumesData Center 2Data Center 1Synchronous Remote Copy + Peer Persistence3PAR3PARQW DC 3WitnessSPLAN/WANHypervisorHypervisorHypervisorHyperviso

39、rFailover ClusterPSSPPrimary RC VolumeSecondary RC Volume VMClustered Applicationactive pathsstandby paths What does it provide?High Availability across data centers How does it work?Automatic or manual transparent LUN swap based on 3PAR Remote Copy and OS MPIOPrimary RC Volume presented with active

40、 pathsSecondary RC Volume presented with passive pathsAutomated LUN swap arbitrated by a Quorum Witness (on a 3rd site)Requirements:FC, iSCSI or FCoE cross-site Server SANTwo synchronous Remote Copy links (RCFC or RCIP)Max replication link latency of 10ms RTT (1000km)3PAR Remote Copy and Peer Persis

41、tence LicensesSupported environments:All OS stated on the next slide Oracle RAC on Windows, HP-UX, RHEL, SUSEAlso see the Peer Persistence product pagePeer Persistence OverviewPeer Persistence is a high availability (HA) storage configuration between two sites with the ability to transparently redir

42、ect host I/O, from the primary to the secondary storage system”switchover” is a manual process allowing to facilitate service optimization and storage system maintenance activities within a high-availability data storage solution“failover” is an automatic process initiated by the secondary array red

43、irecting host I/O from the failed primary to the secondary array. A functional 3PAR Quorum Witness is required for an automatic transparent failover to occurThe Peer volumes must be synchronously replicated over RCFC, RCIP or RCIP and will have the same WWNs RC Link Topology3PAR OSRCFC 3.1.2 MU2RCIP

44、 3.1.3OSMin. 3PAR OSHost Connectivity3PAR Host PersonaVMware vSphere 5.0, 5.13.1.2 MU2FC11VMware vSphere 5.5, 6.x 1)3.1.33.2.1FCFC, iSCSI, FCoE11Windows 2008 R2, 2012 R22016 (Cluster and standalone)3.2.13.2.2 MU3FC, iSCSI, FCoE15RHEL 6.x, 7.x3.2.23.2.2 MU1FC, iSCSI, FCoE2HP-UX v3 3.2.2FC, FCoE13Citr

45、ix Xen Server 6.0, 6.1, 6.26.53.2.2.MU2FC12SLES 10, 11, 123.2.2.MU1FC, iSCSI2Solaris 10, 113.2.2.MU1FC21) ESX VVOL not supported3PAR 3DC Peer Persistence Combine HA and DTWhat does it provide?High Availability across metropolitan distances + Disaster Tolerance across continental distancesHow does it

46、 work?Adds a 3rd tertiary asynchronous copy Synchronous replication for transparent switchover between metropolitan data centers Asynchronous periodic replication for manual failover to a tertiary data center with continental distancesRequirements:For the metropolitan systems in DC1 and DC2 same as

47、with basic Peer Persistence incl. RTTFor the tertiary DC same as with asynchronous periodic replication and IP connectivity incl. RTT Supported environments:Same as basic Peer Persistence Min. 3PAR OS 3.3.1 for all arraysData Center 2Data Center 1Synchronous Remote Copy + Peer Persistence3PAR3PARTer

48、tiary DCWitnessSWAN or SANFailover ClusterP3PARDR ServersSANPSPPTT3PAR 3DC Peer Persistence Active async RC pathsPrimarySecondaryPTTertiarySStandby async RC pathsSync RCpathsInitial statePrimarySecondarySTTertiaryPActive asyncRC pathsAfter transparent failoverPrimarySecondaryPPTertiarySAfter manual

49、failover to tertiary DR due to the loss of primary and secondary DC 3PAR HA/DT Options and Comparison 3PAR Peer Persistence3PAR Cluster Extension (CLX)HPE Serviceguard MetroclusterPrimary Use caseApplication transparent Storage Failover Replicated storage is virtualized across sites; Cluster and sto

50、rage failover is independentCluster Service Failover Storage is a cluster resource; a failover will move applications and storage as oneCluster Service Failover Storage is a cluster resource; a failover will move applications and storage as oneIntegration MethodAgentless and transparent, based on MP

51、IO (ALUA)Agent in the MS Cluster stackAgent in the HPE Serviceguard Cluster stackConfigurations1:1Uniform host access (All hosts in both sites need connectivity to both 3PAR) Sync Remote Copy Non-uniform host access (Hosts are only connected to the local 3PAR)Sync or async Remote Copy Non-uniform ho

52、st access (Hosts are only connected to the local 3PAR)Sync or async Remote Copy 1:2Same as above + non-uniform access to 3rd 3PARAsync periodic Remote CopyAll non-uniform host access3PAR SLD config with sync RC between metro and async periodic RC between continental siteAll non-uniform host access3P

53、AR SLD config with sync RC between metro and async periodic RC between continental siteSupported ConfigurationsvSphere, Windows Server, Windows Hyper-V, RHEL, HP-UX, SUSE, Cirtix, SolarisOracle RAC stretch-cluster (Windows, RHEL, HP-UX)Windows Server 2008, 2012, 2016 with Windows Failover Cluster HP

54、-UX 11v2, v3 with Serviceguard + MetroclusterRHEL 5, 6, 7 with Serviceguard + MetroclusterSUSE 11, 12 with Serviceguard + MetroclusterTriggerManual or automated for metro switch-overManual continental failoverManual or automated for metro failoverManual continental failoverManual or automated for me

55、tro failoverManual continental failoverManual GranularityRemote Copy GroupRemote Copy GroupRemote Copy GroupAutomated GranularityFull ArrayClustered Service / Remote Copy GroupClustered Service / Remote Copy GroupLicensingPP is included in the 3PAR Multi-System Software Suite10000 & 7000: per Server

56、 or per 3PAR array8000 & 20000: included in 3PAR Multi-System Software SuiteLinux: per SocketHP-UX: per Socket or ClusterCluster Extension for WindowsClustering solution protecting against server and storage failureWhat does it provide?Manual or automated site-failover for Server and Storage resourc

57、es Transparent Hyper-V Live Migration between siteSupported environments:Microsoft Windows Server 2003, 2008, 2012, 2016HPE StoreEasy (Windows Storage Server) Max supported distancesRemote Copy sync supported up to 10ms RTT (1000km)Up to MS Cluster heartbeat max of 20ms RTT 1:1 and SLD configuration

58、Sync or async Remote Copy Requirements:3PAR Disk Arrays3PAR Remote Copy (RC)Microsoft ClusterHPE Cluster Extension (CLX)Max 20ms cluster IP network RTTLicensing:Included in the Multi-System all-inclusive SuiteAlso see the HPE CLX General References 3PAR 3PARData Center 2Data Center 1DC 3File share W

59、itnessSynchronous or asynchronous Remote Copymanaged by CLX LAN/WANServiceguard Metrocluster for HP-UX and LinuxEnd-to-end clustering solution to protect against server and storage failureWhat does it provide?Manual or automated site-failover for Server and Storage resourcesSupported environments:HP

60、-UX 11i v2 & v3 with Serviceguard RHEL 5 and 6 with HPE ServiceguardSLES 11with HPE Serviceguard Max supported distancesUp to Remote Copy sync max 10ms RTT (1000km)Up to Remote Copy async max 150ms RTT Requirements:3PAR Disk Arrays 3PAR Remote CopyHPE Serviceguard & HPE MetroclusterLicensing for Lin