BackPak H4.00 Catalog Sync Option

Disaster/Recovery Option Description
11 BackPak H4.00 Catalog Sync Option
- As all volumes are known by the two BackPak domains, the risk of creating
different volumes with the same label is limited to the elapsed time between
the creation on one side and the import of this volume on the other side.
Node name in DSM/TC catalogs
A NonStop node name is present in two areas of the DSM/TC catalog:
In TAPEVOLUME and TAPEFILE entries, there is a node name qualifying the
VOLCAT and FILECAT names
In DISKFILE entries, the name of backed up disk files is qualified by a node
name.
For TAPEVOLUME and TAPEFILE, the fully qualified catalog names are updated by the
regular BackPak import functionality. These VOLCAT/FILECAT names must identify
existing DSM/TC catalogs in the secondary site, accessible locally or via Expand by
the BackPak domain manager.
For DISKFILE, there are two cases:
Case-1: If the node names present in the disk file names are known by the secondary
system, there is no problem to use the original name of backed up files. In
MEDIACOM, the LOCALTOREMOTE parameter of the RECOVER DISKFILE
command might be required.
Case-2: If the node name present in the disk filenames are not known by the
secondary system, MEDIACOM rejects commands qualifying the disk file
name or pattern by these unknown nodes. For example:
MC>INFO DISKFILE \NODEP.$*.*.*
**ERROR-5048** DISKFILE \NODEP.$*.*.* is invalid.
This makes replicated DISKFILE entries useless, and might create
subsequent difficulties in DSM/TC processing.
BackPak provides two possibilities of bypass to this constraint:
1- The user can just prevent DISKFILEs from being replicated, at time of
export and/or at time of import job submission. Only TAPEVOLUME and
TAPEFILE will be replicated.
2- The user can configure BackPak to replace the original node names of
backed up disk files by other node names that are valid in the secondary
system.
Be sure to read this whole sub-section up to the IMPORTANT NOTE at
end.
This node name replacement is a way to automate what is described by
the HP note 100.0.3006075.2839037 present in the HP NonStop