HP Dynamic Root Disk (DRD) manual Example 2-7 The drd clone command output, Success Error

Example 2-7 The drd clone command output

======= 12/01/06 11:07:28 MST BEGIN Clone System Image (user=root) (jobid=drdtest2)

*Reading Current System Information

*Selecting System Image To Clone

*Selecting Target Disk

*Selecting Volume Manager For New System Image

*Analyzing For System Image Cloning

*Creating New File Systems

*Copying File Systems To New System Image

*Making New System Image Bootable

*Unmounting New System Image Clone

*System image: "sysimage_001" on disk "/dev/dsk/c1t2d0"

======= 12/01/06 11:38:19 MST END Clone System Image succeeded. (user=root) (jobid=drdtest2)

Figure 2-3shows the two disks after cloning. Both disks contain the system image. The image on the target disk is the inactive system image.

The DRD clone operation will have some impact on the booted system's I/O resources, particularly if the source disk is on the same SCSI chain as the target disk. DRD's performance is similar to system performance when using Ignite to create recovery images, which many system administrators find acceptable.

Figure 2-3 Disk Configurations After Cloning

After running drd clone, you have identical system images on the system disk and the target disk. The image on the system disk is the active system image. The image on the target disk is the inactive system image.

The drd clone command returns the following values:

0Success

1Error

2Warning

For more details, you can examine messages written to the log file at /var/opt/drd/drd.log.

Here is an example of creating a clone from a HP-UX 11i v3 system to a storage area network (SAN) disk. First, Example 2-8displays the output of the following drd clone command:

# /opt/drd/bin/drd clone -t /dev/disk/disk14 -x overwrite=true

2.7 Creating the clone 15