HP serviceguard t2808-90006 manual P1 uses a mirror md0 Run the following command to

Page 90

Disaster Scenarios and Their Handling

 

 

Table 4-1

Disaster Scenarios and Their Handling (Continued)

 

 

 

 

Disaster Scenario

What Happens When

Recovery Process

This Disaster Occurs

 

 

 

 

 

 

This is a multiple failure

The package (P1) continues

In this scenario, no attempts are

scenario where the failures

to run on Node 1 after the

made to repair the first failure

occur in a particular sequence in

first failure, with the MD0

until the second failure occurs.

the configuration that

that consists of only S1.

Typically the second failure occurs

corresponds to figure 2 where

After the second failure, the

before the first failure is repaired.

Ethernet and FC links do not go

 

package P1 fails over to N2

1. To recover from the first

over DWDM.

 

 

 

and starts with S2. Data

failure, restore the FC links

The RPO_TARGET for the package

that was written to S1 after

between the data centers. As a

P1 is set to IGNORE.

 

the FC link failure is now

 

result, S1 is accessible from

 

 

lost because the

The package is running on Node

N2.

RPO_TARGET was set to

 

1. P1 uses a mirror md0

2. Run the following command to

IGNORE.

consisting of S1 (local to node

 

add S1 to md0 on N2:

N1, - /dev/hpdev/mylink-sde)

 

 

 

and S2 (local to node N2). The

 

# mdadm --add /dev/md0

first failure occurs when all FC

 

/dev/hpdev/mylink-sde

links between the two data

 

This command initiates the

centers fail, causing Node 1 to

 

 

re-mirroring process. When it

lose access to S2 and Node 2 to

 

 

is complete, the extended

lose access to S1.

 

 

 

 

distance cluster detects S1

 

 

 

After sometime a second failure

 

and accepts it as md0.

occurs. Node 1 fails (because of

 

For the second failure, restore N1.

power failure)

 

 

 

 

Once it is restored, it joins the

 

 

 

 

 

 

cluster and can access S1 and S2.

 

 

 

1. Run the following command to

 

 

 

enable P1 to run on N1

 

 

 

# cmmodpkg -e P1 -n N1

 

 

 

 

90

Chapter 4

Image 90
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 Node 1 fails What is a Disaster Tolerant Architecture?High Availability Architecture 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 Data Cent er a Data Center B Los Angeles ClusterNew York Cluster Continental ClusterBenefits of Continentalclusters Comparison of Disaster Tolerant Solutions Continental Cluster With Cascading FailoverContinentalclusters Comparison of Disaster Tolerant Cluster SolutionsAttributes Extended Distance 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 ReplicationData Center a Node 3 Power Circuit Alternative Power SourcesPower Circuit 1 node 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 Supported Operating Systems Installing the Extended Distance Cluster SoftwareInstalling XDC 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 Creating and Editing the Package Control Scripts To Create a Package Control ScriptTo Edit the Datarep Variable To Edit the Xdcconfig File parameter To Configure the RAID Monitoring ServiceEditing the raid.conf File Cases to Consider when Setting Rpotarget RPO Target Definitions Chapter Multipledevices and Componentdevices Raidmonitorinterval Configuring your Environment for Software RAID What happens when this disaster occurs Recovery ProcessDisaster Scenario 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