beautypg.com

HP Hitachi Dynamic Link Manager Software User Manual

Page 145

background image

3. Creating an HDLM Environment

123

6.

Upgrade or re-install HDLM on the active host.
To do so, perform steps 2 through 21 in (2) When Installing HDLM in a Boot Disk

Environment of 3.5.5 Performing an Upgrade Installation or Re-installation of

HDLM on the active host.

7.

Start HACMP on the active host.

(3) Migrating HDLM in an HACMP Environment

When HDLM version 5.8.1 or earlier is migrated to HDLM version 5.9 or later, the

logical device file that can be controlled by the HDLM driver changes from the HDLM

device (

dlmfdrv

n) to hdisk. If the user application uses an LU managed by HDLM,

modify the user application appropriately.
In a virtual I/O server environment, you cannot migrate HDLM when you are running

HACMP services.
The following procedure explains how to migrate HDLM in an HACMP environment.

This procedure explains how to migrate HDLM when you are using HACMP 5.4. For

details about how to use HACMP, see the HACMP documentation along with this

manual.
To migrate HDLM in an HACMP environment:
1.

Log in to AIX as the root user.

2.

If disk heartbeats are set, delete the disk heartbeat settings (because you need to

change the disk name from

dlmfdrv

to

hdisk

).

For details, see the HACMP documentation.

3.

Stop HACMP on the standby host.

4.

Migrate HDLM on the standby host.
To do so, perform steps 10 to 26 in 3.5.6 Migrating from HDLM Version 5.8.1 or

Earlier to Version 5.9 or Later on the standby host.

5.

Start HACMP on the standby host.
When HACMP starts, a warning message may be output, stating that the custom

disk method file (

/usr/DynamicLinkManager/cluster/

dlm_hacmp_gdisk_check

) does not exist. This message can be ignored

because it does not affect any operations.
The following is an example of such a message:

WARNING: Custom disk method: ghostdisks's file:
/usr/DynamicLinkManager/cluster/dlm_hacmp_gdisk_check does

not exist or is not executable on node:

xxx

#