HP serviceguard t2808-90006 manual # mdadm --remove /dev/md0

Page 87

 

 

 

Disaster Scenarios and Their Handling

Table 4-1

Disaster Scenarios and Their Handling (Continued)

 

 

 

 

Disaster Scenario

What Happens When

Recovery Process

This Disaster Occurs

 

 

 

 

 

 

A package (P1) is running on a

The package (P1) continues

Once you restore power to S1, or

node (Node 1). The package uses

to run on Node 1 with the

restore the FC links to S1, the

a mirror (md0) that consists of

mirror that consists of only

corresponding mirror half of S1

two storage components - S1

S2.

(/dev/hpdev/mylink-sde) is

(local to Node 1 -

 

 

accessible from Node 1. To make

/dev/hpdev/mylink-sde) and

 

the restored mirrored half part of

S2 (local to Node 2).

 

 

the MD array, complete the

Access to S1 is lost from both

 

following procedure:

 

 

nodes, either due to power

 

1. Run the following command to

failure to S1 or loss of FC links

 

remove the mirrored half from

to S1.

 

 

 

 

the array:

 

 

 

 

 

 

# mdadm --remove /dev/md0

 

 

 

/dev/hpdev/mylink-sde

 

 

 

2. Run the following command to

 

 

 

add the mirrored half to the

 

 

 

array:

 

 

 

# mdadm --add /dev/md0

 

 

 

/dev/hpdev/mylink-sde

 

 

 

The re-mirroring process is

 

 

 

initiated. When it is complete, the

 

 

 

extended distance cluster detects

 

 

 

the added mirror half and accepts

 

 

 

S1 as part of md0.

 

 

 

 

Chapter 4

87

Image 87
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 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 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