HP-UX Reference (11i v2 07/12) - 1M System Administration Commands A-M (vol 3)

d
drd-clone(1M) drd-clone(1M)
The HP System Management Homepage (see hpsmh(1M)) or System Administration Manager (see
sam(1M)) can be used to investigate the disks on the system and their current usage.
Alternatively, the following command-line utilities may be useful in determining an appropriate target disk:
• The command
ioscan -fknC disk can be used to determine the physical disks on the system.
See ioscan(1M).
• Commands from various volume managers and applications can be used to determine the current
usage of disks on the system. For example,
vgdisplay -v displays the disks currently in use by
the LVM volume manager, usually labeled with the identifier
PV Name. See vgdisplay(1M). Simi-
larly, the command
vxdisk -o alldgs list
can be used to display information about all disks
managed by VxVM. See vxdisk(1M).
• The command
swapinfo can be used to display information about the disks that are currently used
for swap. See swapinfo(1M).
Depending on the applications in use on the system, further checks may be needed to ensure that disks are
not in use. For example, any "raw" disks in use by databases may need to be identified.
Note: It is the administrator’s responsibility to determine which disks are not currently in use and may
therefore be used for a clone of the root group.
The drd clone command itself will perform the following checks:
• If the disk is currently in use by the LVM volume manager, it will be rejected by
drd clone.
• If the disk is currently in use by the VxVM volume manager, it will only be accepted as a
drd clone
target if the disk is an inactive image managed by DRD and the extended option -x
overwrite=true
is specified.
• If the disk is not currently in use by LVM or VxVM, but contains LVM, VxVM, or boot records, it will
only be accepted as a
drd clone target if -x overwrite=true
is specified.
For further information on choosing a target disk for a clone operation, see the Dynamic Root Disk
Administrator’s Guide (see the SEE ALSO section).
The Target Volume Manager
The target volume manager must be the same as the source volume manager.
• If the source group is an LVM volume group of the form
vg
nn, the clone is imported with the volume
group name
drdnn and booted with the original volume name vgnn. For example, if
vg00 is
cloned, the clone is imported as
drd00 and booted as vg00.
• If the source group is an LVM volume group not of the form
vgnn, the clone is imported with a
volume group name formed by prefixing the source group with
drd_.
• If the source group is a VxVM volume group not beginning with drd_
, the clone is imported and
booted with a volume group name formed by prefixing the source group with
drd_
.
• If the source group is a VxVM volume group beginning with
drd_
, the clone is imported and booted
with a volume group name formed by removing the prefix
drd_.
The DRD Log
The DRD log resides at
/var/opt/drd/drd.log. During any DRD operation, the DRD log is written
to the booted system. In addition, since the log is part of the /var file system, it is copied by the drd
clone
command to the target of the drd clone operation. Since the file systems on the clone are
unmounted before the log has been completely written, the DRD log file on the target of a drd clone
operation will be truncated. The messages following the truncated clone log will be those from the first
drd operation run on the clone after it is booted.
RETURN VALUE
drd clone returns one of the following values:
0 Success.
1 Error.
2 Warning.
HP-UX 11i Version 2: December 2007 Update − 3 − Hewlett-Packard Company 203