Veritas NetBackup™ for

Hadoop Administrator's
Guide

UNIX, Windows, and Linux

Release 8.3.0.1
Veritas Hadoop Administrator's Guide
Last updated: 2020-09-03

Legal Notice
Copyright © 2020 Veritas Technologies LLC. All rights reserved.

Veritas, the Veritas Logo, and NetBackup are trademarks or registered trademarks of Veritas
Technologies LLC or its affiliates in the U.S. and other countries. Other names may be
trademarks of their respective owners.

This product may contain third-party software for which Veritas is required to provide attribution
to the third party (“Third-party Programs”). Some of the Third-party Programs are available
under open source or free software licenses. The License Agreement accompanying the
Software does not alter any rights or obligations you may have under those open source or
free software licenses. Refer to the Third-party Legal Notices document accompanying this
Veritas product or available at:

https://www.veritas.com/about/legal/license-agreements

The product described in this document is distributed under licenses restricting its use, copying,
distribution, and decompilation/reverse engineering. No part of this document may be
reproduced in any form by any means without prior written authorization of Veritas Technologies
LLC and its licensors, if any.

THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED

CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED
WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR
NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH
DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. Veritas Technologies LLC SHALL
NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION
WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE
INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE
WITHOUT NOTICE.

The Licensed Software and Documentation are deemed to be commercial computer software
as defined in FAR 12.212 and subject to restricted rights as defined in FAR Section 52.227-19
"Commercial Computer Software - Restricted Rights" and DFARS 227.7202, et seq.
"Commercial Computer Software and Commercial Computer Software Documentation," as
applicable, and any successor regulations, whether delivered by Veritas as on premises or
hosted services. Any use, modification, reproduction release, performance, display or disclosure
of the Licensed Software and Documentation by the U.S. Government shall be solely in
accordance with the terms of this Agreement.

Veritas Technologies LLC

2625 Augustine Drive
Santa Clara, CA 95054

http://www.veritas.com
Technical Support
Technical Support maintains support centers globally. All support services will be delivered
in accordance with your support agreement and the then-current enterprise technical support
policies. For information about our support offerings and how to contact Technical Support,
visit our website:

https://www.veritas.com/support

You can manage your Veritas account information at the following URL:

https://my.veritas.com

If you have questions regarding an existing support agreement, please email the support
agreement administration team for your region as follows:

Worldwide (except Japan) [email protected]

Japan [email protected]

Documentation
Make sure that you have the current version of the documentation. Each document displays
the date of the last update on page 2. The latest documentation is available on the Veritas
website:

https://sort.veritas.com/documents

Documentation feedback
Your feedback is important to us. Suggest improvements or report errors or omissions to the
documentation. Include the document title, document version, chapter title, and section title
of the text on which you are reporting. Send feedback to:

[email protected]

You can also see documentation information or ask a question on the Veritas community site:

http://www.veritas.com/community/

Veritas Services and Operations Readiness Tools (SORT)

Veritas Services and Operations Readiness Tools (SORT) is a website that provides information
and tools to automate and simplify certain time-consuming administrative tasks. Depending
on the product, SORT helps you prepare for installations and upgrades, identify risks in your
datacenters, and improve operational efficiency. To see what services and tools SORT provides
for your product, see the data sheet:

https://sort.veritas.com/data/support/SORT_Data_Sheet.pdf
 Contents

Chapter 1 Introduction ........................................................................... 7

Protecting Hadoop data using NetBackup ........................................... 7

Backing up Hadoop data ................................................................. 9
Restoring Hadoop data .................................................................. 10
NetBackup for Hadoop terminologies ................................................ 11
Limitations .................................................................................. 13

Chapter 2 Verifying the pre-requisites and best practices

for the Hadoop plug-in for NetBackup ................... 15
About deploying the Hadoop plug-in ................................................. 15
Pre-requisites for the Hadoop plug-in ................................................ 16
Operating system and platform compatibility ................................ 16
NetBackup server and client requirements ................................... 16
License for Hadoop plug-in for NetBackup ................................... 16
Preparing the Hadoop cluster .......................................................... 16
Best practices for deploying the Hadoop plug-in .................................. 17

Chapter 3 Configuring NetBackup for Hadoop ............................. 18

About configuring NetBackup for Hadoop .......................................... 18
Managing backup hosts ................................................................. 19
Whitelisting a NetBackup client on NetBackup master server ........... 21
Configure a NetBackup Appliance as a backup host ...................... 22
Adding Hadoop credentials in NetBackup .......................................... 22
Configuring the Hadoop plug-in using the Hadoop configuration file
........................................................................................... 23
Configuring NetBackup for a highly-available Hadoop cluster
..................................................................................... 24
Configuring a custom port for the Hadoop cluster .......................... 27
Configuring number of threads for backup hosts ........................... 28
Configuring communication between NetBackup and Hadoop
clusters that are SSL-enabled (HTTPS) ................................ 29
Configuration for a Hadoop cluster that uses Kerberos ......................... 34
Configuring NetBackup policies for Hadoop plug-in ............................. 35
Creating a BigData backup policy .............................................. 35
 Contents 5

Disaster recovery of a Hadoop cluster .............................................. 40

Chapter 4 Performing backups and restores of Hadoop ........... 42

About backing up a Hadoop cluster .................................................. 42
Pre-requisite for running backup and restore operations for a
Hadoop cluster with Kerberos authentication .......................... 43
Best practices for backing up a Hadoop cluster ............................. 43
Backing up a Hadoop cluster .................................................... 44
About restoring a Hadoop cluster ..................................................... 44
Best practices for restoring a Hadoop cluster ............................... 45
Restoring Hadoop data on the same Hadoop cluster ..................... 46
Restoring Hadoop data on an alternate Hadoop cluster .................. 49

Chapter 5 Troubleshooting ................................................................. 53

About troubleshooting NetBackup for Hadoop issues ........................... 53

About NetBackup for Hadoop debug logging ...................................... 54
Troubleshooting backup issues for Hadoop data ................................. 54
Backup operation fails with error 6609 ........................................ 55
Backup operation failed with error 6618 ...................................... 55
Backup operation fails with error 6647 ........................................ 55
Extended attributes (xattrs) and Access Control Lists (ACLs) are
not backed up or restored for Hadoop ................................... 56
Backup operation fails with error 6654 ........................................ 57
Backup operation fails with bpbrm error 8857 ............................... 57
Backup operation fails with error 6617 ........................................ 57
Backup operation fails with error 6616 ........................................ 57
NetBackup configuration and certificate files do not persist after
the container-based NetBackup appliance restarts .................. 58
Unable to see incremental backup images during restore even
though the images are seen in the backup image selection
..................................................................................... 59
One of the child backup jobs goes in a queued state ...................... 59
Troubleshooting restore issues for Hadoop data ................................. 59
Restore fails with error code 2850 .............................................. 60
NetBackup restore job for Hadoop completes partially .................... 60
Extended attributes (xattrs) and Access Control Lists (ACLs) are
not backed up or restored for Hadoop ................................... 60
Restore operation fails when Hadoop plug-in files are missing on
the backup host ............................................................... 60
Restore fails with bpbrm error 54932 .......................................... 61
Restore operation fails with bpbrm error 21296 ............................. 61
Configuration file is not recovered after a disaster recovery ............. 61
 Contents 6

Index .................................................................................................................... 63
 Chapter 1
Introduction
This chapter includes the following topics:

■ Protecting Hadoop data using NetBackup

■ Backing up Hadoop data

■ Restoring Hadoop data

■ NetBackup for Hadoop terminologies

■ Limitations

Protecting Hadoop data using NetBackup

Using the NetBackup Parallel Streaming Framework (PSF), Hadoop data can now
be protected using NetBackup.
The following diagram provides an overview of how Hadoop data is protected by
NetBackup.
Also, review the definitions of terminologies.See “NetBackup for Hadoop
terminologies” on page 11.
 Introduction 8
Protecting Hadoop data using NetBackup

Figure 1-1 Architectural overview

Hadoop plug-in Is
Hadoop cluster deployed on all the backup
hosts BigData policy

NameNode

Application_Type=hadoop
Backup Host 1
DataNode 1
Master server

DataNode 2
Backup Host 2
Media server
DataNode 3
Storage
Backup Host 3
DataNode n Parallel Streams
...

As illustrated in the diagram:

■ The data is backed up in parallel streams wherein the DataNodes stream data
blocks simultaneously to multiple backup hosts. The job processing is accelerated
due to multiple backup hosts and parallel streams.
■ The communication between the Hadoop cluster and the NetBackup is enabled
using the NetBackup plug-in for Hadoop.
The plug-in is installed as part of the NetBackup installation.
■ For NetBackup communication, you need to configure a BigData policy and add
the related backup hosts.
■ You can configure a NetBackup media server, client, or master server as a
backup host. Also, depending on the number of DataNodes, you can add or
remove backup hosts. You can scale up your environment easily by adding
more backup hosts.
■ The NetBackup Parallel Streaming Framework enables agentless backup wherein
the backup and restore operations run on the backup hosts. There is no agent
footprint on the cluster nodes. Also, NetBackup is not affected by the Hadoop
cluster upgrades or maintenance.
For more information:
■ See “Backing up Hadoop data” on page 9.
 Introduction 9
Backing up Hadoop data

■ See “Restoring Hadoop data” on page 10.

■ See “Limitations” on page 13.
■ For information about the NetBackup Parallel Streaming Framework (PSF) refer
to the NetBackup Administrator's Guide, Volume I.

Backing up Hadoop data

Hadoop data is backed up in parallel streams wherein Hadoop DataNodes stream
data blocks simultaneously to multiple backup hosts.

Note: All the directories specified in Hadoop backup selection must be

snapshot-enabled before the backup.

The following diagram provides an overview of the backup flow:

Figure 1-2 Backup flow

3 Discovery of 4 Workload
Backup job
workload for backup discovery file 1
is triggered.

2 Discovery Master server

job
NameNode
1
6 Child
Backup Host 1 job 1
5
DataNode 1

2
6 Child
DataNode 2 job 2
Backup Host 2

DataNode 3 3
6 Child
job 3
Backup Host 3 Storage
DataNode n 7 Data is backed up in = Workload
parallel streams n distribution files
Hadoop Cluster
(Snapshot Enabled)

As illustrated in the following diagram:

1. A scheduled backup job is triggered from the master server.
2. Backup job for Hadoop data is a compound job. When the backup job is
triggered, first a discovery job is run.
 Introduction 10
Restoring Hadoop data

3. 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.
4. 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.
5. 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.
6. Individual child jobs are executed for each backup host. As specified in the
workload distribution files, data is backed up.
7. 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.
See “About backing up a Hadoop cluster” on page 42.

Restoring Hadoop data

For restore only one backup host is used.
The following diagram provides an overview of the restore flow.
 Introduction 11
NetBackup for Hadoop terminologies

Figure 1-3 Restore flow

2
Backup host connects
with NameNode

NameNode
1 Master server
Restore job
is triggered
DataNode 1
Backup host

DataNode 2 4
Objects are restored on Storage
Hadoop Cluster the associated datanodes
(Snapshot Enabled) 3
Restore
Starts

As illustrated in the diagram:

1. The restore job is triggered from the master server.
2. The backup host connects with the NameNode. Backup host is also the
destination client.
3. The actual data restore from the storage media starts.
4. The data blocks are restored on the DataNodes.
See “About restoring a Hadoop cluster” on page 44.

NetBackup for Hadoop terminologies

The following table defines the terms you will come across when using NetBackup
for protecting Hadoop cluster.
 Introduction 12
NetBackup for Hadoop terminologies

Table 1-1 NetBackup terminologies

Terminology Definition

Compound job A backup job for Hadoop data is a compound job.

■ The backup job runs a discovery job for getting information of the
data to be backed up.
■ Child jobs are created for each backup host that performs the
actual data transfer.
■ After the backup is complete, the job cleans up the snapshots on
the NameNode and is then marked complete.

Discovery job When a backup job is executed, first a discovery job is created. The
discovery job communicates with the NameNode and gathers
information of the block that needs to be backed up and the associated
DataNodes. At the end of the discovery, the job populates a workload
discovery file that NetBackup then uses to distribute the workload
amongst the backup hosts.

Child job For backup, a separate child job is created for each backup host to
transfer data to the storage media. A child job can transfer data blocks
from multiple DataNodes.

Workload discovery During discovery, when the backup host communicates with the
file NameNode, a workload discovery file is created. The file contains
information about the data blocks to be backed up and the associated
DataNodes.

Workload distribution After the discovery is complete, NetBackup creates a workload

file distribution file for each backup host. These files contain information
of the data that is transferred by the respective backup host.

Parallel streams The NetBackup parallel streaming framework allows data blocks from
multiple DataNodes to be backed up using multiple backup hosts
simultaneously.

Backup host The backup host acts as a proxy client. All the backup and restore
operations are executed through the backup host.

You can configure media servers, clients, or a master server as a

backup host.

The backup host is also used as destination client during restores.

 Introduction 13
Limitations

Table 1-1 NetBackup terminologies (continued)

Terminology Definition

BigData policy The BigData policy is introduced to:

■ Specify the application type.

■ Allow backing up distributed multi-node environments.
■ Associate backup hosts.
■ Perform workload distribution.

Application server Namenode is referred to as a application server in NetBackup.

Primary NameNode In a high-availability scenario, you need to specify one NameNode

with the BigData policy and with the tpconfig command. This
NameNode is referred as the primary NameNode.

Fail-over NameNode In a high-availability scenario, the NameNodes other than the primary
NameNode that are updated in the hadoop.conf file are referred
as fail-over NameNodes.

Table 1-2 Hadoop terminologies

Terminology Definition

NameNode NameNode is also used as a source client during restores.

DataNode DataNode is responsible for storing the actual data in Hadoop.

Snapshot-enabled Snapshots can be taken on any directory once the directory is

directories snapshot-enabled.
(snapshottable)
■ Each snapshot-enabled directory can accommodate 65,536
simultaneous snapshots. There is no limit on the number of
snapshot-enabled directories.
■ Administrators can set any directory to be snapshot-enabled.
■ If there are snapshots in a snapshot-enabled directory, it can
cannot be deleted or renamed before all the snapshots are deleted.
■ A directory cannot be snapshot-enabled if one of its ancestors or
descendants is a snapshot-enabled directory.

Limitations
Review the following limitations before you deploy the Hadoop plug-in:
■ Only RHEL and SUSE platforms are supported for Hadoop clusters and backup
hosts.
 Introduction 14
Limitations

■ Delegation Token authentication method is not supported for Hadoop clusters.

■ Hadoop plug-in does not capture Extended Attributes (xattrs) or Access Control
Lists (ACLs) of an object during backup and hence these are not set on the
restored files or folders.
■ For highly available Hadoop cluster, if fail-over happens during a backup or
restore operation, the job fails.
■ If you cancel a backup job manually while the discovery job for a backup
operation is in progress, the snapshot entry does not get removed from the
Hadoop web graphical user interface (GUI).
■ If the CRL expires during the backup of an HTTPS-based Hadoop cluster, the
backup runs partially.
■ If you have multiple CRL-based Hadoop clusters, ensure that you add different
backup hosts for every cluster.
 Chapter 2
Verifying the pre-requisites
and best practices for the
Hadoop plug-in for
NetBackup
This chapter includes the following topics:

■ About deploying the Hadoop plug-in

■ Pre-requisites for the Hadoop plug-in

■ Preparing the Hadoop cluster

■ Best practices for deploying the Hadoop plug-in

About deploying the Hadoop plug-in

The Hadoop plug-in is installed with NetBackup. Review the following topics to
complete the deployment.

Table 2-1 Deploying the Hadoop plug-in

Task Reference

Pre-requisites and See “Pre-requisites for the Hadoop plug-in” on page 16.
requirements

Preparing the See “Preparing the Hadoop cluster” on page 16.

Hadoop cluster
 Verifying the pre-requisites and best practices for the Hadoop plug-in for NetBackup 16
Pre-requisites for the Hadoop plug-in

Table 2-1 Deploying the Hadoop plug-in (continued)

Task Reference

Best practices See “Best practices for deploying the Hadoop plug-in” on page 17.

Verifying the
deployment

Configuring See “About configuring NetBackup for Hadoop” on page 18.

Pre-requisites for the Hadoop plug-in

Ensure that the following pre-requisites are met before you use the Hadoop plug-in:
■ See “Operating system and platform compatibility” on page 16.
■ See “License for Hadoop plug-in for NetBackup” on page 16.

Operating system and platform compatibility

With this release, RHEL and SUSE platforms are supported for Hadoop clusters
and NetBackup backup hosts.
For more information, see the NetBackup Master Compatibility List.

NetBackup server and client requirements

Verify that the following requirements are met for the NetBackup server:

License for Hadoop plug-in for NetBackup

Backup and restore operations using the Hadoop plug-in for NetBackup, require
the Application and Database pack license.
More information is available on how to add licenses.
See the NetBackup Administrator’s Guide, Volume I

Preparing the Hadoop cluster

Perform the following tasks to prepare the Hadoop cluster for NetBackup:
■ Ensure that the Hadoop directory is snapshot-enabled.
To make a directory snapshottable, run the following command on the
NameNodes:
 Verifying the pre-requisites and best practices for the Hadoop plug-in for NetBackup 17
Best practices for deploying the Hadoop plug-in

hdfs dfsadmin -allowSnapshot directory_name

Note: A directory cannot be snapshot-enabled if one of its ancestors or

descendants is a snapshot-enabled directory.

For more information, refer to the Hadoop documentation.

■ Update firewall settings (ensure that the correct port is added along with the
Hadoop credentials) so that the backup hosts can communicate with the Hadoop
cluster.
■ Add the entries of all the NameNodes and DataNodes to the /etc/hosts file
on all the backup hosts. You must add the hostname in FQDN format.
Or
Add the appropriate DNS entries in the /etc/resolv.conf file.
■ Ensure that webhdfs service is enabled on the Hadoop cluster.

Best practices for deploying the Hadoop plug-in

Consider the following when you deploy Hadoop plug-in and configure NetBackup
for Hadoop:
■ Use consistent conventions for hostnames of backup hosts, media servers, and
master server. For example, if you are using the hostname as
hadoop.veritas.com (FQDN format) use the same everywhere.
■ Add the entries of all the NameNodes and DataNodes to the /etc/hosts file
on all the backup hosts. You must add the hostname in FQDN format.
Or
Add the appropriate DNS entries in the /etc/resolv.conf file.
■ Always specify the NameNode and DataNodes in FQDN format.
■ Ping all the nodes (use FQDN) from the backup hosts.
■ Hostname and port of the NameNode must be same as you have specified with
the http address parameter in the core-site.xml of the Hadoop cluster.
■ Ensure the following for a Hadoop cluster that is enabled with SSL (HTTPS):
■ A valid certificate exists on the backup host that contains the public keys
from all the nodes of the Hadoop cluster.
■ For a Hadoop cluster that uses CRL, ensure that the CRL is valid and not
expired.
 Chapter 3
Configuring NetBackup for
Hadoop
This chapter includes the following topics:

■ About configuring NetBackup for Hadoop

■ Managing backup hosts

■ Adding Hadoop credentials in NetBackup

■ Configuring the Hadoop plug-in using the Hadoop configuration file

■ Configuration for a Hadoop cluster that uses Kerberos

■ Configuring NetBackup policies for Hadoop plug-in

■ Disaster recovery of a Hadoop cluster

About configuring NetBackup for Hadoop

Table 3-1 Configuring NetBackup for Hadoop

Task Reference

Adding backup See “Managing backup hosts” on page 19.

hosts
If you want to use NetBackup client as a backup host, you need to
whitelist the NetBackup client on the master server.

See “Whitelisting a NetBackup client on NetBackup master server”

on page 21.
 Configuring NetBackup for Hadoop 19
Managing backup hosts

Table 3-1 Configuring NetBackup for Hadoop (continued)

Task Reference

Adding Hadoop See “Adding Hadoop credentials in NetBackup” on page 22.

credentials in
NetBackup

Configuring the See “Configuring the Hadoop plug-in using the Hadoop configuration
Hadoop plug-in file” on page 23.
using the Hadoop
See “Configuring NetBackup for a highly-available Hadoop cluster”
configuration file
on page 24.

See “Configuring number of threads for backup hosts” on page 28.

Configuring the See “Configuration for a Hadoop cluster that uses Kerberos” on page 34.
backup hosts for
Hadoop clusters
that use Kerberos

Configuring See “Configuring NetBackup policies for Hadoop plug-in” on page 35.
NetBackup policies
for Hadoop plug-in

Managing backup hosts

A backup host acts as a proxy client which hosts all the backup and restore
operations for Hadoop clusters. In case of Hadoop plug-in for NetBackup, backup
host performs all the backup and restore operations without any separate agent
installed on the Hadoop cluster.
The backup host must be a Linux computer. NetBackup 8.1 release supports only
RHEL and SUSE platforms as a backup host.
The backup host can be a NetBackup client or a media server or a master server.
Veritas recommends that you have media server as a backup host.
Consider the following before adding a backup host:
■ For backup operations, you can add one or more backup hosts.
■ For restore operations, you can add only one backup host.
■ A master, media, or client can perform the role of a backup host.
■ Hadoop plug-in for NetBackup is installed on all the backup hosts.
You can add a backup host while configuring BigData policy using either the
NetBackup Administration Console or Command Line Interface.
 Configuring NetBackup for Hadoop 20
Managing backup hosts

For more information on how to create a policy, see See “Creating a BigData backup
policy” on page 35.
To add a backup host
1 In the Backup Selections tab, click New and add the backup host in the
following format:
Backup_Host=<IP_address or hostname>
For more information on how to create a policy, See “Creating a BigData backup
policy” on page 35.

Alternatively, you can also add a backup host using the following command:
For Windows:
<Install_Path>\NetBackup\bin\admincmd\bpplinclude PolicyName -add
"Backup_Host=IP_address or hostname"

For UNIX:
/usr/openv/netbackup/bin/admincmd/bpplinclude PolicyName -add
"Backup_Host=IP_address or hostname"

For more information, See “Using NetBackup Command Line Interface (CLI)
to create a BigData policy for Hadoop clusters ” on page 38.
2 As a best practice, add the entries of all the NameNodes and DataNodes to
the/etc/hosts file on all the backup hosts. You must add the host name in
FQDN format.
OR
Add the appropriate DNS entries in the /etc/resolv.conf file.
 Configuring NetBackup for Hadoop 21
Managing backup hosts

To remove a backup host

1 In the Backup Selections tab, select the backup host that you want to remove.
2 Right click the selected backup host and click Delete.
Alternatively, you can also remove a backup host using the following command:
For Windows:
<Install_Path>\NetBackup\bin\admincmd\bpplinclude PolicyName
-delete "Backup_Host=IP_address or hostname"

For UNIX:
/usr/openv/netbackup/bin/admincmd/bpplinclude PolicyName -delete
'Backup_Host=IP_address or hostname'

Whitelisting a NetBackup client on NetBackup master server

To use the NetBackup client as a backup host, you must whitelist it. Perform the
Whitelisting procedure on the NetBackup master server .
Whitelisting is a security practice used for restricting systems from running software
or applications unless these have been approved for safe execution.
To Whitelist a NetBackup client on NetBackup master server
◆ Run the following command on the NetBackup master server:
■ For UNIX
The directory path to the command:
/usr/openv/netbackup/bin/admincmd/bpsetconfig
bpsetconfig -h masterserver
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 masterserver
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.
 Configuring NetBackup for Hadoop 22
Adding Hadoop credentials in NetBackup

For more information about the APP_PROXY_SERVER = clientname, refer to the

Configuration options for NetBackup clients section in NetBackup Administrator's
Guide, Volume I
Veritas NetBackup Documentation

Configure a NetBackup Appliance as a backup host

Review the following articles if you want to use NetBackup Appliance as a backup
host:
■ Using NetBackup Appliance as the backup host of Hadoop with Kerberos
authentication
For details, contact Veritas Technical Support and have the representative refer
to article 100039992.
■ Using NetBackup Appliance as the backup host with highly-available Hadoop
cluster
For details, contact Veritas Technical Support and have the representative refer
to article 100039990.

Adding Hadoop credentials in NetBackup

To establish a seamless communication between Hadoop clusters and NetBackup
for successful backup and restore operations, you must add and update Hadoop
credentials to the NetBackup master server.
Use the tpconfig command to add Hadoop credentials in NetBackup master server.
For information on parameters to delete and update the credentials using the
tpconfig command, see the NetBackup Commands Reference Guide.

Consider the following when you add Hadoop credentials:

■ For a highly-available Hadoop cluster, ensure that the user for the primary and
fail-over NameNode is the same.
■ Use the credentials of the application server that you will use when configuring
the BigData policy.
■ For a Hadoop cluster that uses Kerberos, specify "kerberos" as
application_server_user_id value.

■ Hostname and port of the NameNode must be same as you have specified with
the http address parameter in the core-site.xml of the Hadoop cluster.
■ For password, provide any random value. For example, Hadoop.
 Configuring NetBackup for Hadoop 23
Configuring the Hadoop plug-in using the Hadoop configuration file

To add Hadoop credentials in NetBackup

1 Run tpconfig command from the following directory paths:
On UNIX systems, /usr/openv/volmgr/bin/
On Windows systems, install_path\Volmgr\bin\
2 Run the tpconfig --help command. A list of options which are required to
add, update, and delete Hadoop credentials is displayed.
3 Run the tpconfig -add -application_server application_server_name
-application_server_user_id user_ID -application_type
application_type -requiredport IP_port_number [-password password
[-key encryption_key]] command by providing appropriate values for each
parameter to add Hadoop credentials.
For example, if you want to add credentials for Hadoop server which has
application_server_name as hadoop1, then run the following command using
the appropriate <user_ID> and <password> details.
tpconfig -add -application_server hadoop1 -application_type hadoop
-application_server_user_id Hadoop -requiredport 50070 -password
Hadoop

Here, the value hadoop specified for -application_type parameter

corresponds to Hadoop.
4 Run the tpconfig -dappservers command to verify if the NetBackup master
server has the Hadoop credentials added.

Configuring the Hadoop plug-in using the Hadoop

configuration file
The backup hosts use the hadoop.conf file to save the configuration settings of
the Hadoop plug-in. You need to create a separate file for each backup host and
copy it to the /usr/openv/netbackup/. You need to manually create the
hadoop.conf file in JSON format. This file is not available by default with the installer.

Note: You must not provide a blank value for any of the parameters, or the backup
job fails.
Ensure that you configure all the required parameters to run the backup and restore
operations successfully.

With this release, the following plug-in settings can be configured:

 Configuring NetBackup for Hadoop 24
Configuring the Hadoop plug-in using the Hadoop configuration file

■ See “Configuring NetBackup for a highly-available Hadoop cluster” on page 24.

■ See “Configuring a custom port for the Hadoop cluster” on page 27.
■ See “Configuring number of threads for backup hosts” on page 28.
■ See “Configuring communication between NetBackup and Hadoop clusters that
are SSL-enabled (HTTPS)” on page 29.
Following is an example of the hadoop.conf file.

Note: For non-HA environment, the fail-over parameters are not required.

{
"application_servers":
{
"hostname_of_the_primary_namenode":
{
"failover_namenodes":
[
{
"hostname":"hostname_of_failover_namenode",
"port":port_of_the_failover_namenode
}
],
"port":port_of_the_primary_namenode
}
},
"number_of_threads":number_of_threads
}

Configuring NetBackup for a highly-available Hadoop cluster

To protect a highly-available Hadoop cluster, when you configure NetBackup for
Hadoop cluster:
■ Specify one of the NameNodes (primary) as the client in the BigData policy.
■ Specify the same NameNode (primary and fail-over) as application server when
you execute the tpconfig command.
■ Create a hadoop.conf file, update it with the details of the NameNodes (primary
and fail-over), and copy it to all the backup hosts. The hadoop.conf file is in
JSON format.
 Configuring NetBackup for Hadoop 25
Configuring the Hadoop plug-in using the Hadoop configuration file

■ Hostname and port of the NameNode must be same as you have specified with
the http address parameter in the core-site.xml of the Hadoop cluster.
■ User name of the primary and fail-over NameNode must be same.
■ Do not provide a blank value for any of the parameters, or the backup job fails.
 Configuring NetBackup for Hadoop 26
Configuring the Hadoop plug-in using the Hadoop configuration file

To update the hadoop.conf file for highly-available Hadoop cluster

1 Update the hadoop.conf file with the following parameters:

{
"application_servers":
{
"hostname_of_primary_namenode1":
{
"failover_namenodes":
[
{
"hostname": "hostname_of_failover_namenode1",
"port": port_of_failover_namenode1
}
],
"port":port_of_primary_namenode1
}
}
}
 Configuring NetBackup for Hadoop 27
Configuring the Hadoop plug-in using the Hadoop configuration file

2 If you have multiple Hadoop clusters, use the same hadoop.conf file to update
the details. For example,

{
"application_servers":
{
"hostname_of_primary_namenode1":
{
"failover_namenodes":
[
{
"hostname": "hostname_of_failover_namenode1",
"port": port_of_failover_namenode1
}
],
"port"::port_of_primary_namenode1
},
"hostname_of_primary_namenode2":
{
"failover_namenodes":
[
{
"hostname": "hostname_of_failover_namenode2",
"port": port_of_failover_namenode2
}
],
"port":port_of_primary_namenode2
}
}
}

3 Copy this file to the following location on all the backup hosts:
/usr/openv/netbackup/

Configuring a custom port for the Hadoop cluster

You can configure a custom port using the Hadoop configuration file. By default,
NetBackup uses port 50070.
 Configuring NetBackup for Hadoop 28
Configuring the Hadoop plug-in using the Hadoop configuration file

To configure a custom port for the Hadoop cluster

1 Update hadoop.conf file with the following parameters:

{
"application_servers": {
"hostname_of_namenode1":{

"port":port_of_namenode1
}
}

2 Copy this file to the following location on all the backup hosts:
/usr/openv/netbackup/

Configuring number of threads for backup hosts

To enhance to the backup performance, you can configure the number of threads
(streams) that each backup host can allow. You can improve the backup
performance either by adding more number of backup hosts or by increasing the
number of threads per backup host.
To decide the number threads consider the following:
■ The default value is 4.
■ You can set minimum 1 and maximum 32 threads for each backup host.
■ Each backup host can have different number of threads configured.
■ When you configure the number of threads, consider the number of cores that
are available and the number of cores you want to use. As a best practice, you
should configure 1 thread per core. For example, if 8 cores are available and
you want to use 4 cores, configure 4 threads.
To update the hadoop.conf file for configuring number of threads
1 Update the hadoop.conf file with the following parameters:

{
"number_of_threads": number_of_threads
}

2 Copy this file to the following location on the backup host:

/usr/openv/netbackup/
 Configuring NetBackup for Hadoop 29
Configuring the Hadoop plug-in using the Hadoop configuration file

Configuring communication between NetBackup and Hadoop clusters

that are SSL-enabled (HTTPS)
To enable communication between NetBackup and Hadoop clusters that are
SSL-enabled (HTTPS), complete the following steps:
■ Update the hadoop.conf file that is located in the /usr/openv/netbackup/
directory on the backup host using the use_ssl parameter in the following format:

{
"application_servers":
{
"hostname_of_namenode1":
{
"use_ssl":true
}
}
}

Configuration file format for SSL and HA:

{
"application_servers":
{
"primary.host.com":
{
"use_ssl":true,
"failover_namenodes":
[
{
"hostname":"secondary.host.com",
"use_ssl":true,
"port":11111
}
]
}
}
}

By default, the value is set to false.

If you use multiple backup hosts, the backup host in that has defined the use_ssl
parameter in the hadoop.conf file is used for communication.
You must define the use_ssl parameter in the hadoop.conf file for every Hadoop
cluster.
 Configuring NetBackup for Hadoop 30
Configuring the Hadoop plug-in using the Hadoop configuration file

■ Use the nbsetconfig command to configure the following NetBackup

configuration options on the access host:
For more information on the configuration options, refer to the NetBackup
Administrator's Guide.

ECA_TRUST_STORE_PATH Specifies the file path to the certificate bundle file that contains
all trusted root CA certificates.

If you have already configured this external CA option, append

the Hadoop CA certificates to the existing external certificate
trust store.

If you have not configured the option, add all the required
Hadoop server CA certificates to the trust store and set the
option.

See “ECA_TRUST_STORE_PATH for NetBackup servers

and clients” on page 31.

ECA_CRL_PATH Specifies the path to the directory where the certificate

revocation lists (CRL) of the external CA are located.

If you have already configured this external CA option, append

the Hadoop server CRLs to the CRL cache.

If you have not configured the option, add all the required
CRLs to the CRL cache and then set the option.

See “ECA_CRL_PATH for NetBackup servers and clients”

on page 31.

HADOOP_SECURE_CONNECT_ENABLED This option affects Hadoop secure communication.

Set this value to YES when you have set the use_ssl as
true in the hadoop.conf file. The single value is applicable
to all Hadoop clusters when use_ssl is set to true.

For Hadoop, secure communication is enabled by default.

This option lets you skip the security certificate validation.

See “HADOOP_SECURE_CONNECT_ENABLED for servers

and clients” on page 32.

HADOOP_CRL_CHECK Lets you validate the revocation status of the Hadoop server
certificate against the CRLs.

The single value is applicable to all Hadoop clusters when

use_ssl is set to true.

By default, the option is disabled.

See “HADOOP_CRL_CHECK for NetBackup servers and

clients” on page 33.
 Configuring NetBackup for Hadoop 31
Configuring the Hadoop plug-in using the Hadoop configuration file

ECA_TRUST_STORE_PATH for NetBackup servers and

clients
The ECA_TRUST_STORE_PATH option specifies the file path to the certificate bundle
file that contains all trusted root CA certificates.
This certificate file should have one or more certificates in PEM format.
Do not specify the ECA_TRUST_STORE_PATH option if you use the Windows certificate
store.
The trust store supports certificates in the following formats:
■ PKCS #7 or P7B file having certificates of the trusted root certificate authorities
that are bundled together. This file may either be PEM or DER encoded.
■ A file containing the PEM encoded certificates of the trusted root certificate
authorities that are concatenated together.
This option is mandatory for file-based certificates.

Table 3-2 ECA_TRUST_STORE_PATH information

Usage Description

Where to use On NetBackup servers or clients.

How to use Use the nbgetconfig and the nbsetconfig commands to

view, add, or change the option.

For information about these commands, see the NetBackup

Commands Reference Guide.

Use the following format:

ECA_TRUST_STORE_PATH = Path to the external CA

certificate

For example: c:\rootCA.pem

Equivalent Administration No equivalent exists in the NetBackup Administration Console

Console property host properties.

ECA_CRL_PATH for NetBackup servers and clients

The ECA_CRL_PATH option specifies the path to the directory where the Certificate
Revocation Lists (CRL) of the external certificate authority (CA) are located.
These CRLs are copied to NetBackup CRL cache. Revocation status of the external
certificate is validated against the CRLs from the CRL cache.
 Configuring NetBackup for Hadoop 32
Configuring the Hadoop plug-in using the Hadoop configuration file

CRLs in the CRL cache are periodically updated with the CRLs in the directory that
is specified for ECA_CRL_PATH based on the ECA_CRL_PATH_SYNC_HOURS option.
If the ECA_CRL_CHECK or HADOOP_CRL_CHECK option is not set to DISABLE (or 0) and
the ECA_CRL_PATH option is not specified, NetBackup downloads the CRLs from
the URLs that are specified in the CRL distribution point (CDP) and uses them to
verify revocation status of the peer host's certificate.

Note: For validating the revocation status of a virtualization server certificate, the
VIRTUALIZATION_CRL_CHECK option is used.

For validating the revocation status of a Hadoop server certificate, the

HADOOP_CRL_CHECK option is used.

Table 3-3 ECA_CRL_PATH information

Usage Description

Where to use On NetBackup servers or clients.

If certificate validation is required for VMware, RHV servers,

Nutanix AHV, or Hadoop, this option must be set on the
NetBackup master server and respective access or backup
hosts, irrespective of the certificate authority that NetBackup
uses for host communication (NetBackup CA or external CA).

How to use Use the nbgetconfig and the nbsetconfig commands

to view, add, or change the option.

For information about these commands, see the NetBackup

Commands Reference Guide.

Use the following format to specify a path to the CRL directory:

ECA_CRL_PATH = Path to the CRL directory

Equivalent Administration No equivalent exists in the NetBackup Administration

Console property Console host properties.

HADOOP_SECURE_CONNECT_ENABLED for servers and

clients
The HADOOP_SECURE_CONNECT_ENABLED option enables the validation of Hadoop
server certificates using its root or intermediate certificate authority (CA) certificates.
 Configuring NetBackup for Hadoop 33
Configuring the Hadoop plug-in using the Hadoop configuration file

Table 3-4 HADOOP_SECURE_CONNECT_ENABLED information

Usage Description

Where to use On all backup hosts.

How to use Use the nbgetconfig and the nbsetconfig commands to view,
add, or change the option.

For information about these commands, see the NetBackup

Commands Reference Guide.

By default, the HADOOP_SECURE_CONNECT_ENABLED is set to YES.

Use the following format to enable certificate validation for Hadoop:

HADOOP_SECURE_CONNECT_ENABLED = YES

Equivalent No equivalent exists in the NetBackup Administration Console

Administration host properties.
Console property

HADOOP_CRL_CHECK for NetBackup servers and clients

The HADOOP_CRL_CHECK option lets you specify the revocation check level for external
certificates of the Hadoop server. Based on the check, revocation status of the
Hadoop server certificate is validated against the certificate revocation list (CRL)
during host communication.
By default, the HADOOP_CRL_CHECK option is disabled. If you want to validate the
revocation status of the Hadoop server certificate against certificate revocation list
(CRL), set the option to a different value.
You can choose to use the CRLs from the directory that is specified for the
ECA_CRL_PATH configuration option or the CRL distribution point (CDP).

See “ECA_CRL_PATH for NetBackup servers and clients” on page 31.

Table 3-5 HADOOP_CRL_CHECK information

Usage Description

Where to use On all backup hosts.

 Configuring NetBackup for Hadoop 34
Configuration for a Hadoop cluster that uses Kerberos

Table 3-5 HADOOP_CRL_CHECK information (continued)

Usage Description

How to use Use the nbgetconfig and the nbsetconfig commands to

view, add, or change the option.

For information about these commands, see the NetBackup

Commands Reference Guide.

Use the following format:

HADOOP_CRL_CHECK = CRL check

You can specify one of the following:

■ DISABLE (or 0) - Revocation check is disabled. Revocation

status of the certificate is not validated against the CRL during
host communication. This is the default value.
■ LEAF (or 1) - Revocation status of the leaf certificate is
validated against the CRL.
■ CHAIN (or 2) - Revocation status of all certificates from the
certificate chain are validated against the CRL.

Equivalent Administration No equivalent exists in the NetBackup Administration Console

Console property host properties.

Example values for the parameters in the bp.conf file

Here is an example of values added in the bp.conf file for a CRL-based Hadoop
cluster that has SSL enabled (HTTPS):

ECA_TRUST_STORE_PATH=/tmp/cacert.pem
ECA_CRL_PATH=/tmp/backuphostdirectory
HADOOP_SECURE_CONNECT_ENABLED=YES/NO
HADOOP_CRL_CHECK=DISABLE / LEAF / CHAIN

Configuration for a Hadoop cluster that uses

Kerberos
For a Hadoop cluster that uses Kerberos, perform the following tasks on all the
backup hosts:
■ Ensure that the Kerberos package is present on all the backup hosts.
■ krb5-workstation package for RHEL
■ krb5-client for SUSE
 Configuring NetBackup for Hadoop 35
Configuring NetBackup policies for Hadoop plug-in

■ Acquire the keytab file and copy it to a secure location on the backup host.
■ Ensure that the keytab has the required principal.
■ Manually update the krb5.conf file with the appropriate KDC server and realm
details.

Note: Enure that default_ccache_name parameter is not set to the

KEYRING:persistent:%{uid} value. You can comment the parameter to use
the default or you can specify a file name such as,
FILE:/tmp/krb_file_name:%{uid}.

■ When you add Hadoop credentials in NetBackup, specify "kerberos" as

application_server_user_id value. See “Adding Hadoop credentials in
NetBackup” on page 22.
■ To run backup and restore operations for a Hadoop cluster that uses Kerberos
authentication, Hadoop needs a valid Kerberos ticket-granting ticket (TGT) to
authenticate with the Hadoop cluster. See “Pre-requisite for running backup and
restore operations for a Hadoop cluster with Kerberos authentication” on page 43.
■ To use Kerberos, the user must be a super user with full access and ownership
of the HDFS. A valid token is required with the user on the backup host.

Configuring NetBackup policies for Hadoop

plug-in
Backup policies provide the instructions that NetBackup follows to back up clients.
For configuring backup policies for Hadoop plug-in for NetBackup, use the BigData
policy as the Policy Type.
You can create BigData policy using either the NetBackup Administration Console
or the Command Line Interface.

Note: Hostname and port of the NameNode must be same as you have specified
with the http address parameter in the core-site.xml of the Hadoop cluster.

For more information on how to create a BigData policy, See “Creating a BigData
backup policy” on page 35.

Creating a BigData backup policy

Use the BigData policy to backup big data applications such as Hadoop clusters.
 Configuring NetBackup for Hadoop 36
Configuring NetBackup policies for Hadoop plug-in

A BigData policy differs from other policies in the following respects:

■ You must specify BigData as the policy type.
■ The entries which are provided in the Clients tab and the Backup Selections
differ based on the application that you want to back up.
■ In the Backup Selections tab, you must specify certain parameters and their
appropriate values.

Creating BigData policy using the NetBackup

Administration Console
If you prefer using the NetBackup Administration Console for creating BigData
policy, you can use either of the following methods:
■ Creating a BigData policy using the Policy Configuration Wizard
■ Creating a BigData policy using the NetBackup Policies utility
The easiest method to set up a BigData policy is to use the Policy Configuration
Wizard. This wizard guides you through the setup process by automatically choosing
the best values for most configurations. Not all policy configuration options are
presented through the wizard. For example, calendar-based scheduling and the
Data Classification setting. After the policy is created, modify the policy in the
Policies utility to configure the options that are not part of the wizard.

Using the Policy Configuration Wizard to create a BigData policy for

Hadoop clusters
Use the following procedure to create a BigData policy with the Policy Configuration
Wizard.
To create a BigData policy with the Policy Configuration Wizard
1 In the NetBackup Administration Console, in the left pane, click NetBackup
Management.
2 In the right pane, click Create a Policy to begin the Policy Configuration
Wizard.
3 Select the type of policy to create:
■ BigData policy : A policy to backup Hadoop data

4 Select the storage unit type for BigData policy.

5 Click Next to start the wizard and follow the prompts.
Click Help on any wizard panel for assistance while running the wizard.
 Configuring NetBackup for Hadoop 37
Configuring NetBackup policies for Hadoop plug-in

Using the NetBackup Policies utility to create a BigData policy for

Hadoop clusters
Use the following procedure to create a BigData policy with the NetBackup Policies
utility.
To create a BigData policy with the NetBackup Policies utility
1 In the NetBackup Administration Console, in the left pane, expand
NetBackup Management > Policies.
2 On the Actions menu, click New > Policy.
3 Type a unique name for the new policy in the Add a New Policy dialog box.
Click OK.
4 On the Attributes tab, select BigData as the policy type.
5 On the Attributes tab, select the storage unit for BigData policy type.
6 On the Schedules tab, click New to create a new schedule.
You can create a schedule for a Full Backup, Differential Incremental
Backup, or Cumulative Incremental Backup for your BigData policy. Once
you set the schedule, Hadoop data is backed up automatically as per the set
schedule without any further user intervention.
7 On the Clients tab, enter the IP address or the host name of the NameNode.
8 On the Backup Selections tab, enter the following parameters and their values
as shown:
■ Application_Type=hadoop
The parameter values are case-sensitive.
■ Backup_Host=IP_address or hostname
The backup host must be a Linux computer. The backup host can be a
NetBackup client or a media server.
You can specify multiple backup hosts.
■ File path or the directory to back up
You can specify multiple file paths.

Note: The directory or folder specified for backup selection while defining
BigData Policy with Application_Type=hadoop must not contain space or
comma in their names.

9 Click OK to save the changes.

 Configuring NetBackup for Hadoop 38
Configuring NetBackup policies for Hadoop plug-in

For more information on using NetBackup for big data applications, refer to the
Veritas NetBackup documentation page.

Using NetBackup Command Line Interface (CLI) to create

a BigData policy for Hadoop clusters
You can also use the CLI method to create a BigData policy for Hadoop.
To create a BigData policy using NetBackup CLI method
1 Log on as an Administrator.
2 Navigate to:.
For Windows:<install_path>\NetBackup\bin\admincmd
For UNIX:/usr/openv/netbackup/bin/admincmd
3 Create a new BigData policy using the default settings.
bppolicynew policyname

4 View the details about the new policy using the -L option.
bpplinfo policyname -L

5 Modify and update the policy type as BigData.

bpplinfo PolicyName -modify -v -M MasterServerName -pt BigData

6 Specify the Application_Type as Hadoop.

For Windows:
bpplinclude PolicyName -add "Application_Type=hadoop"

For UNIX:
bpplinclude PolicyName -add 'Application_Type=hadoop'

Note: The parameter values for Application_Type=hadoop are case-sensitive.

 Configuring NetBackup for Hadoop 39
Configuring NetBackup policies for Hadoop plug-in

7 Specify the backup host on which you want the backup operations to be
performed for Hadoop.
For Windows:
bpplinclude PolicyName -add "Backup_Host=IP_address or hostname"

For UNIX:
bpplinclude PolicyName -add 'Backup_Host=IP_address or hostname'

Note: The backup host must be a Linux computer. The backup host can be a
NetBackup client or a media server or a master server.

8 Specify the Hadoop directory or folder name that you want to backup.
For Windows:
bpplinclude PolicyName -add "/hdfsfoldername"

For UNIX:
bpplinclude PolicyName -add '/hdfsfoldername'

Note: Directory or folder used for backup selection while defining BigData
Policy with Application_Type=hadoop must not contain space or comma in
their names.

9 Modify and update the policy storage type for BigData policy.
bpplinfo PolicyName -residence STUName -modify

10 Specify the IP address or the host name of the NameNode for adding the client
details.
For Windows:
bpplclients PolicyName -M "MasterServerName" -add
"HadoopServerNameNode" "Linux" "RedHat"

For UNIX:
bpplclients PolicyName -M 'MasterServerName' -add
'HadoopServerNameNode' 'Linux' 'RedHat'
 Configuring NetBackup for Hadoop 40
Disaster recovery of a Hadoop cluster

11 Assign a schedule for the created BigData policy as per your requirements.
bpplsched PolicyName -add Schedule_Name -cal 0 -rl 0 -st
sched_type -window 0 0

Here, sched_type value can be specified as follows:

Schedule Type Description

FULL Full backup

INCR Differential Incremental backup

CINC Cumulative Incremental backup

The default value for sched_type is FULL.

Once you set the schedule, Hadoop data is backed up automatically as per
the set schedule without any further user intervention.
12 Alternatively, you can also perform a manual backup for Hadoop data.
For performing a manual backup operation, execute all the steps from Step 1
to Step 11.
13 For a manual backup operation, navigate to /usr/openv/netbackup/bin
Initiate a manual backup operation for an existing BigData policy using the
following command:
bpbackup -i -p PolicyName -s Schedule_Name -S MasterServerName
-t 44

Here, -p refers to policy, -s refers to schedule, -S refers to master server,

and -t 44 refers to BigData policy type.

Disaster recovery of a Hadoop cluster

For disaster recovery of the Hadoop cluster, perform the following tasks:
 Configuring NetBackup for Hadoop 41
Disaster recovery of a Hadoop cluster

Table 3-6 Performing disaster recovery

Task Description

After the Hadoop cluster and nodes are up, Perform the following tasks:
prepare the cluster for operations with
Update firewall settings so that the backup
NetBackup.
hosts can communicate with the Hadoop
cluster.

Ensure that webhdfs service is enabled on

the Hadoop cluster.

See “Preparing the Hadoop cluster”

on page 16.

To establish a seamless communication Use tpconfig command to add Hadoop

between Hadoop clusters and NetBackup for credentials in NetBackup master server.
successful backup and restore operations,
See “Adding Hadoop credentials in
you must add and update Hadoop credentials
NetBackup” on page 22.
to NetBackup master server.

The backup hosts use the hadoop.conf file With this release, the following plug-in
to save the configuration settings of the settings can be configured
Hadoop plug-in. You need to create separate
■ See “Configuring NetBackup for a
file for each backup host and copy it to
highly-available Hadoop cluster”
/usr/openv/netbackup/. You need to
on page 24.
create the hadoop.conf file in JSON format.
■ See “Configuring number of threads for
backup hosts” on page 28.

Update the BigData policy with the original See “Configuring NetBackup policies for
NameNode name. Hadoop plug-in” on page 35.
 Chapter 4
Performing backups and
restores of Hadoop
This chapter includes the following topics:

■ About backing up a Hadoop cluster

■ About restoring a Hadoop cluster

About backing up a Hadoop cluster

Use the NetBackup, Backup, Archive, and Restore console to manage backup
operations.

Table 4-1 Backing up Hadoop data

Task Reference

Process See “Backing up Hadoop data” on page 9.

understanding

(Optional) See “Pre-requisite for running backup and restore operations for a
Complete the Hadoop cluster with Kerberos authentication” on page 43.
pre-requisite for
Kerberos

Backing up a See “Backing up a Hadoop cluster” on page 44.

Hadoop cluster

Best practices See “Best practices for backing up a Hadoop cluster” on page 43.
 Performing backups and restores of Hadoop 43
About backing up a Hadoop cluster

Table 4-1 Backing up Hadoop data (continued)

Task Reference

Troubleshooting For discovery and cleanup related logs, review the following log file on
tips the first backup host that triggered the discovery.

/usr/openv/netbackup/logs/nbaapidiscv

For data transfer related logs, search for corresponding backup host
(using the hostname) in the log files on the master server.

See “Troubleshooting backup issues for Hadoop data” on page 54.

Pre-requisite for running backup and restore operations for a Hadoop

cluster with Kerberos authentication
To run backup and restore operations for a Hadoop cluster that uses Kerberos
authentication, Hadoop needs a valid Kerberos ticket granting-ticket (TGT) to
authenticate with the Hadoop cluster.

Note: During the backup and restore operations, the TGT must be valid. Thus,
specify the TGT validity accordingly or renew it when required during the operation.

Run the following command to generate the TGT:

kinit -k -t /keytab_file_location/keytab_filename principal_name

For example,
kinit -k -t /usr/openv/netbackup/nbusers/hdfs_mykeytabfile.keytab
[email protected]

Also review the configuration-related information. See “Configuration for a Hadoop

cluster that uses Kerberos” on page 34.

Best practices for backing up a Hadoop cluster

Before backing up a Hadoop cluster, consider the following:
■ To backup an entire Hadoop file system provide “/” as the backup selection and
ensure that "/" is snapshot enabled.
■ Before you execute a backup job, ensure for a successful ping response from
the backup hosts to hostname (FQDN) of all the nodes.
■ Update the firewall settings so that the backup hosts can communicate with the
Hadoop cluster.
 Performing backups and restores of Hadoop 44
About restoring a Hadoop cluster

■ Ensure that the local time on the HDFS nodes and the backup host are
synchronized with the NTP server.
■ Ensure that you have valid certificates for a Hadoop cluster that is enabled with
SSL (HTTPS).

Backing up a Hadoop cluster

You can either schedule a backup job or run a backup job manually. See, NetBackup
Administrator's Guide, Volume I
For overview of the backup process, See “Backing up Hadoop data” on page 9.
The backup process comprises of the following stages:
1. Pre-processing: In the pre-processing stage, the first backup host that you
have configured with the BigData policy, triggers the discovery. At this stage,
a snapshot of the complete backup selection is generated. The snapshot details
are visible on the NameNode web interface.
2. Data transfer: During the data transfer process, one child job is created for
each backup host.

3. Post-processing: As part of the post-processing, NetBackup cleans up the

snapshots on NameNode.

About restoring a Hadoop cluster

Use the NetBackup, Backup, Archive, and Restore console to manage restore
operations.
 Performing backups and restores of Hadoop 45
About restoring a Hadoop cluster

Table 4-2 Restoring Hadoop data

Task Reference

Process See “Restoring Hadoop data” on page 10.

understanding

Complete the See “Pre-requisite for running backup and restore operations for a
pre-requisites for Hadoop cluster with Kerberos authentication” on page 43.
Kerberos

Restoring Hadoop ■ See “Using the Restore Wizard to restore Hadoop data on the same
data on the same Hadoop cluster” on page 46.
NameNode or ■ See “Using the bprestore command to restore Hadoop data on the
Hadoop cluster same Hadoop cluster” on page 47.

Restoring Hadoop See “Restoring Hadoop data on an alternate Hadoop cluster” on page 49.
data to an
alternate
NameNode or
Hadoop cluster

This task can be

performed only
using the
bprestore
command.

Best practices See “Best practices for restoring a Hadoop cluster” on page 45.

Troubleshooting See “Troubleshooting restore issues for Hadoop data” on page 59.
tips

Best practices for restoring a Hadoop cluster

When restoring a Hadoop cluster, consider the following:
■ Before you execute a restore job, ensure that there is sufficient space on the
cluster to complete the restore job.
■ Update firewall settings so that the backup hosts can communicate with the
Hadoop cluster.
■ Ensure that you have the valid certificates all the cluster nodes for a Hadoop
cluster that is enabled with SSL (HTTPS).
■ Ensure that you have the valid PEM certificate file on the backup host.
■ Ensure that correct parameters are added in the hadoop.conf file for HTTP or
HTTPS based clusters.
 Performing backups and restores of Hadoop 46
About restoring a Hadoop cluster

■ Ensure that the backup host contains a valid CRL that is not expired.

Restoring Hadoop data on the same Hadoop cluster

To restore Hadoop data on the same Hadoop cluster, consider following:
■ Use the Backup, Archive, and Restore console to initiate Hadoop data restore
operations. This interface lets you select the NetBackup server from which the
objects are restored and the client whose backup images you want to browse.
Based upon these selections, you can browse the backup image history, select
individual items and initiate a restore.
■ The restore browser is used to display Hadoop directory objects. A hierarchical
display is provided where objects can be selected for restore. The objects
(Hadoop directory or files) that make up a Hadoop cluster are displayed by
expanding an individual directory.
■ An administrator can browse for and restore Hadoop directories and individual
items. Objects that users can restore include Hadoop files and folders.

Using the Restore Wizard to restore Hadoop data on the

same Hadoop cluster
This topic describes how to use the Restore Wizard to restore Hadoop data on the
same Hadoop cluster.
To use the Restore Wizard to perform a restore
1 Open the Backup, Archive, and Restore interface.
2 Select the appropriate date range to restore the complete data set.
3 In the Browse directory, specify the root directory ( “/”) as the path to browse.
4 From the File menu (Windows) or Actions menu (UNIX), choose Specify
NetBackup Machines and Policy Type.
5 On the Specify NetBackup Machines and Policy Type wizard, enter the
source and destination details for restore.
■ Specify the Hadoop NameNode as the source for which you want to perform
the restore operation.
From the Source client for restores list, select the required NameNode.
■ Specify the backup host as the destination client.
From the Destination client for restores list, select the required backup
host.
■ On the Specify NetBackup Machines and Policy Type wizard, enter the
policy type details for restore.
 Performing backups and restores of Hadoop 47
About restoring a Hadoop cluster

From the Policy type for restores list, choose BigData as the policy type
for restore.
Click Ok.

6 Go to the Backup History and select the backup images that you want to
restore.
7 In the Directory Structure pane, expand the Directory.
All the subsequent files and folders under the directory are displayed in the
Contents of Selected Directory pane.
8 In the Contents of Selected Directory pane, select the check box for the
Hadoop files that you want to restore.
9 Click Restore.
10 In the Restore Marked Files dialog box, select the destination for restore as
per your requirement.
■ Select Restore everything to its original location if you want to restore
your files to the same location where you performed your backup.
■ Select Restore everything to a different location if you want to restore
your files to a location which is not the same as your backup location.

11 Click Start Restore.

12 Verify the restored files.

Using the bprestore command to restore Hadoop data on

the same Hadoop cluster
The bprestore command lets you restore a backed up or archived file or list of
files. You can also name directories to restore. If you include a directory name,
bprestore restores all files and subdirectories of that directory. You can exclude
a file or a directory path that was previously included in the restore by placing an
exclamation mark (!) in front of the file or the directory path (does not apply to NDMP
restores). For example, the exclude capability is useful if you want to exclude part
of a directory from the restore.
 Performing backups and restores of Hadoop 48
About restoring a Hadoop cluster

To restore Hadoop data on the same location as your backup location

1 Log on as an Administrator or root user based on windows or UNIX system
respectively.
2 Run the following command on the NetBackup master server by providing
appropriate values:
bprestore -S master_server -D backup_host -C client -t 44 -L
progress log -f listfile

Where,
-S master_server

Specifies the name of the NetBackup master server.

-D backup host

Specifies the name of the backup host.

-C client

Specifies a NameNode as a to use for finding backups or archives from which

to restore files. This name must be as it appears in the NetBackup catalog.
-f listfile

Specifies a file (listfile) that contains a list of files to be restored and can be
used instead of the file names option. In listfile, list each file path must be on
a separate line.
-L progress_log

Specifies the name of whitelisted file path in which to write progress information.
-t 44

Specifies BigData as the policy type.

 Performing backups and restores of Hadoop 49
About restoring a Hadoop cluster

To restore Hadoop data on an alternate location

1 Log on as an Administrator.
2 Run the following command on the NetBackup master server by providing
appropriate values:
bprestore -S master_server -D backup_host -C client -t 44 -L
progress log -R rename_file -f listfile

Where,
-S master_server

Specifies the name of the NetBackup master server.

-D backup host

Specifies the name of the backup host.

-C client

Specifies a NameNode as a source to use for finding backups or archives from

which to restore files. This name must be as it appears in the NetBackup
catalog.
-f listfile

Specifies a file (listfile) that contains a list of files to be restored and can be
used instead of the file names option. In listfile, list each file path must be on
a separate line.
-L progress_log

Specifies the name of whitelisted file path in which to write progress information.
-t 44

Specifies BigData as the policy type.

-R rename_file

Specifies the name of a file with name changes for alternate-path restores.
Change the /<source_folder_path> to /<destination_folder_path>

Restoring Hadoop data on an alternate Hadoop cluster

NetBackup lets you restore Hadoop data to another NameNode or Hadoop cluster.
This type of restore method is also referred to as redirected restores.

Note: NetBackup supports redirected restores only using the Command Line
Interface (CLI).
 Performing backups and restores of Hadoop 50
About restoring a Hadoop cluster

Note: Make sure that you have added the credentials for the alternate NameNode
or Hadoop cluster in NetBackup master server and also completed the Whitelisting
tasks on NetBackup master server. For more information about how to add Hadoop
credentials in NetBackup and whitlelisting procedures, See “Adding Hadoop
credentials in NetBackup” on page 22. See “Whitelisting a NetBackup client on
NetBackup master server” on page 21.
 Performing backups and restores of Hadoop 51
About restoring a Hadoop cluster

To perform redirected restore for Hadoop

1 Modify the values for rename_file and listfile as follows:

Parameter Value

rename_file Change /<source_folder_path> to

/<destination_folder_path>
ALT_APPLICATION_SERVER=<alternate
name node>

listfile List of all the Hadoop files to be restored

 Performing backups and restores of Hadoop 52
About restoring a Hadoop cluster

2 Run the bprestore -S master_server -D backup_host -C client -R

rename_file -t 44 -L progress log -f listfile command on the
NetBackup master server using the modified values for the mentioned
parameters in step 1.
Where,
-S master_server

Specifies the name of the NetBackup master server.

-D backup host

Specifies the name of the backup host.

-C client

Specifies a NameNode as a source to use for finding backups or archives from

which to restore files. This name must be as it appears in the NetBackup
catalog.
-f listfile

Specifies a file (listfile) that contains a list of files to be restored and can be
used instead of the file names option. In listfile, list each file path must be on
a separate line.
-L progress_log

Specifies the name of whitelisted file path in which to write progress information.
-t 44

Specifies BigData as the policy type.

-R rename_file

Specifies the name of a file with name changes for alternate-path restores.
Use the following form for entries in the rename file:
change backup_filepath to restore_filepath
ALT_APPLICATION_SERVER=<Application Server Name>

The file paths must start with / (slash).

Note: Ensure that you have whitelisted all the file paths such as
<rename_file_path>, <progress_log_path> that are already not included as
a part of NetBackup install path.
 Chapter 5
Troubleshooting
This chapter includes the following topics:

■ About troubleshooting NetBackup for Hadoop issues

■ About NetBackup for Hadoop debug logging

■ Troubleshooting backup issues for Hadoop data

■ Troubleshooting restore issues for Hadoop data

About troubleshooting NetBackup for Hadoop

issues
Table 5-1 Troubleshooting NetBackup for Hadoop issues

Area References

General logging See “About NetBackup for Hadoop debug logging” on page 54.
and debugging

Backup issues See “Troubleshooting backup issues for Hadoop data” on page 54.

Restore issues See “Troubleshooting restore issues for Hadoop data” on page 59.

To avoid issues See “Best practices for deploying the Hadoop plug-in” on page 17.
also review the
See “Best practices for backing up a Hadoop cluster” on page 43.
best practices
See “Best practices for restoring a Hadoop cluster” on page 45.
 Troubleshooting 54
About NetBackup for Hadoop debug logging

About NetBackup for Hadoop debug logging

NetBackup maintains process-specific logs for the various processes that are
involved in the backup and restore operations. Examining these logs can help you
to find the root cause of an issue.
These log folders must already exist in order for logging to occur. If these folders
do not exist, you must create them.
The log folders reside on the following directories
■ On Windows: install_path\NetBackup\logs
■ On UNIX or Linux: /usr/openv/netbackup/logs

Table 5-2 NetBackup logs related to Hadoop

Log Folder Messages Logs reside on

related to

install_path/NetBackup/logs/bpVMutil Policy configuration Master server

install_path/NetBackup/logs/nbaapidiscv BigData framework, Backup host

discovery, and
Hadoop
configuration file
logs

install_path/NetBackup/logs/bpbrm Policy validation, Media server

backup, and restore
operations

install_path/NetBackup/logs/bpbkar Backup Backup host

install_path/NetBackup/logs/tar Restore and Hadoop Backup host

configuration file

For more details, refer to the NetBackup Logging Reference Guide.

Troubleshooting backup issues for Hadoop data

Review the following topics:
■ See “About NetBackup for Hadoop debug logging” on page 54.
■ See “Backup operation fails with error 6609” on page 55.
■ See “Backup operation failed with error 6618” on page 55.
■ See “Backup operation fails with error 6647” on page 55.
 Troubleshooting 55
Troubleshooting backup issues for Hadoop data

■ See “Extended attributes (xattrs) and Access Control Lists (ACLs) are not backed
up or restored for Hadoop” on page 56.
■ See “Backup operation fails with error 6654” on page 57.
■ See “Backup operation fails with bpbrm error 8857” on page 57.
■ See “Backup operation fails with error 6617” on page 57.
■ See “Backup operation fails with error 6616” on page 57.

Backup operation fails with error 6609

This error is encountered during the following scenarios:
1. The Hadoop plug-in files are deleted or missing from any of the backup hosts
(single or multiple).
Workaround:
Download and install the Hadoop plug-in.
2. The Application_Type details are incorrect.
Workaround:
Use hadoop instead of Hadoop while specifying Application_Type.

Backup operation failed with error 6618

Backup operation failed with error 6618 wherein the following error is displayed:

NetBackup cannot find the file to complete the operation.(6618)

This error is encountered if you have provided an invalid directory as backup

selection.
Workaround:
Provide a valid directory as backup selection in the BigData policy.

Backup operation fails with error 6647

Backup operation fails with error 6647 wherein the following error is displayed:

Unable to create or access a directory or a path. (6647)

This error is encountered in one of the following scenarios:

■ Directory is not snapshot-enabled.
 Troubleshooting 56
Troubleshooting backup issues for Hadoop data

■ Policy is configured to take snapshot of the root folder as backup selection,

whereas one of the child folder is already snapshot-enabled.
■ Policy is configured to take snapshot of a child folder as backup selection,
whereas one of the parent folder is already snapshot-enabled.
■ Policy is configured to take snapshot of a file as backup selection
Workaround:
Nested snapshot-enabled directories are not allowed in Hadoop. If the parent
directory is already a snapshot-enabled, than any other child directory under the
parent directory cannot be enabled for snapshot. For backup selection in Bigdata
policy type, only snapshot-enabled directory must be selected for backup and any
other child directories must not be selected.

Extended attributes (xattrs) and Access Control Lists (ACLs) are not
backed up or restored for Hadoop
Extended attributes allow user applications to associate additional metadata with
a file or directory in Hadoop. By default, this is enabled on Hadoop Distributed File
System (HDFS).
Access Control Lists provide a way to set different permissions for specific named
users or named groups, in addition to the standard permissions. By default, this is
disabled on HDFS.
Hadoop plug-ins do not capture extended attributes or Access Control Lists (ACLs)
of an object during backup and hence these are not set on the restored files or
folders.
Workaround:
If the extended attributes are set on any of the files or directories that is backed up
using the BigData policy with Application_Type = hadoop, then, you have to
explicitly set the extended attributes on the restored data.
Extended attributes can be set using the Hadoop shell commands such as fs
-getfattr and hadoop fs -setfattr.

If the Access Control Lists (ACLs) are enabled and set on any of the files or
directories that is backed up using the BigData policy with Application_Type =
hadoop, then, you have to explicitly set the ACLs on the restored data.

ACLs can be set using the Hadoop shell commands such as hadoop fs -getfacl
and hadoop fs -setfacl.
 Troubleshooting 57
Troubleshooting backup issues for Hadoop data

Backup operation fails with error 6654

This error is encountered during the following scenarios:
■ If Hadoop credentials are not added in NetBackup master server
Workaround:
Ensure that the Hadoop credentials are added in NetBackup master server. Use
the tpconfig command. For more information, See “Adding Hadoop credentials
in NetBackup” on page 22.
■ If Hadoop plug-in files are not installed on backup host.
Workaround:
Ensure that the Hadoop plug-in files are installed on all backup hosts before
you begin backup operation.
■ If a NetBackup client that is used as a backup host is not whitelisted.
Workaround:
Ensure that the NetBackup client that is used as a backup host is whitelisted
before you begin backup operation.
See “Whitelisting a NetBackup client on NetBackup master server” on page 21.

Backup operation fails with bpbrm error 8857

This error is encountered if you have not whitelisted NetBackup client on NetBackup
master server.
Workaround:
You must perform the whitelisting procedure on NetBackup master server if you
want to use the NetBackup client as the backup host. For more information, See
“Whitelisting a NetBackup client on NetBackup master server” on page 21.

Backup operation fails with error 6617

Backup operation failed with error 6617 wherein the following error is displayed:
A system call failed.

Verify that the backup host has valid Ticket Granting Ticket (TGT) in case of
Kerberos enabled Hadoop cluster.
Workaround:
Renew the TGT.

Backup operation fails with error 6616

Backup operation fails with error 6616 wherein the following error is logged:
 Troubleshooting 58
Troubleshooting backup issues for Hadoop data

hadoopOpenConfig: Failed to Create Json Object From Config File.

Workaround:
Verify the hadoop.conf file to ensure that blank values or incorrect syntax is not
used with the parameter values.

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/netbackup/hadoop.conf
■ HBase:/usr/openv/netbackup/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/
 Troubleshooting 59
Troubleshooting restore issues for Hadoop data

Unable to see incremental backup images during restore even though

the images are seen in the backup image selection
This issue occurs when you try to restore incremental backup images and the
Backup Selections list in the backup policy has Backup Selection(s) in a subfolder
of /.
For example:

/data/1
/data/2

Workaround
To view the available data that can be restored from an incremental backup image,
select the related full backup images along with the incremental backup images.

One of the child backup jobs goes in a queued state

One of the child backup jobs goes in a queued state for a scenario with multiple
backup hosts and it keeps waiting for the media server.
Reason:
This issue is seen in the NetBackup Appliance environment where multiple backup
hosts are used and the media server goes in an inactive state.
Workaround:
From the Media and Device Management > Devices > Media servers menu in
NetBackup Administration Console, right-click and Activate the media server that
has the status as Deactivated.

Troubleshooting restore issues for Hadoop data

■ See “Restore fails with error code 2850” on page 60.
■ See “NetBackup restore job for Hadoop completes partially” on page 60.
■ See “Extended attributes (xattrs) and Access Control Lists (ACLs) are not backed
up or restored for Hadoop” on page 56.
■ See “Restore operation fails when Hadoop plug-in files are missing on the backup
host” on page 60.
■ See “Restore fails with bpbrm error 54932” on page 61.
■ See “Restore operation fails with bpbrm error 21296” on page 61.
 Troubleshooting 60
Troubleshooting restore issues for Hadoop data

Restore fails with error code 2850

This error is encountered in the following scenarios:
■ Error:2850 "errno = 62 - Timer expired"
Workaround:
Update firewall settings so that the backup hosts can communicate with the
Hadoop cluster.
■ Requested files are not recovered.
Workaround:
Verify that the backup host has valid Ticket Granting Ticket (TGT) in case of
Kerberos enabled Hadoop cluster.
Renew the TGT.
■ Incorrect values and invalid credentials for the application server.
Workaround:
Ensure that you have correctly entered hostname of destination Hadoop cluster
during restore. This should be same as provided in tpconfig command.

NetBackup restore job for Hadoop completes partially

A restore job completes partially if the restore data is more than the space available
on the Hadoop cluster.
Workaround:
Clean up space on the Hadoop cluster.

Extended attributes (xattrs) and Access Control Lists (ACLs) are not
backed up or restored for Hadoop
For more information about this issue, See “Extended attributes (xattrs) and Access
Control Lists (ACLs) are not backed up or restored for Hadoop” on page 56.

Restore operation fails when Hadoop plug-in files are missing on the
backup host
When a restore job is triggered on a backup host which does not have Hadoop
plug-in files installed, the restore operation fails with the following error:

client restore EXIT STATUS 50: client process aborted

Workaround: Download and install the Hadoop plug-in.

 Troubleshooting 61
Troubleshooting restore issues for Hadoop data

Restore fails with bpbrm error 54932

This error is encountered if the files that you want to restore are not backed up
successfully.
Workaround:
Before you begin the restore operation, make sure that the backup is completed
successfully.
Alternatively, on Activity Monitor menu, click Job Status tab to locate the specific
Job ID and review the error message details.

Restore operation fails with bpbrm error 21296

This error is encountered if you have provided incorrect values for
<application_server_name> while adding Hadoop credentials to NetBackup
master server.
Workaround:
Verify if the details provided for <application_server_name> are correct.

Configuration file is not recovered after a disaster recovery

When you use NetBackup master server as a backup host for high availability with
a Hadoop cluster or a Hadoop cluster that is SSL-enabled (HTTPS) and run a full
catalog recovery, the hadoop.conf configuration file is not recovered.
Create the configuration file manually. Use the following format for the configuration
file:

{
"application_servers":
{
"primary.host.com":
{
"use_ssl":true
"failover_namenodes":
[
{
"hostname":"secondary.host.com",
"use_ssl":true
"port":11111
}
],
"port":11111
 Troubleshooting 62
Troubleshooting restore issues for Hadoop data

}
},
"number_of_threads":5
}
 Index

A N
Adding NetBackup
backup host 19 debug logging 54
server and client requirements 16
B NetBackup Appliance
backup host 22
Backup 44
Hadoop 42
backup 9 O
BigData policy overview
Command Line Interface 38 backup 7
NetBackup Administration Console 36 configuration 7
Policies utility 37 deployment 7
Policy Configuration Wizard 36 installation 7
restore 7
C
compatibility P
supported operating system 16 parallel streaming framework 7
Creating policies
BigData backup policy 35 configuring 35
Preparing
D Hadoop 16
disaster recovery 40
R
H Removing
backup host 19
Hadoop credentials
Restore
adding 22
bprestore command 47
Hadoop 44
K restore 10
Kerberos Restoring
post installation 34 alternate NameNode 49
kerberos Hadoop cluster 46
backup 43
restore 43
T
terms 11
L Troubleshoot
License backup 54
Hadoop 16 troubleshooting
Limitations 13 restore 60
 Index 64

W
Whitelisting
backuphost 21