NetBackup™ for Hadoop Administrator's Guide
- Introduction
- Prerequisites and best practices for the Hadoop plug-in for NetBackup
- Configuring NetBackup for Hadoop
- About configuring NetBackup for Hadoop
- Managing backup hosts
- Adding Hadoop credentials in NetBackup
- Configuring the Hadoop plug-in using the Hadoop configuration file
- Configuring NetBackup for a highly-available Hadoop cluster
- Configuring a custom port for the Hadoop cluster
- Configuring number of threads for backup hosts
- Configuring number of streams for backup hosts
- Configuring distribution algorithm and golden ratio for backup hosts
- Configuring communication between NetBackup and Hadoop clusters that are SSL-enabled (HTTPS)
- Configuration for a Hadoop cluster that uses Kerberos
- Hadoop.conf configuration for parallel restore
- Create a BigData policy for Hadoop clusters
- Disaster recovery of a Hadoop cluster
- Performing backups and restores of Hadoop
- Troubleshooting
- About troubleshooting NetBackup for Hadoop issues
- About NetBackup for Hadoop debug logging
- Troubleshooting backup issues for Hadoop data
- Backup operation fails with error 6609
- Backup operation failed with error 6618
- Backup operation fails with error 6647
- Extended attributes (xattrs) and Access Control Lists (ACLs) are not backed up or restored for Hadoop
- Backup operation fails with error 6654
- Backup operation fails with bpbrm error 8857
- Backup operation fails with error 6617
- Backup operation fails with error 6616
- Backup operation fails with error 84
- NetBackup configuration and certificate files do not persist after the container-based NetBackup appliance restarts
- Unable to see incremental backup images during restore even though the images are seen in the backup image selection
- One of the child backup jobs goes in a queued state
- Troubleshooting restore issues for Hadoop data
- Restore fails with error code 2850
- NetBackup restore job for Hadoop completes partially
- Extended attributes (xattrs) and Access Control Lists (ACLs) are not backed up or restored for Hadoop
- Restore operation fails when Hadoop plug-in files are missing on the backup host
- Restore fails with bpbrm error 54932
- Restore operation fails with bpbrm error 21296
- Hadoop with Kerberos restore job fails with error 2850
- Configuration file is not recovered after a disaster recovery
- Index
NetBackup configuration and certificate files do not persist after the container-based NetBackup appliance restarts
The NetBackup configuration files like hadoop.conf or hbase.conf or SSL certificate and CRL paths do not persist after the container-based NetBackup Appliance restarts for any reason. This issue is applicable where container-based NetBackup Appliance is used as a backup host to protect the Hadoop or HBase workload.
Reason:
In the NetBackup Appliance environments the files that are available in the docker host's persistent location are retained after restart operation. The hadoop.conf and hbase.conf files are custom configuration files and are not listed in the persistent location.
The configuration files are used for defining values like HA (high availability) nodes during a failover and number of threads for backup. If these files get deleted, backups use the default values for both HA and number of threads that are Primary Name Node and 4 respectively. Backup fails only if the primary node goes down in such a case as plug-in fails to find secondary server.
If the SSL certificates and CRL path files are stored at a location that is not persistent the appliance restart, the backups and restore operations fail.
Workaround:
If custom configuration files for Hadoop and HBase get deleted after a restart, you can manually create the files at the following location:
Hadoop:
/usr/openv/var/global/hadoop.confHBase:
/usr/openv/var/global/hbase.conf
You can store the CA certificate that has signed the Hadoop or HBase SSL certificate and CRL at the following location:
/usr/openv/var/global/