BackPak H4.00 Catalog Sync Option HP Part Number: 748420-002 Published: March 2014 Edition: G06.24, H06.06 or J06.
Legal Notice © Copyright 2013 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor’s standard commercial license. The information contained herein is subject to change without notice.
Preface Table of Contents Preface ........................................................................................5 RELATED DOCUMENTATION ..................................................................................... 5 Catalog Sync Option Description .................................................6 INTRODUCTION ................................................................................................... 6 HIGH-LEVEL OPERATIONS ........................................................
Preface Import execution traces ...............................................................................37 Sample EMS Messages ........................................................................................................................................... 38 Sample import report .............................................................................................................................................. 38 Configuration changes..............................................
Preface Preface This manual documents the configuration and operation of the BackPak Catalog Sync option, available for both BackBox (Virtual tape) and BackLib (Library management). The Catalog Sync Option of BackPak contributes to a whole D/R by replicating the tape catalogues. The supported catalogues are the BackPak catalogue and the DSM/TC catalogue.
Disaster/Recovery Option Description 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.
Disaster/Recovery Option Description 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.
Disaster/Recovery Option Description High-level operations For all BackPak personalities, the catalog replication operates the same way. The replication over Expand is executed in two steps: 1. In the primary system, as soon as a tape volume written by a tape application is unloaded, the related new catalog information is sent by automatic Export processes to a staging area on the remote secondary system. Other important events, such as the creation of tape volumes, initiate also Export processes. 2.
Disaster/Recovery Option Description 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.
Disaster/Recovery Option Description data store), and non-BackPak volumes, it is suggested to create a distinct DSM/TC catalog to receive the entries created by BackPak Catalog Sync import for each primary source. The main reason for this isolation is that FILEID naming convention generally does not ensure the uniqueness of a FILEID across an enterprise; the collision between FILEID created by DSM/TC for local backups and FILEID created by BackPak will corrupt the DSM/TC catalogue.
Disaster/Recovery Option Description - 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.
Disaster/Recovery Option Description Knowledge Base “DSM/TC: How to adjust a FILECAT containing CATALOGFILES for a missing system”. A list of node names pairs (old value, new value) must be entered in the configuration of catalog import at data store level. In all catalog import processes for this data store, the node part of disk file name will be adjusted in the inserted DISKFILE entries.
Disaster/Recovery Option Description Types of data store processing A BackPak domain processes the tape volumes of a data store depending on the “Domain access” configured for the data store. Figure 2.
Disaster/Recovery Option Description Figure 3.
Disaster/Recovery Option Description Full or Update export/import Full Export extracts the catalog information about all the volumes of a BackPak primary data store. Full Import replaces the catalog information already known about the volumes of a BackPak secondary data store, by the content of the staging area. Export Update extracts the new catalog information that was not successfully written to the staging area.
Disaster/Recovery Option Description At the implementation of the replication, by using the GUI, On a regular basis to ensure the synchronization of the two sites and remove the volumes that were deleted on the primary site after being replicated, by scheduling TACL macros in NetBatch.
Disaster/Recovery Option Description Considerations for encrypted volumes If the volumes were written with encryption, the encryption key is needed to restore on the secondary side. BackBox encryption keys are always stored in a tier-party Key manager such as HP ESKM or KMIP compatible Key manager.
Initial setup Initial Setup and Configuration Setup Prepare BackPak for DSM/TC Catalog Sync In the domains on both sides, primary and secondary, the BackPak package version 3.10 and up must have been installed with the preparation of BBDBM for Catalog Sync option if DSM/TC catalogs must be replicated. BBDBM is the program reading and writing the DSM/TC catalogues.
Initial setup Manual preparation of BBDBM. To prepare BBDBM manually, start a TACL session running with SUPER.SUPER, and enter: >VOLUME >SQLCOMP /IN BBDBM / CATALOG target-sql-catalog >FUP LICENSE BBDBM Reserve a disk subvol per secondary data store On the secondary NonStop node, a disk sub-volume must be reserved for the metadata staging area, one sub-volume per secondary data store.
Initial setup Configure the primary Data store When the Catalog Sync option is set in the license key, the list of data stores shows a link to “Catalog Sync Export” that is a third data store configuration page, in addition to the main page and the “Advanced Properties” page. Figure 5. Data store configuration - Menu page In the main data store attributes, click the Switch to Edit mode link, click the Catalog Sync Export link for a PRIMARY Data Store. Catalog Sync Export configuration page Figure 6.
Initial setup Export Report Location: location of the export process log. A spooler location is suggested to hold more than the latest execution log. Export Destination: identifies the staging area, a remote subvol where export files will be written. The presence of an Export Destination is the trigger to execute exports. Process Priority: priority of the started Export process.
Initial setup Configure the secondary Data store The data store and its volume groups must be configured in the secondary site, in the usual Data store and Volume group configuration pages. Note that for the secondary Volume groups associated to DSM/TC, not only VOLCAT and POOL, but also FILECAT must be entered. The id of data store and volume groups corresponding between primary and secondary sides should ideally be the same.
Initial setup Data store main configuration page The Data Store must be created with SECONDARY as Domain Access. Figure 8. Data store - Main configuration page Page elements to consider for a secondary Volume Group Domain Access To Data Store: Must be SECONDARY. Primary Data Store ID: Must be entered if the Data Store ID is different on the primary side. 23 BackPak H4.
Initial setup Catalog Sync Import configuration page Click the Catalog Sync Import link. Figure 9. Data store configuration - Catalog import page Page elements Import source: staging area receiving export files. Import Report Location: location of the import process log. A spooler location is suggested to hold more than the latest execution log. Process Priority: priority of the started Export process.
Initial setup (Check box) Allow to store replicated DSM/TC entries in local DSM/TC catalogue that is not dedicated to the replication (i.e. merged with other replications or local backups) system: This check box disables a validation at import time. At import time, it is verified that the target DSM/TC catalogue is different from the DSM/TC catalogue used for registering the backups executed locally.
Initial setup Volume Group configuration This section refers only to specifics of secondary Volume groups; see the regular BackBox User Manual or BackLib User Manual for a common description of the configuration of a Volume Group. Page elements to consider for a secondary Volume Group Primary Volume Group ID: This is element is available only for SECONDARY or RESTRICTED Data Stores.
Initial setup Volcat : Obviously, the DSM/TC VOLCAT and FILECAT catalogues cannot be duplicated on themselves; therefore their names qualified by the node name must be different in the secondary data store. But when primary and secondary systems are not linked by Expand and both systems share the same node name, the qualified catalog names can be identical, a check box must be un-check in the Catalog Sync Import configuration page to allow the same name. Pool: Their name can be equal as well as different.
Initial setup Schedule batch on the secondary side No import is internally initiated by the BackPak. Any systematic import must be scheduled in NetBatch jobs running the BB027_IMPORT_CATALOG macro. Reasons to run periodically an import, the actual update of the secondary catalogs: Verify the whole replication is running correctly Maintain the secondary catalogs as close as possible of the primary catalogs on side to minimize the work to switch the production on secondary site.
Export operations Export operations Graphical User Interface Storage Admin page When the license key is set for Catalog Sync option, a new column appears in the list of Data stores presented in the Storage Admin tab, “Catalog Sync Import/Export” that presents a link to an “Export Status” page. Figure 10. Storage Admin – Menu page Export Status page Figure 11.
Export operations Latest Export process: identifies the latest export process submitted. Page buttons Export Full Catalog button: initiates a full export. Export Catalog Updates button: initiates an export for pending volumes. There is normally no need to initiate manually Export Updates or their retries. Refresh button: gets the latest status. Most recent volume exported When there is no pending export during regular tape operations, this shows the most recent volume loaded for a backup.
Export operations Start time: Starting time of the export process. Report: Location of the export log. Number of exported volumes: Number of volumes whose catalog information was extracted. Export written to: Staging area where export files were written. Export Confirmation page Figure 12. Storage Admin – Export confirmation page Page elements Include DSM/TC disk file entries: check to send the content of backups to the remote staging area.
Export operations Confirm button: starts the Export process. Cancel button: returns to the Export status. Export execution traces For each export process are issued: A starting process EMS message, if EMS Verbose is set in the domain configuration Possible EMS error messages An ending process EMS message, if EMS Verbose is set in the domain configuration A log report in the location set in the export configuration Sample EMS Messages 2013-09-19 12:40:31 \ETINIUM.$X0Z9 ETINET.100.
Export operations ETINIUM_TMF NO-CATALOGUE TMF catalog: \ETINIUM TMF211 unloaded on 2013-09-05 01:52:10 12 0 no tape catalog BCC78 updated on 2013-09-18 00:25:26 44 0 BPAK-I3279 \ETINIUM.$X0ZA exported FULL catalogs for data store WIN1 (80 volumes processed). Report in $S.#BPAK.EXPORT BPAK-BB051 Process \ETINIUM.$X0ZA ended on 33 2013-09-19 12:41 BackPak H4.
Import operations Import operations Graphical User Interface Storage Admin page When the license key is set for Catalog Sync option, a new column appears in the list of Data stores presented in the Storage Admin tab, “Catalog Sync Import/Export” that presents a link to an “Import Status” page. Figure 14. Storage Admin – Menu page Import Status page Figure 15.
Import operations Available Catalog Information to Import: reports about the export files in the staging area. Latest Completed Full Import: identifies the latest Full import that completed without fatal error. Latest Import: identifies the latest import process submitted. Page buttons Check against primary configuration button: compares the configuration of volume groups in the primary and secondary data stores. Import Full catalog button: initiates an import from the whole staging area.
Import operations Latest import Staging sub-volume: sub-volume where export files were read. Export Id: timestamp that was assigned at export time. Process Name: Guardian name of the import process. Import type: FULL | UPDATE. Process status: RUNNING | FINISHED. Import Start time: Starting time of the import process. Import Report: Location of the import log. Number of processed volumes: Number information was applied to the catalogs.
Import operations Import Confirmation page Figure 17. Storage admin – Catalog import confirmation page Page elements Include DSM/TC disk file entries: check to insert the missing DSM/TC DISKFILEs. Confirm button: starts the Import process. Cancel button: returns to the Import status. Import execution traces For each import process are issued: A starting process EMS message, if EMS Verbose is set in the domain configuration 37 BackPak H4.
Import operations Possible EMS error messages An ending process EMS message, if EMS Verbose is set in the domain configuration A log report in the location set in the import configuration Sample EMS Messages 2013-09-19 15:43:56 \MONT.$Y9G5 ETINET.100.100 3286 BPAK2-I3286 Process \MONT.$Y9G6 started for IMPORTING the entire catalogs of data store WIN1. Output report sent to $S.#BPAK2.IMPORT. 2013-09-19 15:44:15 \MONT.$Y9G6 ETINET.100.100 3342 BPAK2-I3342 \MONT.
Import operations BBC007 ETINIUM_BACKUPS ... / ... BCC80 NOCAT LSH001 NOCAT LSH002 NOCAT SCRATCH Deletion of unreferenced volumes IMPORT RESULT SUMMARY: Numbers of tape volumes Volume group ====== Import source ======= <===BackPak catalog===> Added Updated Deleted ===== ======= ======= <===NSK tape catalog==> Added Updated Deleted ===== ======= ======= ETINIUM_BACKUPS DSM/TC volcat \MONT.
Configuration changes Configuration changes Procedures below that should be considered as startup samples; the actual procedures vary largely depending on the exact Catalog Sync setup and context. Careful planning is always required because of the potential impact.
Configuration changes o Delete the volumes of the primary data store, by using the BackPak GUI “Volume”. This will delete these three items: Actual backup data in the storage Entries in the DSM/TC or TMF catalogues Entries in the primary BackPak catalogue o Remove the Volume groups and Data Store from the configuration, by using the BackPak GUI “Configuration”.
Configuration changes In this page, the ‘Most recently written volume exported’ label and unload time should help in steps 3- and 4- below. Fix conditions preventing the export updates to complete. If the EMS Extractor is stopped, automatic Export executions and retries will not execute; it is possible to initiate manually a final Export update from this page.
Configuration changes 11- Execute a test backup on system /B and verify the restore from replicated data and metadata in system \A. 43 BackPak H4.
Appendix A – transport without Expand Appendix A – transport without Expand If Expand is not available between the primary and the secondary sites to quickly move the export files, the user must implement an additional intermediate staging area target of the export function on the primary side. He must set and operate the move of these export files between the intermediate staging area on the primary side and the regular staging area on the secondary side.
