NetBackup™ for HBase Administrator's Guide

Last Published:
Product(s): NetBackup & Alta Data Protection (10.4)
  1. Introduction
    1.  
      Protecting HBase data using NetBackup
    2.  
      Backing up HBase data
    3.  
      Restoring HBase data
    4.  
      NetBackup for HBase terminologies
    5.  
      Limitations
  2. Deploying HBase plug-in for NetBackup
    1.  
      About the HBase plug-in deployment
    2.  
      Pre-requisites for installing the HBase plug-in
    3.  
      Operating system and platform compatibility
    4.  
      License for HBase plug-in for NetBackup
    5.  
      Preparing the HBase cluster
    6.  
      Best practices for deploying the HBase plug-in
    7.  
      Post installation procedures
    8.  
      Verifying the deployment of the HBase plug-in
  3. Configuring NetBackup for HBase
    1.  
      About configuring NetBackup for HBase
    2. Managing backup hosts
      1.  
        Adding a NetBackup client to the allowed list
      2.  
        Configure a NetBackup Appliance as a backup host
    3.  
      Adding HBase credentials in NetBackup
    4. Configuring the HBase plug-in using the HBase configuration file
      1.  
        Configuring NetBackup for a highly-available HBase cluster
      2.  
        Configuring communication between NetBackup and HBase clusters that have SSL enabled (HTTPS)
    5.  
      Configuration for a HBase cluster that uses Kerberos
    6.  
      Create a BigData policy for HBase clusters
    7.  
      Disaster recovery of a HBase cluster
  4. Performing backups and restores of HBase
    1. About backing up a HBase cluster
      1.  
        Prerequisites for running backup and restore operations for a HBase cluster with Kerberos authentication
      2.  
        Backing up a HBase cluster
      3.  
        Best practices for backing up a HBase cluster
    2. About restoring an HBase cluster
      1.  
        Restoring HBase data on the same HBase cluster
    3.  
      Restoring HBase data on an alternate HBase cluster
    4.  
      Restoring truncated tables
    5.  
      Best practices for restoring a HBase cluster
  5. Troubleshooting
    1.  
      About NetBackup for HBase debug logging
    2.  
      Backup fails with error 6609
    3.  
      Backup fails with error 6601
    4.  
      Backup fails with error 6623
    5.  
      Restore fails with error 2850
    6.  
      Backup fails with error 20
    7.  
      Backup fails with error 112
    8.  
      Backup operation fails with error 6654
    9.  
      NetBackup configuration and certificate files do not persist after the container-based NetBackup appliance restarts
    10.  
      Configuration file is not recovered after a disaster recovery

Adding a NetBackup client to the allowed list

To use the NetBackup client as a backup host, you must add it to the allowed list. Perform this procedure on the NetBackup primary server.

Adding a host to an allowed list is a security practice used for restricting systems from running software or applications unless these have been approved for safe execution.

To add a NetBackup client to the allowed list

  • Run the following command on the NetBackup primary server:
    • For UNIX

      The directory path to the command: /usr/openv/var/global/bin/admincmd/bpsetconfig

      bpsetconfig -h primaryserver

      bpsetconfig> APP_PROXY_SERVER = clientname.domain.org

      bpsetconfig>

      UNIX systems: <ctl-D>

    • For Windows

      The directory path to the command: <install_path>\NetBackup\bin\admincmd\bpsetconfig

      bpsetconfig -h primaryserver

      bpsetconfig> APP_PROXY_SERVER = clientname1.domain.org

      bpsetconfig> APP_PROXY_SERVER = clientname2.domain.org

      bpsetconfig>

      Windows systems: <ctl-Z>

This command sets the APP_PROXY_SERVER = clientname entry in the backup configuration (bp.conf) file or the Windows registry.

For more information about the APP_PROXY_SERVER = clientname, refer to the Configuration options for NetBackup clients section in the NetBackup Administrator's Guide, Volume I.