drd-clone.1m (2010 09)

d
drd-clone(1M) drd-clone(1M)
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, available at the
http://www.hp.com/go/drd-docs
web site.
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
vgnn, 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 begin-
ning 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.
Options
drd clone recognizes the following options:
-? Displays the usage message.
-p Sets preview mode.
-q Decreases the verbosity level by one each time it is specified. For example,
-qq will reduce the
verbosity from the default value of 4 to 2. If both
-x verbosity=5 and -qqq are included
on the command line, the effective verbosity is 2. The minimum verbosity level is 0. (See also the
-x verbosity option).
-v Increases the verbosity level by one each time it is specified. For example,
-v will increase the
effective verbosity from the default value of 4 to 5. If both
-x verbosity=1 and -vv are
included on the command line, the effective verbosity is 3. The maximum verbosity level is 5.
(See also the -x verbosity option).
-x -? Displays the list of possible -x (extended) options.
-x option=value
Sets the extended option to a value. See Extended -x Options definitions below.
-X option_file
Gets the extended options from a file.
-t device_special_file
Specifies the block device special file of a single physical disk on which the cloned system image
is to be written. The block device special file must exist on the system and be writable. All data
previously on the disk will be unavailable after a clone operation. (See the -x overwrite
extended option.)
Extended -x Options
drd clone recognizes the following -x (extended) options:
-x enforce_dsa=true
Usage: Advanced/Dangerous
Controls whether or not a failure in the disk space analysis (DSA) part of the analysis phase is fatal
2 Hewlett-Packard Company − 2 − HP-UX 11i Version 3: September 2010