HP serviceguard t2808-90006 manual N1, for example Becomes accessible from N2

Page 94

Disaster Scenarios and Their Handling

 

 

Table 4-1

Disaster Scenarios and Their Handling (Continued)

 

 

 

 

Disaster Scenario

What Happens When

Recovery Process

This Disaster Occurs

 

 

 

 

 

 

In this case, the package (P1)

When the first failure

Complete the following steps to

runs with RPO-TARGETset to 60

occurs, the package (P1)

initiate a recovery:

seconds.

 

continues to run on N1 with

1. Restore the FC links between

In this case, initially the

md0 consisting of only S1.

 

the data centers. As a result,

package (P1) is running on node

When the second failure

S2 (/dev/hpdev/mylink-sdf)

N1. P1 uses a mirror md0

occurs, the package fails

becomes available to N1 and

consisting of S1 (local to node

over to N2 and starts with

S1 (/dev/hpdev/mylink-sde)

N1, for example

 

S2.

 

becomes accessible from N2.

/dev/hpdev/mylink-sde) and

 

When N2 fails, the package

2. To start the package P1 on N1,

S2 (local to node N2). The first

does not start on node N1

failure occurs when all FC links

check the package log file in

because a package is

between the two data centers

the package directory and run

allowed to start only once

fail, causing N1 to lose access to

the commands which will

with a single disk. You must

S2 and N2 to lose access to S1.

appear to force a package

repair this failure and both

 

 

start.

Immediately afterwards, a

disks must be synchronized

When the package starts up on

second failure occurs where

and be a part of the MD

node (N1) goes down because of

array before another failure

N1, it automatically adds S2 back

a power failure.

 

of same pattern occurs.

into the array and the

After N1 is repaired and

In this failure scenario, only

re-mirroring process is started.

When re-mirroring is complete,

brought back into the cluster,

S1 is available to P1 on N1,

the extended distance cluster

package switching of P1 to N1 is

as the FC links between the

detects and accepts S1 as part of

enabled.

 

data centers are not

 

md0.

 

 

repaired. As P1 started once

IMPORTANT: While it is not a

 

with S2 on N2, it cannot

 

good idea to enable package

 

start on N1 until both disks

 

switching of P1 to N1, it is

 

are available.

 

described here to show recovery

 

 

 

from an operator error.

 

 

The FC links between the data centers are not repaired and N2 becomes inaccessible because of a power failure.

94

Chapter 4

Image 94
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 To Create a Package Control Script Creating and Editing the Package Control ScriptsTo Edit the Datarep Variable To Configure the RAID Monitoring Service To Edit the Xdcconfig File parameterEditing the raid.conf File Cases to Consider when Setting Rpotarget RPO Target Definitions Chapter Multipledevices and Componentdevices Raidmonitorinterval Configuring your Environment for Software RAID Recovery Process What happens when this disaster occursDisaster 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