BackPak H4.00 Catalog Sync Option

Disaster/Recovery Option Description
7 BackPak H4.00 Catalog Sync Option
The catalog replication is implemented as two independent operations executed in
two distinct BackPak domains:
1. New catalog information is automatically exported from the primary site as soon
as possible after each backup execution, and written to a staging disk area in the
secondary site
2. The catalogs of the secondary site are updated from the staging area, by import
processes manually initiated through the UI Client, or scheduled in NetBatch.
Full catalog resynchronization can also be scheduled or initiated manually.
In the current BackPak version, the catalog information is transferred over Expand.
When Expand is not available up to the staging area of the secondary system, an
intermediate staging area is set in any NonStop node including the primary system,
but as much as possible in a different system. The user is then responsible to
transport the export files from this intermediate area to the secondary system. See
“Appendix A – transport without Expand” for a sample setup of backup / restore.
Catalog export and import are configured and operated through the regular BackPak
UI Client. Operations can also be triggered by TACL macros that can be included in
jobs scheduled in NetBatch.
When the BackPak domain license contains the Catalog Sync option, new pages and
new elements appear in the UI Client pages. The Catalog Sync specific elements are
described in this manual only.
Export and import can also be used to migrate parts of DSM/TC catalogs, from a
node to another, or to merge or split a BackPak domains data store by data store.
See also the ‘Data store detach’ function in the regular BackBox/BackLib manuals.