Use Case: Disaster Recovery Failover Scenario

SystemA is unavailable, and SystemB is configured as the new DSU.

Considerations

Steps

1. To enable SystemB, issue snapmirror break on the two volumes on SystemB:SystemB> snapmirror break volume1SystemB> snapmirror break volume2
2. Add a bp.conf entry for each volume that was being failed over on each UNIX media server.

   On media server...	The following is the content of the bp.conf entry (on UNIX)/registry key (on Windows)...
   mediaserver1	NEARSTORE_FAILOVER_SERVER = SystemA:/vol/volume1 SystemB:/vol/volume1
   mediaserver2	NEARSTORE_FAILOVER_SERVER=SystemA:/vol/volume2 SystemB:/vol/volume2

   Mediaserver1

   • If mediaserver1 is a UNIX server, add the following NEARSTORE_FAILOVER_SERVER entry to the /usr/openv/netbackup/bp.conf file: NEARSTORE_FAILOVER_SERVER = SystemA:/vol/volume1 SystemB:/vol/volume1
   • If mediaserver1 is a Windows server, add a registry key at this location: KEY_LOCAL_MACHINE\SOFTWARE\VERITAS\NetBackup\ConcurrentVersion\Config

     The key should be named NEARSTORE_FAILOVER_SERVER and be of type multi-string value. The value should be:SystemA:/vol/volume1 SystemB:/vol/volume1

     For exact location of the registry key for Windows, see the NetBackup Administrators Guide.

   Mediaserver2

   • If mediaserver2 is a UNIX server, add the following NEARSTORE_FAILOVER_SERVER entry to the /usr/openv/netbackup/bp.conf file: NEARSTORE_FAILOVER_SERVER=SystemA:/vol/volume2 SystemB:/vol/volume2
   • If mediaserver2 is a Windows server, add a registry key at this location: KEY_LOCAL_MACHINE\SOFTWARE\VERITAS\NetBackup\ConcurrentVersion\Config

     The key should be named NEARSTORE_FAILOVER_SERVER and be of type multi-string value.

     The value should be: SystemA:/vol/volume2 SystemB:/vol/volume2

   The NearStore host name must match the listing in the Storage Device > NDMP Hosts section in NetBackup. For example, if you add SystemA as an NDMP Host to the NetBackup Storage Device by the name SystemA and add SystemB by the name SystemB.domain.com, the entry will read: SystemA:/vol/volume2 SystemB.domain.com:/vol/volume2

3. To display differences between the contents on the catalog, and contents on the DSU on each media server, issue the bpstsinfo –comparedbandstu command. The following is the command for mediaserver1: /usr/openv/netbackup/bin/admincmd/bpstsinfo –comparedbandstu -oldservervolume SystemA:/vol/volume1 –servername SystemB –serverprefix ntap: -lsuname /vol/volume1 The following is the command for mediaserver2: /usr/openv/netbackup/bin/admincmd/bpstsinfo –comparedbandstu -oldservervolume SystemA:/vol/volume2 –servername SystemB –serverprefix ntap: -lsuname /vol/volume2

   If no discrepancy exists between the images in the catalog and images on the NearStore volume, no images are listed in the output. The output will contain only debug logging:

   STS: STH_ESDEBUG: comparedbandstu: libsts openp() 06/09/12 10:48:37: opening module /usr/openv/lib/libstspibasicdiskMT.so 
   STS: STH_ESDEBUG: comparedbandstu: libsts openp() 06/09/12 10:48:38: opening module /usr/openv/lib/libstspinearstoreMT.so 
    Nearstore disk subtype

   If a mismatch exists—for example, if one image did not get replicated to SystemB before SystemA went down—the output contains additional information:

   STS: STH_ESDEBUG: comparedbandstu: libsts openp() 06/09/12 10:39:37: opening module /usr/openv/lib/libstspibasicdiskMT.so 
   Nearstore disk subtype
   ONLY IN CATALOG 
   imagename:mediaserver1_1157990060 policy:powerpoint_backup copy_num:1 frag_num:0 is_header:TRUE resume_num:0
   ONLY IN CATALOG
   imagename: mediaserver1_1157990060 policy: powerpoint_backup copy_num:1 frag_num:1 is_header:FALSE resume_num:0
   

   Use the NetBackup GUI or run the bpexpdate command to remove the entries for this image from the NetBackup catalog.
   Note: Two images are listed, but they represent only one backup. There are separate files for the header and the actual backup data. If this backup is enabled for True Image Restore, three images are printed. The key is to look at the imagename field. Both images have the same image name, which indicates that these images are part of the same backup.

   The following is the bpexpdate command to remove the entry from the catalog: /usr/openv/netbackup/bin/admincmd/bpexpdate -backupid mediaserver1_1157990060 -d 0

4. If the original volumes on SystemA are never expected to recover (that is, no SnapMirror resync to back up the volume), perform the following steps to manually delete the Snapshot copies used by the SnapMirror transfer on volumes, volume1 and volume2.
   1. Issue snapmirror status –l on the destination volume on SystemB: SystemB> snapmirror status –l vsmtest1

      The output will appear similiar to the following sample output:

      SystemB> snapmirror status -l volume1
      SnapMirror is on.
      
      Source:                 SystemA:volume1
      Destination:            SystemB:volume1
      Status:                 Idle
      Progress:               -
      State:                  Broken-off
      Lag:                    00:05:28
      Mirror Timestamp:       Fri Sep 29 10:39:28 PDT 2006
      Base Snapshot:          SystemB(0101178726)_volume1.2
      Current Transfer Type:  -
      Current Transfer Error: -
      Contents:               Replica
      Last Transfer Type:     Resync
      Last Transfer Size:     72 KB
      Last Transfer Duration: 00:00:03
      Last Transfer From:     SystemA:volume1
      

   2. Delete the base Snapshot copy associated with the volume: SystemB> snap delete volume1 SystemB(0101178726)_volume1.2
   3. Repeat this procedure for volume2.
5. Remove any SnapMirror schedules that were added in the snapmirror.conf file for these volumes.
6. Reconfigure the storage units originally configured to the volumes on SystemA, to point to the storage units on SystemB using the following command:/usr/openv/netbackup/bin/admincmd/bpsturep -label storage unit label -nh SystemB