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

VERITAS Storage Foundation 4.1 no longer requires rootdg to be configured. The existing rootdg disk

group will continue to work and does not need updating other than as mentioned earlier, but it is no

longer required and may be deleted, if desired.

VERITAS 4.1 also introduces a new Cross-platform Data Sharing (CDS) disk layout as the default disk

layout for any new disks. Because existing disk layouts continue to be supported, this will only be of

consideration when creating new disks, unless you want to make existing data portable across

different UNIX® platforms. Detailed information about disk layouts and tools that can be used to

convert between them appears in the VERITAS Volume Manager Administration Guide.

With Storage Foundation 4.1, new disk groups are created with version 120 and new file systems

are created with disk layout version 6, unless explicitly specified otherwise, which makes new disk

groups and file systems incompatible with versions of VERITAS Storage Foundation earlier than 4.1.

This condition is a limitation only if you intend to use them with earlier versions of VERITAS software.

Any user-developed applications that make file system calls in the statvfsdev() family of functions must

be re-linked to enable them to work with file systems that have disk layout version 6.

HP Serviceguard configuration considerations

If a stand-alone version of CVM is installed on the cluster, it must be uninstalled before installing any

of the HP Serviceguard Storage Management Suite bundles. This operation requires halting and

deleting all CVM related packages: the application packages that specify STORAGE_GROUP attributes

in their configuration and the SMNP package (VxVM-CVM-pkg for CVM 3.5 or SG-CFS-pkg for CVM

4.1). After a CFS bundle is installed, these packages can be reapplied or upgraded, as described in

this section.

If the installation included installing CVM 4.1 (either stand-alone or as part of a bundle), the new

SG-CFS-pkg SMNP must be used to manage CVM. No changes are required to existing application

packages before reapplying them. The SG-CFS-pkg package can be configured and started using the

following commands, if one of the CFS bundles is installed.

# cfscluster config

# cfscluster start

If stand-alone CVM is installed, these commands are unavailable. The SMNP for CVM can be applied

with the cmapplyconf command in this case. The package name is VxVM-CVM-pkg for CVM 3.5

and SG-CFS-pkg for CVM 4.1. The package ASCII files and control scripts for these packages are

located in /etc/cmcluster/cvm and /etc/cmcluster/cfs directories for CVM 3.5 and CVM 4.1,

respectively.

If one of the CFS bundles is installed and you want to upgrade the existing packages to take

advantage of the new dependency features, HP recommends that you use the following procedure:

1. Configure and start the CVM SMNP.

2. Configure and start disk group MNPs with the following commands:

# cfsdgadm add <dg-name> all=sw # for shared/write everywhere

# cfsdgadm activate <dg-name>

3. Edit application packages’ ASCII configuration files to remove STORAGE_GROUP attributes and

add dependencies on the disk group packages created in step 2.

4. Generate new package scripts for these packages with cmmakepkg –s. Copy any custom code

present in the old scripts to the new scripts. Because any disk groups used by the package are

already defined in the MNPs, no variables that describe CVM disk groups used (for example,

CVM_DG[*] and CVM_DISK_ACTIVATION) must be set in the script.

5. Apply and start the upgraded application packages.