Veritas NetBackup™ in Highly Available Environments Administrator's Guide

Last Published:
Product(s): NetBackup (8.1.1, 8.1)
  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 partial catalog restore

With partial catalog approach, it is assumed that restore operations do not need tapes to be assigned or located in specific media pools. It is also assumed that a tape exists in EMM and NetBackup can mount and read the tape for restoring. The following steps must be carried out before restores can be started:

To prepare for partial catalog restore

  1. On UNIX and Linux master servers create copies of the bp.conf and vm.conf files.
  2. Recover only the NetBackup catalog image and configuration files.

    • When using the NetBackup Administration Console, select the Partial catalog recovery option when prompted.

    • Or run the bprecover -wizard command.

    Note:

    The DR master server must have the same name as the production master server.

    Note:

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

  3. Run the cat_export - all - staging to export the metadata from the replicated relational database backup.
  4. Run the command cat_import - all to import the exported metadata into the active relational database. Alternatively, set the parameter LIST_FS_IMAGE_HEADERS to YES in the bp.conf file or the registry depending on the master server platform. This will cause the next catalog cleanup job to automatically import the exported metadata.
  5. 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.

  6. Shut down NetBackup.
  7. 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
  8. Start NetBackup.
  9. Inventory all the tape libraries to ensure that the tapes are added to the non-scratch media pool. This pool prevents tapes from being accidentally overwritten by active backup policies at a later time.

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