Dynamic Root Disk Frequently Asked Questions (766143-001, March 2014)

1-8. Q:
I have many disks I would like to clone in one operation. Is the target a single
disk?
A:
Yes, for this release of DRD, the target disk must be a single disk.
top
1-9. Q:
What if the DRD contains more than one disk? Does DRD handle this?
A:
Currently, the target disk must be a single physical disk, or SAN LUN, large enough to
hold all of the root volume file systems. This allows a customer to clone the root
volume group even if it is spread across multiple disks. Note that this is a one-way,
many-to-one operation.
top
1-10. Q:
Can DRD clone all the partitions; s1, s2, & s3?
A:
All partitions are created and s1 and s2 are copied. This release of DRD does not copy
the HP service partition.
top
1-11. Q:
Does DRD work with both LVM and VxVM root disks?
A:
Yes, the root group being cloned can be managed by any release of LVM on an OS
release supported by DRD. In addition, the root group can be managed by VxVM 4.1,
VxVM 5.0, VxVM 5.0.1, or VxVM 5.1 SP1. See the DRD Installation webpage for
information about the required patches if you are cloning a VxVM root.
If you are cloning a supported root, you can have non-root groups on the system
managed by any release of LVM or VxVM, including VxVM 5.0, 5.0.1, and 5.1SP1.
These groups are, of course, not cloned.
top
1-12. Q:
Does DRD support vPars?
A:
Follow this procedure for DRD usage with vPars and nPars
1. Clone each vPar on the system with the following command. Note that this does
not clone custom EFI contents. You must use EFI commands outside DRD if
custom EFI contents are to be copied to the clone. # drd clone -t
/dev/disk/disk5 -x overwrite=true
2. Activate each clone with the following command. This changes the vPars
bootpath that is stored in the vPar database. The bootpath for vpmon on the nPar
is not updated when a clone is activated from a running vPar. # drd activate
-x reboot=true