Recovering OMS Data

Scenario

Manager data needs to be recovered in the following scenarios: data is modified or deleted unexpectedly and needs to be restored. After an administrator performs critical data adjustment in FusionInsight Manager, an exception occurs or the operation has not achieved the expected result. All modules are faulty and become unavailable.

System administrators can create a recovery task in FusionInsight Manager to recover Manager data. Only manual recovery tasks are supported.

• Data recovery can be performed only when the system version is consistent with that of data backup.
• To recover data when the service is running properly, you are advised to manually back up the latest management data before recovering data. Otherwise, the Manager data that is generated after the data backup and before the data recovery will be lost.

Impact on the System

• In the recovery process, the Controller needs to be restarted and FusionInsight Manager cannot be logged in or operated during the restart.
• In the recovery process, all clusters need to be restarted and cannot be accessed during the restart.
• After Manager data recovery, the data, such as system configuration, user information, alarm information, and audit information, that is generated after the data backup and before the data recovery will be lost. This may result in data query failure or cluster access failure.
• After the Manager data is recovered, the system forces the LdapServer of each cluster to synchronize data from the OLadp.

Prerequisites

• To restore data from the remote HDFS, you 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, configure system mutual trust. For details, see Configuring Cross-Manager Cluster Mutual Trust Relationships. If the active cluster is deployed in normal mode, do not configure mutual trust.

• Cross-cluster replication has been configured for the active and standby clusters. For details, see Enabling Cross-Cluster Replication.
• The time of the active cluster and standby cluster must be the same, and the NTP service in the active and standby clusters must use the same time source.
• The status of the OMS resources and the LdapServer instances of each cluster is normal. If the status is abnormal, data recovery cannot be performed.
• The status of the cluster hosts and services is normal. If the status is abnormal, data recovery cannot be performed.
• The cluster host topologies during data recovery and data backup are the same. If the topologies are different, data recovery cannot be performed and you need to back up data again.
• The services added to the cluster during data recovery and data backup are the same. If the topologies are different, data recovery cannot be performed and you need to back up data again.
• The upper-layer applications that depend on the MRS cluster are stopped.

Procedure

1. On FusionInsight Manager, choose O&M > Backup and Restoration > Backup Management.
2. In the Operation column of a specified task in the task list, click More > View History to view historical backup task execution records.

   In the displayed window, locate a specified success record and click View in the Backup Path column to view the backup path information of the task and find the following information:

   • Backup Object specifies the data source of the backup data.
   • Backup Path specifies the full path where the backup files are saved.

     Select the correct item, and manually copy the full path of backup files in Backup Path.

3. On FusionInsight Manager, choose O&M > Backup and Restoration > Restoration Management > Create.
4. Set Task Name to the name of the recovery task.
5. Set Recovery Object to OMS.
6. Select OMS.
7. Set Path Type of OMS to a backup directory type.

   The settings vary according to backup directory types:

   • LocalDir: indicates that the backup files are stored on the local disk of the active management node.

     If you select this value, you need to set Source Path to select the backup file, for example, version_data source_task execution time.tar.gz.

   • LocalHDFS: indicates that the backup files are stored in the HDFS directory of the current cluster.
     If you select this value, you need to set the following parameters:

     • Source Path: indicates the full path of the backup file in HDFS, for example, backup path/backup task name_task creation time/version_data source_task execution time.tar.gz.
     • Cluster for Restoration: Enter the cluster name mapping to the restoration directory.
     • Source NameService Name: indicates the NameService name that corresponds to the backup directory when the recovery task is executed. The default value is hacluster.
   • RemoteHDFS: indicates that the backup files are stored in the HDFS directory of the standby cluster.
     If you select this value, you need to set the following parameters:

     • Source NameService Name: indicates the NameService name of the backup data 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: 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.
     • Source NameNode IP Address: indicates the NameNode service plane IP address of the standby cluster, supporting the active node or standby node.
     • Source Path: indicates the full path of the HDFS directory for storing standby cluster backup data. For example, backup path/backup task name_data source_task creation time/version_data source_task execution time.tar.gz.
     • Source Cluster: Select the cluster of the Yarn queue used by the recovery data from Source Cluster.
     • 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 backup files are stored in the NAS over the NFS protocol.
     If you select NFS, set the following parameters:

     • IP Mode: 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 NAS server IP address.
     • Source Path: indicates the complete path of the backup file on the NAS server. For example, backup path/backup task name_data source_task creation time/version_data source_task execution time.tar.gz.
   • CIFS: indicates that backup files are stored in the NAS over the CIFS protocol.
     If you select CIFS, set the following parameters:

     • IP Mode: 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 NAS server IP address.
     • 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 that is configured when setting the CIFS protocol.
     • Password: indicates the password that is configured when setting the CIFS protocol.
     • Source Path: indicates the complete path of the backup file on the NAS server. For example, backup path/backup task name_data source_task creation time/version_data source_task execution time.tar.gz.
   • SFTP: Indicates that backup files are stored in the server using SFTP.
     If you select SFTP, set the following parameters:

     • IP Mode: 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: Enter the IP address of the server where the backup data is stored.
     • Port: Enter the port number used by the SFTP protocol to connect to the backup server. The default value is 22.
     • Username: Enter the username for connecting to the server using SFTP.
     • Password: Enter the password for connecting to the server using SFTP.
     • Source Path: Enter the full path of the backup file on the backup server. For example, backup path/backup task name_data source_task creation time/version_data source_task execution time.tar.gz.
   • OBS: indicates that the backup files are stored in the OBS directory.
     If you select this value, you need to set the following parameters:

     • Source Path: indicates the full path for storing backup data in OBS. For example, backup path/backup task name_data source_task creation time/version_data source_task execution time.tar.gz.
       

       MRS 3.1.0 and later versions support saving backup files to OBS.

8. Click OK to save the settings.
9. In the recovery task list, locate a created task and click Start in the Operation column to execute the recovery task.
   • 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.

10. Log in to the active and standby management nodes as user omm.
11. Run the following command to restart OMS:

    sh ${BIGDATA_HOME}/om-server/om/sbin/restart-oms.sh

    The command is run successfully if the following information is displayed:

    start HA successfully.

    Run sh ${BIGDATA_HOME}/om-server/om/sbin/status-oms.sh to check whether HAAllResOK of the management node is Normal and whether FusionInsight Manager can be logged in again. If yes, the restart is successful.

12. On FusionInsight Manager, choose Cluster > Name of the desired cluster > Services > KrbServer > More > Synchronize Configuration, click OK, and wait for the KrbServer configuration to be synchronized and the service to be restarted.
13. Choose Cluster > Name of the desired cluster > More > Synchronize Configurations, click OK, and wait for the cluster configuration to be synchronized.
14. On FusionInsight Manager, choose Cluster > Name of the desired cluster > More > Restart. In the displayed dialog box, enter the password of the current login user and click OK. Wait for the cluster to be restarted.