drd-sync.1m (2011 03)

d
drd-sync(1M) drd-sync(1M)
NAME
drd sync - propagate file system changes from the booted original system to the inactive clone image.
SYNOPSIS
drd sync [
-?][-p][-q][-v][-x option=
value][-x -?][
-X option_file ]
DESCRIPTION
The drd sync command propagates file system changes from the active system image that have been
modified or added since clone creation time.
The implementation of
drd sync only supports refresh of the inactive clone from the booted original
system.
A file or directory 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 are satisfied:
• The file on the booted original system has a modification time or size different than the same file
on the inactive clone, AND
- The file on the inactive clone has the same size and modification time as what drd last put on
the clone by either
drd clone or
drd sync, AND
- The file on the active system has a modification time greater than or equal to the modification
time of the file on the inactive clone. This includes the case that the file does not exist on the
inactive clone.
• The file does NOT reside in the non-synchronized locations:
/var/adm/sw/ /var/tmp/ /var/opt/drd/tmp/
/stand/ /tmp/ /etc/lvmconf/
/etc/vx/ /etc/vxvmconf/
Also the fully qualified name of the file or directory cannot contain this prefix:
/dev/<clone_group>
where clone_group is the name of the LVM group used to import the clone (usually
drd00). The
last non-synchronized location,
/dev/<clone_group>, does not apply to VxVM-managed roots.
• The file does NOT appear in the Installed Products Database (i.e. 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,
AND
- The volatile file was part of a product installed during clone creation time.
If the
/etc/fstab, /etc/lvmpvg, /etc/lvmtab,or/etc/lvmtab_p files are copied to the clone,
it is further modified to reflect clone device file and/or volume manager group.
A
newconfig template is the delivered template for a configuration file that is copied to create a "vola-
tile" 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.
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.
The
drd sync command uses the pax utility to copy files to the clone.
HP-UX 11i Version 3: Mar 2011 − 1 − Hewlett-Packard Company 1