Dynamic Root Disk: Quick Start & Best Practices

6
succeeded. (user=root) (jobid=mesa)
On an LVM-based system:
• The clone that has been created is not visible (when executing commands such as bdf or
vgdisplay) at the completion of the clone operation. This is because the file systems on the clone
are unmounted and the clone volume group is exported at completion of the drd clone
command. See the information below regarding drd mount to view the clone.
• If the root group name is “vgnn”, the clone group is “drdnn”. If the root group does not have the
form “vgnn”, the clone group name is formed by prefixing the root group with “drd”.
• When the clone is booted, the root group is the same as the original root group that was cloned.
On a VxVM-based system:
• The cloned disk group will be displayed in the output of commands such as vxdisk, vxprint,
and vxstat. A VxVM clone is not deported by the drd clone command because a deported
group cannot be booted.
• If the root group is “rootdg”, the clone group is “drd_rootdg”. If the root group is “drd_rootdg”, the
clone group is “rootdg”. More generally, the clone group name is formed by prefixing the root
group name with “drd_”, or by removing the prefix.
• When the clone is booted the root group is the same as the clone group name when it was visible
on the original system. (Thus, the name of the root group changes when the clone is booted.)
If a system administrator wants to check the contents of particular files, the clone can be mounted by
executing the command:
# /opt/drd/bin/drd mount
and subsequently unmounted by executing the command:
# /opt/drd/bin/drd umount
See drd-runcmd(1M), drd-mount(1M), and drd-umount(1M) for options available on these
commands.
If a system administrator needs to verify the software contents of the clone, the following commands
can be executed:
# /opt/drd/bin/drd runcmd swlist
# /opt/drd/bin/drd runcmd swverify
When software is installed in a drd runcmd session, its configuration scripts are postponed until the
image is booted. As a result, the state attribute of a fileset is installed rather than configured. When
the clone is booted, the swlist command shows the states as configured.
If a system administrator wants to run both of these commands, but eliminate the overhead of
mounting and unmounting the clone for each command, the following sequence is preferable:
# /opt/drd/bin/drd mount
# /opt/drd/bin/drd runcmd swlist
# /opt/drd/bin/drd runcmd swverify
# /opt/drd/bin/drd umount