AutoSYNC Software User's Guide (Update 17)

Command Interpreter
HP AutoSYNC User’s Guide522580-018
8-104
SYNCHRONIZE
Purging of files occurs on a subvolume by subvolume basis. A destination
file is not purged if it does not exist in a corresponding source subvolume,
unless the SUBVOLPURGE option is also specified.
Extra SQL objects in the destination like tables, views and indexes are
purged. Catalog files are not supported and they are not synchronized or
purged by Autosync.
Extra SQL tables and views are purged explicitly, indexes and secondary
partitions are purged implicitly, with the main table.
OSS files and directories:
If PURGE is specified, subordinate directories not present in the source file
set are purged on the destination. Note that this is different than the
processing of Guardian subvolumes. Guardian subvolumes are not purged
unless SUBVOLPURGE is specified.
An entry is written into the log file for each file or OSS directory that is purged
as a result of the synchronization.
PURGE is not supported for SQL tables.
RATE percentage
the percentage of elapsed time the synchronization process should be active.
The default is 100%.
TIMEEX[ACT]
a file is synchronized if the modification timestamp of the source does not
exactly match the modification timestamp of the destination file.
By default, a file is synchronized only when the source file has been modified
after the destination file was last modified. The comparison of timestamps
accounts for differences in system clocks and time zones..
TRIGGER { tacl-command | oss-shell-command }
Note on symbolic links. Because source and destination modification
timestamps of symbolic links never match, TIMEEXACT is ignored if specified
for symbolic links. For further details on symbolic link synchronization, see
paragraph Modification Timestamp of Symbolic Links on page 5-4
Note on SQL Shorthand Views.
A SQL view has no modification timestamp.
Instead AutoSYNC uses creation timestamps. This prevents a shorthand view
from being synchronized every time the file set is synchronized.
However if TIMEEXACT is specified, the shorthand view will always be
synchronized because the creation time of the destination is always newer
than the creation time of the source. For further details on SQL View
synchronization, see paragraph SQL Views on page 3-8.