AutoSYNC Software User's Guide (Update 17)

One-time Synchronization
HP AutoSYNC User’s Guide—522580-018
3-15
Files Opened for Update

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
and synchronizes the file only if the OPENUPDATE interval has elapsed since the
last update. If the file is being updated at the time AutoSYNC attempts to back up
the file set, the file is not synchronized.

In rare cases, a user might wish to synchronize a file, even if it is being modified
while AutoSYNC is backing up the file set. To enable the synchronization of a file
that is being updated, use the UNPROTECTED option, in conjunction with
OPENUPDATE.
UNPROTECTED is supported only for the following file types:

OSS files

Unstructured files that are not edit files

Entry-sequenced files
To specifying the OPENUPDATE option, the following conditions must be met:

The file must not be audited.

The file cannot be opened for exclusive access.

Recovery must be enabled for the fileset.
Changing File Ownership
By default, the ownership of each synchronized file is preserved. You may specify the
OWNER option to give the files to any user ID, including your own user ID.
Caution. The user should be aware that backing up a file that is being updated
could cause the destination file to be corrupted.