Veritas NetBackup™ for HBase Administrator's Guide

Last Published:
Product(s): NetBackup (8.2, 8.1.2)
Platform: Linux,UNIX,Windows
  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.  
        Whitelisting a NetBackup client on NetBackup master server
      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
    5.  
      Configuration for a HBase cluster that uses Kerberos
    6. Configuring NetBackup policies for HBase plug-in
      1. Creating a BigData backup policy
        1. Creating BigData policy using the NetBackup Administration Console
          1.  
            Using the Policy Configuration Wizard to create a BigData policy for HBase clusters
          2.  
            Using the NetBackup Policies utility to create a BigData policy for HBase clusters
        2.  
          Using NetBackup Command Line Interface (CLI) to 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.  
        Pre-requisite 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 a HBase cluster
      1. Restoring HBase data on the same HBase cluster
        1.  
          Using the Restore Wizard to restore HBase data on the same cluster
        2.  
          Using the bprestore command to restore 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

Configuring NetBackup for a highly-available HBase cluster

To protect a highly-available HBase cluster, when you configure NetBackup for HBase cluster:

  • Specify one of the HMaster (primary) as the client in the BigData policy.

  • Specify the same HMaster (primary and fail-over) as application server when you execute the tpconfig command.

  • Create a hbase.conf file, update it with the details of the HMaster (primary and fail-over), and copy it to all the backup hosts. The hbase.conf file is in JSON format.

  • Hostname and port of the HMaster must be same as you have specified with the http address parameter in the hbase-site.xml of the HBase cluster.

  • User name of the primary and fail-over HMaster must be same.

  • Do not provide a blank value for any of the parameters, or the backup job fails.

To update the HBase.conf file for highly-available HBase cluster

  1. Update the hbase.conf file with the following parameters:
    {
 "application_servers": 
 {
		"hostname_of_primary_HMaster1":
		{
			"failover_HMaster":
			[
				{
					"hostname": "hostname_of_failover_HMaster1"
			}				
	 	]
		 
  }
 }
}
  2. If you have multiple HBase clusters, use the same hbase.conf file to update the details. For example,
    {
	"application_servers": 
 {
		"hostname_of_primary_HMaster1":
  {
		 "failover_HMaster":
   [
			 {
				 "hostname": "hostname_of_failover_HMaster1"
				 
			 }
	 	],
   
  },
  "hostname_of_primary_HMaster2":
  {
		 "failover_HMaster":
   [
			 {
			  "hostname": "hostname_of_failover_HMaster2",
			  
			 }
	 	],
	}
 }
}
  3. Copy this file to the following location on all the backup hosts:

    /usr/openv/netbackup/