NetBackup™ for Hadoop Administrator's Guide
- Introduction
- Prerequisites and best practices for the NetBackup for Hadoop plug-in for NetBackup
- Configuring NetBackup for Hadoop
- About configuring NetBackup for NetBackup for Hadoop
- Managing backup hosts
- Adding NetBackup for Hadoop credentials in NetBackup
- Configuring the NetBackup for Hadoop plug-in using the NetBackup for Hadoop configuration file
- Configuring NetBackup for a highly-available NetBackup for Hadoop cluster
- Configuring a custom port for the NetBackup for 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 NetBackup for Hadoop cluster that uses Kerberos
- Hadoop.conf configuration for parallel restore
- Create a BigData policy for Hadoop clusters
- Disaster recovery of a NetBackup for Hadoop cluster
- Performing backups and restores of Hadoop
- Troubleshooting
- About troubleshooting NetBackup for NetBackup for Hadoop issues
- About NetBackup for Hadoop debug logging
- Troubleshooting backup issues for NetBackup 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 NetBackup for Hadoop data
- Restore fails with error code 2850
- NetBackup restore job for NetBackup 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
Backing up NetBackup for Hadoop data
NetBackup for Hadoop data is backed up in parallel streams wherein NetBackup for Hadoop DataNodes stream data blocks simultaneously to multiple backup hosts.
Note:
All the directories specified in NetBackup for Hadoop backup selection must be snapshot-enabled before the backup.
The following diagram provides an overview of the backup flow:
As illustrated in the following diagram:
A scheduled backup job is triggered from the primary server.
Backup job for NetBackup for Hadoop data is a compound job. When the backup job is triggered, first a discovery job is run.
During discovery, the first backup host connects with the NameNode and performs a discovery to get details of data that needs to be backed up.
A workload discovery file is created on the backup host. The workload discovery file contains the details of the data that needs to be backed up from the different DataNodes.
The backup host uses the workload discovery file and decides how the workload is distributed amongst the backup hosts. Workload distribution files are created for each backup host.
Individual child jobs are executed for each backup host. As specified in the workload distribution files, data is backed up.
Data blocks are streamed simultaneously from different DataNodes to multiple backup hosts.
The compound backup job is not completed until all the child jobs are completed. After the child jobs are completed, NetBackup cleans all the snapshots from the NameNode. Only after the cleanup activity is completed, the compound backup job is completed.