AutoSYNC Software User's Guide (Update 18)

One-time Synchronization
HP AutoSYNC User’s Guide—522580-019
3-12
Synchronization Options
Catalog mapping
The information supplied by MAPNAMES is also used to perform SQL catalog volume
mapping. You should include mapnames-file entries if catalogs are located on different
volumes or subvolumes on the destination system.
Note that SQL catalogs are never synchronized by AutoSYNC, but synchronized SQL
objects have references to SQL catalogs that might require name mapping.
AutoSYNC default catalog mapping is designed to select a valid volume where a
catalog can be created with AUTOCREATECATALOG and CATALOG options. If you
have a more specific requirement, specify explicit catalogs for the SQL objects being
synchronized by adding catalog mapping entries in mapnames-file. The catalog
mapping entries follow file mapping entries, and are preceded by the keyword
“CATALOGS:”, including the colon (:), as follows:
CATALOGS entries are checked for proper syntax, and passed along to the RESTORE
process.
To find out the file name and catalog mapping being supplied to RESTORE, specify
KEEPBACKUPINFILE and examine the ZRSnnnnn file in the destination MapDB
subvolume.
Synchronization Options
Numerous options provide flexibility for synchronization. Most of options apply to both
one-time and scheduled synchronizations.
Making Exact Copies
Excluding ZZ Files
Excluding Specific Files
Purging Extra Destination Files
Purging Extra Subvolumes in the Destination File Set
Replacing Open Destination Files
Changing File Ownership
Synchronizing Based on Ownership
Synchronizing based on REDEFINITION timestamp
Synchronizing based on Binder or Linker timestamp
$DATA TO $BACK
\NEWYORK.$DATA*.DB TO $BACK.BACKUPDB
$DATA*.DB.PARTFILE TO \TOKYO.*
CATALOGS:
$CATS.BACKCAT FOR $BACK.*.*
$CATS.DBCAT FOR $BACK.BACKUPDB.*
\TOKYO.$CATS.DBCAT for \TOKYO.*.*.*