HP NonStop G-Series - Manual (Page 39)

One-time Synchronization
HP AutoSYNC User’s Guide—522580-015
3-3
Data Transfer and File Writing
•
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.
System swap files are also temporary files and are not synchronized. You can
request such files to be synchronized by using the ZZINCLUDE option.
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.
•
A corrupt or broken destination file is always replaced, even if it is newer than the
source file.
•
Files that do not have the same modification times are synchronized if the
TIMEEXACT option is specified.
Data Transfer and File Writing
Once the list of files to be synchronized is complete, AutoSYNC transfers the files
using an efficient data-streaming protocol. Reading the source files, transferring the
data from the source to destination nodes, and writing the destination files is
parallelized and proceeds at maximum throughput.
Authorization
A one-time synchronization is invoked interactively. It uses only the user ID and access
rights of the user who issued the command. It requires appropriate remote passwords
to a remote destination system.
Ownership and Security
Source files to be synchronized must be secured for read access by the user ID. The
destination file is owned by the owner of the source file.
Ownership can be changed by using the OWNER option.
Default READ, WRITE, and EXECUTE Security
The security of the destination file is the same as the security of the source file, unless
the destination is on a remote system, in which case the security of the destination file
is changed to allow users on the source system the same level of access to the