HP Dynamic Root Disk (DRD) manual Overview, Quick start-basic synchronization

Page 27

5 Synchronizing the inactive clone image with the booted system

5.1 Overview

The drd sync command is introduced in release B.11.xx.A.3.5 of Dynamic Root Disk (DRD) to propagate root volume group file system changes from the booted original system to the inactive clone image.

Example 5-1 drd sync scenario

Here is a sample scenario that can be improved by using the drd sync command:

1.A system administrator creates a DRD clone on a Thursday.

2.The administrator applies a collection of software changes to the clone on Friday using the drd runcmd command.

3.On Friday, several log files are updated on the booted system.

4.On Saturday, the clone is booted.

Prior to DRD release B.11.xx.A.3.5, the system administrator needed to take manual actions to ensure that changes made to log files on the booted system (on Friday) were copied to the clone before or after it was booted. This was particularly important for logs that were audited for security purposes.

With the introduction of the drd sync command, the administrator can run drd sync before booting the clone (preferably as part of a shutdown script) to ensure that changes made to the booted system are propagated to the clone.

The drd sync command does not propagate changes to software installed on the clone. In most cases, software installed on the clone is intentionally different from software installed on the booted system. For example, patches might have been applied to the clone, new revisions of software products installed, or an entire new release of HP-UX installed using drd runcmd. More information on how drd sync handles software changes is provided in “The drd sync command” (page 28).

IMPORTANT: HP recommends that drd sync not be used for clones that have diverged greatly from the booted system over a period of time. In some cases, it is more appropriate to re-create the clone and apply the software changes, or install newer software changes. For ways to determine how much a clone differs from the original booted system, see “Using the drd sync preview to determine divergence of the clone from the booted system” (page 30).

5.2 Quick start—basic synchronization

To propagate the maximum number of file changes from the booted system to the inactive clone image, you need to create a shutdown script on the booted system that does the following:

Mount the clone:

#/opt/drd/bin/drd mount

Execute the drd sync command:

#/opt/drd/bin/drd sync

Remove the copy of the script on the clone:

#/usr/bin/rm /var/opt/drd/mnts/sysimage_001/<rc_location>

Unmount the clone:

#/opt/drd/bin/drd umount

5.1 Overview 27

Image 27
Contents Dynamic Root Disk A.3.10.* Administrators Guide Document Part Number DRD Version Supported Operating Systems Table of Contents Glossary Index Troubleshooting DRD Support and other resourcesDRD commands Rehosting and unrehosting systemsList of Figures List of Examples Terminology Commands overviewAbout Dynamic Root Disk Conceptual overviewDownloading and installing Dynamic Root Disk Locating disks on HP-UX 11i v2 systems Cloning the active system imageActive system image Locating disks# /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 Logverbosity=4 HAalternatebootdisk=blockdevicespecialfileIgnoreunmountedfs=truefalse Logfile=/var/opt/drd/drd.logCopyautofile option Drd clone commandReboot=truefalse Verbosity=3 DefaultCopyautofile=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