drd-clone.1m (2010 09)

d
drd-clone(1M) drd-clone(1M)
NAME
drd clone - clone the root volume group.
SYNOPSIS
drd clone
[-?][-p][-q][-v] -t
target_device_file [
-x option=value][-x -?
]
[
-X option_file ]
DESCRIPTION
The
drd clone command creates a copy of the LVM volume group or VxVM disk group containing the
root file system ("/"). In particular, it creates a new group, creates a volume in the new group for each
volume in the root group, configures swap and dump volumes, and copies the contents of each file system
in the root group to the corresponding file system in the new group.
The Source
The source of the
drd clone command - the group that is copied - is the group containing the root file
system ("/").
The source of the clone may reside on multiple disks, and may be mirrored. However, if a VxVM root
resides on multiple disks, each disk must contain the same list of volumes, that is, each disk must be a
mirror of every other disk.
When the
drd clone command is run, DRD records information about the original system image and
the newly created, inactive clone image. This information is used when other DRD commands, such as
drd mount and drd activate are run. DRD only manages two images, the original disk image and
the clone disk image. If the drd clone command is run again, any previously created clone is "forgot-
ten" and the currently booted image and the new clone are recorded for use by future commands.
When cloning a VxVM root, some patches to VxVM may be required. Please check the DRD web site,
http://www.hp.com/go/DRD
, to determine VxVM fixes that are needed, as well as any temporary
restriction on VxVM roots that can be cloned using DRD.
Choosing a target disk
The target disk must be specified as a block device file. An appropriate target disk should be writable by
the system, not currently in use by other applications and large enough to hold a copy of each logical
volume in the root group.
The physical disk need not be as large as the disk allocated for the root group as long as there is sufficient
space for a copy of each volume in the root group. However, the disk will need to be bigger than the used
space in each volume, since each volume will be created with the number of physical extents currently
allocated to the corresponding root volume.
The HP System Management Homepage, hpsmh(1M), or System Administration Manager, 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.
• 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, usu-
ally labeled with the identifier PV Name. Similarly, the command vxdisk -o alldgs list can
be used to display information about all disks managed by VxVM.
• The command
swapinfo can be used to display information about the disks that are currently used
for swap.
Depending on the applications in use on the system, further checks may be needed to ensure that disks
are not in use.
Note: A selected target disk will not be overwritten if it is part of the root volume. However the
drd
clone command will overwrite swap or raw data disks - it does not detect this type of usage. For exam-
ple, any "raw" disks in use by databases would be overwritten if given as the target clone disk.
CAUTION: 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.
HP-UX 11i Version 3: September 2010 − 1 − Hewlett-Packard Company 1