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 Service Data

Restoring Elasticsearch Service Data

Scenario

Elasticsearch service data 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 critical data adjustment) on Elasticsearch, an exception occurs or the operation has not achieved the expected result, causing all modules to be faulty; data is migrated to a new cluster.

This section describes how to create an Elasticsearch service data 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 service data when services are normal, manually back up the latest service data first and then restore the service data. Otherwise, the Elasticsearch service data that is generated after the data backup and before the data recovery will be lost.
  • The number of index shards to be restored must be the same as the number of index shards in the snapshot.
  • During the restoration task execution, the indexes to be restored are automatically closed. After the restoration task is complete, the indexes are automatically opened. If the indexes to be restored do not exist, the indexes are automatically created. Therefore, service operations of the indexes may be affected during the restoration task execution.
  • The Elasticsearch service data restoration needs to invoke the snapshot interface through the EsNode1 instance. Therefore, ensure that all EsNode1 instances in the cluster are in good health status and can receive requests normally.

Impact on the System

  • After the data is restored, the data generated between the backup time and the restoration time is lost.
  • After the data is recovered, the Elasticsearch upper-layer applications need to be started.

Prerequisites

  • The directory for storing the Elasticsearch backup files has been checked.
  • The Elasticsearch upper-layer applications have been stopped.
  • 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.
  • Time of the active and standby clusters is consistent, and the Network Time Protocol (NTP) service in the active and standby clusters use the same time source.

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 manually 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 Service data.
  7. In the displayed Elasticsearch area, set Path Type to the restoration directory type.

    The following restoration directory types are supported:

    • RemoteHDFS: indicates that data is restored from the HDFS directory of the standby cluster. If this parameter is selected, set the following parameters:
      • Source NameNode IP Address: indicates the service plane IP address of the active NameNode in the standby cluster.
      • Source Path: indicates the full HDFS path of a backup file. For example, backup path/backup task name_data source_task creation time.
      • Restoration Point List: Click Refresh and select an Elasticsearch snapshot that has been backed up in the standby cluster.

  8. In the Data Configuration area, select one or more pieces of backed up data for Backup Object based on service requirements.
  9. Specify Force recovery. The value false does not take effect. All backup data is forcibly recovered when there are indexes with the same name. If the index contains new data added after backup, the new data will be lost after the data recovery.
  10. Click Verify to check whether the restoration task is configured correctly.

    • If the specified directory to be recovered does not exist, the verification fails.
    • If the forcible replacement conditions are not met, the verification fails.

  11. Click OK to save the configurations.
  12. 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: 7415

Downloads: 12

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