Updated on 2022-11-10 GMT+08:00

Backing Up HBase Metadata

Scenario

To ensure HBase metadata security (including tableinfo files and HFiles) or before a major operation on HBase system tables (such as upgrade or migration), you need to back up HBase metadata to prevent HBase service unavailability caused by HBase system table directory or file damages. The backup data can be used to recover the system if an exception occurs or the operation has not achieved the expected result, minimizing the adverse impacts on services.

You can create a backup task on FusionInsight Manager to back up HBase metadata. Both automatic and manual backup tasks are supported.

Prerequisites

  • If data needs to be backed up to the remote HDFS, you have prepared a standby cluster for data backup. The authentication mode of the standby cluster is the same as that of the active cluster. For other backup modes, you do not need to prepare the standby cluster.
  • If the active cluster is deployed in security mode and the active and standby clusters are not managed by the same FusionInsight Manager, mutual trust has been configured. For details, see Configuring Cross-Manager Mutual Trust Between Clusters. If the active cluster is deployed in normal mode, no mutual trust is required.
  • Time is consistent between the active and standby clusters and the NTP services on the active and standby clusters use the same time source.
  • The backup type, period, policy, and other specifications have been planned based on the service requirements and you have checked whether Data storage path/LocalBackup/ has sufficient space on the active and standby management nodes.
  • If you want to back up data to NAS, you have deployed the NAS server in advance.
  • The fs.defaultFS parameter settings of HBase are the same as those of Yarn and HDFS.
  • If HBase data is stored in the local HDFS, HBase metadata can be backed up to OBS. If HBase data is stored in OBS, data backup is not supported.
  • If you want to back up data to OBS, you have connected the current cluster to OBS and have the permission to access OBS.

Procedure

  1. On FusionInsight Manager, choose O&M > Backup and Restoration > Backup Management.
  2. Click Create.
  3. Set Name to the name of the backup task.
  4. Select the cluster to be operated from Backup Object.
  5. Set Mode to the type of the backup task.

    Periodic indicates that the backup task is executed by the system periodically. Manual indicates that the backup task is executed manually.

    Table 1 Periodic backup parameters

    Parameter

    Description

    Started

    Indicates the time when the task is started for the first time.

    Period

    Indicates the task execution interval. The options include Hours and Days.

    Backup Policy

    • Full backup at the first time and incremental backup subsequently
    • Full backup every time
    • Full backup once every n times
    NOTE:
    • Incremental backup is not supported when Manager data and component metadata are backed up. Only Full backup every time is supported.
    • If Path Type is set to NFS or CIFS, incremental backup cannot be used. When incremental backup is used for NFS or CIFS backup, the latest full backup data is updated each time the incremental backup is performed. Therefore, no new recovery point is generated.

  6. In Configuration, select HBase under Metadata and other data.

    If there are multiple HBase services, all HBase services are backed up by default. You can click Assign Service to specify the services to be backed up.

  7. Set Path Type of HBase to a backup directory type.

    The following backup directory types are supported:
    • LocalDir: indicates that the backup files are stored on the local disk of the active management node and the standby management node automatically synchronizes the backup files.

      The default storage directory is Data storage path/LocalBackup/, for example, /srv/BigData/LocalBackup.

      If you select this option, you need to set the maximum number of replicas to specify the number of backup file sets that can be retained in the backup directory.

    • RemoteHDFS: indicates that the backup files are stored in the HDFS directory of the standby cluster.
      If you select this option, set the following parameters:
      • Destination NameService Name: indicates the NameService name of the standby cluster. You can set it to the NameService name (haclusterX, haclusterX1, haclusterX2, haclusterX3, or haclusterX4) of the built-in remote cluster of the cluster, or the NameService name of a configured remote cluster.
      • IP Mode: indicates the mode of the target IP address. The system automatically selects the IP address mode based on the cluster network type, for example, IPv4 or IPv6.
      • Target NameNode IP Address: indicates the IP address of the NameNode service plane in the standby cluster. It can be of an active or standby node.
      • Target Path: indicates the HDFS directory for storing standby cluster backup data. The storage path cannot be an HDFS hidden directory, such as a snapshot or recycle bin directory, or a default system directory, such as /hbase or /user/hbase/backup.
      • Maximum Number of Backup Copies: indicates the number of backup file sets that can be retained in the backup directory.
      • Queue Name: indicates the name of the Yarn queue used for backup task execution. The name must be the same as the name of the queue that is running properly in the source cluster.
    • NFS: indicates that backup files are stored in the NAS using the NFS protocol.
      If you select this option, set the following parameters:
      • IP Mode: indicates the mode of the target IP address. The system automatically selects the IP address mode based on the cluster network type, for example, IPv4 or IPv6.
      • Server IP Address: indicates the IP address of the NAS server.
      • Server Shared Path: indicates the configured shared directory of the NAS server. (The shared path of the server cannot be set to the root directory, and the user group and owner group of the shared path must be nobody:nobody.)
      • Maximum Number of Backup Copies: indicates the number of backup file sets that can be retained in the backup directory.
    • CIFS: indicates that backup files are stored in the NAS using the CIFS protocol.
      If you select this option, set the following parameters:
      • IP Mode: indicates the mode of the target IP address. The system automatically selects the IP address mode based on the cluster network type, for example, IPv4 or IPv6.
      • Server IP Address: indicates the IP address of the NAS server.
      • Port: indicates the port number used to connect to the NAS server over the CIFS protocol. The default value is 445.
      • Username: indicates the username set when the CIFS protocol is configured.
      • Password: indicates the password set when the CIFS protocol is configured.
      • Server Shared Path: indicates the configured shared directory of the NAS server. (The shared path of the server cannot be set to the root directory, and the user group and owner group of the shared path must be nobody:nobody.)
      • Maximum Number of Backup Copies: indicates the number of backup file sets that can be retained in the backup directory.
    • SFTP: indicates that backup files are stored in the server using the SFTP protocol.

      If you select this option, set the following parameters:

      • IP Mode: indicates the mode of the target IP address. The system automatically selects the IP address mode based on the cluster network type, for example, IPv4 or IPv6.
      • Server IP Address: indicates the IP address of the server where the backup data is stored.
      • Port: indicates the port number used to connect to the backup server over the SFTP protocol. The default value is 22.
      • Username: indicates the username for connecting to the server using the SFTP protocol.
      • Password: indicates the password for connecting to the server using the SFTP protocol.
      • Server Shared Path: indicates the backup path on the SFTP server.
      • Maximum Number of Backup Copies: indicates the number of backup file sets that can be retained in the backup directory.
    • OBS: indicates that backup files are stored in OBS.

      If you select this option, set the following parameters:

      • Target Path: indicates the OBS directory for storing backup data.
      • Maximum Number of Backup Copies: indicates the number of backup file sets that can be retained in the backup directory.

        Only MRS 3.1.0 or later supports data backup to OBS.

  8. Click OK.
  9. In the Operation column of the created task in the backup task list, click More and select Back Up Now to execute the backup task.

    After the backup task is executed, the system automatically creates a subdirectory for each backup task in the backup directory. The format of the subdirectory name is Backup task name_Task creation time, and the subdirectory is used to save data source backup files. The format of the backup file name is Version_Data source_Task execution time.tar.gz.