MAE
V100R024C10
iMaster MAE Product Documentation
(EulerOS, TaiShan)
Issue Date
2024-11-29
HUAWEI TECHNOLOGIES CO., LTD.
Copyright © Huawei Technologies Co., Ltd. 2025. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information, and
recommendations in this document are provided "AS IS" without warranties, guarantees or representations of
any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.
Address:
Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website:
https://www.huawei.com
Email:
support@huawei.com
iMaster MAE Product Documentation (EulerOS, TaiShan)
Contents
Contents...........................................................................................................................................................................................................1
1 Backing Up and Restoring the MAE System....................................................................................................................................2
1.1 Backup and Restoration Solution ...............................................................................................................................................2
1.1.1 Backup Scenarios and Policies ............................................................................................................................................2
1.1.2 Restoration Scenarios and Policies ....................................................................................................................................5
1.1.3 Backup Server Requirements...............................................................................................................................................7
1.1.4 Configuring Backup Parameters.........................................................................................................................................9
1.2 Backing Up Products.....................................................................................................................................................................12
1.2.1 Backing Up Product Data on a Scheduled Basis ........................................................................................................13
1.2.2 Backing Up Product Data ...................................................................................................................................................15
1.2.3 Backing Up Product Applications ....................................................................................................................................15
1.2.4 Backing Up Database Applications .................................................................................................................................16
1.3 Restoring a Product.......................................................................................................................................................................16
1.3.1 Restoring Database Applications.....................................................................................................................................17
1.3.2 Restoring Product Applications ........................................................................................................................................18
1.3.3 Restoring Product Data.......................................................................................................................................................20
2025-02-15
1
iMaster MAE Product Documentation (EulerOS, TaiShan)
1 Backing Up and Restoring the MAE System
This section describes how to back up and restore the MAE system.
Backup and Restoration Solution
This section describes the MAE data backup and restoration solution, backup scenarios, and restoration scenarios.
Backing Up Products
For reliability purposes, you need to periodically back up all data after backup parameters are configured. If the
product is abnormal due to misoperations or other situations, you can use the backup data to restore it.
Restoring a Product
This section describes how to restore MAE system data. When MAE cannot run properly due to data damage, you
can use the backup data to restore MAE to a normal historical running state.
1.1 Backup and Restoration Solution
This section describes the MAE data backup and restoration solution, backup scenarios, and restoration
scenarios.
Backup Scenarios and Policies
Before using the backup function, you are advised to learn the backup scenarios and policies to create backup
tasks properly. In an MAE single-server system, OSMU does not support the backup and restoration of the product
OS.
Restoration Scenarios and Policies
Before using the restoration function, you are advised to learn the restoration scenarios and policies to ensure
that you can create restoration tasks successfully.
Backup Server Requirements
The backup server stores backup data. A backup server that meets certain requirements must be prepared. You
can use a third-party backup server or OSMU node as the backup server.
Configuring Backup Parameters
Backup files are backed up to the corresponding backup server according to the preconfigured backup policy. You
need to configure backup server parameters and backup file storage policies before backing up data on OSMU.
1.1.1 Backup Scenarios and Policies
Before using the backup function, you are advised to learn the backup scenarios and policies to create
backup tasks properly. In an MAE single-server system, OSMU does not support the backup and restoration
of the product OS.
2025-02-15
2
iMaster MAE Product Documentation (EulerOS, TaiShan)
Typical Backup Scenarios and Recommended Policies
Table 1 lists common backup scenarios and backup methods. You can adjust policy items based on site
requirements.
Table 1 Typical backup scenarios and recommended policies
Operations in
Different Scenarios
Scenario
Backup Object
Backup Method
Initial installation and
commissioning
After a product is installed
and commissioned
Applications and
data
Create scheduled tasks for backing
up the product. For details, see
Backing Up Product Data on a
Scheduled Basis .
Manually create tasks for backing
up the product by following
instructions provided in:
Backing Up Product Data
Backing Up Product Applications
Backing Up Database Applications
Modifying a large
amount of
configuration data
For example, after IP
addresses or routes are
changed
Applications and
data
Back up data by following
instructions provided in:
Backing Up Product Data
Backing Up Product Applications
Backing Up Database Applications
Upgrade or patch
installation
Before the OS is upgraded, or
an OS patch is installed
Applications and
data
Back up data by following
instructions provided in:
Backing Up Product Data
Backing Up Product Applications
Backing Up Database Applications
Before product applications
are upgraded
Applications and
data of products
After product applications
have been upgraded
Before the database
application is upgraded, or a
database application patch is
installed
Backing Up Product Data
Backing Up Product Applications
Applications and
data of products
Routine maintenance
Back up data by following
instructions provided in:
Backing Up Product Data
Backing Up Product Applications
After the database application
is upgraded, or a database
application patch is installed
Routine maintenance
Back up data by following
instructions provided in:
Backing Up Database Applications
Applications and
data
Back up data by following
instructions provided in:
Backing Up Product Data
2025-02-15
3
iMaster MAE Product Documentation (EulerOS, TaiShan)
Table 1 Typical backup scenarios and recommended policies
Operations in
Different Scenarios
Scenario
Backup Object
Backup Method
Backing Up Product Applications
Backing Up Database Applications
Storage Thresholds for Backup Files
Backup file storage threshold indicates the maximum number of backup files that can be stored. If the
number of backup files exceeds the storage threshold, the earliest backup files will be deleted
automatically.
Table 2 lists the default number of latest backup files that can be stored.
Table 2 Backup file storage thresholds
Type
Backup File Storage
Threshold
Description
Product data
7
The storage threshold is configurable and must be an integer from 1
to 14. For details, see Configuring Backup Parameters .
Product
application
5
The storage threshold is not configurable.
Database
application
5
The storage threshold is not configurable.
Introduction to MAE System Backup
Table 3 describes the backup contents, backup file paths, and file naming conventions of MAE.
Table 3 Introduction to MAE system backup
Item Backup
Content
Save Path of the Backup Files
Naming
Convention
Stati All files in
c
the
data installation
path of the
MAE
application.
For
example,
the
installation
path of the
MAE static
The backup files of the MAE application data are saved in the folder
/Root directory of the backup server/Global backup parameter
configuration path/MAE-X/static/YYYYMMDDhhmmssmmm/Node
name/APP and the latest five backup files can be saved at most.
Backup files in the
backup folder are
named in the
YYYYMMDDhhmm
ssmmm.tar.gz
format.
2025-02-15
YYYYMMDDhhmmssmmm indicates the start time of the backup
task.
For example,
/export/home/osmubackup/osmubackup/backup/ossbackup/MAE1/static/20160504153020000/MAE–Master/APP is the name of the
backup folder generated at 15:30:20:000 on May 4, 2016 for backing
up static data of the MAE–Master node whose alias is MAE-1.
4
iMaster MAE Product Documentation (EulerOS, TaiShan)
Table 3 Introduction to MAE system backup
Item Backup
Content
Save Path of the Backup Files
Naming
Convention
The backup files of the database data are saved in the folder /Root
directory of the backup server/Global backup parameter
Naming
conventions for the
backup files in the
backup folder:
data is
/opt/oss.
Stati GaussDB T
c
V3
data database
configuration
path/management/management/YYYYMMDDhhmmssmmm/Node
name and the latest five backup files can be saved at most.
YYYYMMDDhhmmssmmm indicates the start time of the backup
management.tar.gz
task.
For example,
/export/home/osmubackup/osmubackup/backup/ossbackup/manage
ment/management/20160504153020000/MAE–Master is the name of
the backup folder generated at 15:30:20:000 on May 4, 2016 for
backing up database data of the MAE–Master node.
Prod Database
uct
data
data
For details,
see MAE
Databases .
The backup files of the product data are saved in the folder /Root
directory of the backup server/Global backup parameter
configuration path/MAE-X/dynamic/YYYYMMDDhhmmssmmm/Node
name/Service name and the latest seven backup files are saved by
default.
YYYYMMDDhhmmssmmm indicates the start time of the backup
MAE
task.
system files
For example,
Some files /export/home/osmubackup/osmubackup/backup/ossbackup/MAEin the
1/dynamic/20180504153020000/MAE–Master/MAE–TSService is the
/export/ho name of the folder generated at 15:30:20:000 on May 4, 2018 for
me/MAE
backing up data of MAE–TSService of the MAE–Master node on
alias and
MAE-1.
/export/ho
me/sysm
directories
Backup data for
each service is
stored in a
subfolder named
after the service in
the backup file
folder.
1.1.2 Restoration Scenarios and Policies
Before using the restoration function, you are advised to learn the restoration scenarios and policies to
ensure that you can create restoration tasks successfully.
Typical Restoration Scenarios and Recommended Policies
Table 1 lists common restoration scenarios and recommended policies. You can adjust policy items based
on site requirements.
Table 1 Recommended policies
Operations in different scenarios
Recommended Policy
Database fault
For details, see Table 2.
2025-02-15
5
iMaster MAE Product Documentation (EulerOS, TaiShan)
Table 1 Recommended policies
Operations in different scenarios
Recommended Policy
Other faults related to product application, product data, or upgrade
For details, see Table 3.
Table 2 Typical restoration scenarios and recommended policies for database faults
Scenario
Object
Restoration Method
The files of the database where the product nodes reside
are damaged, but the OS is running properly on database
nodes.
The product
Perform the following
database application operations in sequence:
Restoring Database
Applications
Restoring Product Data
Table 3 Typical restoration scenarios and recommended policies for other faults
Operations in
different scenarios
Scenario
Object
Product application The product application is abnormal, but the Product
fault
OS of the product is normal.
applications
NOTE:
Restoration Method
Perform the following
operations in sequence:
This operation is not affected by the
Restoring Product
Applications
deployment mode of OSMU and the
Restoring Product Data
product node.
Product data fault
The database instance is normal, but the
product is abnormal due to product data
errors.
Product data
Restoring Product Data
Database
applications
Perform the following
operations in sequence:
NOTE:
This operation is not affected by the
deployment mode of OSMU and the
product node.
Upgrade or patch
rollback
OSMU cannot be used due to incorrect
database application upgrade operations.
Restoring Database
Applications
Restoring Product Data
OSMU cannot be used due to incorrect
product application upgrade operations.
Product
applications
Perform the following
operations in sequence:
Restoring Product
Applications
Restoring Product Data
2025-02-15
6
iMaster MAE Product Documentation (EulerOS, TaiShan)
1.1.3 Backup Server Requirements
The backup server stores backup data. A backup server that meets certain requirements must be prepared.
You can use a third-party backup server or OSMU node as the backup server.
Table 1 lists the requirements for the backup server.
• If the OSMU node is used as the backup server:
• If OSMU node is damaged, the backup data stored on OSMU node may also be damaged, which
hinders the data restoration of OSMU.
• During the OS restoration, the backup file cannot be obtained because the OS will be restarted. If
OSMU is deployed in single-server mode, OSMU node OS cannot be restored.
• If a third-party server is used as the backup server:
• NAT cannot be configured between the third-party backup server and OSMU.
• Ensure that the third-party server can properly communicate with OSMU and all product nodes
using the IP address of the OSS_Self_Maintenance plane. Alternatively, you can use OSMU as the
backup server because OSMU can properly communicate with all its managed product nodes.
• During the backup or restoration, ensure that at least one backup server is accessible.
Table 1 Backup server requirements
Item
Requirement
SFTP
requirements
The server supports the SFTP protocol. The username and password of the backup server
that uses SFTP to transfer files are available.
The user who logs in to the backup server using SFTP has read and write permissions to the
SFTP shared directory.
The settings of the SFTP connection parameters MaxSessions, MaxStartups, MaxAuthTries,
and LoginGraceTime meet the connection requirements. It is recommended that the
parameters be set as follows for a Linux-based backup server:
MaxSessions: 500
MaxStartups: 2000
MaxAuthTries: 6
LoginGraceTime: 120
The backup server supports secure key exchange algorithms, for example, diffie-hellmangroup-exchange-sha256, diffie-hellman-group14-sha256, diffie-hellman-group15-sha512,
diffie-hellman-group16-sha512, diffie-hellman-group17-sha512, diffie-hellman-group18sha512, ecdh-sha2-nistp256, ecdh-sha2-nistp384, and ecdh-sha2-nistp521.
The custom Banner cannot contain password (case-insensitive). Otherwise, backup tasks may
fail.
Port
The default port number of the backup server is 22, and the port number range is 1 to
65535.
User name
The username cannot be empty.
The username contains a maximum of 32 characters.
2025-02-15
7
iMaster MAE Product Documentation (EulerOS, TaiShan)
Table 1 Backup server requirements
Item
Requirement
The username cannot contain spaces, newline characters, carriage return characters, tab
characters, form feeds, or special characters <>&"',;$()`\|/@
Password
To ensure the security of backup server users, you are advised to periodically change the
password for the backup server users. The basic requirements of the password are as follows:
The password must contain 1 to 64 characters. It is recommended that the password contain
8 to 64 characters. Plan a password based on the server type.
The password must contain at least one of the following: lowercase letters, uppercase letters,
digits, and special characters ~@#%=^*-_+[{}]:./?! (Starting with ! is not allowed.)
Ensure that the correct password is obtained. The user may be locked if an incorrect
password is entered. Enter the password with caution.
Private key
password
To ensure the security of backup server users, you are advised to periodically change the
passphrase for the backup server users. The basic requirements of the passphrase are as
follows:
The passphrase must contain 1 to 64 characters. It is recommended that the passphrase
contain 8 to 64 characters. Plan a passphrase based on the server type.
The passphrase must contain at least one of the following: lowercase letters, uppercase
letters, digits, and special characters ~@#%=^*-_+[{}]:./?! (Starting with ! is not allowed.)
Ensure that the correct passphrase is obtained. The user may be locked if an incorrect
passphrase is entered. Enter the passphrase with caution.
Key file
To ensure the security of backup server users, you are advised to periodically update the key
file of the backup server.
The key file to be imported must meet the following rules:
The key file cannot exceed 4 KB, and only one file can be uploaded.
The key file name must meet the following requirements:
The file name must contain at least one of the following: letters, digits, hyphens (-), and
underscores (_).
The file name can contain a maximum of 60 characters.
The file name extension can be .key, .pem, or no extension.
Backup path
The path is a relative path on the backup server relative to the home directory of the SFTP
user. The path cannot start with a slash (/) or hyphen (-), and can contain only letters, digits,
hyphens (-), and underscores (_). The path can contain a maximum of 60 characters.
If the OSMU server is used as the backup server, the backup path is fixedly set to
backup/ossbackup (relative path).
Connectivity
Data can be transferred between the backup server and all nodes in SFTP or NFS mode if the
backup server is a standard or local backup server.
If the backup server is a third-party backup server, only the connectivity between OSMUM01
and the backup server and between OSMUM02 and the backup server is verified.
Backup server
IP address
2025-02-15
If OSMU is deployed in cluster mode, use the fixed IP address instead of the floating IP
address of the backup server to configure the backup server.
8
iMaster MAE Product Documentation (EulerOS, TaiShan)
Table 1 Backup server requirements
Item
Requirement
Disk space
1.2 TB or above
NOTE:
You are advised to periodically clear the disk space. Otherwise, the upload and download speed
of backup files may decrease due to high disk usage, and the backup and restoration tasks may
take a long time or fail.
Bandwidth
Recommended: 1.5 Gbit/s
Minimum: 1 Gbit/s
1.1.4 Configuring Backup Parameters
Backup files are backed up to the corresponding backup server according to the preconfigured backup
policy. You need to configure backup server parameters and backup file storage policies before backing up
data on OSMU.
Prerequisites
• You have logged in to OSMU. For details, see Logging In to OSMU .
• For the SFTP data transfer mode, you have obtained the IP address of the backup server, the user
name and password of the SFTP protocol, and the storage path for the backup files.
• If the OSMU server is used as a backup server, you have obtained the IP address of the
OSS_Self_Maintenance plane of the OSMU node and the passwords for the sopuser and
osmubackup users.
• If a third-party server is used as the backup server:
• You have obtained the IP address of the third-party server, SFTP user name and password,
and storage path of backup files.
• Ensure that the IP address of the third-party server can communicate with the service IP
address of the product.
• Ensure that you can access the SFTP shared directory after connecting to the third-party
server in SFTP mode.
Context
A maximum of 10 backup servers can be added to OSMU. If multiple backup servers are configured in the
same region, the same backup files are saved on all the backup servers. If a backup server is faulty, other
backup servers can still provide backup files for data restoration.
Precautions
2025-02-15
9
iMaster MAE Product Documentation (EulerOS, TaiShan)
• For the NFS transfer mode, backup server parameters are automatically adapted. No manual
configuration is required.
• If the backup server transfers data using SFTP, the system performs SFTP fingerprint authentication
when you verify the connectivity to the server. You can verify the SFTP fingerprint authentication
information to improve the data security of OSMU.
• If multiple sites share the same backup server, the backup paths for these sites must be unique.
Otherwise, backup or restoration tasks will be abnormal, and the backup file information synchronized
to OSMU will be different from the actual information.
• If the parameters of the backup server are changed, update the parameters in the Backup Server area
and back up the application and data of OSMU again. Otherwise, OSMU cannot be backed up or
restored. For details, see Backing Up Products . In a remote cold backup scenario, update the
parameters of the SFTP backup server on the HA > Remote High Availability System > Manage Cold
Backup System page.
Procedure
1. On the main menu of OSMU, choose Backup and Restore > Configuration > Configure Backup
Parameters.
2. Configure backup parameters.
• Configure backup server parameters.
a. In the Backup Server area, click Add Backup Server, and perform related operations as
prompted by referring to the backup server information obtained in "Prerequisites."
b. On the Add Backup Server page, configure the backup server information by referring to
Table 1.
Table 1 Backup parameters
Parameter
Using OSMU as the Backup Server
Using a Third-Party Server as the Backup
Server
Backup server
IP address
IP address of the OSS_Self_Maintenance plane
of OSMU at the current site.
IP address of the third-party server.
Port number
SFTP port number of the backup server at the
standby site. The default value is 22. Set this
parameter based on the site requirements.
SFTP port number of the third-party
server. The default value is 22.
Authentication
mode
Set this parameter based on the site
requirements.
Set this parameter based on the site
requirements.
• Password: The authentication mode of the
third-party server is password authentication.
2025-02-15
Ensure that the IP address of the thirdparty server can communicate with the IP
address of the OSS_Service plane of the
MAE server.
• Password: The authentication mode of the
third-party server is password
authentication.
10
iMaster MAE Product Documentation (EulerOS, TaiShan)
Table 1 Backup parameters
Parameter
Using OSMU as the Backup Server
Using a Third-Party Server as the Backup
Server
• Key: The authentication mode of the third-party• Key: The authentication mode of the
server is key authentication.
third-party server is key authentication.
Username
Set this parameter to osmubackup.
SFTP user name of the third-party server.
Password
Password for the osmubackup user. Set this
parameter based on the site requirements.
Set this parameter to the password for the
SFTP user of the third-party server.
This parameter needs to be set only when
Authentication mode is set to Password.
This parameter needs to be set only when
Authentication mode is set to Password.
Private key file of the OSMU server. The file
name extension can be .key, .pem, or empty. For
details about how to obtain key files, see
Obtaining the Public and Private Key Files of a
Backup Server .
Private key file of the third-party server.
The file name extension can be .key, .pem,
or empty. For details about how to obtain
key files, see Obtaining the Public and
Private Key Files of a Backup Server .
This parameter needs to be set only when
Authentication mode is set to Key.
This parameter needs to be set only when
Authentication mode is set to Key.
Password for the key file.
Password for the key file.
This parameter needs to be set only when
Authentication mode is set to Key.
This parameter needs to be set only when
Authentication mode is set to Key.
Set this parameter to backup/ossbackup.
Path for storing backup files. Generally,
the path is an SFTP shared directory. In a
remote cold backup scenario, the backup
paths at the active and standby sites must
be different.
Key file
Passphrase
Backup path
Click
next to Backup path to set the backup path for the backup server, and then
click OK.
The backup path is a relative path of the SFTP shared directory and must be a subdirectory in the
SFTP shared directory.
c. After the backup server information is configured, click OK to save the configuration.
d. In the Backup Server area, click
to check whether the backup server information is
correct.
e. If OSMU detects that there are nodes where SFTP fingerprint authentication has not been
performed, perform the operations as required:
• (Recommended) If you click OK in the Warning dialog box, OSMU automatically
performs the SFTP fingerprint authentication on the nodes.
2025-02-15
11
iMaster MAE Product Documentation (EulerOS, TaiShan)
• If you click Cancel in the Warning dialog box that is displayed, log in to each node
where the SFTP fingerprint authentication has not been performed and manually
perform the authentication.
• If the default storage thresholds provided for product data backup files cannot meet
requirements, configure a storage policy for product data backup files.
In the Storage Strategy for the Product Data Backup Files area, perform operations by referring
to Table 2.
Table 2 Modifying storage thresholds for backup files
Task
Operation
Modifying the storage
thresholds for products
Modify the thresholds one by Select the products for which you want to modify
one or in batches.
the backup file storage threshold.
Click Modify Product Threshold.
In the dialog box that is displayed, configure the
number of backup files and click Save.
• If the default storage threshold of the OSMU backup files cannot meet the actual requirements,
perform the following operations to set the storage policy for the OSMU backup files.
a. In the Storage Strategy for the OSMU Backup Files area, set the number of backup files.
b. Click Save.
1.2 Backing Up Products
For reliability purposes, you need to periodically back up all data after backup parameters are configured.
If the product is abnormal due to misoperations or other situations, you can use the backup data to restore
it.
Backing Up Product Data on a Scheduled Basis
When a product is running properly, you can create scheduled tasks for backing up the product data, applications,
and database applications so that the backup data can be periodically saved to the backup server. If the product
becomes abnormal due to misoperations or other situations, you can restore the product to the state at a certain
time point.
Backing Up Product Data
Before a configuration file that affects product functions is modified, and before and after the product is
upgraded, you can use OSMU to manually back up the product data. This ensures that the product can be
restored by using the backup data if the product is abnormal due to misoperations or other situations.
Backing Up Product Applications
After the initial installation of the product application or before and after the upgrade of the product application,
you can back up the product application in real time on OSMU. If a product application runs abnormally or fails
to be upgraded and needs to be rolled back to the previous state, you can use the backup file to restore the
product application to the state before the backup.
2025-02-15
12
iMaster MAE Product Documentation (EulerOS, TaiShan)
Backing Up Database Applications
After the initial installation of the database application or before and after the upgrade of the database
application, you can back up the database application, that is, the database data that does not change in real
time when the system runs, on OSMU. If the database is not running properly because a file in the database
application is damaged or lost, but the OS of the node is running properly, you can use the backup file to restore
the database application to the state before the backup.
1.2.1 Backing Up Product Data on a Scheduled Basis
When a product is running properly, you can create scheduled tasks for backing up the product data,
applications, and database applications so that the backup data can be periodically saved to the backup
server. If the product becomes abnormal due to misoperations or other situations, you can restore the
product to the state at a certain time point.
Prerequisites
• You have logged in to OSMU. For details, see Logging In to the OSMU Client .
• The backup parameters have been configured. For details, see Configuring Backup Parameters .
• When backing up the product data and database applications, ensure that the database instances of
all the nodes are in the Running state. For details, see Monitoring Databases .
• When backing up the product data, ensure that the product deployment status of the product is
Installed. For details, see Querying the Deployment Status of a Product .
• The time among nodes is consistent. Otherwise, the scheduled task for backing up the product data
fails. For details, see Changing the Time Zone and Time of the MAE Server .
Context
• When the product information is imported on OSMU for the first time, OSMU creates a default
scheduled task for backing up the product data. After the product installation is complete and the
backup parameters are configured, the task automatically backs up the product data. When the
number of products, nodes or service instances is changed due to upgrade or capacity expansion, the
modified product data is automatically backed up by the scheduled backup task after the upgrade or
capacity expansion is complete.
Precautions
• You are advised to stagger the start time of each scheduled backup task, for example, at an interval of
two hours. For details about the execution sequence of backup tasks, see Backup Scenarios and
Policies .
2025-02-15
13
iMaster MAE Product Documentation (EulerOS, TaiShan)
• To prevent high resource usage caused by conflicts between scheduled backup tasks and NE data
synchronization, stagger the execution period of the scheduled backup tasks and that of NE data
synchronization or service provisioning.
• If the interval for scheduled backup is excessively long, service data may be lost during data
restoration. Specify a backup interval as required.
• For product data, you are advised to set the backup interval to 24 hours.
• For product applications, database applications, and operating systems, you are advised to set the
backup interval to 720 hours.
• In a remote cold backup scenario, scheduled tasks for backing up product data are executed only at
the active site, and scheduled tasks for backing up product OSs and applications can be executed at
both the active site and standby site.
Procedure
1. On OSMU, choose Backup and Restore > Configuration > Configure Scheduled Backup Task from the
main menu.
2. On the Configure Scheduled Backup Task page, Click Create.
3. Perform operations according to Table 1.
Table 1 Backing up data
Backup Data
Operation
Description
Product data
In the Backup Object area, select the MAE
or MAE product, click next to the
product to expand the product, and select
the service groups under the MAE product.
If the Analytics component data needs
to be backed up, select the PAIR-TSP
Database, PAIR-TSP HDFS, and PAIRTSP Hive service groups at the same
time.
Product
application
In the Backup Object area, select the MAE
product.
-
Database
application
4. In the Scheduled Parameters area, perform operations by referring to Table 2.
Table 2 Backing up products on a scheduled basis
Task
Operation
One-time backup at a specified time point
Select One-Time and perform operations as prompted.
Periodic backup within a specified period
Select Periodic and perform operations as prompted.
• After a scheduled backup task is created successfully, you can enable or disable the task in the Enabled
State column.
2025-02-15
14
iMaster MAE Product Documentation (EulerOS, TaiShan)
• If you need to execute a task with higher priority, you can click
in the Operation column of the task
whose progress is less than 90% in the task list to forcibly stop the scheduled backup task.
1.2.2 Backing Up Product Data
Before a configuration file that affects product functions is modified, and before and after the product is
upgraded, you can use OSMU to manually back up the product data. This ensures that the product can be
restored by using the backup data if the product is abnormal due to misoperations or other situations.
Prerequisites
• You have logged in to OSMU. For details, see Logging In to the OSMU Client .
• The backup parameters have been configured. For details, see Configuring Backup Parameters .
• When backing up the product data and database applications, ensure that the database instances of
all the nodes are in the Running state. For details, see Monitoring Databases .
• When backing up the product data, ensure that the product deployment status of the product is
Installed. For details, see Querying the Deployment Status of a Product .
• The time among nodes is consistent. Otherwise, the scheduled task for backing up the product data
fails. For details, see Changing the Time Zone and Time of the MAE Server .
Precautions
• To ensure product data accuracy during backup, do not manually back up data during service
provisioning.
• In a remote cold backup scenario, the task for backing up product data can be executed only at the
active site.
Procedure
1. On OSMU, choose Backup and Restore > Data Backup > Back Up Product Data from the main menu.
2. On the Back Up Product Data page, select an MAE product, or select a service group under the MAE
product after click
next to the product. Then, complete operations as prompted.
1.2.3 Backing Up Product Applications
After the initial installation of the product application or before and after the upgrade of the product
application, you can back up the product application in real time on OSMU. If a product application runs
abnormally or fails to be upgraded and needs to be rolled back to the previous state, you can use the
backup file to restore the product application to the state before the backup.
Prerequisites
2025-02-15
15
iMaster MAE Product Documentation (EulerOS, TaiShan)
• You have logged in to OSMU. For details, see Logging In to the OSMU Client .
• The backup parameters have been configured. For details, see Configuring Backup Parameters .
Context
In a remote cold backup system, tasks for backing up product applications can be executed at both the
active site and standby site.
Procedure
1. On the main menu of OSMU, choose Backup and Restore > Data Backup > Back Up Product
Application.
On the Back Up Product Application page, perform operations as prompted.
1.2.4 Backing Up Database Applications
After the initial installation of the database application or before and after the upgrade of the database
application, you can back up the database application, that is, the database data that does not change in
real time when the system runs, on OSMU. If the database is not running properly because a file in the
database application is damaged or lost, but the OS of the node is running properly, you can use the
backup file to restore the database application to the state before the backup.
Prerequisites
• You have logged in to OSMU. For details, see Logging In to the OSMU Client .
• The backup parameters have been configured. For details, see Configuring Backup Parameters .
Context
In a remote cold backup scenario, tasks for backing up database applications can be executed at both the
active site and standby site.
Procedure
1. On the main menu of OSMU, choose Backup and Restore > Data Backup > Back Up Database
Application.
On the Back Up Database Application page, perform operations as prompted.
1.3 Restoring a Product
This section describes how to restore MAE system data. When MAE cannot run properly due to data
damage, you can use the backup data to restore MAE to a normal historical running state.
Restoring Database Applications
2025-02-15
16
iMaster MAE Product Documentation (EulerOS, TaiShan)
If a database application is abnormal due to corruption, but the OS of the emergency system node runs properly,
you can restore the database application data by following the instructions provided in this section.
Restoring Product Applications
If the product applications are abnormal due to damaged file of the product applications or configuration files,
but the OS of the product node is still running properly, the product applications need to be restored.
Restoring Product Data
If database instances are running properly, but MAE cannot be used properly due to MAE product data exceptions,
you can use OSMU to restore the MAE product data.
1.3.1 Restoring Database Applications
If a database application is abnormal due to corruption, but the OS of the emergency system node runs
properly, you can restore the database application data by following the instructions provided in this
section.
Prerequisites
• You have logged in to the OSMU client. For details, see Logging In to the OSMU Client .
• There are backup files for the database applications to be restored.
Context
• Before the database applications are restored, OSMU automatically stops the databases and MAE
services using the database.
• If the backup files on a backup server are manually deleted, or the files are not displayed in the
Backup File column, click Synchronize to update the backup file list.
• The system automatically verifies the integrity of the backup file. If the file passes the verification, the
system will use it for restoration.
• In a single-server remote cold backup system, the restoration operations at the active site and standby
site are the same.
Procedure
1. In a remote cold backup scenario, delete the remote cold backup system. For details, see Deleting
the Remote Cold Backup System . In other scenarios, skip this step.
2. Perform 3 to 6 to restore the MAE database applications at the active site.
3. On the main menu of OSMU, choose Backup and Restore > Data Restoration > Restore Database
Application.
2025-02-15
17
iMaster MAE Product Documentation (EulerOS, TaiShan)
4. On the Restore Database Application page, select the backup server where the files to be restored
reside. If multiple backup servers are available, select the IP address of the backup server from the
Backup server drop-down list. Otherwise, skip this step.
5. Use the function of restoring OSMU to restore the database applications as prompted in the Backup
File column. For details, see section "Restoring the Application and Data of OSMU" in OSMU User
Guide (EulerOS, TaiShan).
You can obtain OSMU User Guide (EulerOS, TaiShan) from the following path at
https://support.huawei.com: Support > Software > Wireless Network > SingleOSS-MBB > SingleOSSMBB > MAE-M > MAE-OSMU.
• If the system uses the protection password for the data integrity verification key and the protection
password has changed, you need to use the backup files generated after the protection password change
to restore database applications. Otherwise, the restoration task fails.
• If the database user password is changed, you need to use the backup file generated after the database
user password change to restore the database application. Otherwise, the database functions are
abnormal after the restoration.
• If the version of the selected backup file is inconsistent with the product version, service exceptions may
occur after the restoration. You are advised to select a backup file with the same version as the product
you need to restore. If such a file is unavailable, contact Huawei technical support.
• During the restoration of the database applications, OSMU automatically stops services of the product to
be restored. After the restoration is complete, these services are in the Not running state and do not need
to be manually started. When restoring the product data, you can choose whether to manually or
automatically start them.
6. Restore the product data. For details, see Restoring Product Data .
7. Repeat 3 to 6 to restore the MAE database applications at the standby site.
8. In a remote cold backup scenario, rebuild a remote cold backup system. For details, see Configuring
a Remote Cold Backup System . In other scenarios, skip this step.
1.3.2 Restoring Product Applications
If the product applications are abnormal due to damaged file of the product applications or configuration
files, but the OS of the product node is still running properly, the product applications need to be restored.
Prerequisites
• You have logged in to the OSMU client. For details, see Logging In to the OSMU Client .
• There are backup files for the product applications to be restored.
Context
• Before the product applications are restored, OSMU automatically stops the MAE service to be
restored.
2025-02-15
18
iMaster MAE Product Documentation (EulerOS, TaiShan)
• If the backup files on a backup server are manually deleted, or the files are not displayed in the
Backup File column, click Synchronize to update the backup file list.
• OSMU automatically checks integrity of the backup file, and starts data restoration only if the check
succeeds.
• In a single-server remote cold backup system, the restoration operations at the active site and standby
site are the same.
Procedure
1. In a remote cold backup scenario, delete the remote cold backup system. For details, see Deleting
the Remote Cold Backup System . In other scenarios, skip this step.
2. Perform 3 to 7 to restore the MAE product applications at the active site.
3. On the main menu of OSMU, choose Backup and Restore > Data Restoration > Restore Product
Application.
4. On the Restore Product Application page, select the backup server where the files to be restored
reside. If multiple backup servers are available, select the IP address of the backup server from the
Backup server drop-down list. Otherwise, skip this step.
5. Select an object to be restored and select the target file in the Backup File column. Restore the data
based on Table 1.
Table 1 Restoring product applications
Task
Operation
Restoring products
Select a product and perform operations as prompted.
• If the system uses the protection password for the data integrity verification key and the protection
password has changed, you need to use the backup files generated after the protection password change
to restore product applications. Otherwise, the restoration task fails.
• If the version of the selected backup file is inconsistent with the product version, service exceptions may
occur after the restoration. You are advised to select a backup file with the same version as the product
you need to restore. If such a file is unavailable, contact Huawei technical support.
• During the restoration of the product application, OSMU automatically stops services of the product to be
restored. After the restoration is complete, these services are in the Not running state and do not need to
be manually started. When restoring the product data, you can choose whether to manually or
automatically start them.
6. On the main menu of OSMU, choose System > Task List and view the execution status of the task
for restoring the product applications.
• If Task Status is Execution Succeeded, the product applications have been successfully restored.
• If Task Status is Execution Failed, the product applications fail to be restored. Contact Huawei
technical support.
2025-02-15
19
iMaster MAE Product Documentation (EulerOS, TaiShan)
7. Restore the product data. For details, see Restoring Product Data .
8. Repeat 3 to 7 to restore the MAE product applications at the standby site.
9. In a remote cold backup scenario, rebuild a remote cold backup system. For details, see Configuring
a Remote Cold Backup System . In other scenarios, skip this step.
1.3.3 Restoring Product Data
If database instances are running properly, but MAE cannot be used properly due to MAE product data
exceptions, you can use OSMU to restore the MAE product data.
Prerequisites
• You have logged in to OSMU. For details, see Logging In to the OSMU Client .
• There are backup files for the MAE data to be restored.
• All databases under MAE are in the Running state. To check database status, see Monitoring
Databases .
Context
• Before the product data is restored, OSMU automatically stops the MAE service to be restored.
• If multiple backup servers are configured in the same region, the same backup data is stored on all
the backup servers in the region. Backup servers in this region work in redundancy mode. Accordingly,
when data is restored, all the backup servers can provide backup data. By default, OSMU randomly
selects data from one of the backup servers. You can also specify another backup server to provide
backup data.
• If the backup files on a backup server are manually deleted, or the files are not displayed in the
Backup File column, click Synchronize to synchronize the backup file information on the backup server
to OSMU.
• In a single-server remote cold backup system, product data can be restored only at the active site.
• OSMU automatically checks integrity of the backup file, and starts data restoration only if the check
succeeds.
Procedure
1. In a remote cold backup scenario, delete the remote cold backup system. For details, see Deleting
the Remote Cold Backup System . In other scenarios, skip this step.
2. Perform 3 to 10 to restore the MAE data at the active site.
3. Stop all MAE services. For details, see Stopping MAE Services .
4. Restart database services.
2025-02-15
20
iMaster MAE Product Documentation (EulerOS, TaiShan)
a. Stop all database services. For details, see Stopping Database Services .
b. Start all database services. For details, see Starting Database Services .
5. On the main menu of OSMU, choose Backup and Restore > Data Restoration > Restore Product
Data.
6. On the Restore Product Data page, select the backup server where the files to be restored reside. If
multiple backup servers are available, select the IP address of the backup server from the Backup
server drop-down list. Otherwise, skip this step.
7. Select an object to be restored and select the target file in the Backup File column. Restore the data
based on Table 1.
Table 1 Restoring MAE product data
Task
Operation
Restoring MAE products
Select a product and perform operations as prompted.
• If you select No in the displayed dialog box asking you whether to automatically start services, manually
start all MAE services after the restoration is complete.
• If you select Yes in the displayed dialog box asking you whether to automatically start services, manually
start all MAE services if some services are not started after the restoration. This is because the automatic
service startup function starts only the services involved in the backup and restoration tasks.
• If the protection password for the data integrity verification key is used and then changed, you need to
use the backup files generated after the protection password change to restore product data. Otherwise,
the restoration task fails.
8. On the main menu of OSMU, choose System > Task List. On the Task List page, view the execution
status of the task for restoring the product data.
• If Task Status is Execution Succeeded, the product data is restored successfully.
• If Task Status is Execution Failed, the product data failed to be restored. Contact Huawei
technical support.
9. Start all MAE services. For details, see Starting MAE Services .
10. Manually synchronize the NE measurement result.
After the product data is restored, manually re-collect the NE performance result data that is lost
within the restoration period. For details, see section "How Do I Synchronize Performance Results
Forcibly?" in Performance Management.
11. In a remote cold backup scenario, rebuild a remote cold backup system. For details, see Configuring
a Remote Cold Backup System . In other scenarios, skip this step.
2025-02-15
21