Upgrading to HP Serviceguard 11.17 with Cluster Volume Manager/Cluster File Systems, December 2005

Appendix A presents a set of illustrations of various upgrade scenarios that describe different

possibilities of configuring Serviceguard to manage storage.

Data migration to CVM/CFS

Many sites will want to upgrade the way the application data is stored to take advantage of the CFS

capabilities available with some of the bundles. Existing LVM volumes can continue to be used in the

current form as long as desired, before upgrading to take advantage of the new features. Because

there is no rolling upgrade process available from earlier versions of CVM under Serviceguard control

to CFS, when CVM is used, the data cannot be migrated without restarting the applications.

As with earlier versions of Serviceguard and VERITAS, VxVM- and LVM-based storage can be used

simultaneously both within a cluster and within a single package.

Because Serviceguard supports only LVM disks for cluster lock disk use, it does not make sense to

upgrade these disks, unless the cluster is being reconfigured to use a Quorum Server instead.

Current data might reside on file systems or raw volumes. The raw data might be on CVM (with pre-

4.1 VERITAS), LVM, or SLVM volumes. The file system is typically OnlineJFS (VxFS) on LVM or VxVM

disk volumes.

Migrated data may reside on either raw CVM volumes or CFS file systems.

To convert Shared Logical Volume Manager (SLVM) data to CVM, the volume must be deactivated

and unshared. The instructions for unsharing and deactivating an SLVM volume appear in the Using

Serviceguard Extension for RAC Third Edition manual.

LVM volume groups must also be deactivated and taken out of the cluster to be converted. This can be

accomplished with the following command (after halting any packages that might be using the volume

groups):

# vgchange –a n <vg-name>; vgchange –c n <vg-name>

The volumes can then be converted ”in place” to VxVM using the vxvmconvert command. Detailed

documentation on this process can be found in the VERITAS Volume Manager Migration Guide. After

the migration is complete, the resulting VxVM disk groups can be configured for Serviceguard

management with cfsdgadm and used with applications as described in the “HP Serviceguard

configuration considerations” section. If the data currently resides in a VxFS file system, this procedure

can also be used to convert the underlying volume to VxVM, so it can be used as a CFS file system.

If the data is currently on a raw volume, the volume might need to be dumped to an intermediate

location and restored to a new file system that is created for the data. Data could also be moved

directly with dd, as detailed in the VERITAS Storage Foundation Administration Guide.

Oracle provides a variety of tools to move data—some of which are version-independent, and others

are available with certain versions of Oracle Database. The canonical tools are the exp and imp

commands, which work for all versions of the database and can be done without taking down the

database, but might not perform as well as some of the other options. Oracle 10g features the new

Data Pump mechanism that is designed for high performance and is recommended. A white paper

describing this feature can be found on Oracle Technology Network website under the name DATA

PUMP IN ORACLE® DATABASE 10g: FOUNDATION FOR ULTRA HIGH-SPEED DATA MOVEMENT

UTILITIES. For earlier versions of Oracle, the database instance must be stopped for conversion. For

Oracle 9i, HP recommends converting to Oracle Disk Manager files. Conversion processes for Oracle

9i are described in detail in the VERITAS Storage Foundation for Oracle Administrators Guide.

Other applications that support both CVM raw volumes and CFS file systems define their own

procedures for data conversion. Consult application-specific documentation for the recommended

procedures.