HP Dynamic Root Disk (DRD) manual Drd sync command, Usr/sbin/swlist -l file, or

Page 64

A.1.8 The drd sync command

The drd-sync(1M) command propagates file system changes—whose modification time is newer than the clone creation time—from the booted original system to the inactive clone image.

NOTE: The initial implementation of drd sync only supports refresh of the inactive clone from the booted original system.

A file in the root LVM volume group or VxVM disk group on the booted original system is copied to the inactive clone if all of the following criteria is satisfied:

The file does NOT reside in the following non-synchronized locations:

/stand/*

/tmp/*

/var/adm/sw/*

/var/opt/drd/tmp/*

/var/tmp/*

/etc/lvmconf*

/etc/vx/*

/etc/vxvmconf/*

/dev/<clone_group>/* (Where clone_group is the name of the LVM group used to import the clone (usually drd00.) This non-synchronized location does not apply to VxVM-managed roots.)

The file does NOT appear in the Installed Products Database (that is, the output of

/usr/sbin/swlist -l file), OR:

The file appears in the Installed Products Database with the attribute is_volatile set to true, AND:

The newconfig templates for the file on the original system and the clone are the same.

A newconfig template is the delivered template for a configuration file that is copied to create a “volatile” file when some Software Distributor packages are installed.

If the path to the volatile file is path, the path to the newconfig template is generally

/usr/newconfig/<path>, or <product_dir>/newconfig/<path>, where product_dir is the value of the “directory” product attribute of the product delivering the volatile file.

If the newconfig templates do not match, or the location of the newconfig template cannot be determined, the file is not copied.

The files contained in the SW-DIST Installed Products Database are not copied to the clone because these files are intended to be managed by SW-DIST commands. Similarly, the contents of /var/ adm/sw, which contains the Installed Products Database and logs associated with SW-DIST commands executed on the booted system, are not copied.

See drd-runcmd(1M) for information about using drd runcmd swinstall to install software to the clone.

Files containing blocks of binary zeroes that are copied by drd sync are converted to sparse files on the clone.

The drd runcmd command returns the following error codes:

0Success

1 Error

2 Warning

The drd sync command syntax is:

drd sync [-?] [-p] [-q] [-v] [-x extended option=value] [-x -?] [-X option_file]

64 DRD commands

Image 64
Contents Dynamic Root Disk A.3.10.* Administrators Guide Document Part Number DRD Version Supported Operating Systems Table of Contents Troubleshooting DRD Support and other resources DRD commandsRehosting and unrehosting systems Glossary IndexList of Figures List of Examples Commands overview About Dynamic Root DiskConceptual overview TerminologyDownloading and installing Dynamic Root Disk Cloning the active system image Active system imageLocating disks Locating disks on HP-UX 11i v2 systemsLocating disks on HP-UX 11i v3 Integrity systems # /usr/sbin/ioscan -fnkC disk# /usr/sbin/ioscan -m dsf Using DRD for limited disk availability checks Using other utilities to determine disk availabilityChoosing a target disk Using drd clone to analyze disk size Creating the cloneCloning the active system image Example 2-7 The drd clone command output Success ErrorExample 2-8 The drd clone command output for SAN disk Adding or removing a diskSwinstall Swremove Swlist Swmodify Swverify Swjob DRD-Safe commands and PackagesUpdating and maintaining software on the clone Updating and managing patches with drd runcmd Kctune Update-ux View Kcmodule Kconfig Mkkernel Swm jobDRD-Safe patches and the drdunsafepatchlist file Updating and managing products with drd runcmd Patches with special installation instructionsSpecial considerations for firmware patches Viewing logs Accessing the inactive system image Mounting the inactive system imagePerforming administrative tasks on the inactive system image Enter the patches into a file such as Compare vxconfigbackup with the clone copy Unmounting the inactive system imageUnmounting the inactive system image Page Overview Quick start-basic synchronizationDetermining the list of files in the booted volume group Drd sync commandTrimming 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 Activating the inactive system image Preparing the inactive system image to activate later# /opt/drd/bin/drd activate # /usr/bin/more /stand/bootconf l /dev/dsk/c2t0d0s2 Undoing activation of the inactive system imageActivating the inactive system image Undoing activation of the inactive system image Page Rehosting overview Rehosting and unrehosting systemsRehosting examples Rehosting a mirrored image Example 7-1 Provisioning a new systemUnrehosting overview # rm /var/opt/drd/registry/registry.xmlPage Troubleshooting DRD Page Support and other resources Contacting HPLocating this guide New and changed information in this editionRelated information Typographic conventions Find1 Page DRD command syntax DRD commandsDrd activate command HAalternatebootdisk=blockdevicespecialfile Ignoreunmountedfs=truefalseLogfile=/var/opt/drd/drd.log Logverbosity=4Drd clone command Reboot=truefalseVerbosity=3 Default Copyautofile optionTtargetdevicefile Copyautofile=truefalseblockdevicespecialfileEnforcedsa=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 Drd sync command Usr/sbin/swlist -l file, orDrd umount command Excludelist=Alternatebootdisk=blockdevicespecialfile Drd unrehost command Fsysteminformationfile Mirrordisk=blockdevicespecialfile Page Booted system GlossarySystem image Index Idisk partition, 10, 11 inactive system file system