AutoSYNC Software User's Guide (Update 17)

One-time Synchronization
HP AutoSYNC User’s Guide522580-018
3-3
File Set Comparison
File Set Comparison
AutoSYNC creates a list of all file names in the source file set.
Some files are not eligible for synchronization; these files include:
Files that are opened exclusively. AutoSYNC cannot gain access to such files.
Files that are opened for update. Copying files that are being updated often results
in corrupt files. You can request such files to be synchronized by using the
OPENUPDATE option.
Broken or corrupt files.
Excluded files. Files that match a file name or pattern in the specified list of
excluded files are not synchronized.
Files in subvolumes $<vol>.ZYQ*.*: These subvolumes are excluded from
Guardian file sets because they contain OSS files.
SQL/MX tables. Because SQL/MX tables are always audited, audit trail-based
replication tools such as RDF are better suited to replicate SQL/MX objects.
Other files require special consideration when they are synchronized:
Audited files. It is assumed that audited files are databases and will be replicated
using TMF audit and the NonStop RDF product or another replication product. By
default, audited files are not synchronized. You can request such files to be
synchronized by using the AUDITED option.
Partitioned files and tables. AutoSYNC does not prevent synchronization of
partitioned files, but the PARTONLY option to synchronize a single partition is not
supported. To synchronize partitioned Enscribe files or SQL tables, use the
MAPNAMES option to specify the mapping of source partitions to destination
volumes.
ZZ files and system swap files. Files whose name begin with the letters ZZ are
usually temporary or abandoned work files that should be purged. By default, ZZ*
files are not synchronized. You can choose to synchronize these files by specifying
the ZZINCLUDE option.
Temporary files of the form $<vol>.#* are not synchronized.
The source file list that is created is compared to files in the destination file set. A
source file is synchronized if it was modified after the destination file was last modified.
Timestamp comparisons account for differences in time zones and system clocks. Files
that have the same modification timestamp are never synchronized.
Exceptions:
A destination file that is opened exclusively is never replaced.
A non audited destination file that is opened for read access or execute access
may be replaced if the RENAMEOPEN option is specified.