HP serviceguard t2808-90006 manual S2 is non-current by less

Page 91

 

 

 

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 failure is the same as the

Package P1 continues to run

In this scenario, no attempts are

previous failure except that the

on N1 after the first failure

made to repair the first failure

package (P1) is configured with

with md0 consisting of only

until the second failure occurs.

RPO_TARGET set to 60 seconds.

S1

Typically, the second failure occurs

In this case, initially the

After the second failure,

before the first failure is repaired.

 

package (P1) is running on N 1.

package P1 fails over to N2

1. To recover from the first

P1 uses a mirror md0 consisting

and starts with S2. This

failure, restore the FC links

of S1 (local to node N1 -

happens because the disk

between the data centers. As a

/dev/hpdev/mylink-sde) and

S2 is non-current by less

result, S1

S2 (local to node N2). The first

than 60 seconds. This time

(/dev/hpdev/mylink-sde) is

failure occurs when all FC links

limit is set by the

accessible from N2.

between the two data centers

RPO_TARGET parameter.

2. Run the following command to

fail, causing N1 to lose access to

Disk S2 has data that is

S2 and N2 to lose access to S1.

older than the other mirror

add S1 to md0 on N2:

After the package resumes

half S1.

# mdadm --add /dev/md0

 

activity and runs for 20 seconds,

However, all data that was

/dev/hpdev/mylink-sde.

a second failure occurs causing

written to S1 after the FC

This command initiates the

N 1 to fail, perhaps due to power

link failure is lost

re-mirroring process. When it is

failure.

 

 

 

 

complete, the extended distance

 

 

 

 

 

 

cluster detects S1 and accepts it as

 

 

 

md0 again.

 

 

 

For the second failure, restore N1.

 

 

 

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

 

 

 

 

Chapter 4

91

Image 91
Contents Page Legal Notices Contents Disaster Scenarios and Their Handling Managing an MD Device Contents Contents Editions and Releases Printing HistoryHP Printing Division Document Organization Intended AudiencePage Related Page Disaster Tolerance Evaluating the Need for Disaster Tolerance Evaluating the Need for Disaster Tolerance Pkg B Client Connections What is a Disaster Tolerant Architecture?High Availability Architecture Node 1 failsDisaster Tolerant Architecture Extended Distance Clusters Understanding Types of Disaster Tolerant ClustersFrom both storage devices Extended Distance Cluster Two Data Center Setup Benefits of Extended Distance Cluster Cluster Extension CLX Cluster CLX for Linux Serviceguard Cluster Shows a CLX for a Linux Serviceguard cluster architectureBenefits of CLX Differences Between Extended Distance Cluster and CLX Continental Cluster Continental Cluster Los Angeles ClusterNew York Cluster Data Cent er a Data Center BBenefits of Continentalclusters Continental Cluster With Cascading Failover Comparison of Disaster Tolerant SolutionsCluster HP-UX only Comparison of Disaster Tolerant Cluster SolutionsAttributes Extended Distance ContinentalclustersUnderstanding Types of Disaster Tolerant Clusters Understanding Types of Disaster Tolerant Clusters Understanding Types of Disaster Tolerant Clusters WAN EVA Protecting Nodes through Geographic Dispersion Disaster Tolerant Architecture GuidelinesOff-line Data Replication Protecting Data through ReplicationPhysical Data Replication On-line Data ReplicationDisadvantages of physical replication in hardware are Advantages of physical replication in hardware areAdvantages of physical replication in software are Logical Data Replication Disadvantages of physical replication in software areDisadvantages of logical replication are Ideal Data Replication Using Alternative Power SourcesCreating Highly Available Networking Alternative Power SourcesPower Circuit 1 node Data Center a Node 3 Power CircuitDisaster Tolerant Wide Area Networking Disaster Tolerant Local Area NetworkingDisaster Tolerant Cluster Limitations Managing a Disaster Tolerant Environment Manage it in-house, or hire a service?How is the cluster maintained? Additional Disaster Tolerant Solutions Information Building an Extended Distance Dwdm Types of Data Link for Storage NetworkingTwo Data Center and Quorum Service Location Architectures Two Data Center and Quorum Service Location Architectures Server Two Data Centers and Third Location with Dwdm and QuorumTwo 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 Prerequisites Installing the Extended Distance Cluster SoftwareInstalling XDC Supported Operating Systems# rpm -Uvh xdc-A.01.00-0.rhel4.noarch.rpm Verifying the XDC InstallationInstalling the Extended Distance Cluster Software Configuring the Environment Configuring the Environment Configuring the Environment Setting the Value of the Link Down Timeout Parameter Configuring Multiple Paths to StorageCluster Reformation Time and Timeout Values Http//docs.hp.com Using Persistent Device NamesTo Create and Assemble an MD Device Creating a Multiple Disk 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 Cat /proc/mdstat Viewing the Status of the MD DeviceExample A-1 Stopping the MD Device /dev/md0 Stopping the MD DeviceExample A-2 Starting the MD Device /dev/md0 Starting the MD Device# udevinfo -q symlink -n sdc1 Removing and Adding an MD Mirror Component Disk# mdadm --remove /dev/md0 /dev/hpdev/sde Adding a Mirror Component DeviceIndex 104