HP serviceguard t2808-90006 manual Verifying the XDC Installation

Page 64

Configuring your Environment for Software RAID

Installing the Extended Distance Cluster Software

Complete the following procedure to install XDC:

1.Insert the product CD into the drive and mount the CD.

2.Open the command line interface.

3.If you are installing XDC on Red Hat 4, run the following command:

#rpm -Uvh xdc-A.01.00-0.rhel4.noarch.rpm

4.If you are installing XDC on Novell SUSE Linux Enterprise Server 9, run the following command:

#rpm -Uvh xdc-A.01.00-0.sles9.noarch.rpm

5.If you are installing XDC on Novell SUSE Linux Enterprise Server 10, run the following command:

#rpm -Uvh xdc-A.01.00-0.sles10.noarch.rpm

This command initializes the XDC software installation. After you install XDC, you need to copy the raid.conf.template into each package directory that you need to enable Software RAID.

6.Run the following command to copy the raid.conf.template file as raid.conf file into each package directory:

#cp $SGROOT/xdc/raid.conf.template \ $SGCONF/<pkgdir>/raid.conf

The file is copied into the package directory.

NOTE	Installing the Extended Distance Cluster software does not enable
	Software RAID for every package in your environment. You need to
	manually enable Software RAID for a package by copying the files into
	the package directories. Also, if you need to enable Software RAID for
	more than one package in your environment, you need to copy the files
	and templates into each of those package directories. You must edit these
	template files later.

Verifying the XDC Installation

After you install XDC, run the following command to ensure that the software is installed:

#rpm -qa grep xdc

64

Chapter 3

Image 64

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