Restoring Manager Data (MRS 3.x and Later Versions)

Scenarios

Manager data restoration is required in the following scenarios: when data is unexpectedly modified or deleted and requires retrieval; when major data adjustments on FusionInsight Manager cause exceptions in system data or fail to achieve the expected result; and when all modules fail and become unavailable.

Manager data restoration tasks can be created on FusionInsight Manager. The system supports manual data restoration only.

MRS clusters support multiple data path types for restoring Manager data.

LocalDir: indicates that data is restored from the local disk of the active management node.
LocalHDFS: indicates that data is restored from the HDFS directory of the current cluster.
RemoteHDFS: indicates that data is restored from the HDFS directory of the standby cluster.
NFS: indicates that data is restored from the NAS using the NFS protocol.
CIFS: indicates that data is restored from the NAS using the CIFS protocol.
SFTP: indicates that data is restored from the server using the SFTP protocol.
OBS: indicates that data is restored from OBS.

To restore data when the service is running properly, it is recommended that you manually back up the latest management data before performing data restoration. Otherwise, the Manager data that is generated after the data backup and before the data restoration will be lost.

Notes and Constraints

Data restoration can be performed only when the system version is consistent with the version used during data backup.
MRS 3.1.0 and later versions support the storage of Manager data backup files to OBS.

Impact on the System

In the restoration process, the Controller needs to be restarted and FusionInsight Manager cannot be logged in or operated during the restart.
In the restoration process, all clusters need to be restarted and cannot be accessed during the restart.
After data restoration, the data, such as system configuration, user information, alarm information, and audit information, that is generated after the data backup and before the data restoration will be lost. This may result in data query failure or cluster access failure.
Once Manager data is restored, the system automatically forces each cluster's LDAP server to synchronize data from OLDAP.

Prerequisites

To restore data from a remote HDFS, the following conditions must be met:
- A standby cluster has been created for data restoration, and its data has been backed up. For details, see Backing Up Manager Data (MRS 3.x and Later Versions). 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 Mutual Trust Between MRS Clusters. If the active cluster is deployed in normal mode, mutual trust is not required.
- Cross-cluster replication has been configured for the active and standby clusters. For details, see Enabling MRS Inter-Cluster Replication.
- Time is consistent between the active and standby clusters, with the NTP services on both clusters configured to 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 restoration cannot be performed.
The status of the cluster hosts and services is normal. If the status is abnormal, data restoration cannot be performed.
The cluster host topologies during data restoration and data backup are the same. If the topologies are different, data restoration cannot be performed and you need to back up data again.
The services added to the cluster during data restoration and data backup are the same. If the topologies are different, data restoration cannot be performed and you need to back up data again.
The upper-layer applications that depend on the cluster are stopped.

Restoring Manager Data

Log in to MRS Manager.

For details about how to log in to MRS Manager, see Accessing MRS Manager.
Choose O&M > Backup and Restoration > Backup Management.
In the row containing the specified backup task, choose More > View History in the Operation column to display the task's historical execution records.

In the displayed window, locate the desired success record and click View in the Backup Path column to display the task's backup path information and obtain the following details:
- Backup Object: indicates the backup data source.
- Backup Path: indicates the full path where the backup files are stored.
  Locate the correct path, and manually copy the full path of the backup files from the Backup Path column.
Choose O&M > Backup and Restoration > Restoration Management. On the displayed page, click Create.

Figure 1 Creating a restoration task
Set Task Name to the name of the restoration task.
Set Recovery Object to OMS.
Select OMS.

Select a backup directory type for Path Type of OMS.

**Table 1** Path for data restoration
Type	Parameter	Description
LocalDir	Source Path	Backup file to be restored. File name format: Version_Data source_Task execution time.tar.gz
LocalHDFS	Source Path	Full path of the HDFS directory storing backup files. Path format: Backup path/Backup task name_Task creation time/Version_Data source_Task execution time.tar.gz
	Cluster for Restoration	Name of the cluster used to execute the restoration task.
	Source NameService Name	NameService name of the backup directory during restoration task execution. The default value is hacluster.
RemoteHDFS	Source NameService Name	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. You can also set it to the NameService name of a configured remote cluster.
	IP Mode	IP version of the target IP address. The system automatically determines the IP version, such as IPv4 or IPv6, based on the cluster network type.
	Source NameNode IP Address	Service plane IP address of the active or standby NameNode in the standby cluster.
	Source Path	Full path of the HDFS directory storing backup data in the standby cluster. Path format: Backup path/Backup task name_Data source_Task creation time/Version_Data source_Task execution time.tar.gz
	Source Cluster	Cluster containing the YARN queue used by the data you want to restore.
	Queue Name	Name of the YARN queue used for backup task execution. The name must be identical to that of a queue currently running properly in the cluster.
NFS	IP Mode	IP version of the target IP address. The system automatically determines the IP version, such as IPv4 or IPv6, based on the cluster network type.
	Server IP Address	IP address of the NAS server.
	Source Path	Full path of the NAS server directory storing backup files. Path format: Backup path/Backup task name_Data source_Task creation time/Version_Data source_Task execution time.tar.gz
CIFS	IP Mode	IP version of the target IP address. The system automatically determines the IP version, such as IPv4 or IPv6, based on the cluster network type.
	Server IP Address	IP address of the NAS server.
	Port	Port number used by the CIFS protocol to connect to the NAS server. The default value is 445.
	Username	Username configured during CIFS protocol setup.
	Password	Password configured during CIFS protocol setup.
	Source Path	Full path of the NAS server directory storing backup files. Path format: Backup path/Backup task name_Data source_Task creation time/Version_Data source_Task execution time.tar.gz
SFTP	IP Mode	IP version of the target IP address. The system automatically determines the IP version, such as IPv4 or IPv6, based on the cluster network type.
	Server IP Address	IP address of the server where the backup data is stored.
	Port	Port number used by the SFTP protocol to connect to the backup server. The default value is 22.
	Username	Username used to connect to the server over SFTP.
	Password	Password used to connect to the server over SFTP.
	Source Path	Full path of the backup server directory storing backup files. Path format: Backup path/Backup task name_Data source_Task creation time/Version_Data source_Task execution time.tar.gz
OBS (available in MRS 3.1.0 and later)	Source Path	Full path of the OBS directory storing backup files. Path format: Backup path/Backup task name_Data source_Task creation time/Version_Data source_Task execution time.tar.gz

Click OK.
In the restoration task list, locate the row containing the created task, and click Start in the Operation column to execute the restoration task.
- After the restoration is successful, the progress bar is in green.
- After the restoration is successful, the restoration task cannot be executed again.
- If the restoration task fails during the first execution, rectify the fault and click Retry to execute the task again.
Log in to the active and standby management nodes as user omm.
Run the following command to restart OMS:

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

The command is successfully executed 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, OMS is restarted successfully.
On FusionInsight Manager, click Cluster, click the name of the target cluster, and choose Services > KrbServer. On the displayed page, choose More > Synchronize Configuration, click OK, and wait for the KrbServer configuration to be synchronized and the service to be restarted.
Choose Cluster, click the name of the desired cluster, and choose More > Synchronize Configurations, click OK, and wait until the cluster configuration is synchronized successfully.
On FusionInsight Manager, click Cluster, click the name of the target cluster, and choose More > Restart. On the displayed page, enter the password of the current login user, click OK, and wait for the cluster to be restarted.