AutoSYNC Software User's Guide (Update 19)

One-time Synchronization
HP AutoSYNC User’s Guide—522580-020
3-18
Process Priority and Throttling
throughput. In most environments, the increase in CPU usage outweighs the savings in
data volume.
The use of compression can be set globally through the global parameter
[AUTO]SYNCCOMPRESS or, for a specific synchronization, through the COMPRESS
option.
Process Priority and Throttling
You may specify a process PRIORITY for a synchronization to ensure that
synchronization does not impact higher priority work. Specifying the PRIORITY might
be especially useful if you have enabled compression.
Another way to reduce the impact on other work is to specify a throttling RATE, which
limits AutoSYNC to being active for some percentage (1 percent to 100 percent) of the
elapsed time. AutoSYNC will pause for short periods to reduce its activity, with a
corresponding increase in the time required to complete the synchronization.
Recovery
While a replacement file is being transferred, AutoSYNC retains an existing destination
file by renaming it to a file named AAnnnnnn and placing it in a subvolume with the
MapDB name (normally ASYMAPDB) on the destination file set volume. Partitions,
alternate indexes and protection views are named ABnnnnnn, ACnnnnnn, and so on.
After the synchronization of a file is completed, the renamed recovery file, AAnnnnnn,
is purged unless a failure occurs. If the new file cannot be placed in the destination
location or a failure leaves the replacement file in a corrupt state, the saved version is
used to recover the file.
An archive index file named AAINDEX in the MapDB subvolume contains the mapping
of the original filename to the AAnnnnnn name.
This feature is controlled with the [AUTO]SYNCRECOVER global parameter. By
default, recovery is enabled. You can enable or disable recovery for a specific file set
or for a one-time synchronization by setting the RECOVERY attribute with ADD or
ALTER SYNCFILESET or specifying it as an option in the SYNCHRONIZE command.
Saved recovery files are purged when the replacement file has been transferred
successfully.
Recovery occurs immediately if the destination ASYSYNC process detects the failure
that would leave the file in a corrupt state. If, however, a cpu or media failure prevents
immediate recovery, any subsequent synchronization of the affected file sets will
perform the recovery.