HP NonStop G-Series - Manual (Page 48)

One-time Synchronization
HP AutoSYNC User’s Guide—522580-015
3-12
Purging Extra Destination Files
from being purged if the corresponding source file does not exist and the PURGE
option is specified.
Purging Extra Destination Files
Specify the PURGE option to purge all destination files that do not exist in the source.
To create an exact duplicate of a source file set, this option is required to eliminate
extra files in the destination file set.
By default, the purge operation only applies to subvolumes that have files in the source
file set. Thus, if the synchronization is from $DATA.*.* to $BACKUP.*.*, a subvolume on
$BACKUP is not purged if no corresponding subvolume files exist on $DATA. To purge
extra subvolumes, specify the SUBVOLPURGE option in addition to the PURGE
option, as described in the paragraph
Purging Extra Subvolumes in the Destination File
Set below.
PURGE also applies to patterns such as $DATA.MYSUB*.SRV*. For each source
subvolume that has files that match the pattern, AutoSYNC purges extra destination
files that match the source file set pattern.
Excluded Files and Purge
EXCLUDE does not apply to the destination. Therefore AutoSYNC purges extra files
that do not exist on the source system, even if they have been listed in the exclude file
specified with the EXCLUDE option.
Purging Extra Subvolumes in the Destination File Set
To purge entire subvolumes that do not exist in the source file set, specify the
SUBVOLPURGE option in conjunction with the PURGE option.
All other synchronization options specified apply to the selection of files to purge in the
destination file set. For example, if the AUDIT option is specified, the audited files in
the extra destination subvolumes are purged.
Use the REPORT function to display the extra subvolumes that will be purged if
SUBVOLPURGE is used in the synchronization.
Replacing Open Destination Files
To replace destination files that are currently open with new versions, specify the
RENAMEOPEN option. Just before the destination file is created, an existing, but
open, file with the same name is renamed.
This option is often used for object files, especially when the object files are currently
executing at the destination. When a new object file is released and installed at the
Caution. Some performance degradation could occur if an exclude file containing a
long list of files is shared by multiple syncfilesets.