HP Integrity NonStop H-Series - Manual (Page 54)

One-time Synchronization
HP AutoSYNC User’s Guide—522580-021
3-14
Purging Extra Subvolumes in the Destination File
Set
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
The exclude list specified by the EXCLUDE option applies only to source files. It does
not apply to files in the destination that do not exist on the source. Therefore file in the
exclude list that do not exist on the source are considered for purging on the
destination (they are not excluded from purge).
To exclude files that exist only on the destination from being purged, specify the
EXCLUDEPURGE option with an excludepurge list.
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. To exclude specific
subvolumes from being purged, use the EXCLUDEPURGE 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
source, it is copied to the destination, but existing processes continue to use the
renamed object file.
Only files that are open for shared read access or execute access are renamed. Files
open exclusively or for write access are not renamed or replaced.
AutoSYNC deletes renamed files after they are closed.
The renamed files are named AAnnnnnn, where nnnnnn is a sequence number, and
are placed in same subvolume as the AutoSYNC MapDB, in the destination file set
volume. Renamed partitions, alternate indexes and protection views are named
ABnnnnnn, ACnnnnnn, and so on.