Professional Documents
Culture Documents
ZTE CORPORATION
No. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: +86-755-26771900
Fax: +86-755-26770801
URL: http://support.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright 2015 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or
distribution of this document or any portion of this document, in any form by any means, without the prior written
consent of ZTE CORPORATION is prohibited.
Revision History
Revision No.
Revision Date
Revision Reason
R2.0
2015-06-15
R1.0
2014-11-30
SJ-20141110151550-010|2015-06-15 (R1.0)
Contents
About This Manual ......................................................................................... I
Chapter 1 Overview .................................................................................... 1-1
1.1 Data Backup and Restoration.............................................................................. 1-1
1.2 Precautions for Data Backup and Restoration ...................................................... 1-2
Glossary .......................................................................................................... I
I
SJ-20141110151550-010|2015-06-15 (R1.0)
II
SJ-20141110151550-010|2015-06-15 (R1.0)
Intended Audience
This manual is intended for:
l
l
l
Debugging engineers
Network planning engineers
Maintenance engineers
Chapter 2, Backup
Chapter 3, Restoration
Related Documentation
l
Conventions
This manual uses the following conventions.
Caution: indicates a potentially hazardous situation. Failure to comply can result in
moderate injury, equipment damage, or interruption of minor services.
Note: provides additional information about a topic.
I
SJ-20141110151550-010|2015-06-15 (R1.0)
II
SJ-20141110151550-010|2015-06-15 (R1.0)
Chapter 1
Overview
Table of Contents
Data Backup and Restoration.....................................................................................1-1
Precautions for Data Backup and Restoration ............................................................1-2
Data Backup
Data backup is a process to save data to the specified path as required. Backup data is
used for data restoration if the existing data is damaged or missing.
Backup is classified into the following two types:
l
l
Automatic backup: The system backs up key data regularly to avoid data loss. In
case of emergency, system data can be restored through backup data.
Manual backup: Key data of the system is saved by system operators or maintainers
to restore the system in case of data loss or insoluble problems.
l
l
l
Full database structure backup: The structures of all databases used by the EMS are
backed up, including the structures of all database objects.
Basic data backup: All the basic data (data records, excluding table structures and
historical data) of the EMS is backed up. The historical data, such as historical alarms,
notifications, logs, and original performance data, is backed up separately.
File backup: Version, runtime, and configuration files of the EMS are backed up.
Log data backup: Operation, security, and system logs are backed up.
Alarm data backup: Historical alarms and notifications are backed up.
1-1
SJ-20141110151550-010|2015-06-15 (R1.0)
l
l
Data Restoration
Data restoration is a process to restore the data files provided by users to the
corresponding database tables. This process covers the operations of data preparation
and restoration, and the operations that make data available after data restoration.
Data is restored manually.
Restoration tasks fall into the following types:
l
l
l
Log data restoration: Operation, security, and system logs are restored.
Alarm data restoration: Historical alarms and notifications are restored.
Configuration data restoration: Configuration data of NEs is restored.
Full database structures, basic data, and files are restored by offline tools and are not
involved in this manual.
Restraints
l
Caution!
Data backup must be performed during idle time (for example, 0 to 4 o'clock) because
data backup has significant impact on disk I/O and network operation. Data must be
backed up only by persons designated for data backup through strict examination and
approval.
1-2
SJ-20141110151550-010|2015-06-15 (R1.0)
Chapter 1 Overview
l
l
l
l
Never
Never
Never
Never
1-3
SJ-20141110151550-010|2015-06-15 (R1.0)
1-4
SJ-20141110151550-010|2015-06-15 (R1.0)
Chapter 2
Backup
Table of Contents
Backup Strategies ......................................................................................................2-1
Managing Scheduled Backup Tasks ...........................................................................2-2
Executing Manual Backup Tasks ................................................................................2-2
Backing Up Configuration Data ..................................................................................2-2
Execution
Auto
Execu-
Backup
Remark
Mode
tion Interval
Full DB
Automatic
Every
/ums-server/run-
All data
structure
or manual
day
data/backup/sysbak/alldb
backup
Refer to
2.2 Man-
backup
aging
Basic data
Automatic
Every
/ums-server/run-
All data
backup
or manual
day
data/backup/sysbak/basicdb
backup
File backup
Automatic
Every 7
/ums-server/run-
All data
or manual
days
data/backup/sysbak/file
backup
Log data
Automatic
Every
/ums-server/rundata/backup/log-
Mod-
backup
or manual
day
bak
ified
Scheduled
Backup
Tasks for
automatic
backup.
l
Refer
data
to2.3
backup
Executing
Alarm data
Automatic
Every
/ums-server/rundata/backup/fm-
Mod-
Manual
backup
or manual
day
bak
ified
Backup
data
Tasks for
backup
manual
backup.
Performance
Automatic
Every
/ums-server/run-
Mod-
data backup
or manual
day
data/backup/pmbak
ified
data
backup
2-1
SJ-20141110151550-010|2015-06-15 (R1.0)
Item
Execution
Auto
Execu-
Backup
Remark
Mode
tion Interval
Configuration
Manual
None
/ums-clnt/cmdata/cmbak
data backup
All data
Refer to2.4
backup
Backing Up
Configuration
Data.
Prerequisite
Configuration data is backed up on the EMS client. Before data backup, ensure that the
following requirements are met:
l
l
l
Steps
Opening the Configuration Management Page
1. In the EMS topology tree, right-click an NE agent node and select Start NE
Management. The NE management function is enabled and a green mark appears
at the bottom right of the NE agent node icon.
2-2
SJ-20141110151550-010|2015-06-15 (R1.0)
Chapter 2 Backup
4. Click the Browse button on the right of the File path text box and select a path to save
the backup file.
5. Enter a character string in the File name prefix text box.
l File name prefix is a mandatory option with a length of less than 100 characters.
l A backup file is named in the following format: file prefix_date_time.zip.
For example, if File name prefix is ConfigData, the file name is
ConfigData_20110711_130455.zip.
6. (Optional) Enter additional information about the backup file in the Backup note text
box.
7. In the Select backup NEs area, click the NEs whose data is to be backed up.
8. Click the Back Up button. The Back Up Data dialog box is displayed. A confirmation
dialog box is displayed after data backup.
9. Click Yes or No as required.
2-3
SJ-20141110151550-010|2015-06-15 (R1.0)
To ...
Do ...
Click Yes.
Click No.
10. Click the Close button. The Data Backup dialog box is closed.
End of Steps
2-4
SJ-20141110151550-010|2015-06-15 (R1.0)
Chapter 3
Restoration
Table of Contents
Restoration Strategies ................................................................................................3-1
Log and Alarm Data Restoration.................................................................................3-1
Restoring Configuration Data .....................................................................................3-2
Method
Remark
Data Restoration.
Configuration data of an
NE is deleted or modified
of the NE.
Configuration Data.
by mistake.
l
Note:
When you restore data by selecting the backup files of the component in question from the
backup server, you should perform the operation in this way: view the time when the alarm
occurs on the component, and then select the latest backup files saved before the alarm.
3-1
SJ-20141110151550-010|2015-06-15 (R1.0)
Context
Data sharing between EMS scenarios indicates that configuration data saved on two EMS
servers can be shared for rapid NE establishment. For example, there are two EMS
scenarios, scenario A and B. NE0 is created in scenario A and data of NE0 is backed
up. After that, another NE can be created rapidly in scenario B through configuration data
restoration.
If NE0 has a snapshot area, the restored NE in scenario B also has a snapshot area. For
EMS configuration, a snapshot area and a modification area are described as follows:
l
Snapshot area: Data in this area is consistent with that in the NEs concerned and
cannot be configured or modified. A snapshot area can be generated automatically
after successful data synchronization or online reverse construction.
Modification area: It is a configuration area where all user operations are performed.
Prerequisite
Configuration data is restored on the EMS client. Before data backup, make sure that the
following requirements are met:
l
l
l
l
Steps
1. In the upper left part of the Configuration Management page, click Configuration
Management and select Data Restoration. The Data Restoration dialog box is
displayed, see Figure 3-1.
3-2
SJ-20141110151550-010|2015-06-15 (R1.0)
Chapter 3 Restoration
Do ...
i.
ii.
Click the Browse button and select a backup file from the local
locally
disk.
Get a data backup file from the
i.
ii.
server
list.
3-3
SJ-20141110151550-010|2015-06-15 (R1.0)
To ...
Restore all data
Do ...
i.
Check the Restore the backup file data after deleting all
SubNetworks and NEs check box.
ii.
i.
ii.
iii. In the Select NEs to restore area, click the NEs whose data
is to be restored.
iv. Click the Restore button.
v.
4. Click the Close button. The Data Restoration dialog box is closed.
End of Steps
3-4
SJ-20141110151550-010|2015-06-15 (R1.0)
Glossary
EMS
- Element Management System
FTP
- File Transfer Protocol
I
SJ-20141110151550-010|2015-06-15 (R1.0)