HP serviceguard t2808-90006 Creating a Multiple Disk Device, To Create and Assemble an MD Device

Page 72

Configuring your Environment for Software RAID

Creating a Multiple Disk Device

 

Creating a Multiple Disk Device

 

As mentioned earlier, the first step for enabling Software RAID in your

 

environment is to create the Multiple Disk (MD) device using two

 

underlying component disks. This MD device is a virtual device which

 

ensures that any data written to it is written to both component disks. As

 

a result, the data is identical on both disks that make up the MD device.

 

This section describes how to create an MD device. This is the only step

 

that you must complete before you enable Software RAID for a package.

 

The other RAID operations are needed only during maintenance or

 

during recovery process after a failure has occurred.

 

 

NOTE

For all the steps in the subsequent sections, all the persistent device

 

names, and not the actual device names, must be used for the two

 

component disks of the MD mirror.

 

To Create and Assemble an MD Device

 

 

This example shows how to create the MD device /dev/md0, you must

 

create it from a LUN of storage device 1 (/dev/hpdev/sde1) and another

 

LUN from storage 2 (/dev/hpdev/sdf1).

 

Run the following command to create an MD device:

 

# mdadm --create --verbose /dev/md0 --level=1 \

 

--raid-devices=2 /dev/hpdev/sde1 /dev/hpdev/sdf1

 

This command creates the MD device.

 

Once the new RAID device, /dev/md0, is created on one of the cluster

 

nodes, you must assemble it on the nodes where the package must run.

 

You create an MD device only once and you can manage other functions

 

using the XDC scripts.

 

To assemble the MD device, complete the following procedure:

1.Stop the MD device on the node where you created it, by running the following command:

# mdadm -S /dev/md0

72

Chapter 3

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