HP CLX Migration Whitepaper

ManualsBrandsHP ManualsSoftwareHP Serviceguard for Linux ProLiant Cluster

Technical white paper

HP CLX Migration

Migration from HP Cluster Extension Software on Linux to HP Serviceguard Metrocluster

on Linux

Table of contents

Introduction .................................................................................................................................................................................... 2

Audience ...................................................................................................................................................................................... 2

Overview .......................................................................................................................................................................................... 2

HP Cluster Extension Software solution on Linux ............................................................................................................. 2

HP Serviceguard for Linux ....................................................................................................................................................... 2

HP Serviceguard Metrocluster............................................................................................................................................... 2

Preparing the CLX for Migration ................................................................................................................................................. 3

Comparison of some important terminologies .................................................................................................................. 6

Mapping of RHCS and SLE HA cluster attributes to SG/LX cluster attributes ............................................................... 6

Mapping of RHCS and SLE HA system attributes to SG/LX node attributes ................................................................. 7

Mapping the 3PAR CLX attributes to SG Metrocluster attributes ....................................................................................... 7

Mapping the CLX XP cluster attributes to Serviceguard Metrocluster attributes ........................................................... 9

Mapping the CLX EVA cluster attributes to Serviceguard Metrocluster attributes ......................................................... 9

Unsupported use cases.............................................................................................................................................................. 11

Migration procedure ................................................................................................................................................................... 11

Appendix ........................................................................................................................................................................................ 13

3PAR .......................................................................................................................................................................................... 13

P9000 ........................................................................................................................................................................................ 14

P6000 ........................................................................................................................................................................................ 15

References .................................................................................................................................................................................... 15

Summary of content (15 pages)

PAGE 1
Technical white paper HP CLX Migration Migration from HP Cluster Extension Software on Linux to HP Serviceguard Metrocluster on Linux Table of contents Introduction .................................................................................................................................................................................... 2 Audience..........................................................................................................................................................
PAGE 2
Introduction This white paper describes a procedure to migrate an HP Cluster Extension Software (CLX) on Linux to HP Serviceguard Metrocluster on Linux. It also provides an overview of functionalities and advantages of using Metrocluster. Audience The target audience for this document is HP Cluster Extension Software administrators who want to migrate to HP Serviceguard Metrocluster on Linux.
PAGE 3
Important Before migrating to HP Serviceguard Metrocluster on Linux, complete the following tasks: 1. 2. HP recommends that you backup the most recent copy of the application data. This protects data loss in the event of any operator error during the migration. Verify the support matrix requirements for a Metrocluster. This migration procedure is applicable for all the replication modes, and the Serviceguard and Metrocluster versions mentioned in the supported matrix.
PAGE 4
• Quorum Server Quorum Server can be used as a membership arbitration method for multiple clusters at a time. The Quorum Server does not have any limitation in terms of number of nodes in a cluster. The Quorum Server software can be configured as a Serviceguard package, or standalone, but in either case it must run on a system outside of the cluster for which it is providing quorum services. The Quorum Server listens to connection requests from the Serviceguard nodes on a known port.
PAGE 5
Figure 1.
PAGE 6
Comparison of some important terminologies The following table compares the important RHCS and SLE HA terminologies with SG/LX terminologies. Table 1. Important Terminologies RHCS Terminology SLE HA Terminology SG/LX Terminology Description System Node Node Member of cluster Cluster Service Cluster Resources Package Way to package all hardware and software resource together as single unit. Resource Resource Modules Way to manage (start/stop/monitor) hardware and software resources.
PAGE 7
totem token Totem token MEMBER_TIMEOUT In RHCS, the token timeout is the number of milliseconds a node has to send the token before the node is considered failed. cman sets this to a default of 10000 (10 seconds). In SG/LX, The MEMBER_TIMEOUT parameter defaults to 14000000 (14 seconds). If a heartbeat is not received from a node within this time, it is declared dead and the cluster reforms without that node. A value of 10 to 25 seconds is appropriate for most installations.
PAGE 8
applications. In MC 3PAR, each package has its own folder. ApplicationStartup (optional) RESYNC_WAIT_TIMEOUT ResyncWaitTimeout If “Application Startup” is set to “RESYNCWAIT” then use “ ResyncWaitTimout” value for HP Serviceguard Metrocluster. If “ApplicationStartup” is set to “FASTFAILBACK”. Then, use “RESYNC_WAIT_TIMEOUT = 0” for HP Serviceguard Metrocluster. N/A CLUSTER_TYPE CLUSTER_TYPE = metro.
PAGE 9
Mapping the CLX XP cluster attributes to Serviceguard Metrocluster attributes The following table maps the CLX XP cluster attributes to the closest SG/LX Metrocluster attributes. Table 5. CLX XP cluster attributes and SG/LX cluster attributes Component Attributes CLX XP attributes Corresponding SG/LX Metrocluster attributes XPSerialNumbers N/A This is not required for Metrocluster XP, The communication is only through raid manager.
PAGE 10
Table 6. CLX EVA cluster attributes and SG/LX cluster attributes Component Attributes CLX EVA attributes Corresponding SG/LX Metrocluster attributes UseNonCurrentDataOk DT_APPLICATION_STARTUP_POLICY Description If ‘UseNonCurrentDataOk’ is set to “YES”, then, configure DT_APPLICATION_STARTUP_POLICY to “Availability_Preferred” If ‘UseNonCurrentDataOk’ is set to “NO”, then, configure DT_APPLICATION_STARTUP_POLICY to “Data_Currency_Preferred”.
PAGE 11
- dts_pkg_dir dts_pkg_dir is the package directory where the force flag file is created. In CLX, force flag file for all the packages is created under the same directory as mentioned in the ApplicationDir parameter. The force flag file format in the Metrocluster is “FORCEFLAG” whereas in CLX, it is “.forceflag” - CLUSTER_TYPE Do not make any changes. Retain the default value as “metro”.
PAGE 12
NODE STATUS STATE Metro2 up running 11. To view the values of the attributes, use the cmgetpkgenv command.
PAGE 13
Figure 2. Migrated architecture of Serviceguard Metrocluster Appendix The following table illustrates how this information is used to populate the Serviceguard package configuration worksheets.
PAGE 14
N/A CLUSTER_TYPE DC_A_InServStorage_SerNum DC1_STORAGE_SYSTEM_NAME DC_B_InServStorage_SerNum DC2_STORAGE_SYSTEM_NAME N/A DC1_STORAGE_SYSTEM_USER N/A DC2_STORAGE_SYSTEM_USER RCVolumeGroupA DC1_RC_VOLUME_GROUP RCVolumeGroupB DC2_RC_VOLUME_GROUP DC_A_Hosts DC1_NODE_LIST DC_B_Hosts DC2_NODE_LIST UseNonCurrentDataOk (optional) AUTO_NONCURDATA PostExecScript (optional) RESYNC_WAIT_TIMEOUT ApplicationStartup (optional) DR_NOTIFICATION_CHOICES N/A DC1_RC_TARGET_FOR_DC2 N/A DC2_RC_TARGET_F
PAGE 15
ResyncMonitorAutoRecover AUTO_RESYNC ------------- ResyncMonitorInterval (optional) MON_POLL_INTERVAL ------------- ResyncWaitTimeout (optional) WAITTIME ------------- ResyncMonitor (optional) Service_Cmd ------------- CLX EVA attributes Corresponding SG/LX cluster attribute Values UseNonCurrentDataOk DT_APPLICATION_STARTUP_POLICY ------------- DC_A_StorageCellWWN DC1_STORAGE_WORLD_WIDE_NAME ------------- DC_B_StorageCellWWN DC2_STORAGE_WORLD_WIDE_NAME DeviceGroup DR_GROUP_NAME DC_A