NetBackup™ in Highly Available Environments Administrator's Guide

Last Published:
Product(s): NetBackup & Alta Data Protection (10.2)
  1. About in this guide
    1.  
      What's in this guide
    2.  
      Documents related to NetBackup in highly available environments
  2. NetBackup protection against single points of failure
    1. Protecting against component failures
      1.  
        Network link failures
      2. Storage device connection failures
        1.  
          SAN connection failures
        2.  
          Robotic control connection failures
      3.  
        Storage device failure
      4.  
        Media availability failures
      5.  
        Primary server failures
      6. Media server failures
        1.  
          Dedicated media server failures
        2.  
          Non-dedicated media servers failures
        3.  
          SAN media server failures
        4.  
          Restoring tape backups using an alternative media server
        5.  
          Restoring disk backups using an alternative media server
      7.  
        LAN client failures
      8.  
        SAN client failures
    2.  
      Site failures
    3.  
      Protecting the catalog in highly available environments
  3. 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 a 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
  4. 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
  5. Deploying NetBackup primary servers with full catalog replication
    1.  
      About replication considerations
    2. About non-clustered NetBackup primary server with catalog replication
      1. Installing and configuring non-clustered NetBackup primary server with catalog replication
        1.  
          Installing and configuring the main NetBackup primary server
        2.  
          Installing and configuring an alternate NetBackup primary server
        3.  
          Upgrading NetBackup primary server in a non-clustered replicated configuration
    3. About globally clustered NetBackup primary servers with catalog replication
      1. Installing and configuring a globally clustered NetBackup primary server with catalog replication
        1.  
          About clustering considerations
        2.  
          Installing and configuring the main NetBackup primary server cluster
        3.  
          Installing and configuring an alternate NetBackup primary server cluster
      2.  
        Populating the server tables in the NetBackup database
      3.  
        Upgrading NetBackup in a clustered replication configuration
      4.  
        Failing over to an alternate primary server cluster
      5.  
        Testing the NetBackup primary server cluster in clustered replication environment
  6. 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

Failing over to an alternate primary server cluster

You must failover to the alternate primary server cluster under the following circumstances:

  • All the nodes of the main primary server cluster fail.

  • Access to the main site is denied.

The exact failover procedure can vary for different replication technologies. Refer the following procedure listing the high-level steps to failover to the alternate primary server cluster.

To fail over to an alternate primary server cluster

  1. Stop NetBackup on the main primary server cluster.
  2. Stop or reverse the replication of the catalog volume.
  3. If necessary, update the DNS with the new virtual IP address for the primary server.
  4. Start NetBackup on the alternate primary server cluster.

Note:

Steps 1 and 2 occur automatically if the main site fails.

In globally clustered environment the process of failing over to alternate primary server can be automated. To automate the process, multiple heartbeat connections must exist between the clusters. Failure of the heartbeat network can cause the alternate primary server cluster to come online while the main primary server cluster is still operational.