BackPak H4.00 Catalog Sync Option

Disaster/Recovery Option Description
6 BackPak H4.00 Catalog Sync Option
Catalog Sync Option Description
Introduction
The BackPak Catalog Sync option replicates the catalogs of ETI-NET BackPak and HP
DSM/TC, from a primary NonStop system to a secondary system. The information
replicated is:
the BackPak catalog of the volumes it manages,
the DSM/TC catalog entries related to BackPak volumes: TAPEVOLUME, TAPEFILE
and optionally DISKFILE.
The replication of the data, the image of tape volumes written by the NonStop
backups, is independent from this replication of metadata. The replication of data
remains totally under the responsibility of the user, and depends on the storage
personality(ies):
BackBox: duplicate Windows file through LUN mirroring, BackBox scripts, or the
replication feature of high-end NAS such as StoreOnce and DataDomain
BackLib: use virtual library features to vault/replicate volumes, or manually vault
physical volumes, etc…
A third replication is required for encrypted volumes, the replication of the encryption
keys stored in a Key manager such as the HP ESKM. The user is responsible to
enable the replication offered by the Key manager, and configure in the secondary
BackPak domain a Key Manager with the same BackPak id and pointing to the
secondary key manager that contains the replicated keys.
Important notes:
• The volume labels must be unique in the Enterprise to freely copy
tape volume data and metadata from environment to environment.
First, the NonStop tape environment issues Mount requests where
only the volume label is specified, requiring unique volume labels per
NonStop node.
Second, a tape label must be unique in a BackPak domain.
Third, a tape label must be unique in the DSM/TC SSL (System
Search List). Primary and secondary systems linked by SSL are
incompatible with the duplication of volumes. See more in DSM/TC
management about labels and file ids.
• Even if restore tests using the replicated catalogs are successfully
executed during the setup, an additional check and verification must
be done once all setup activities have completed.
It is especially important to clearly distinguish how each DSMTC
catalogues is updated. A DSMTC catalogue updated by both locally
executed backups and by BackPak import processes is at risk: as
soon as a tape volume label or a tapefile fileid is not unique across
both environments, the DSMTC catalogue will be corrupted.