Backing Up MOTService Service Data

Updated on 2024-12-27 GMT+08:00

View PDF

Scenario

To ensure MOTService service data security routinely or before a major operation on MOTService (such as upgrade or migration), you need to back up MOTService service data. 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 MOTService service data. 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 (with Kerberos authentication enabled) and the active and standby clusters are not managed by the same FusionInsight Manager, mutual trust must be configured. For details, see Configuring Cross-Manager Mutual Trust Between Clusters. If the active cluster is deployed in normal mode (with Kerberos authentication disabled), mutual trust is not required.
The time on the active and standby clusters must be the same, and the NTP service on the active and standby clusters uses the same time source.

You have planned the backup type, period, object, and directory based on service requirements.
The HDFS in the standby cluster has sufficient space. You are advised to save backup files in a custom directory.

Procedure

On FusionInsight Manager, choose O&M > Backup and Restoration > Backup Management.
Click Create.
Set Name to the name of the backup task.
Select the desired cluster from Backup Object.

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	The time when the task is started for the first time.
Period	The task execution interval. Value options include Hours and Days.
Backup Policy	Only Full backup every time is supported. Full backup at the first time and incremental backup subsequently Full backup every time Full backup once every n times

In Configuration, choose MOTService > MOTService under Service data.
Set Path Type of MOTService to a backup directory type.
Currently, the backup directory supports only the RemoteHDFS type. RemoteHDFS indicates the HDFS directory for storing backup files in the standby cluster.
- Destination NameService Name: indicates the NameService name of the standby cluster, for example, hacluster. You can obtain it from the NameService Management page of HDFS of the standby cluster.
- IP Mode: indicates the mode of the target IP address. The system automatically selects an IP address mode based on the cluster network type, for example, IPv4 or IPv6.
- Destination Active NameNode IP Address: indicates the service plane IP address of the active NameNode in the standby cluster.
- Destination Standby NameNode IP Address: indicates the service plane IP address of the standby NameNode in the standby cluster.
- Destination NameNode RPC Port: indicates the value of dfs.namenode.rpc.port in the HDFS basic configuration of the destination cluster.
- 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.
Click OK.
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 Data source_Task creation time, and the subdirectory is used to save latest data source backup files.

Parent topic: Backing Up Data

Previous topic: Backing Up Elasticsearch Service Data

Next topic: Backing Up NameNode Data

Feedback

Was this page helpful?

Helpful Not helpful

Provide feedback

Thank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.

The system is busy. Please try again later.

Which of the following issues have you encountered?

Content is inconsistent with the product UI

Unclear descriptions

Lack of examples or code

Incorrect steps

Can't find what I need

Lack of best practices

Feedback (optional)

0/500

Select at least one type of issue, and enter your comments or suggestions.

Enter a maximum of 500 characters.

Submit Cancel

For any further questions, feel free to contact us through the chatbot.

Chatbot