HP Dynamic Root Disk (DRD) Cloning the active system image, Active system image, Locating disks

Page 9

2 Cloning the active system image

This chapter describes how to use the drd clone command to clone the active system image. It also describes where the cloned image is saved.

NOTE: You must be logged in as root to use any DRD command.

2.1 The active system image

The drd clone command creates a bootable disk that is a copy of the volume group containing the root file system (/). The source of the drd clone command is the LVM volume group or VxVM disk group containing the root (/) and boot (/stand) file systems. For a system with an LVM root, the source does not need to reside on a single physical disk. For a system with a VxVM root, all volumes in the root disk group must reside on every physical disk in the root group. Thus, each disk must be a mirror of every other disk. The target must be a single physical disk large enough to hold all volumes in the root group. In addition, a mirror for the target may be specified. For more details, see the Dynamic Root Disk and MirrorDisk/UX white paper, available at http:// www.hp.com/go/drd-docs.

Because the drd clone operation clones a single group, systems with file systems to be patched must not reside in multiple volume groups. (For example, if /stand resides in vg00 and /var resides in vg01, the system is not appropriate for DRD.)

For additional information about source and target disks, see the drd-clone(1M) manpage (man drd-clone) and the Dynamic Root Disk: Quick Start & Best Practices white paper, available at http://www.hp.com/go/drd-docs.

NOTE:

After creating a DRD clone, your system has two system images—the original and the cloned image. Throughout this document, the system image that is currently in use is called the active system image. The image that is not in use is called the inactive system image.

2.2 Locating disks

The target of a drd clone operation must be a single disk or SAN LUN that is write-accessible to the system and not currently in use. Depending on your HP-UX operating system, refer to one of the following sections:

Locating Disks on HP-UX 11i v2

Locating Disks on HP-UX 11i v3

2.2.1Locating disks on HP-UX 11i v2 systems

To help find and select the target disk on an HP-UX 11i v2 system, you can find out what disks are on the system with the ioscan command:

# /usr/sbin/ioscan -fnkC disk

The ioscan command displays a list of system disks with identifying information, location, and size. On a PA-RISC system, the output looks similar to Example 2-1.

2.1 The active system image

9

Image 9
Contents Dynamic Root Disk A.3.10.* Administrators Guide Document Part Number DRD Version Supported Operating Systems Table of Contents DRD commands Troubleshooting DRD Support and other resourcesRehosting and unrehosting systems Glossary IndexList of Figures List of Examples About Dynamic Root Disk Commands overviewConceptual overview TerminologyDownloading and installing Dynamic Root Disk Active system image Cloning the active system imageLocating disks Locating disks on HP-UX 11i v2 systems# /usr/sbin/ioscan -fnkC disk Locating disks on HP-UX 11i v3 Integrity systems# /usr/sbin/ioscan -m dsf Using other utilities to determine disk availability Using DRD for limited disk availability checksChoosing a target disk Creating the clone Using drd clone to analyze disk sizeCloning the active system image Success Error Example 2-7 The drd clone command outputAdding or removing a disk Example 2-8 The drd clone command output for SAN diskDRD-Safe commands and Packages Swinstall Swremove Swlist Swmodify Swverify SwjobUpdating and maintaining software on the clone Kctune Update-ux View Kcmodule Kconfig Mkkernel Swm job Updating and managing patches with drd runcmdDRD-Safe patches and the drdunsafepatchlist file Patches with special installation instructions Updating and managing products with drd runcmdSpecial considerations for firmware patches Viewing logs Mounting the inactive system image Accessing the inactive system imagePerforming administrative tasks on the inactive system image Enter the patches into a file such as Unmounting the inactive system image Compare vxconfigbackup with the clone copyUnmounting the inactive system image Page Quick start-basic synchronization OverviewDrd sync command Determining the list of files in the booted volume groupTrimming the list of files to be synchronized Files that have changed on the clone Copying the files to the inactive clone image Drd sync system shutdown script Page Preparing the inactive system image to activate later Activating the inactive system image# /opt/drd/bin/drd activate Undoing activation of the inactive system image # /usr/bin/more /stand/bootconf l /dev/dsk/c2t0d0s2Activating the inactive system image Undoing activation of the inactive system image Page Rehosting and unrehosting systems Rehosting overviewRehosting examples Example 7-1 Provisioning a new system Rehosting a mirrored image# rm /var/opt/drd/registry/registry.xml Unrehosting overviewPage Troubleshooting DRD Page Contacting HP Support and other resourcesNew and changed information in this edition Locating this guideRelated information Typographic conventions Find1 Page DRD commands DRD command syntaxDrd activate command Ignoreunmountedfs=truefalse HAalternatebootdisk=blockdevicespecialfileLogfile=/var/opt/drd/drd.log Logverbosity=4Reboot=truefalse Drd clone commandVerbosity=3 Default Copyautofile optionCopyautofile=truefalseblockdevicespecialfile TtargetdevicefileEnforcedsa=truefalse Drd deactivate command Drd mount command Example A-1 File system mount points Drd rehost command Devicespecialfile -v-xextended option=value -x-?-Xoptionfile Extended options Drd runcmd command Extended options Drd status command Alternatebootdisk=blockdevicespecialfile Usr/sbin/swlist -l file, or Drd sync commandExcludelist= Drd umount commandAlternatebootdisk=blockdevicespecialfile Drd unrehost command Fsysteminformationfile Mirrordisk=blockdevicespecialfile Page Glossary Booted systemSystem image Index Idisk partition, 10, 11 inactive system file system