 |
Index for
Section 8 |
|
 |
Alphabetical
listing for C |
|
 |
Bottom of
page |
|
clu_bdmgr(8)
NAME
clu_bdmgr - Configures a replacement cluster member boot disk, or saves or
restores the h partition of an existing member boot disk
SYNOPSIS
Configure a member boot disk:
/usr/sbin/clu_bdmgr -c target_device-name memberid
Repair the h partition:
/usr/sbin/clu_bdmgr -h target_device-name [conf_file]
Write the contents of the h partition to the standard output:
/usr/sbin/clu_bdmgr -d device-name
For use by system software:
/usr/sbin/clu_bdmgr -b
/usr/sbin/clu_bdmgr -u
OPTIONS
-c Configures the disk specified by target_device-name as the boot
disk for the member specified by memberid.
This option checks that the disk is not already in use, and
creates the appropriate partitions and disk label for a boot
disk.
Note
Partitioning the disk causes all data on it to be lost.
After the successful completion of clu_bdmgr -c, you can use the
clu_bdmgr -h command to copy the CNX information to the newly
configured disk.
You can run the -c option on a single-member cluster to repair
another member's boot disk, as long as there is a path to the
disk.
-h Writes the appropriate CNX h partition information from the file
specified by conf_file. Typically, this is the member-specific
file /cluster/members/{memb}/boot_partition/etc/clu_bdmgr.conf.
If you do not specify a file in the command line, the information
is written directly from the h partition of the boot disk of the
cluster member where the clu_bdmgr command executes. The
destination is the h partition on the disk designated by
target_device-name. Use this option to repair a member's CNX
partition.
This option can be run a single-member cluster.
-d Writes the h partition information for device-name to the
standard output. The output is ASCII text. You can use this
option to save the h partition information of a functioning
member boot disk, or to examine the content of the h partition of
a corrupted disk.
-b This option is not for use by the administrator. It is
automatically called at boot time to save a copy of the booting
cluster member's h partition. The copy is saved in ASCII text
format in
/cluster/members/{memb}/boot_partition/etc/clu_bdmgr.conf. You
can use this file to restore the h partition on a corrupted
member boot disk or when creating a new member boot disk.
The -b option is valid only on a booting cluster member.
-u This option is not for use by the administrator. It is called by
utilities, such as rmvol and addvol, that store information in
the h partition. When volumes associated with the cluster_root
domain are changed, the information must be updated across all
cluster members.
The -u option is valid only on a running cluster member.
DESCRIPTION
The clu_bdmgr command configures a cluster member boot disk, creating the
needed boot, swap, and h partitions. The command can also save and restore
the h partition of a member boot disk. The clu_create command
automatically configured a member boot disk when it created the initial
cluster member, and the clu_add_member command automatically configures a
member boot disk when it adds a new cluster member. You use the clu_bdmgr
command to maintain these files.
The boot partition, rootmemberID_domain#root, holds the clusterized kernel,
some /etc files, and other information needed for the member to boot. The
h partition contains CNX information in binary format. The clu_bdmgr
command can write out the h partition information as ASCII text, or can
take this ASCII text output and write it in binary format to the h
partition of a member's boot disk.
If more than just the h partition of a member's boot disk needs repair or
replacement, then use clu_bdmgr in conjunction with a backup/restore
utility, which can back up and restore the content of the boot partition of
a member boot disk.
If a member's boot disk goes bad and no backups exist of the boot
partition, then clu_bdmgr cannot repair the disk. In this case, you have
to delete the member and add it again to the cluster. To avoid this
situation, make regular backups of member boot partitions,
rootmemberID_domain#root.
You can backup a member's boot partition as you would any file system. For
example, you can use the vdump command to backup the contents of boot
partitions. and vrestore to restore them.
Use the -c option to initially configure the boot disk partitions for a
member disk. This option causes all data on the disk to be lost. Apply it
only to a disk that is not currently in use.
If the memberid argument specifies a member that is currently configured in
the cluster, then you must manually edit the member's /etc/sysconfigtab
file. In the the vm stanza, swapdevice must specify the b partition of
target_device-name. In the clubase stanza, cluster_seqdisk_major and
cluster_seqdisk_minor must specify the major and minor numbers of the h
partition of target_device-name. Use the file command to get the major and
minor numbers of the h partition of target_device-name. For example, if
target_device-name is dsk8, the command file /dev/disk/dsk8h returns the
major and minor numbers of the h partition for dsk8.
If you run clu_bdmgr -c before making these changes to /etc/sysconfigtab,
the command displays instructions about the needed changes. See the
EXAMPLES section for details.
If memberid does not correspond to a current cluster member, then
target_device-name becomes the name of the boot disk for that member when
it joins the cluster.
The -c option configures the a, b, and h partitions as follows:
_________________________________________________________________
Partition Content
_________________________________________________________________
a AdvFS boot partition
b Swap partition (all space between partitions a and h)
h CNX binary partition (1 MB)
_________________________________________________________________
If the cluster is down, boot the clusterized kernel of one member to create
a single-member cluster. You can use the -h option and specify
/cluster/members/{memb}/boot_partition/etc/clu_bdmgr.conf or an appropriate
CNX configuration file that you previously saved with the clu_bdmgr -d
command. If you use the -h option with no argument, the command will get
the CNX partition information from the cluster member where you are logged
on.
EXAMPLES
1. The following example repairs member3's h partition with the content
of the h partition of the member where the command executes. In the
example, dsk9 is member3's boot disk.
# /usr/sbin/clu_bdmgr -h dsk9
2. The following example repairs member3's h partition with member3's
clu_bdmgr.conf file. The example assumes that member3 is down, but
that its member boot disk, dsk9, is accessible to the running cluster
members.
a. Get access to the backup configuration file,
/cluster/members/member3/boot_partition/etc/clu_bdmgr.conf, by
mounting member3's root domain on the running cluster member:
# mount root3_domain#root /mnt
b. Copy the information from the backup configuration file to the h
partition of member3's boot disk:
# /usr/sbin/clu_bdmgr -h dsk9 /mnt/etc/clu_bdmgr.conf
c. Unmount the root domain:
# umount /mnt
For an extended example of how to backup and recover a member boot disk,
see the chapter on troubleshooting in the TruCluster Server Cluster
Administration manual.
EXIT VALUES
The exit values for clu_bdmgr are:
0 The command succeeded.
1 An error occurred.
FILES
/usr/sbin/clu_bdmgr
Command path.
/cluster/members/{memb}/boot_partition/etc/clu_bdmgr.conf
An ASCII text file containing CNX information from the h
partition of a cluster member boot disk. This file is member
specific.
RELATED INFORMATION
TruCluster Server Cluster Administration
|
Index for
Section 8 |
|
|
Alphabetical
listing for C |
|
 |
Top of
page |
|