Veritas NetBackup™ in Highly Available Environments Administrator's Guide

Last Published:
Product(s): NetBackup (8.2)
Platform: Linux,UNIX,Windows
  1. NetBackup protection against single points of failure
    1. About protecting against component failures
      1.  
        About protecting against network link failures
      2. About protecting against storage device connection failures
        1.  
          About protecting against SAN connection failures
        2.  
          About protecting against robotic control connection failures
      3.  
        About protecting against storage device failure
      4.  
        About protecting against media availability failures
      5.  
        About protecting against master server failures
      6. About protecting against media server failures
        1.  
          About protecting against dedicated media server failures
        2.  
          About protecting against non-dedicated media servers failures
        3.  
          About protecting against SAN media server failures
        4.  
          Restoring tape backups using an alternative media server
        5.  
          Restoring disk backups using an alternative media server.
      7.  
        About protecting against LAN client failures
      8.  
        About protecting against SAN client failures
    2.  
      About protecting against site failures
    3.  
      About protecting catalog in highly available environments
  2. About site disaster recovery with catalog backup and recovery
    1.  
      Disaster recovery packages
    2. About catalog recovery
      1.  
        About full catalog recovery
      2.  
        Performing full catalog restore
      3.  
        Making the DR environment consistent after a full catalog restore
      4.  
        About partial catalog recovery
      5.  
        Performing partial catalog restore
      6.  
        Making the DR environment consistent after a partial catalog restore
    3. About disk recovery in DR domain
      1.  
        Disk recovery in single-domain replication DR environment
      2.  
        Auto Image Replication
      3.  
        Disk recovery in cross-domain replication DR environment
  3. About site loss protection with auto image and catalog replication
    1.  
      About Auto Image Replication (AIR)
    2. About NetBackup catalog replication
      1.  
        About conditions for support of replicated NetBackup catalogs
      2.  
        About catalog synchronization
      3. About multi-site single domain replication
        1.  
          About multi-site single domain with stretched SAN
        2.  
          About multi-site single domain with optimized duplication
      4. About multi-site cross domain replication
        1.  
          About multi-site cross domain and BasicDisk storage
        2.  
          Planning a cross domain replication disaster recovery domain
      5. About full catalog replication
        1.  
          Recovering the catalog with full catalog replication
        2.  
          Making the DR environment consistent with full catalog replication
      6. About partial catalog replication
        1.  
          Preparing an environment for partial catalog replication
        2.  
          Recovering the environment with partial catalog replication
        3.  
          Making the disaster recovery environment consistent with partial catalog replication
        4.  
          Considerations for managing tapes with partial catalog replication
  4. Deploying NetBackup master servers with full catalog replication
    1.  
      About replication considerations
  5. Using NetBackup to perform backups and restores in a cluster
    1. About backups and restores with NetBackup in a cluster
      1.  
        Performing user-directed backups with NetBackup in a cluster
      2. About restoring data in a cluster
        1.  
          Example: Performing a user-directed restore in a NetBackup cluster
    2. About supported NetBackup application agents in a cluster
      1.  
        About backing up database files in a cluster
      2.  
        About user backups
      3.  
        About NetBackup client in a cluster

Performing full catalog restore

With full catalog recovery the complete catalog backup is recovered to the DR master server. The media servers that do not exist in the DR environment are deactivated to avoid unnecessary pooling. All device records are removed because the device configuration at the DR site can be different to the production site. Device discovery is run to update the EMM database. You must perform the following procedure before restores can be started. Also, document the procedure in your DR plan.

To prepare for full catalog restore

  1. On UNIX and Linux master servers, create copies of the bp.conf and vm.conf files.
  2. Run the bprecover command to recover the entire catalog.

    Note:

    The DR master server must have the same name and topology as the production master server. If the production master server is a cluster then the DR master server must also be a cluster. The number of member nodes and the names of the nodes can be different.

    Note:

    If a catalog backup that was created on a separate media server is used, then a media server with the same name is required for the catalog recovery.

  3. After you run the bprecover command, set a passphrase for disaster recovery package for the subsequent catalog backups to be successful.

    See Disaster recovery packages.

  4. During catalog recovery, security certificates for cluster nodes are not recovered. Only the virtual name certificate is recovered.

    If NetBackup certificates are used for host communication

    For successful host communication, you must deploy NetBackup certificates (host name-based and host ID-based certificates) on all cluster nodes after a disaster.

    For more details, refer to the Generating a certificate on a clustered master server after disaster recovery installation chapter from the NetBackup Security and Encryption Guide.

    If external certificates are used for host communication

    For successful host communication, you must configure all cluster nodes to use external certificates after a disaster.

    For more details, refer to the NetBackup Security and Encryption Guide.

  5. Clear white list cache and restart the service on all hosts in the domain.
  6. Deactivate all the backup policies to prevent backups from starting automatically.
    • You can do this manually using the NetBackup Adminstration Console.

    • Or run the bpplinfo <policy> -modify -inactive CLI.

  7. Shut down NetBackup.
  8. On UNIX and Linux master servers, replace the bp.conf and the vm.conf files that were restored from the catalog backup with the copies created in step 1.
  9. Start the NetBackup Relational Database Manager, NetBackup PBX, and EMM services on the new master server.
    • On UNIX and Linux master servers, run the following commands:

      • /usr/openv/netbackup/bin/nbdbms_start_stop start

      • start /opt/VRTSpbx/bin/pbx_exchange

      • /usr/openv/netbackup/bin/nbemm

    • On Windows master servers, start the following Windows services:

      • NetBackup Relational Database Manager

      • Veritas Private Branch Exchange

      • NetBackup Enterprise Media Manager

      Note:

      The PBX process may already be running because the NetBackup commands do not stop and start PBX.

      For more information about NetBackup Relational Database Manager service, see the NetBackup Troubleshooting Guide.

  10. Deactivate the media servers that are not part of the DR environment. Run the following command:

    nbemmcmd -updatehost -machinename <Media Server> -machinestateop set_admin_pause -machinetype media -masterserver <Master Server>

  11. Delete all the tape devices from the EMM database. Run the following command:

    nbemmcmd -deletealldevices -allrecords

  12. This step is required if you have NAT clients in your environment.

    If the NetBackup Messaging Broker (or nbmqbroker) service is configured, after the catalog restore you need to enable the cluster to monitor the service using the configureMQ -enableCluster command.

    For more information on the command, refer to the NetBackup Command Reference Guide.

  13. Restart NetBackup.
  14. Using the Device Configuration wizard create the new tape drive and library configuration.
  15. If bar code masking rules were used at step 9, ensure that the same rules are set here. If necessary, add them.
  16. Using the NetBackup Adminstration Console, verify if all the recovery media are set to non-robotic.
    • If some recovery media still need to be set to non-robotic, do the following:

    • Select the robotic media, right-click and select Move.

    • Change the robot field to Standalone.

    • Click OK to save the changes.

  17. Once all the recovery media are set to non-robotic, in the Inventory all the tape libraries field ensure that the media are identified in the correct library.

You can now start restore and recovery operations of the client data that is backed up at the production datacenter.

If you have configured an external CA-signed certificate for the NetBackup web server, you must run the configureWebServerCerts command on the active node to ensure that the external certificate is used after the failover.

For more information on the command, see the NetBackup Commands Reference Guide.

For all cluster nodes, do the following:

  • Define the external certificate configuration options (ECA_CERT_PATH, ECA_CRL_PATH, and so on) in the configuration file on the node.

  • Run the nbcertcmd -enrollCertificate on the node.

    For more details, refer to the NetBackup Security and Encryption Guide.