NetBackup for HBase terminologies
The following table defines the terms you will come across when using NetBackup for protecting HBase cluster.
Table: NetBackup terminologies
Terminology | Definition |
|---|---|
Compound job | A backup job for HBase data is a compound job.
|
Discovery job | When a backup job is executed, first a discovery job is created. The discovery job communicates with the HMaster and gathers information of the block that needs to be backed up and the associated Region servers. 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 Region servers. |
Workload discovery file | During discovery, when the backup host communicates with the HMaster, a workload discovery file is created. The file contains information about the data blocks to be backed up and the associated Region servers. |
Workload distribution file | After the discovery is complete, NetBackup creates a workload 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 Region servers 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. |
BigData policy | The BigData policy is introduced to:
|
Application server | HMaster is referred to as a application server in NetBackup. |
Primary HMaster | In a high-availability scenario, you need to specify one HMaster with the BigData policy and with the tpconfig command. This HMaster is referred as the primary HMaster. |
Fail-over HMaster | In a high-availability scenario, the HMaster other than the primary HMaster that are updated in the |