The examples in this section assume a two-node cluster that uses one disk drive each for the cluster-wide root, /usr, and /var file systems; one disk drive for each member boot disk; and 1 drive for the quorum disk.
Performing the Cloned Installation
To create an exact duplicate of your system on an alternate set of disk drives, you can find a third-party program that will do it for you, or you can use the following list of tasks as a guide for doing it yourself:
Download and extract the latest Tru64 UNIX version or mount the latest Tru64 UNIX version CD to your Version 5.1B-3 or higher system and run the dupatch command to install the latest tools, including the necessary cloning tools. See Chapter 3 for more information on installing the new tools.
Identify the alternate set of disks you will use for the new software
Partition the alternate drives so those partitions are as large or larger than the current drive set
Duplicate all cluster file systems onto the alternate disk set. This includes cluster_root, cluster_usr, and cluster_var.
Duplicate all member-specific root partitions onto the alternate disk set. (that is, root1_domain, root2_domain, and so forth.)
Create the CNX partitions for all member root drives and the quorum disk (if it exists).
Be careful to ensure that the alternate drive CNX partitions reference the disk device number of the alternate drives, not the drives used by the currently running operating system. For example:
A cluster comprised of two members has the following disk setup.
|dsk0a: contains the cluster_root file system|
|dsk0g: contains the cluster_var file system|
|dsk1g: contains the cluster_usr file system|
|dsk2a: contains the member1 root partition|
|dsk2h: contains the member1 CNX partition|
|dsk3a: contains the member2 root partition|
|dsk3h: contains the member2 CNX partition|
|dsk4h: contains the quorum disk partition|
Additionally, the cluster has five unused disks available to it (dsk10, dsk11, dsk12, dsk13, dsk14), which are as large as or larger than, the existing system disks.
The spare drives are used as a duplicate, or “clone,” of the existing operating system and they are mounted on a mount point called /clone” The steps are:
Partition dsk10a to be as large or larger than dsk0a
Partition dsk10g to be as large or larger than dsk0g
Partition dsk11g to be as large or larger than dsk1g
Partition dsk12a to be as large or larger than dsk2a
Partition dsk12h for the special size of a CNX partition
Partition dsk13a to be as large or larger than dsk3a
Partition dsk13h for the special size of a CNX partition
Partition dsk14h for the special size of a quorum disk
Build the CNX partitions for dsk12h, dsk13h, and dsk14h
Create AdvFS domains and file sets for all file systems (that is, alt_cluster_root, alt_cluster_usr, alt_cluster_var, alt_boot1, alt_boot2.)
Use common UNIX commands to exactly duplicate existing cluster and member file systems onto the alternate disks.
Mount all file systems in a hierarchical form on the mount point /clone.
When these steps are complete, the mount command will display output similar to the following:
cluster_root#root on / type advfs (rw)
root1_domain#root on /cluster/members/member1/boot_partition type advfs (rw)
cluster_usr#usr on /usr type advfs (rw)
cluster_var#var on /var type advfs (rw)
root2_domain#root on /cluster/members/member2/boot_partition type advfs (rw)
alt_cluster_root#root on /clone type advfs (rw)
alt_cluster_usr#usr on /clone/usr type advfs (rw)
alt_cluster_var#var on /clone/var type advfs (rw)
alt_boot1#root on /clone/cluster/members/member1/boot_partition
alt_boot2#root on /clone/cluster/members/member2/boot_partition
The first five file systems in this output represent the current operating system version; the last five represent an exact duplicate of the current operating system mounted on an alternate root path named /clone.”
The final step is to apply the latest patch kit to the alternate root using the dupclone command. This will install the new patch kit onto the alternate set of drives, which can then be booted. If for any reason the installation or the reboot fails, you can simply reboot on the original set of disk drives.
dupclone(8) Reference Page
This section reproduces the dupclone(8) reference page, which is installed on your system with the patch installation tools.
|dupclone – Clone Tru64 UNIX cluster|
| || |
|dupclone [–r rootpath] [–k kitpath] [–license]|
| || |
|–r rootpath|| |
Identifies the root directory of the cloned operating system.
|–k kitpath|| |
Identifies the path to the patch kit being installed.
Indicates that you accept the license agreement. A printed copy of the license agreement is included in the release notes that came with your patch kit.
The dupclone command installs a Tru64 UNIX patch kit located at kitpath into an alternate root directory defined by rootpath. The specified rootpath must be the root directory of a complete identical copy of the existing Tru64 UNIX operating system, including all members of the cluster.
The dupclone command can only be used on clusters. It is not supported for use on stand-alone systems.
The following example shows a typical cloning operation:
# dupclone -r /clone -k /usr/T64/patch_kit -license
You have accepted the license agreement.
Cluster Name: jungle
Member-1: apeman.zoo.com 10.0.0.1
Member-2: safari.zoo.com 10.0.0.2
Checking patch kit for transmission errors during download...
Verifying current software on member 1
Verifying current software on member 2
Creating master inventory of current system...
Getting list of patch subsets to install...
| || |
This file captures dupclone activities.