In the event that SystemA becomes unavailable, the backup administrator must manually break the applicable SnapMirror relationships on SystemA and then make a few configuration adjustments in NetBackup to allow NetBackup to fail over from volumes on SystemA to volumes on SystemA.
Steps
- To enable read and write access to the replicated volumes on SystemA break the SnapMirror relationships by issuing a snapmirror break command for each of the replicated volumes on SystemA.
- To enable SystemA to restore images that had been backed up to SystemA , add an entry to the /usr/openv/netbackup/bp.conf file on UNIX, or add a multi-string type registry key, as described in the below example, on Windows. One entry or registry key is required for each replicated volume and all affected media servers must be updated.
The exact content
of the entry or the registry key is illustrated in the disaster recovery example later in this section.
- Because the SnapMirror replication is performed asynchronously, there is a small chance that images might not have been fully replicated before SystemA went down. A new option to the bpstsinfo command line utility in NetBackup compares the contents of the NetBackup catalog with the list of images reported by the NearStore storage system. This command compares the catalog entries for images on the failed SystemA volumes and the current SystemA volumes. It pulls a list of images on SystemA and compares that list to the images that SystemA reports that it has. It outputs any images that are not present both in the catalog and on SystemA as well as the location of that image, whether it is only in the catalog or on media. This informs the administrator of any discrepancy so the appropriate action can be taken.
- Change the NearStore server field in each NetBackup storage unit from SystemA to SystemA.
- If the catalog had been backed up to SystemA and the disaster necessitates the recovery of the catalog, see the information about recovering the catalog in the NetBackup Administrators Guide for the platform.
Note: Catalog backups are restricted to NearStore storage systems that do not have file system exposure enabled.