BackPak H4.00 Catalog Sync Option

Disaster/Recovery Option Description
9 BackPak H4.00 Catalog Sync Option
Unit of management
The scope of a replication is not a full BackBox VOLUME file, or a full DSM/TC
VOLCAT or FILECAT, but is the set of entries in these files related to a data store and
all its volumes. The Data Store is the main entity unit managed by Catalog Sync
operations. Incremental changes are transmitted volume per volume.
On the replication source side, the BackPak domain has PRIMARY access to the data
store.
On the target side, the receiving domain has SECONDARY access to the replicated
data store.
There is no more need to reserve dedicated BackPak domains for Catalog Sync. A
BackPak domain defines a tape processing environment where both primary and
secondary data stores can be included.
In sites where a BackPak domain was implemented for each NonStop node, these
same domains can operate both the regular “primary” activity of the node, and the
possible other “secondary” activity for other nodes in remote domains.
A primary Data Store can become secondary and vice-versa. It is the user
responsibility to maintain coherent roles between domains.
The corresponding Data Store and Volume Groups should ideally have the same
name in the two domains. But it is possible to use different names on the secondary
side. When they are different, the original primary name is entered in the secondary
side configuration. See the BackBox/BackLib User manual for the Volume group, and
the configuration of catalogue import page in this manual.
DSM/TC management
The unit of management of an export/import operation for DSM/TC is all entries
(TAPEVOLUME, TAPEFILE, DISKFILE) related to the volumes of a BackPak data store.
Entries not related to these BackPak volumes are not impacted by the replication.
DSM/TC System Search List (SSL)
In DSM/TC, the replication of volumes on the secondary NonStop systems will create
instances of the same volume labels, that violates the label unicity rule of DM/TC if
the two systems are present in an SSL on a system.
Primary and secondary systems must not belong to the same SSL that must be
verified/adjusted on each side by:
MEDIACOM INFO MEDIADEFS
MEDIACOM ALTER MEDIADEFS , SSL (…)
Number of DSM/TC catalogues on the secondary site
Although the same DSM/TC catalog can contain the result of backups executed
locally (primary data store), the result of BackPak Catalog Sync import (secondary