Help Center > > User Guide> MRS Manager Operation Guide (Earlier Versions)> Backup and Restoration> Introduction

Introduction

Updated at: Dec 31, 2019 GMT+08:00

Overview

MRS Manager provides backup and recovery for user data and system data. The backup function is provided based on components to back up Manager data (including OMS data and LdapServer data), Hive user data, component metadata saved in DBService, and HDFS metadata.

Backup and recovery tasks are performed in the following scenarios:

  • Routine backup is performed to ensure the data security of the system and components.
  • If the system is faulty, backup data can be used to restore the system.
  • If the active cluster is completely faulty, an image cluster identical to the active cluster needs to be created. Backup data can be used to perform restoration operations.
Table 1 Backing up metadata

Backup Type

Backup Content

OMS

Back up database data (excluding alarm data) and configuration data in the cluster management system.

LdapServer

Back up user information, including the username, password, key, password policy, and group information.

DBService

Back up metadata of the component (Hive) managed by DBService.

NameNode

Back up HDFS metadata.

Principles

Task

Before backup or recovery, you need to create a backup or recovery task and set task parameters, such as the task name, backup data source, and type of directories for saving backup files. When Manager is used to recover the data of HDFS, Hive, and NameNode, the cluster cannot be accessed.

Each backup task can back up different data sources and generate independent backup files for each data source. All the backup files generated in each task form a backup file set, which can be used in recovery tasks. Backup files can be stored on Linux local disks, HDFS of the local cluster, and HDFS of the standby cluster. The backup task provides both full and incremental backup policies. HDFS and Hive backup tasks support the incremental backup policy, while OMS, LdapServer, DBService, and NameNode backup tasks support only the full backup policy.

The rules for task execution are as follows:

  • If a task is being executed, it cannot be executed repeatedly and other tasks cannot be started at the same time.
  • The interval at which a periodic task is automatically executed must be greater than 120s; otherwise, the task is postponed and will be executed in the next period. Manual tasks can be executed at any interval.
  • When a periodic task is to be automatically executed, the current time cannot be 120s later than the task start time; otherwise, the task is postponed and will be executed in the next period.
  • When a periodic task is locked, it cannot be automatically executed and needs to be manually unlocked.
  • Before an OMS, LdapServer, DBService, or NameNode backup task starts, ensure that the LocalBackup partition on the active management node has more than 20 GB available space; otherwise, the backup task cannot be started.
  • When planning backup and recovery tasks, select the data you want to back up or recover according to the service logic, data storage structure, and database or table association. By default, the system creates periodic backup task default that has an execution interval of 24 hours to perform full backup of OMS, LdapServer, DBService, and NameNode data to the Linux local disk.

Specifications

Table 2 Backup and recovery feature specifications

Item

Specifications

Maximum number of backup or recovery tasks

100

Number of concurrent running tasks

1

Maximum number of waiting tasks

199

Maximum size of backup files on a Linux local disk (GB)

600

Table 3 Specifications of the default task

Item

OMS

LdapServer

DBService

NameNode

Backup period

1 hour

Maximum number of backups

2

Maximum size of a backup file

10 MB

20 MB

100 MB

1.5 GB

Maximum size of disk space used

20 MB

40 MB

200 MB

3 GB

Save path of backup data

Data save path/LocalBackup/ on active and standby management nodes

The administrator must regularly transfer the backup data of the default task to an external cluster based on the enterprise's O&M requirements.

Did you find this page helpful?

Submit successfully!

Thank you for your feedback. Your feedback helps make our documentation better.

Failed to submit the feedback. Please try again later.

Which of the following issues have you encountered?







Please complete at least one feedback item.

Content most length 200 character

Content is empty.

OK Cancel