No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

FusionInsight HD 6.5.0 Administrator Guide 02

Rate and give feedback :
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Restoring Elasticsearch Metadata

Restoring Elasticsearch Metadata

Scenario

Elasticsearch metadata needs to be recovered in the following scenarios: Data is modified or deleted unexpectedly and needs to be restored; after an administrator performs a critical operation (such as upgrade or migration) on ZooKeeper, an exception occurs or the operation has not achieved the expected result, causing all Elasticsearch components to be faulty; data is migrated to a new cluster.

This section describes how to create an Elasticsearch metadata restoration task on FusionInsight Manager. The data can only be manually restored.

  • Data restoration can be performed only when the system version for data backup is consistent with the current system version.
  • To restore Elasticsearch metadata when services are normal, manually back up the latest metadata first and then restore the metadata. Otherwise, the Elasticsearch metadata that is generated after the data backup and before the data recovery will be lost.

Impact on the System

  • Before metadata is restored, the Elasticsearch service is stopped. All upper-layer applications are affected and cannot work properly.
  • After the metadata is restored, the data generated between the backup time and the restoration time is lost.
  • After the metadata is recovered, the Elasticsearch upper-layer applications need to be started.

Prerequisites

  • The directory for storing the Elasticsearch metadata backup files has been checked.
  • The Elasticsearch service has been stopped before the Elasticsearch metadata is restored.
  • Cross-cluster mutual trust has been configured for the active and standby clusters if data needs to be restored to the standby cluster and the active cluster is deployed in security mode. For details, see Configuring Cross-Cluster Mutual Trust Relationships. If the active cluster is deployed in normal mode, cross-cluster mutual trust is not required.
  • Cross-cluster replication has been configured for the active and standby clusters. For details, see Enabling Cross-Cluster Replication.

Procedure

  1. Log in to FusionInsight Manager, and choose O&M > Backup and Restoration > Backup Management.
  2. Locate the specified task, and choose More > View History in the Operation column.

    In the displayed window, locate a specified success record. Click View to open the task execution logs. Find the following information:

    • Backup Object: indicates the backup data source.
    • Backup Path: indicates the path for storing backup files.

      Select the correct item, and copy the full path of backup files.

  3. Choose O&M > Backup and Restoration > Restoration Management.
  4. Click Create.
  5. On the displayed page, set Task Name to the name of a restoration task.
  6. In the Restoration Configuration area, select Elasticsearch under Metadata and other data.

    NOTE:

    If there are multiple Elasticsearch services, specify the Elasticsearch service to be restored.

  7. In the displayed Elasticsearch area, set Path Type to the restoration directory type.

    The settings vary according to backup directory types:

    • LocalDir: Indicates that data is restored from the local disk of the active management node. If you select this parameter, you need to set Source Path to specify the backup files to be restored. The format of the backup file name is backup task name_data source_task execution time.tar.gz.
    • RemoteHDFS: indicates that data is restored from the HDFS directory of the standby cluster. If this parameter is selected, set the following parameters:
      • Target NameNode IP Address: indicates the service plane IP address of the active or standby NameNode in the standby cluster.
      • Source Path: indicates the full path of the HDFS directory for storing standby cluster backup data. The format of the path is backup path/backup task name_data source_task creation time/backup task name_data source_task execution time.tar.gz.
      • 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 cluster.
    • NFS: indicates that data is restored from the NAS using the NFS protocol. If this parameter is selected, set the following parameters:
      • Server IP Address: indicates the IP address of the NAS server.
      • Source Path: indicates the complete path of the backup file on the NAS server. The format of the path is backup path/backup task name_data source_task creation time/backup task name_data source_task execution time.tar.gz.
    • CIFS: indicates that data is restored from the NAS using the CIFS protocol. If this parameter is selected, set the following parameters:
      • Server IP Address: indicates the IP address of the NAS server.
      • Port: indicates the port ID used by the CIFS protocol to connect to the NAS server. The default value is 445.
      • Username: indicates the user name configured when you set the CIFS protocol.
      • Password: indicates the password configured when you set the CIFS protocol.
      • Source Path: indicates the complete path of the backup file on the NAS server. The format of the path is backup path/backup task name_data source_task creation time/backup task name_data source_task execution time.tar.gz.

  8. Click OK to save the configurations.
  9. In the recovery task list, locate the row where the created task resides, and click Execute in the Operation column.

    • After the recovery is successful, the progress bar is in green.
    • After the recovery is successful, the recovery task cannot be executed again.
    • If the recovery task fails during the first execution, rectify the fault and click Retry to execute the task again.

Download
Updated: 2019-05-17

Document ID: EDOC1100074522

Views: 5933

Downloads: 12

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next