HP Dynamic Root Disk (DRD) manual Files that have changed on the clone

Page 29

filtered_out_by_non_synced_location_filter_sync_phase file, which is refreshed each time drd sync is run, even if the command is run with the -p preview option.

2.Files that have changed on the clone

A file residing on the clone might have been changed by a drd runcmd operation, and it may have been updated on the booted system as well. This can occur even if the file is not listed in the Software Distributor Installed Products Database (that is, in the output of swlist –l file). For example, the installation of a product can add a new user to /etc/passwd.

In the case that a file has been updated on the booted system and updated on the clone by a mechanism other than a previous drd sync, drd sync does not copy the file. This avoids overwriting any changes made by installation (or removal) of software on the clone.

Because administrators might be interested in identifying changed files on the clone that will not be synchronized, the list of such files is written to the /var/opt/drd/ filtered_out_by_target_changed_filter_sync_phase file, even if the drd sync command is run with the -ppreview option. For any file listed in /var/opt/drd/ filtered_out_by_target_changed_filter_sync_phase, the administrator can use a command such as diff to compare the versions of the file on the booted disk and the clone. If the administrator determines that the file should be copied to the clone, the copy on the clone can be erased and the drd sync command executed again.

3.Nonvolatile files in the Software Distributor Installed Products Database (IPD)

Most files delivered in software packages should not be changed by a system administrator. To emphasize this fact, the files have the attribute is_volatile set to false. Any change to such a file results in an error if the swverify command is run (on the booted system if the file is changed there, or through drd runcmd if the file is changed on the clone.)

To keep files delivered by Software Distributor in accordance with the information recorded about them in the Software Distributor Installed Products Database (IPD), changes to nonvolatile files in the IPD are not propagated by drd sync. (Note that nonvolatile files are those displayed as output from the command /usr/sbin/swlist -l file -a is_volatile grep false).

The list of files on the booted system that are not propagated by drd sync because they are nonvolatile files in the Installed Products Database is written to /var/opt/drd/ filtered_out_by_nonvolatile_filter_sync_phase, even if the drd sync command is run with the -ppreview option.

4.Volatile files in the Software Distributor Installed Products Database. (IPD)

Files delivered by Software Distributor with the file attribute is_volatile set to true may be changed by the system administrator. In fact, in many cases, they must be changed by the system administrator. For example, the /etc/rc.config.d/netconf file must be customized for each system to include its network configuration. Typically, such a customization applies to both the booted system and the clone image. Thus, such changes are ordinarily propagated to the clone by the drd sync command.

However, if the clone has been updated to a new release of the operating system (or a release of a particular software package that changes the format of the file), propagation of the changes may be inappropriate. DRD uses the configuration template (delivered to a location containing a directory named newconfig) for the volatile file to determine if the changes should be propagated to the clone. If the templates are the same, the change is propagated, otherwise, they are not.

Volatile files that cannot be copied to the clone due to differing templates, are listed in the

/var/opt/drd/filtered_out_by_volatile_filter_sync_phase file, even if the drd sync command is run with the -p preview option.

After criteria 1 through 4 (above) are applied, the list of files to be copied to the inactive clone during a drd sync operation is written to /var/opt/drd/

5.3 The drd sync command 29

Page 28 Page 30
Image 29
Page 28 Page 30
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 Choosing a target disk Using other utilities to determine disk availabilityUsing DRD for limited disk availability checks 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 diskUpdating and maintaining software on the clone DRD-Safe commands and PackagesSwinstall Swremove Swlist Swmodify Swverify Swjob DRD-Safe patches and the drdunsafepatchlist file Kctune Update-ux View Kcmodule Kconfig Mkkernel Swm jobUpdating and managing patches with drd runcmd Special considerations for firmware patches Patches with special installation instructionsUpdating and managing products with drd runcmd 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 OverviewTrimming the list of files to be synchronized Drd sync commandDetermining the list of files in the booted volume group 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 examples Rehosting and unrehosting systemsRehosting overview 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 resourcesRelated information Typographic conventions New and changed information in this editionLocating this guide Find1 Page Drd activate command DRD commandsDRD command syntax 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
Top Page Image Contents