HP serviceguard t2808-90006 manual Understanding Types of Disaster Tolerant Clusters

Page 32

Disaster Tolerance and Recovery in a Serviceguard Cluster

Understanding Types of Disaster Tolerant Clusters

Table 1-1

Comparison of Disaster Tolerant Cluster Solutions (Continued)

 

 

 

 

Attributes

Extended Distance

CLX

Continentalclusters

Cluster

(HP-UX only)

 

 

 

 

 

 

Key

No ability to check the

Specialized storage

No automatic failover

Limitation

state of the data before

required. Currently, XP

between clusters.

 

starting up the

with Continuous Access,

 

 

application. If the

and EVA with

 

 

volume group (vg) can

Continuous Access are

 

 

be activated, the

supported.

 

 

application will be

 

 

 

started. If mirrors are

 

 

 

split or multiple paths

 

 

 

to storage are down, as

 

 

 

long as the vg can be

 

 

 

activated, the

 

 

 

application will be

 

 

 

started.

 

 

 

Data resynchronization

 

 

 

does not have a big

 

 

 

impact on system

 

 

 

performance. However,

 

 

 

the performance varies

 

 

 

depending on the

 

 

 

number of times data

 

 

 

resynchronization

 

 

 

occurs. In the case of

 

 

 

MD, data

 

 

 

resynchronization is

 

 

 

done one disk at a time,

 

 

 

using about 10% of the

 

 

 

available CPU time

 

 

 

and taking longer to

 

 

 

resynchronize multiple

 

 

 

LUNs. The amount of

 

 

 

CPU time used is a

 

 

 

configurable MD

 

 

 

parameter.

 

 

 

 

 

 

32

Chapter 1

Image 32
Contents Page Legal Notices Contents Disaster Scenarios and Their Handling Managing an MD Device Contents Contents Printing History Editions and ReleasesHP Printing Division Intended Audience Document OrganizationPage Related Page Disaster Tolerance Evaluating the Need for Disaster Tolerance Evaluating the Need for Disaster Tolerance What is a Disaster Tolerant Architecture? High Availability ArchitectureNode 1 fails Pkg B Client ConnectionsDisaster Tolerant Architecture Understanding Types of Disaster Tolerant Clusters Extended Distance ClustersFrom both storage devices Extended Distance Cluster Two Data Center Setup Benefits of Extended Distance Cluster Cluster Extension CLX Cluster Shows a CLX for a Linux Serviceguard cluster architecture CLX for Linux Serviceguard ClusterBenefits of CLX Differences Between Extended Distance Cluster and CLX Continental Cluster Los Angeles Cluster New York ClusterData Cent er a Data Center B Continental ClusterBenefits of Continentalclusters Comparison of Disaster Tolerant Solutions Continental Cluster With Cascading FailoverComparison of Disaster Tolerant Cluster Solutions Attributes Extended DistanceContinentalclusters Cluster HP-UX onlyUnderstanding Types of Disaster Tolerant Clusters Understanding Types of Disaster Tolerant Clusters Understanding Types of Disaster Tolerant Clusters WAN EVA Disaster Tolerant Architecture Guidelines Protecting Nodes through Geographic DispersionProtecting Data through Replication Off-line Data ReplicationOn-line Data Replication Physical Data ReplicationAdvantages of physical replication in hardware are Disadvantages of physical replication in hardware areAdvantages of physical replication in software are Disadvantages of physical replication in software are Logical Data ReplicationDisadvantages of logical replication are Using Alternative Power Sources Ideal Data ReplicationAlternative Power Sources Power Circuit 1 nodeData Center a Node 3 Power Circuit Creating Highly Available NetworkingDisaster Tolerant Local Area Networking Disaster Tolerant Wide Area NetworkingDisaster Tolerant Cluster Limitations Manage it in-house, or hire a service? Managing a Disaster Tolerant EnvironmentHow is the cluster maintained? Additional Disaster Tolerant Solutions Information Building an Extended Distance Types of Data Link for Storage Networking DwdmTwo Data Center and Quorum Service Location Architectures Two Data Center and Quorum Service Location Architectures Two Data Centers and Third Location with Dwdm and Quorum ServerTwo Data Center and Quorum Service Location Architectures Rules for Separate Network and Data Links Guidelines on Dwdm Links for Network and Data Guidelines on Dwdm Links for Network and Data Guidelines on Dwdm Links for Network and Data Chapter Configuring your Environment Understanding Software RAID Installing the Extended Distance Cluster Software Installing XDCSupported Operating Systems PrerequisitesVerifying the XDC Installation # rpm -Uvh xdc-A.01.00-0.rhel4.noarch.rpmInstalling the Extended Distance Cluster Software Configuring the Environment Configuring the Environment Configuring the Environment Configuring Multiple Paths to Storage Setting the Value of the Link Down Timeout ParameterCluster Reformation Time and Timeout Values Using Persistent Device Names Http//docs.hp.comCreating a Multiple Disk Device To Create and Assemble an MD Device# mdadm -A -R /dev/md0 /dev/hpdev/sde1 /dev/hpdev/sdf1 Chapter Linux #RAIDTAB= # MD RAID Commands To Edit the Datarep Variable Creating and Editing the Package Control ScriptsTo Create a Package Control Script Editing the raid.conf File To Edit the Xdcconfig File parameterTo Configure the RAID Monitoring Service Cases to Consider when Setting Rpotarget RPO Target Definitions Chapter Multipledevices and Componentdevices Raidmonitorinterval Configuring your Environment for Software RAID Disaster Scenario What happens when this disaster occursRecovery Process Disaster Scenarios and Their Handling Disaster Scenarios and Their Handling# mdadm --remove /dev/md0 # mdadm -add /dev/md0 Dev/hpdev/mylink-sdf P1 uses a mirror md0 Run the following command to S2 is non-current by less # cmrunpkg packagename Execute the commands that With md0 consisting of only N1, for example Becomes accessible from N2 Center Disaster Scenarios and Their Handling Managing an MD Device Viewing the Status of the MD Device Cat /proc/mdstatStopping the MD Device Example A-1 Stopping the MD Device /dev/md0Starting the MD Device Example A-2 Starting the MD Device /dev/md0Removing and Adding an MD Mirror Component Disk # udevinfo -q symlink -n sdc1Adding a Mirror Component Device # mdadm --remove /dev/md0 /dev/hpdev/sdeIndex 104