AutoSYNC Software User's Guide (Update 19)

Command Interpreter
HP AutoSYNC User’s Guide—522580-020
8-23
ADD SYNCFILESET
the security of destination files. If this option is omitted, the security of a
destination file is the same as that of the source file unless
NETWORKSECURE is on and the destination files are on a destination
system.
SQLREDEF
instructs AutoSYNC to synchronize SQL tables based on differences in the
redefinition timestamps, in addition to differences in modified timestamps. This
option allows AutoSYNC to be sensitive to certain DML changes performed on
SQL tables, such as ADD COLUMN, which do not cause the modification
timestamp to change.
By default, AutoSYNC compares only modification timestamps of source and
destination SQL tables.
SUBVOLPURGE
instructs AutoSYNC to process subvolumes in the destination file set even if
the subvolumes do not exist on the source file set.
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.
The REPORT function also lists the extra subvolumes if both PURGE and
SUBVOLPURGE are specified.
SUBVOLPURGE requires the PURGE option. If only PURGE is specified, the
extra subvolumes in the destination file set are not purged.
SYNCVIEWS | NO SYNCVIEWS
controls the synchronization of shorthand views. If enabled (the default), a
shorthand view is synchronized along with the table or tables it references,
regardless of whether it is in the syncfileset definition or not. This behavior is
similar to the way in which SQL/MP automatically moves protection views
when underlying tables are moved.
If disabled (NO SYNCVIEWS), a shorthand view is not automatically
synchronized with the tables it references. When the data in a SQL table
changes or when the SQL DDL changes and SQLREDEF is configured,
Autosync synchronizes the table but does not list any associated shorthand
view in the BACKUP input list, because the view did not change. On the
destination, the view is dropped when RESTORE drops and replaces the
referenced table, but the view is not recreated. The view is eventually replaced
at the next synchronization.
Note. A SQL view or index is synchronized automatically with the primary partition of
the base table. If the redefinition date of an index or view in the source subvolume is
newer than in the destination subvolume but the primary source partition is older than
the primary destination partition, the view or index is not synchronized.