AutoSYNC Software User's Guide (Update 16)

One-time Synchronization
HP AutoSYNC User’s Guide—522580-017
3-14
Replacing Open Destination Files
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.
Exceptions:
•
If the AUDIT option is specified and the destination file is audited, the rename
operation cannot succeed. AutoSYNC issues a warning message, the file is
skipped and the destination file is not replaced.
•
A synchronized file, table, index or view does not replace an existing object of a
different type.
Files Opened for Update
By default, AutoSYNC does not synchronize a file from the source file set if the file is
opened for update. Synchronizing such files could result in a loss of data integrity.
However, there are cases where this restriction can be overridden using the
OPENUPDATE option:
•
Some files are opened for update by application programs, but they are modified
infrequently. If such files cannot be audited, replicating them is a problem. In such
cases, the interval between updates provides a window where these files can be
synchronized without compromising their integrity. The user configures the interval
during which the file must remain unchanged before it can be synchronized. When
the synchronization process starts, it checks the last modified timestamp for the file