OceanStor BCManager 8.1.0 EBackup User Guide (Virtualization) 03
OceanStor BCManager 8.1.0 EBackup User Guide (Virtualization) 03
8.1.0
Issue 03
Date 2022-05-25
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.
Website: https://e.huawei.com
Overview
Provides an introduction to OceanStor BCManager 8.1.0 eBackup (eBackup for
short), including the product positioning, features, architecture, service
configuration process, management operations, and system maintenance.
Intended Audience
This document is intended for:
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Symbol Description
Change History
Issue Date Description
Contents
3 Backup......................................................................................................................................64
3.1 Backup Process...................................................................................................................................................................... 64
4 Restore................................................................................................................................... 114
4.1 Restoring FusionSphere VMs.......................................................................................................................................... 114
4.1.1 Restoring a VM................................................................................................................................................................ 114
4.1.2 Batch Restoring VMs...................................................................................................................................................... 116
4.1.3 Restoring a Disk on a VM............................................................................................................................................ 118
4.1.4 Batch Restoring Disks on Multiple VMs.................................................................................................................. 119
4.1.5 Restoring Files on a Disk (File-Level Restore)...................................................................................................... 121
4.2 (Optional) Viewing a Restore Job.................................................................................................................................127
4.3 Example for Restoring the FusionSphere VM Configuration...............................................................................129
6.8.3.2 Clearing a Trust Relationship Between Nodes and Files Generated in an Upgrade............................ 258
6.8.3.3 Stopping Services......................................................................................................................................................... 259
6.8.4 Process................................................................................................................................................................................ 259
6.8.4.1 Starting the eBackup Process.................................................................................................................................. 259
6.8.4.2 Stopping the eBackup Process................................................................................................................................ 260
6.8.4.3 Viewing the eBackup Process.................................................................................................................................. 260
6.8.4.4 Restarting the eBackup Process..............................................................................................................................261
6.8.5 HA......................................................................................................................................................................................... 262
6.8.5.1 Stopping the HA Process and HA Monitoring Process................................................................................... 262
6.8.5.2 Starting the HA Process and HA Monitoring Process..................................................................................... 262
6.8.5.3 Stopping the HA Process........................................................................................................................................... 263
6.8.5.4 Querying the HA Active/Standby State............................................................................................................... 263
6.8.5.5 Clearing HA Configuration Information.............................................................................................................. 264
6.8.5.6 Monitoring Data Synchronization Between Active and Standby Gauss Databases............................. 264
6.8.6 Others................................................................................................................................................................................. 265
6.8.6.1 Using Backup Database Files to Restore a Database..................................................................................... 265
6.8.6.2 Restoring a Database by Importing backups..................................................................................................... 266
6.8.6.3 Backup and Restoration Script of Huawei Distributed Block Storage.......................................................266
6.8.6.4 Auxiliary Scripts of iptables...................................................................................................................................... 268
6.8.6.5 Using the Inspection Tool to View Desired Information................................................................................ 271
6.8.6.6 Enabling CLI................................................................................................................................................................... 272
6.8.6.7 Managing open-iscsi...................................................................................................................................................273
6.8.6.8 Enabling the Log Collection Tool........................................................................................................................... 273
6.8.6.9 S3 Connection Check Tool........................................................................................................................................ 274
6.8.6.10 Deleting Residual Differential Bitmap Volumes After Data Backup....................................................... 275
6.8.6.11 Deleting Residual Snapshots After Data Backup........................................................................................... 277
6.8.6.12 Deleting Residual Backup Data............................................................................................................................ 278
7 Troubleshooting...................................................................................................................280
7.1 Troubleshooting Process...................................................................................................................................................280
7.2 Information Collection...................................................................................................................................................... 281
7.2.1 Collecting System Messages and Alarm Information.........................................................................................281
7.2.2 Collecting Log Information.......................................................................................................................................... 282
7.3 Troubleshooting Cases...................................................................................................................................................... 288
7.3.1 Installation and Uninstallation................................................................................................................................... 288
7.3.1.1 The Uninstallation Task Lasts for a Long Period After the uninstall.sh Command Is Executed...... 288
7.3.1.2 The Newly Added Backup Proxy Cannot Be Viewed on the Backup Server Page.................................289
7.3.2 Login.................................................................................................................................................................................... 291
7.3.2.1 The eBackup GUI Displays a Message Indicating "System Is in Restricted Mode" When I Log In to
eBackup......................................................................................................................................................................................... 291
7.3.3 Backup................................................................................................................................................................................ 292
7.3.3.1 A Backup Job May Be in the In progress State and Cannot Be Interrupted If the Network of an
NFS Storage Unit Is Constantly or Intermittently Interrupted During Backup.....................................................292
7.3.3.2 A Backup Job May Be in the In progress State for a Long Time If Networks of Production Storage
Are Constantly or Intermittently Interrupted During Backup.................................................................................... 293
7.3.3.3 A VM Fails to Be Backed Up and a VM Snapshot Fails to Be Created on the Task Details Page....294
7.3.3.4 VM Backup Fails and the Disk Description Fails to Be Obtained in the Task Details on the GUI...297
7.3.3.5 Disks of VMs Cannot Be Selected When You Create or Modify a Protected Set on eBackup.......... 297
7.3.3.6 What Should I Do If an Internal Error Is Reported After a Disk Fails to Be Opened, Read, Or Closed
During Backup?.......................................................................................................................................................................... 300
7.3.4 Restore................................................................................................................................................................................ 302
7.3.4.1 xfs File System in FusionSphere VMs Failed to Be Mounted........................................................................302
7.3.4.2 After a Restore Job Is Successfully Executed, Restored Non-system Disks Are Not Displayed on the
Virtual Machine Running Windows 7................................................................................................................................. 303
7.3.4.3 Linux VM Network Adapters Are in Disorder When Data Is Restored From a VM Or System Disks
to a New VM............................................................................................................................................................................... 305
7.3.4.4 Residual Disk Cannot Be Automatically Detached from the Target VM After a File-Level Restore
Task Fails....................................................................................................................................................................................... 308
7.3.5 Application........................................................................................................................................................................ 309
7.3.5.1 When a User Runs the rescan-scsi-bus.sh Command to Scan for the New Mapped LUNs, the Task
Keeps Running for a Long Time........................................................................................................................................... 309
7.3.5.2 The eBackup Service Stops When the Capacity Usage of the /opt Partition on the Backup Server
Exceeds 96%................................................................................................................................................................................ 309
7.3.5.3 A Standby Node Fails to Be Removed When the HA Function Is Being Used and the Standby Node
Is in the Irrecoverable Inaccessible State...........................................................................................................................310
7.3.5.4 In an HA Scenario, After Command sh status_ha.sh Is Executed on Both Active and Standby
Nodes, the Command Output Indicates Abnormal GaussDB Resources................................................................311
7.3.5.5 In an HA Scenario, the Active and Standby Nodes Are Correctly Configured. However, Services on
the Active Node Fail to Be Started...................................................................................................................................... 313
7.3.5.6 Backup Proxies Fail to Be Registered on the Backup Server Because Public and Private Key
Information Has Changed After eBackup Is Reconfigured......................................................................................... 314
7.3.5.7 The License Becomes Unavailable After HA Is Enabled and an Active/Standby Switchover Is
Performed..................................................................................................................................................................................... 315
7.3.5.8 Backups Are Lost After the HA Function Is Enabled and an Active/Standby Switchover Is
Performed..................................................................................................................................................................................... 316
7.3.5.9 Failed to Delete backups........................................................................................................................................... 317
7.3.6 Maintenance..................................................................................................................................................................... 319
7.3.6.1 Large Time Difference Between the NTP Server and Backup Server........................................................ 319
7.3.6.2 The NTP Service of a Backup Proxy Is Abnormal, the Time of the Backup Proxy Fails to Be
Synchronized with that of the Backup Server, and No Alarm Is Generated......................................................... 320
11 FAQ....................................................................................................................................... 429
11.1 In What Configuration Modes Can Disks Not Be Restored by eBackup in LAN-free Mode.................. 429
11.2 Do VMs Created on FusionCompute Need to Be Restarted After Their CPUs and Memory Are
Adjusted........................................................................................................................................................................................ 430
A Glossary.................................................................................................................................432
B Abbreviation.........................................................................................................................444
1 Overview
Background
As the trend of cloud-based enterprise IT systems speeds up, an increasing number
of enterprises deploy their service systems in cloud and virtual environments. Data
protection in cloud and virtual environments includes:
● Protection for massive data on VMs and disks
● Backup and restore of virtual machines (VMs)
● Reduction of backup cost and the total cost of ownership (TCO) for IT
systems
Enterprises and users are in urgent need for backup solutions that provide easy-to-
operate and cost-effective protection for backup of massive data on VMs, disks.
Software Positioning
eBackup is virtual and cloud-oriented backup software developed by Huawei.
Based on VM or disk snapshot, Changed Block Tracking (CBT), and snapshot
1.2 Features
The eBackup software provides data protection for massive virtual machines
(VMs) and disks in virtual environments. The eBackup software provides the
following function and security features.
Function Features
Table 1-1 shows function features provided by the eBackup software.
Feature Description
Security Features
The eBackup software provides the following security features:
● HTTPS security access
● Sensitive data (such as eBackup passwords and private keys) encryption
● Verification code authentication for login and login error lock settings to
prevent brute force password cracking
● User password complexity and session timeout policies
● Integrity check before installation
● User operation logs
● Default database hardening, web hardening, and OS hardening
● Web application security, such as protection against cross-site scripting,
structured query language (SQL) injection attacks, and cross-site request
forgery (CSRF) attacks
time sequence. All backups on this chain are generated by the same backup object
and stored in the same repository when this object is backed up based on the
same backup policy.
Figure 1-1 shows three backups generated by three backups that are performed
for a disk at different points of time. A, B, C, D, E, and F are backup data blocks in
the backups.
● The first backup is a full backup, generating backup 1, followed by an
incremental backup generating backups 2 and 3.
● During the second incremental backup, if data changes occur in data blocks B
and C on the disk, backup data blocks B1 and C1 are generated in backup 2. If
no data change occurs in data blocks A and D, these data blocks in backup 1
are referenced by backup 2.
● During the third incremental backup, if data changes occur in data block D,
backup data block D1 is generated in backup 3. If no data change occurs in
data blocks A, B1, and C1, these data blocks in backup 2 are referenced by
backup 3. If new data blocks E and F are written into the disk, backup data
blocks E and F are generated in backup 3.
● When a backup is deleted, backup data blocks referenced by this image will
not be deleted, but other backup data blocks will. For example, when you
delete backup 2, database D is used by backup 1, and data block D is not
deleted. Data blocks A, B1, and C1 will stay because they are referenced by
backup 3.
Figure 1-2 shows how eBackup restores data for the damaged data blocks C1 and
F using backup 3.
● eBackup restores data in incremental mode. When a disk is damaged,
eBackup compares the data of the damage time point with data in a backup.
If both data is consistent, no restore is required. If not, eBackup restores only
the differential data at the damage time point. As shown in the figure,
backup 3 is used to restore only data blocks C1 and F.
● When restoring disk data using a backup, you do not need to synthesize
backup data blocks before the restore. For example, when restoring disk data
using backup 3, you do not need to synthesize backup data block C1 from
backup 2 into backup 3.
● eBackup software
The eBackup software is deployed on backup server and backup proxy. After
initial configuration, the software can implement backup and recovery
management.
● FusionSphere virtualization environment
FusionSphere virtualizes hardware resources using the virtualization software
deployed on physical servers so that one physical server can function as
multiple virtual servers. FusionSphere contains key components, such as VRM
(Virtual Resource Management), Computing Node Agent (CNA), and
production storage.
● Production storage
FusionSphere virtualization environment
Supported production storage: Huawei distributed block storage and
virtualized storage (including SAN, NAS, and local disks)
● Backup storage
NAS storage, S3 storage and SAN(XFS) storage can be used as backup storage
to improve backup performance and backup reliability.
In LAN-Free backup mode, backup and restore jobs do not occupy Ethernet
network resources, releasing network bandwidth.
1.6 Restrictions
Restrictions on Backup and Restore
● VMs created on FusionCompute can be backed up and restored.
● VMs whose protected environment is VMware cannot be backed up or
restored.
● LUNs whose protected environment is a storage device cannot be backed up
or restored.
● If the production storage is Huawei distributed block storage, backup and
restore in LAN-free mode are supported.
● If the production storage is virtualized storage (including SAN storage, NAS
storage, and local disks), only the LAN-Base backup and restore mode is
supported.
● Disks that have not been mounted to VMs cannot be backed up or restored.
● S3 and SAN(XFS) storage units do not support deduplication-related backup
or restore.
● Supported production storage: Huawei distributed block storage and
virtualized storage (including SAN, NAS, and local disks). The ARM platform
of FusionCompute 8.1.1 does not support virtualized SAN storage.
● Disks whose bus type is SCSI or VIRTIO can be backed up and restored. Disks
whose bus type is IDE cannot be backed up or restored. If IDE disks have been
mounted to a VM, the VM can be backed up only after the IDE disks are
unmounted.
● Backup and restore across wide area networks (WANs) between protected
environments (such as FusionCompute VRM, CNA, and production storage)
and the eBackup system, between backup proxies, and between backup
proxies and backup storage are not supported.
● As the number of disks on which concurrent backup and restore jobs can be
performed is limited at the production end, accessing disks may take a long
period of time during backup and restore until other backup and restore jobs
have finished and the production system releases available resources.
● If no CBT information is returned by the production end during the execution
of a full backup job, no data will be backed up. In this case, when the
generated backup is used for restore, no data will be written into the disks at
the production end. That is, the data in such disks remains consistent with
that before the restore.
● In an eBackup system, ARM and x86 servers cannot be deployed together.
● Backups of ARM and x86 architectures do not support cross-restore. For
example, backups generated by ARM VMs cannot be restored to x86 VMs,
clusters, or hosts.
● VMs that have both Huawei distributed block storage and virtualized storage
mounted cannot be backed up. You can select disks of the same type on a VM
for backup. If multiple disks of the VM need to be restored, the datastores to
which the disks are to be restored must be of the same type.
● If the VM disk is set to Independent & persistent or Independent &
nonpersistent, the disk is not backed up when the VM is backed up.
● If the system disk of a VM is set to Independent & persistent or
Independent & nonpersistent, data can be restored to the original VM. If the
system disk of a specified VM is set to Independent & persistent or
Independent & nonpersistent, the VM cannot be restored to the specified
VM.
● If the data disk of a VM is set to Independent & persistent or Independent
& nonpersistent, data can be restored to the original VM. If the data disk of
a specified VM is set to Independent & persistent or Independent &
nonpersistent, the VM can be restored to the specified VM.
● Shared disk backup and recovery are not supported.
● One set of eBackup supports only one set of Huawei distributed block storage
as production storage.
● If the storage unit type is SAN(XFS), the backup storage supports only IP SAN.
● eBackup nodes do not support hybrid deployment of IPv4 and IPv6. For
example, IPv4 and IPv6 cannot be deployed on the same network plane and
on different network planes. The eBackup IP address types cannot be
switched between IPv4 and IPv6.
● The network type (IPv4 or IPv6) of the production storage and backup
storage must be the same as that of the eBackup server.
● Backup and restoration cannot be performed for FusionCompute VMs in the
HA solution (distributed storage-based HA solution).
Backup Restrictions
● The eBackup software must be deployed on physical servers or VMs.
● When eBackup is deployed on a VM, resources occupied by eBackup must be
isolated to prevent mutual impact with service VMs.
Restore Restrictions
● File-level restore is supported for FusionSphere VMs.
● You cannot restore the backup data on a VM of an earlier FusionSphere
version to a VM of the later FusionSphere version.
● File-level restore is not supported when UltraPath is used on FusionCompute
CNA hosts.
● When performing file-level restore, pay attention to the following points:
– Target VMs must support disk detaching during VM running. For details,
see Detaching a Disk from a VM in the FusionCompute 8.1.0 Product
Documentation.
– If disk attaching or detaching during file-level restore is not supported by
target VMs, you can attach disks to VMs that meet requirements and
then use the VMs to share disks with target VMs to perform file-level
restore.
– File-level restore is not supported for target VMs added to disaster
recovery (DR) clusters.
– During file-level restore, you are advised not to attach CentOS system
volumes. Otherwise, the existing /boot partition will be overwritten.
● Do not restore data of non-system disks to FusionSphere VM system disks.
Otherwise, the system will fail to be started.
● Before restoring a VM, ensure that the VM has been shut down. Otherwise,
the eBackup backup management system will forcibly shut it down.
● During the VM restore, do not perform other operations on the VM, such as
starting and deleting the VM, deleting or uninstalling VM disks, creating
snapshots, migrating storage, and exporting images. Otherwise, the VM
restore or corresponding operations may fail, or an error may occur during
data restore or exporting.
● If only a part of the disks that have undergone volume management (such as
logical volume management on Linux or dynamic volume management on
Windows) are restored, data on these disks cannot be properly accessed.
● Network adapter IP addresses stored on disks of operating systems are
historical backup data. Therefore, in VM or disk restore scenarios where disks
of operating systems are restored, note the following:
– If target VMs are the original ones, network adapter IP addresses stored
on disks of operating systems can be used in the current restored
network environment.
– If target VMs are not the original ones, network adapter IP addresses
stored on disks of operating systems cannot be used in the current
restored network environment. After restore, you need to log in to VMs
through VNC and reconfigure them.
● In some VM restore scenarios, eBackup will associate network adapters of
newly created VMs with the original port group. If eBackup fails to detect the
original port group, it will delete the network adapters. Therefore, you must
add network adapters based on your actual conditions and associate the
network adapters to a proper network after the restore is complete. Such VM
restore scenarios include:
– Restoring VMs to other protected environments.
– Restoring VMs to the original protected environments (The port group
that is associated with the network adapters of the VMs does not exist in
the location to which the VMs are restored.)
● In the following restore scenarios, disk space into which backup data is not
written will not be zeroed or reclaimed:
– Incremental restore where backup data is written into original disks.
– Full restore where backup data is written into original disks.
● Restoring disks of a VM will fail in the following scenarios:
– Other disks (data disks) are restored to the original VM and the original
data disks exist. The datastore type during the restore is different from
that of the original VM data disks.
– The system disk is restored to a new VM and the system disk of the new
VM exists. The datastore type during the restore is different from that of
the new VM system disks.
Precautions
Note the following precautions:
Management Specifications
Table 1-3 lists specifications of a single eBackup system.
Number of protected 4 -
environments
Maximum number of 64 -
backup proxy systems
NOTE
It is recommenced that each backup proxy system be deployed with 200 VMs for planning
and configuration. The number of VMs configured for each backup proxy system varies
based on the performance of production servers, backup servers, backup storage devices,
and networks in different scenarios.
NOTE
For details about the compatibility specifications of maintenance terminals and storage
devices, see OceanStor BCManager 8.1.0 eBackup Compatibility List (Virtualization).
This section describes the installation and uninstallation processes of the eBackup
software, including the installation process, installation preparations, installation
and uninstallation operations, and backup server and backup proxy configuration,
helping you install the software successfully.
2.1 Installation and Configuration Process
2.2 Preparing for Installation
2.3 Installing eBackup
2.4 Configuring eBackup Servers
2.5 Configuring Management Data Backup Storage
2.6 (Optional) Configuring HA
2.7 Importing a License
2.8 (Optional) Interconnecting with FusionCube Center Vision
2.9 Uninstalling eBackup
NOTICE
If multiple eBackup servers have been planned for a backup management system,
install eBackup on all eBackup servers. After installation, initialize one eBackup
server as the backup server and other eBackup servers as backup proxies.
You can expand or reduce the capacity of the eBackup backup management
system based on the number of VMs to be backed up. To expand the capacity, you
need to install and configure new backup proxies and add them to the eBackup
backup management system. For details, see 2.3.1 Installing eBackup Using a
Template, 2.3.2 Installing eBackup Using a Software Package, and 2.4.2
(Optional) Configuring a Backup Proxy. To reduce the capacity, uninstall
eBackup on backup proxies. For details, see 2.9 Uninstalling eBackup.
NOTE
For details about the compatibility specifications of maintenance terminals and storage
devices, see OceanStor BCManager 8.1.0 eBackup Compatibility List (Virtualization).
Item Description
Management node Management nodes refer to VRM, and host nodes refer
and host at the to FusionCompute compute nodes.
production end For details, see 10.4 Protected Environments
Supported by eBackup.
Item Description
Number and roles of To ensure that the eBackup software runs properly and
network planes securely, four network planes need to be configured. The
roles are as follows: Management plane, internal
communication plane, production storage plane, and
backup storage plane. The backup management plane
and production management plane are the same
network plane.
The eBackup software can be installed in either of the following modes: installed
on FusionCompute using a template or installed using a software package on a
physical server. For two installation modes, you need to configure different
network adapters for the management plane, internal communication plane,
production storage plane, and backup storage plane. If the number of network
adapters is sufficient, you are advised to configure four different network adapters
for four network planes.
NOTICE
Prerequisites
● You have obtained the user name and password for logging into
FusionCompute.
● You have prepared for the installation. For details, see 2.2.1 Checking the
Deployment Environment and 2.2.2 Network Planning.
● You have obtained eBackup template package OceanStor BCManager
8.1.0_eBackup_KVMtemplate_euler_arm64_virtualization.zip (ARM
template package) or OceanStor BCManager
8.1.0_eBackup_KVMtemplate_euler_x86_64_virtualization.zip (x86
template package). How to obtain:
– For enterprise users: Click here.
– For carrier users: Click here.
NOTE
To prevent the software package from being maliciously tampered with during
transmission or storage, download the corresponding digital signature file for integrity
verification while downloading the software package.
After the software package is downloaded from Huawei Support website, verify its
PGP digital signature by referring to OpenPGP Signature Verification Guide. If the
verification fails, do not use the software package, and contact Huawei technical
support.
Before the software package is used for installation or upgrade, its digital signature
also needs to be verified by referring to the OpenPGP Signature Verification Guide to
ensure that the software package is not tampered with. To obtain this document, visit
the following link:
For carrier users, log in to http://support.huawei.com/carrier/
digitalSignatureAction.
For enterprise users, log in to https://support.huawei.com/enterprise/en/tool/pgp-
verify-TL1000000054.
● If the LAN-Free backup feature is used, ensure that the production storage at
the production end provides Ethernet ports to connect to eBackup.
NOTICE
To ensure sufficient network bandwidth resources for backup, you are advised
to install the backup software on physical servers.
For details about the installation method, see 2.3.2 Installing eBackup Using
a Software Package.
Procedure
Step 1 Import an eBackup template.
----End
Follow-up Procedure
After eBackup has been installed, you need to assign a role for each eBackup
server. Two roles are available: backup server and backup proxy. For details, see
2.4 Configuring eBackup Servers.
Prerequisites
● You have installed the OS on a physical server. For details about how to install
the OS, see 9.11 Installing the OS. You can obtain OS installation package
OceanStor BCManager 8.1.0_EulerOS_ARM.zip (OS installation package of
the ARM server) or OceanStor BCManager 8.1.0_EulerOS_X86.zip (OS
installation package of the x86 server) from the following path:
– For enterprise users: Click here.
– For carrier users: Click here.
NOTE
● The default password of user root for installing the Euler operating system is
Cloud12#$.
● After the operating system is installed on the physical server, run the
following commands in sequence to disable the SELINUX option and restart
the system. Otherwise, eBackup logs may fail to be dumped.
/usr/bin/sed -i 's/^SELINUX=.*$/SELINUX=disabled/g' /etc/selinux/config
reboot
● You have obtained eBackup software installation package
eBackup_8.1.0_Euler_arm64.tar.gz (ARM server software package) or
eBackup_8.1.0_Euler_x86_64.tar.gz (x86 server software package). The path
is as follows:
– For enterprise users: Click here.
– For carrier users: Click here.
NOTE
To prevent the software package from being maliciously tampered with during transmission
or storage, download the corresponding digital signature file for integrity verification while
downloading the software package.
After the software package is downloaded from Huawei Support website, verify its PGP
digital signature by referring to OpenPGP Signature Verification Guide. If the verification
fails, do not use the software package, and contact Huawei technical support.
Before the software package is used for installation or upgrade, its digital signature also
needs to be verified by referring to the OpenPGP Signature Verification Guide to ensure
that the software package is not tampered with. To obtain this document, visit the
following link:
For carrier users, log in to http://support.huawei.com/carrier/digitalSignatureAction.
For enterprise users, log in to https://support.huawei.com/enterprise/en/tool/pgp-verify-
TL1000000054.
● You have prepared for the installation. For details, see 2.2.1 Checking the
Deployment Environment and 2.2.2 Network Planning. IP addresses of
network adapters on servers have been configured according to network
plans. All the IP addresses are static ones. You can bind the network adapters
of eBackup servers, configure virtual network adapters, and set multiple IP
addresses for a single network adapter.
The bond configuration is used as an example to describe how to configure
the IP address of the eBackup server. For details, see 9.8 Configuring
Network Adapter Binding.
Procedure
Step 1 Copy the eBackup software installation package to any directory on the server.
Step 2 Run the cd eBackup software installation package directory command to go to the
directory where the eBackup software installation package is stored.
Step 4 Run the following command to enter the installation script directory:
NOTE
----End
Follow-up Procedure
After eBackup has been installed, you need to assign a role for each eBackup
server. Two roles are available: backup server and backup proxy. For details, see
2.4 Configuring eBackup Servers.
Prerequisites
You have obtained the OceanStor BCManager 8.1.0_eBackup_patch.tar.gz
eBackup patch package.
Procedure
Step 1 Use WinSCP to copy eBackup patch package OceanStor BCManager
8.1.0_eBackup_patch.tar.gz to the /home/hcp/ directory of the eBackup server.
Step 2 Use PuTTY to log in to the eBackup server.
Default account: hcp. Default password: PXU9@ctuNov17!.
Step 3 Run the su root command and enter the password of user root to switch to user
root.
The default password of user root is Cloud12#$.
Step 4 Run the following command to go to directory /home/hcp/:
cd /home/hcp/
Step 5 Run the following command to decompress the eBackup patch package:
tar xvf "OceanStor BCManager 8.1.0_eBackup_patch.tar.gz"
Step 6 Run the following command to go to directory /home/hcp/patch:
cd /home/hcp/patch
Step 7 Run the following command to install the patch:
sh patch.sh
Step 8 Repeat the preceding steps to install the patch on all other eBackup servers.
----End
Prerequisites
● Parameters of backup servers have been planned based on pre-installation
preparations. For details, see 2.2.2 Network Planning.
● You have configured an IP address for the NIC of the eBackup server.
– If you install eBackup using a template, configure the NIC IP address
when provisioning an eBackup VM using the template. For details, see
Step 2.
– If you install eBackup using a software package, configure the NIC IP
address before installing eBackup. For details, see Prerequisites.
Procedure
Step 1 If eBackup uses the IPv6 network type and the production storage is Huawei
distributed block storage, add the eBackup server to the Huawei distributed block
storage cluster before configuring the eBackup server. Otherwise, skip this step.
For details, see 3.4.1 Adding an eBackup Server to a Huawei Distributed Block
Storage Cluster (Applicable to Huawei Distributed Block Storage 8.1.0/8.1.1).
If the eBackup server has not been added to the Huawei distributed block storage
cluster, adding the eBackup server to the Huawei distributed block storage cluster
will fail after the eBackup server is configured. This is because after a floating IP
address is configured for eBackup, two IP addresses are bound to the same NIC. As
a result, the eBackup server cannot be added to the cluster on Huawei distributed
block storage.
Step 2 Use PuTTY to log in to the eBackup server.
Default account: hcp. Default password: PXU9@ctuNov17!.
Step 3 Run the su root command and enter the password of user root to switch to user
root.
The default password of user root is Cloud12#$.
Step 4 Run the TMOUT=0 command to disable user logout upon system timeout.
NOTE
After you run the preceding command, the system continues to run even when no
operation is performed, resulting in security risks. For security purposes, you are advised to
run the exit command to exit the system after completing your operations.
Step 5 Run the cd eBackup initial configuration script directory command to switch to the
initial configuration script directory.
NOTE
NOTE
eBackup nodes do not support hybrid deployment of IPv4 and IPv6. For example, IPv4 and
IPv6 cannot be deployed on the same network plane and on different network planes. The
eBackup IP address types cannot be switched between IPv4 and IPv6.
Step 7 For example, if the IPv4 environment is used, input 1 and press Enter.
Please select a role for this machine:
1.Backup Server
2.Backup Proxy
3.Backup Manager
4.Backup Workflow Server
Step 9 Select a network adapter to be bound with the backup management plane, and
press Enter.
For example, if you select network adapter enp4s0 to be bound with the backup
management plane, input 1, and press Enter.
Set network adapter for 'Internal communication' network plane:
[1] enp4s0 MAC=28:6e:d4:89:ad:1c IP=10.133.40.209 MASK=255.255.0.0
[2] enp5s0 MAC=28:6e:d4:88:e0:8a IP=192.168.40.209 MASK=255.255.0.0
[3] enp6s0 MAC=28:6e:d4:87:ea:6d IP=10.122.10.20 MASK=255.255.0.0
[4] enp7s0 MAC=28:6e:d4:86:ac:4e IP=10.122.40.15 MASK=255.255.0.0
Which network adapter from the above list would you like to bind to the 'Internal communication' network
plane?
Step 10 Select a network adapter to be bound with the internal communication plane, and
press Enter.
For example, if you select network adapter enp5s0 to be bound with the internal
communication plane, input 2, and press Enter.
Set network adapter for 'Production management' network plane:
[1] enp4s0 MAC=28:6e:d4:89:ad:1c IP=10.133.40.209 MASK=255.255.0.0
[2] enp5s0 MAC=28:6e:d4:88:e0:8a IP=192.168.40.209 MASK=255.255.0.0
[3] enp6s0 MAC=28:6e:d4:87:ea:6d IP=10.122.10.20 MASK=255.255.0.0
[4] enp7s0 MAC=28:6e:d4:86:ac:4e IP=10.122.40.15 MASK=255.255.0.0
Which network adapter from the above list would you like to bind to the 'Production management'
network plane?
Step 11 Select a network adapter to be bound with the production management plane,
and press Enter.
For example, if you select network adapter enp4s0 to be bound with the
production management plane, input 1, and press Enter.
Set network adapter for 'Production Storage' network plane:
[1] enp4s0 MAC=28:6e:d4:89:ad:1c IP=10.133.40.209 MASK=255.255.0.0
[2] enp5s0 MAC=28:6e:d4:88:e0:8a IP=192.168.40.209 MASK=255.255.0.0
[3] enp6s0 MAC=28:6e:d4:87:ea:6d IP=10.122.10.20 MASK=255.255.0.0
[4] enp7s0 MAC=28:6e:d4:86:ac:4e IP=10.122.40.15 MASK=255.255.0.0
Which network adapter from the above list would you like to bind to the 'Production Storage' network
plane?
Step 12 Select a network adapter to be bound with the production storage plane, and
press Enter.
For example, if you select network adapter enp6s0 to be bound with the
production storage plane, input 3, and press Enter.
Set network adapter for 'Backup Storage' network plane:
[1] enp4s0 MAC=28:6e:d4:89:ad:1c IP=10.133.40.209 MASK=255.255.0.0
[2] enp5s0 MAC=28:6e:d4:88:e0:8a IP=192.168.40.209 MASK=255.255.0.0
[3] enp6s0 MAC=28:6e:d4:87:ea:6d IP=10.122.10.20 MASK=255.255.0.0
[4] enp7s0 MAC=28:6e:d4:86:ac:4e IP=10.122.40.15 MASK=255.255.0.0
Which network adapter from the above list would you like to bind to the 'Backup Storage' network plane?
Step 13 Select a network adapter to be bound with the backup storage plane, and press
Enter.
For example, if you select network adapter enp7s0 to be bound with the backup
storage plane, input 4, and press Enter.
Enter a floating IP address that is in the same network segment as the internal communication plane.
Step 14 Input the floating IP address of the internal communication plane and press Enter.
If the command output is as follows, the configuration is successful.
Configuration succeeded.
The ebk_accelerator agent of OceanStor BCManager eBackup was started successfully.
Start:ebk_accelerator service succeeded.
The ebk_backup agent of OceanStor BCManager eBackup was started successfully.
Start:ebk_backup service succeeded.
The ebk_copy agent of OceanStor BCManager eBackup was started successfully.
Start:ebk_copy service succeeded.
The ebk_delete agent of OceanStor BCManager eBackup was started successfully.
Start:ebk_delete service succeeded.
The ebk_fsbackup agent of OceanStor BCManager eBackup was started successfully.
Start:ebk_fsbackup service succeeded.
The ebk_jobmanager agent of OceanStor BCManager eBackup was started successfully.
Start:ebk_jobmanager service succeeded.
The ebk_mgr agent of OceanStor BCManager eBackup was started successfully.
Start:ebk_mgr service succeeded.
The ebk_restore agent of OceanStor BCManager eBackup was started successfully.
Start:ebk_restore service succeeded.
The ebk_vmware agent of OceanStor BCManager eBackup was started successfully.
Start:ebk_vmware service succeeded.
Step 15 Optional: If you cannot use a browser to access the eBackup server, add the IP
address of the maintenance terminal where the browser resides to the firewall
rules of the eBackup server.
NOTE
Security of eBackup has been hardened. By default, external systems only on the same
network segments as eBackup network planes can access the eBackup server. If the IP
address of a maintenance terminal where the browser resides and that of the backup server
management plane are not on the same network segment, configure firewall rules to
enable the maintenance terminal to access the backup server. For details, see 6.8.6.4
Auxiliary Scripts of iptables.
1. Run the cd /opt/huawei-data-protection/ebackup/bin command to enter
the save path of the iptables script.
2. Run the sh iptablesHelper.sh accept HCPManagementPlane IP address or
network segment of the maintenance terminal where the browser resides
Backup management plane IP address or network segment of eBackup
command to add iptables rules
Step 16 For security purposes, harden the security of the operating system
comprehensively to improve system security. For details, see OceanStor
BCManager 8.1.0 eBackup Security Hardening (Euler).
----End
Follow-up Procedure
Check whether the installation is successful:
After you log in to the eBackup system, you need to view the status of eBackup
nodes to discover and handle exceptions in a timely manner. For details, see 6.1.4
Managing an eBackup Server.
If you want to change the IP address of an eBackup server after the configuration,
you need to configure the eBackup server again by referring to 9.4 Reconfigure
eBackup Servers after Changing the IP Address.
After configuration, eBackup uses the time zone of the system by default. To
modify the time zone or add an NTP server, see 6.2.3 Configuring System Time
and Zone.
After configuration, an eBackup node has a default public/private key pair. If you
want to query or update the public/private key pair or handle connection
exceptions on the backup server or a backup proxy, log in to the backup server,
and go to the CLI mode to perform the related operations. For details, see
descriptions of the change server_keypair, change proxy_keypair, show
server_public_key, and add public_key commands in Server Key Management
of OceanStor BCManager 8.1.0 eBackup Command Reference. For security
purposes, you need to update the private and public keys of eBackup servers in
time after configuration and periodically during the running of the system.
Security of eBackup has been hardened. By default, external systems only on the
same network segments as eBackup network planes can access the eBackup
server. Therefore, other network segments or IP addresses used to access the
management or storage plane (including production storage plane and backup
storage plane) must be configured. Configure routers and firewalls in sequence. If
multiple network adapters or IP addresses are configured on the storage plane, for
example, for multipath or network adapter binding, you can use the auxiliary
commands of iptables.
Prerequisites
● Multiple backup proxies can be configured in an eBackup system. Parameters
of backup proxies have been planned. For details, see 2.2.2 Network
Planning.
● A backup server has been configured.
● You have configured an IP address for the NIC of the eBackup server.
– If you install eBackup using a template, configure the NIC IP address
when provisioning an eBackup VM using the template. For details, see
Step 2.
– If you install eBackup using a software package, configure the NIC IP
address before installing eBackup. For details, see Prerequisites.
● If you need to expand the capacity of the backup system (by adding a backup
proxy) and the system to be expanded has unfinished tasks, add the new
eBackup node to the Huawei distributed block storage cluster and then
initialize the eBackup node. Otherwise, tasks delivered to the node may fail.
For details about how to add a new eBackup node to a Huawei distributed
block storage cluster, see 3.4.1 Adding an eBackup Server to a Huawei
Distributed Block Storage Cluster (Applicable to Huawei Distributed
Block Storage 8.1.0/8.1.1).
Procedure
Step 1 If eBackup uses the IPv6 network type and the production storage is Huawei
distributed block storage, add the eBackup server to the Huawei distributed block
storage cluster before configuring the eBackup server. Otherwise, skip this step.
For details, see 3.4.1 Adding an eBackup Server to a Huawei Distributed Block
Storage Cluster (Applicable to Huawei Distributed Block Storage 8.1.0/8.1.1).
If the eBackup server has not been added to the Huawei distributed block storage
cluster, adding the eBackup server to the Huawei distributed block storage cluster
will fail after the eBackup server is configured. This is because after a floating IP
address is configured for eBackup, two IP addresses are bound to the same NIC. As
a result, the eBackup server cannot be added to the cluster on Huawei distributed
block storage.
Step 3 Run the su root command and enter the password of user root to switch to user
root.
Step 4 Run the TMOUT=0 command to disable user logout upon system timeout.
NOTE
After you run the preceding command, the system continues to run even when no
operation is performed, resulting in security risks. For security purposes, you are advised to
run the exit command to exit the system after completing your operations.
Step 5 Run the cd eBackup initial configuration script directory command to switch to the
initial configuration script directory.
NOTE
NOTE
eBackup nodes do not support hybrid deployment of IPv4 and IPv6. For example, IPv4 and
IPv6 cannot be deployed on the same network plane and on different network planes. The
eBackup IP address types cannot be switched between IPv4 and IPv6.
Step 7 For example, if the IPv4 environment is used, input 1 and press Enter.
Please select a role for this machine:
1.Backup Server
2.Backup Proxy
3.Backup Manager
4.Backup Workflow Server
Step 9 Select a network adapter to be bound with the backup management plane, and
press Enter.
For example, if you select network adapter enp4s0 to be bound with the backup
management plane, input 1, and press Enter.
Step 10 Select a network adapter to be bound with the internal communication plane, and
press Enter.
For example, if you select network adapter enp5s0 to be bound with the internal
communication plane, input 2, and press Enter.
Set network adapter for 'Production management' network plane:
[1] enp4s0 MAC=28:6e:d4:89:da:cc IP=10.133.40.211 MASK=255.255.0.0
[2] enp5s0 MAC=28:6e:d4:88:e3:e8 IP=192.168.40.211 MASK=255.255.0.0
[3] enp6s0 MAC=28:6e:d4:87:eb:6f IP=10.122.10.21 MASK=255.255.0.0
[4] enp7s0 MAC=28:6e:d4:86:cd:5e IP=10.122.40.16 MASK=255.255.0.0
Which network adapter from the above list would you like to bind to the 'Production management'
network plane?
Step 11 Select a network adapter to be bound with the production management plane,
and press Enter.
For example, if you select network adapter enp4s0 to be bound with the
production management plane, input 1, and press Enter.
Set network adapter for 'Production Storage' network plane:
[1] enp4s0 MAC=28:6e:d4:89:da:cc IP=10.133.40.211 MASK=255.255.0.0
[2] enp5s0 MAC=28:6e:d4:88:e3:e8 IP=192.168.40.211 MASK=255.255.0.0
[3] enp6s0 MAC=28:6e:d4:87:eb:6f IP=10.122.10.21 MASK=255.255.0.0
[4] enp7s0 MAC=28:6e:d4:86:cd:5e IP=10.122.40.16 MASK=255.255.0.0
Which network adapter from the above list would you like to bind to the 'Production Storage' network
plane?
Step 12 Select a network adapter to be bound with the production storage plane, and
press Enter.
For example, if you select network adapter enp6s0 to be bound with the
production storage plane, input 3, and press Enter.
Set network adapter for 'Backup Storage' network plane:
[1] enp4s0 MAC=28:6e:d4:89:da:cc IP=10.133.40.211 MASK=255.255.0.0
[2] enp5s0 MAC=28:6e:d4:88:e3:e8 IP=192.168.40.211 MASK=255.255.0.0
[3] enp6s0 MAC=28:6e:d4:87:eb:6f IP=10.122.10.21 MASK=255.255.0.0
[4] enp7s0 MAC=28:6e:d4:86:cd:5e IP=10.122.40.16 MASK=255.255.0.0
Which network adapter from the above list would you like to bind to the 'Backup Storage' network plane?
Step 13 Select a network adapter to be bound with the backup storage plane, and press
Enter.
For example, if you select network adapter enp7s0 to be bound with the backup
storage plane, input 4, and press Enter.
Please input the leader IP(The IP of internal communication plane at backup server):
Step 14 Enter the internal communication plane IP address of the backup server, and press
Enter.
Please input the floating IP address at backup server:
Step 15 Enter the internal communication plane floating IP address of the backup server,
and press Enter.
Do not check the network segment.
Please enter the public key of the backup server. To obtain the public key, run the following CLI command:
show server_public_key.
To use the default public key, press Enter.
Step 16 Input the public key of the backup server and press Enter. If you use the default
public key, press Enter.
NOTE
You have performed the initial configuration on the backup proxy. Once you replace the
backup server, reconfigure the backup proxy. When reconfiguring the backup proxy, you
cannot use the default public key. Perform the following operations to obtain a new public
key of the backup server. For details, see Related Operations.
Step 17 For security purposes, harden the security of the operating system
comprehensively to improve system security. For details, see OceanStor
BCManager 8.1.0 eBackup Security Hardening (Euler).
----End
Related Operations
Obtain the public key of the backup server.
cd /opt/huawei-data-protection/ebackup/cli/
Step 3 Run the following command and enter the password of user admin:
sh hcpcli.sh admin
NOTE
----End
Follow-up Procedure
After you log in to the eBackup system, you need to view the status of eBackup
nodes to discover and handle exceptions in a timely manner. For details, see 6.1.4
Managing an eBackup Server.
If you want to change the IP address of an eBackup server after the configuration,
you need to configure the eBackup server again by referring to 9.4 Reconfigure
eBackup Servers after Changing the IP Address.
After configuration, an eBackup node has a default public/private key pair. If you
want to query or update the public/private key pair or handle connection
exceptions on the backup server or a backup proxy, log in to the backup server,
and go to the CLI mode to perform the related operations. For details, see
descriptions of the change server_keypair, change proxy_keypair, show
server_public_key, and add public_key commands in Server Key Management
of OceanStor BCManager 8.1.0 eBackup Command Reference. For security
purposes, you need to update the private and public keys of eBackup servers in
time after configuration and periodically during the running of the system.
Security of eBackup has been hardened. By default, external systems only on the
same network segments as eBackup network planes can access the eBackup
server. Therefore, other network segments or IP addresses used to access the
management or storage plane (including production storage plane and backup
storage plane) must be configured. Configure routers and firewalls in sequence. If
multiple network adapters or IP addresses are configured on the storage plane, for
example, for multipath or network adapter binding, you can use the auxiliary
commands of iptables.
Context
● When eBackup management data is backed up, the shared storage capacity
must be calculated in advance. When the shared storage capacity is
insufficient, the latest backup job will fail. The available capacity of shared
storage must be at least 65 GB. The capacity is planned based on the backup
data retention policy.
– When Daily Backup is selected
Capacity of shared storage for storing backup management data =
[(Number of yearly backup copies + Number of monthly backup copies +
Number of weekly backup copies + Number of daily backup copies +1) x
10 + 15] GB.
When Yearly Backup is set to Permanent, planned capacities depend on
the number of years for saving backup copies. The capacity of shared
storage for storing backup management data = [(Number of planned
yearly backup copies + Number of monthly backup copies + Number of
weekly backup copies + Number of daily backup copies+ 1) × 10 + 15]
GB.
– When Hourly Backup is selected
Capacity of shared storage for storing backup management data =
[(Number of yearly backup copies + Number of monthly backup copies +
Number of weekly backup copies + Number of daily backup copies +
Number of hourly backup copies + 1) × 10 + 15] GB.
When Yearly Backup is set to Permanent, planned capacities depend on
the number of years for saving backup copies. The capacity of shared
storage for storing backup management data = [(Number of planned
yearly backup copies + Number of monthly backup copies + Number of
weekly backup copies + Number of daily backup copies + Number of
hourly backup copies + 1) × 10 + 15] GB.
● Configure separate backup storage space for eBackup management data.
2.5.1 NFS
When eBackup uses the NFS shared storage as the backup storage for
management data (such as databases and configuration files), configure backup
storage information and backup policies to restore the eBackup management
system after management data exceptions occur as instructed in this section.
Prerequisites
● You have planned the capacity of the NFS shared storage. The capacity of the
shared storage must meet the requirements. Otherwise, the backup job will
fail. For details, see Context.
● You have created the NFS shared storage in advance. The client IP address of
the NFS share is the backup storage plane IP address of the eBackup server,
and the storage side does not restrict the permission of user root of the
eBackup server. That is, user root has full control permission on the NFS share
directory. For example, if OceanStor 9000 is used as the NFS shared storage,
select no_all_squash and no_root_squash when setting NFS file sharing
parameters, and set the permission to Read and write.
Procedure
Configuring the backup storage
Step 2 On the menu bar, choose > Configuration > Management Data Backup >
Set Backup Storage.
Step 3 Configure the backup storage information for eBackup management data.
eBackup supports the NFS, S3, FTP and SFTP storage as the backup storage for
management data. This section describes how to configure the backup storage of
the NFS type. Table 2-3 describes the related parameters.
NOTICE
Backup storage of management data and backup storage for storing user VM data
cannot use the same NFS shared directory. Otherwise, the backup task may fail.
After the configuration is completed, the backup storage configuration status will
be shown to the right of the Set Backup Storage button.
NOTE
If you change the value of Daily Backup to Hourly Backup, Hourly Backup does not
take effect immediately. After the modification, the first backup job is Daily Backup.
After the backup job is complete, the next backup job is Hourly Backup.
If you need Hourly Backup to take effect immediately after the modification, log in to
the active eBackup node and run the service hcp restart command to restart the
eBackup service.
● When Hourly Backup is selected, the following figure shows the default
system settings.
Step 6 After the automatic backup policy is configured, click OK. The policy takes effect
immediately.
You are advised to set the backup time to off-peak hours to reduce impact on
services, for example, 00:00 to 02:00.
If backup time overlaps (for example, monthly backup and weekly backup happen
on the same Monday), the system defines backup data with the highest priority.
The priority is Yearly Backup > Monthly Backup > Weekly Backup > Daily Backup >
Hourly Backup.
----End
2.5.2 S3
When eBackup uses the S3 storage as the backup storage for management data
(such as databases and configuration files), configure backup storage information
and backup policies to restore the eBackup management system after
management data exceptions occur as instructed in this section.
Prerequisites
● You have planned the capacity of the S3 shared storage. The capacity of the
shared storage must meet the requirements. Otherwise, the backup job will
fail. For details, see Context.
● You have obtained the domain name or IP address of the S3 storage service
plane from the S3 storage service administrator, as well as the bucket name,
AK, and SK that stores backup data.
Procedure
Configuring the backup storage
Step 2 On the menu bar, choose > Configuration > Management Data Backup >
Set Backup Storage.
Step 3 Configure the backup storage information for eBackup management data.
eBackup supports the NFS, S3, FTP and SFTP storage as the backup storage for
management data. This section describes how to configure the backup storage of
the S3 type. Table 2-4 describes the related parameters.
NOTICE
Backup storage of management data and backup storage for storing user VM data
cannot use the same bucket. Otherwise, the backup task may fail.
● When Daily Backup is selected, the following figure shows the default system
settings.
NOTE
If you change the value of Daily Backup to Hourly Backup, Hourly Backup does not
take effect immediately. After the modification, the first backup job is Daily Backup.
After the backup job is complete, the next backup job is Hourly Backup.
If you need Hourly Backup to take effect immediately after the modification, log in to
the active eBackup node and run the service hcp restart command to restart the
eBackup service.
● When Hourly Backup is selected, the following figure shows the default
system settings.
Step 6 After the automatic backup policy is configured, click OK. The policy takes effect
immediately.
You are advised to set the backup time to off-peak hours to reduce impact on
services, for example, 00:00 to 02:00.
If backup time overlaps (for example, monthly backup and weekly backup happen
on the same Monday), the system defines backup data with the highest priority.
The priority is Yearly Backup > Monthly Backup > Weekly Backup > Daily Backup >
Hourly Backup.
----End
2.5.3 FTP
When eBackup uses the FTP storage as the backup storage for management data
(such as databases and configuration files), configure backup storage information
and backup policies to restore the eBackup management system after
management data exceptions occur as instructed in this section.
Prerequisites
● You have planned the capacity of the FTP shared storage. The capacity of the
shared storage must meet the requirements. Otherwise, the backup job will
fail. For details, see Context.
● eBackup has full control permission on the FTP shared directory.
Procedure
Configuring the backup storage
Step 2 On the menu bar, choose > Configuration > Management Data Backup >
Set Backup Storage.
Step 3 Configure the backup storage information for eBackup management data.
eBackup supports the NFS, S3, FTP and SFTP storage as the backup storage for
management data. This section describes how to configure the backup storage of
the FTP type. Table 2-5 describes the related parameters.
Protocol Network protocol for the ● When using the FTPs protocol,
communication between import a valid certificate for
the eBackup the backup management
management system system to verify the FTP
and FTP storage. storage information. Obtain the
Options include FTP and certificate from the FTP storage
FTPs. administrator.
For details about how to
import a certificate, see section
6.4.2.9 Managing Certificates.
● Security risks arise if the
protocol is set to FTP. You are
advised to select the FTPS
protocol.
Path Path for accessing the The path format is "/File path".
FTP server. The file path is the file directory
where the FTP backup storage
resides. A file path consists of 1 to
255 letters, digits, and special
characters including .#%-=@{_}~/:
and cannot end with a slash (/).
NOTICE
The FTP management data backup
storage and the NFS storage unit or
NFS management data backup
storage cannot use the same file
system.
● When Daily Backup is selected, the following figure shows the default system
settings.
NOTE
If you change the value of Daily Backup to Hourly Backup, Hourly Backup does not
take effect immediately. After the modification, the first backup job is Daily Backup.
After the backup job is complete, the next backup job is Hourly Backup.
If you need Hourly Backup to take effect immediately after the modification, log in to
the active eBackup node and run the service hcp restart command to restart the
eBackup service.
● When Hourly Backup is selected, the following figure shows the default
system settings.
Step 6 After the automatic backup policy is configured, click OK. The policy takes effect
immediately.
You are advised to set the backup time to off-peak hours to reduce impact on
services, for example, 00:00 to 02:00.
If backup time overlaps (for example, monthly backup and weekly backup happen
on the same Monday), the system defines backup data with the highest priority.
The priority is Yearly Backup > Monthly Backup > Weekly Backup > Daily Backup >
Hourly Backup.
----End
2.5.4 SFTP
When eBackup uses the SFTP storage as the backup storage for management data
(such as databases and configuration files), configure backup storage information
and backup policies to restore the eBackup management system after
management data exceptions occur as instructed in this section.
Prerequisites
● You have planned the capacity of the SFTP shared storage. The capacity of the
shared storage must meet the requirements. Otherwise, the backup job will
fail. For details, see Context.
● eBackup has full control permission on the SFTP shared directory.
Procedure
Configuring the backup storage
Step 2 On the menu bar, choose > Configuration > Management Data Backup >
Set Backup Storage.
Step 3 Configure the backup storage information for eBackup management data.
eBackup supports the NFS, FTP and SFTP storage as the backup storage for
management data. This section describes how to configure the backup storage of
the FTP type. Table 2-6 describes the related parameters.
Path Path for accessing the The path format is "/File path".
SFTP server. The file path is the file directory
where the SFTP backup storage
resides. A file path consists of 1
to 255 letters, digits, and special
characters including .#%-
=@{_}~/: and cannot end with a
slash (/).
Note: If SFTP management data backup storage is used for disaster recovery,
the SFTP address and path configured before disaster recovery must be the
same as the SFTP address and path configured during disaster recovery.
NOTE
If you change the value of Daily Backup to Hourly Backup, Hourly Backup does not
take effect immediately. After the modification, the first backup job is Daily Backup.
After the backup job is complete, the next backup job is Hourly Backup.
If you need Hourly Backup to take effect immediately after the modification, log in to
the active eBackup node and run the service hcp restart command to restart the
eBackup service.
● When Hourly Backup is selected, the following figure shows the default
system settings.
Step 6 After the automatic backup policy is configured, click OK. The policy takes effect
immediately.
You are advised to set the backup time to off-peak hours to reduce impact on
services, for example, 00:00 to 02:00.
If backup time overlaps (for example, monthly backup and weekly backup happen
on the same Monday), the system defines backup data with the highest priority.
The priority is Yearly Backup > Monthly Backup > Weekly Backup > Daily Backup >
Hourly Backup.
----End
Context
HA refers to that active and standby modules work in hot or cold backup mode to
implement specific functions. When the active module is faulty, the standby
module automatically takes over the role of the active module to implement
system functions, improving system reliability.
To enable eBackup to support the HA function, plan at least two eBackup servers.
(Initialize one as the backup server, and the other servers as backup proxies.) After
eBackup is installed and configured, the HA function is disabled by default. You
need to configure HA parameters to configure eBackup as an HA system. After the
configuration, the backup server and one backup proxy work in active/standby
mode. After the backup server fails, the backup proxy takes over the role of the
backup server to ensure normal system operation.
Prerequisites
The advanced-edition license has been imported. For details, see 2.7 Importing a
License.
Procedure
Step 1 Log in to the eBackup backup management system using a browser.
Step 3 Click the drop-down arrow of HA Management and choose Add HA member
from the shortcut menu that is displayed.
Step 4 Select a backup proxy whose Accessibility Status is Accessible, and Register
Status is Registered as the standby node in the HA system as prompted. Then set
the backup server as the active node.
Set Floating IP address and Quorum gateway(s). IP Address Type does not
need to be set. The system matches the IP address type of the current eBackup
node.
----End
Follow-up Procedure
To improve system O&M security, you are advised to use a certificate issued by a
third-party certification authority to replace the SSL certificates used for
communication between active and standby nodes and encrypt the private key
files. For details, see 6.4.2.4 Replacing the SSL Certificate of eBackup OMMHA
for Communication Between the Active and Standby Backup Servers and
6.4.2.6 Replacing the SSL Certificate of eBackup GaussDB for Communication
Between the Active and Standby Backup Servers.
The eBackup system time is within the validity period of SSL certificates used for
communication between active and standby nodes. If certificates expire,
Accessibility Status of Backup server (standby) is Inaccessible. In this case,
replace the expired certificates with a new one. You can perform the following
steps to query the validity period of the certificates:
1. Use PuTTY to log in to the active and standby nodes, respectively.
Default account: hcp. Default password: PXU9@ctuNov17!.
2. Run the su root command and enter the password of user root to switch to
user root.
The default password of user root is Cloud12#$.
3. Run the TMOUT=0 command to prevent the system from exiting due to
timeout.
4. Run the openssl x509 -text -in /opt/huawei-data-protection/ebackup/ha/
local/cert/server.crt command to check the validity period of the SSL
certificates of eBackup OMMHA for communication between the active and
standby backup servers.
5. Run the openssl x509 -text -in /opt/huawei-data-protection/ebackup/db/
cert/server.crt command to check the validity period of the SSL certificates of
eBackup GaussDB for communication between the active and standby backup
servers.
NOTE
In the follow-up usage, pay attention to the validity periods of certificates. Replace
certificates before they expire. Otherwise, the HA function may become abnormal.
NOTE
eBackup can be configured as an HA system only when there are at least two eBackup
servers in the system, that is, there is at least one independent backup proxy server.
If security of eBackup has been hardened, external systems only on the same
network segments as eBackup network planes can access eBackup servers by
default. If the IP address of a maintenance terminal where the browser resides
and that of the standby node management plane are not on the same network
segment, configure firewall rules to enable the maintenance terminal to access
the standby node. For details, see 6.8.6.4 Auxiliary Scripts of iptables.
Prerequisites
● You have obtained the IP address, user name, and password for logging in to
FusionCube Center Vision.
● The network connection between eBackup and FusionCube Center Vision is
normal.
Step 1 Use PuTTY to log in to the backup server using the management plane IP address.
Default account: hcp Default password: PXU9@ctuNov17!
Step 2 Run the su root command and enter the password of user root to switch to user
root.
The default password of user root is Cloud12#$.
Step 3 Run the TMOUT=0 command to disable user logout upon system timeout.
NOTE
After you run the preceding command, the system continues to run even when no
operation is performed, resulting in security risks. For security purposes, you are advised to
run the exit command to exit the system after completing your operations.
cd /opt/huawei-data-protection/ebackup/microservice/ebk_iam/conf
----End
Step 2 On FusionCube Center Vision, create an account for interconnecting with the
backup server of eBackup. For details, see Creating Accounts in the FusionCube
1000 Solution 6.0 Product Documentation.
NOTE
Step 3 On the map of the FusionCube Center Vision home page, find the site where
eBackup is located and click the site.
Step 4 Click next to the site name and select eBackup Configuration.
Step 6 After the configuration is complete, click In this case, you can log in to the
eBackup management system without a password required, as shown in Figure
2-3.
----End
Step 1 Log in to the eBackup management system and choose > Configuration >
Alarm Reporting.
Parameter Description
----End
Prerequisites
● You have prepared a cross-platform remote access tool.
● If the eBackup server is a backup server, ensure that no jobs are running
during the uninstallation to avoid impacts on services. If the eBackup server is
a backup proxy, ensure that no jobs associated with the server are running.
● You have closed all the databases and files related to eBackup.
● If the eBackup server is a backup proxy, unregister the backup proxy. For
details, see 6.1.4 Managing an eBackup Server.
● If you need to remotely log in to an eBackup server to uninstall the eBackup
software but user root of this eBackup server does not have the SSH-based
remote login permission, perform the following steps to grant the SSH-based
remote login permission to user root:
a. Use PuTTY to log in to the eBackup server as user hcp using the
management IP address.
b. Run the su root command to switch to user root.
c. Run the vi /etc/ssh/sshd_config command and press i to edit the
configuration file.
Procedure
Step 1 Use PuTTY to log in to the eBackup server as user root.
Step 2 Run the TMOUT=0 command to disable user logout upon system timeout.
NOTE
After you run the preceding command, the system continues to run even when no
operation is performed, resulting in security risks. For security purposes, you are advised to
run the exit command to exit the system after completing your operations.
Step 3 Run the w command to check whether other users are logging in to the eBackup
server as user hcp.
Check whether hcp is displayed in the USER column in the command output.
[root@eBackup ~]# w
17:14:50 up 56 min, 3 users, load average: 6.83, 5.80, 4.76
USER TTY LOGIN@ IDLE JCPU PCPU WHAT
root pts/0 17:14 1.00s 0.01s 0.01s w
hcp pts/1 16:33 38:58 0.08s 0.05s sshd: hcp [priv]
root pts/2 17:11 3:06 0.03s 0.03s -bas
● If yes, another user is logging in to the eBackup server as user hcp. Log out
the user. Alternatively, run the pkill -kill –t Value corresponding to the TTY
column command, such as pkill -kill -t pts/1, to stop the user login. Go to
Step 4.
● If no, go to Step 4.
Step 7 After reading the information that is displayed, enter y to confirm the information
and press Enter.
NOTE
After you execute the sh uninstall.sh script to uninstall the software in the /opt/huawei-
data-protection/ebackup/bin path, you can view the log in the /var/log/messages path
by entering hcp_log as a keyword to search for the log. After you execute sh
ebackup_utilities.sh uninstall to uninstall the software in the path where the backup
software package resides, the uninstallation log is saved in the current path.
----End
Follow-up Procedure
After uninstalling the backup software, you can run service ntp stop and
chkconfig ntp off to stop the NTP service if you do not need it (make sure that
other applications on servers do not cling to the NTP service).
3 Backup
Backup is a process of replicating data from the production end to the back-end
storage with which the backup system is associated. If the production system fails
or data in the production system is lost, the backup data can be used to restore
the system or data. The eBackup backup management system can back up
FusionSphere VM data to its associated back-end storage.
3.1 Backup Process
3.2 Preparing for Backup
3.3 (Optional) Registering a Backup Proxy Manually
3.4 Configuring Production Storage
3.5 Creating a Storage Unit
3.6 Creating a Storage Pool
3.7 Creating a Repository
3.8 Creating a Protected Set
3.9 Creating a Backup Policy
3.10 Creating a Backup Plan
3.11 (Optional) Executing a Backup Job Manually
3.12 (Optional) Viewing a Backup Job
3.13 Example for Backing Up the FusionSphere VM Configuration
Collect related information based on requirements described in the Table 3-1. You
are advised to print the table for information collection purposes so that data can
be found easily in later service configuration.
Prerequisites
Accessibility Status and Register Status of the backup proxy that you want to
register is Accessible and Unregistered respectively.
Context
For more details about the servers, go to 6.1.4 Managing an eBackup Server.
Procedure
Step 1 Log in to the eBackup backup management system using a browser.
Default account: admin. Default password: PXU9@ctuNov17!.
----End
Prerequisites
You have obtained the OceanStor-Pacific_8.1.x_api.tar.gz software package from
the following path:
Procedure
Step 1 Create VBS on DeviceManager.
1. Log in to DeviceManager using a browser.
2. On the top navigation bar, choose Resources > Access > VBS.
3. Choose New Node > Manually Add Node.
4. Configure the eBackup node information. Table 3-2 describes the key
parameters.
Parameter Description
Username hcp
Parameter Description
Note: Only the parameters that need to be set are described in this table.
The parameters that are not described do not need to be set.
Step 2 Import the Huawei distributed block storage certificate to the backup server and
backup proxy.
NOTE
d. Run the following command to export the FSM certificate and key file.
export fsm certificate
During the replacement, you need to enter the password of the certificate,
which is the password set in Step 2.1.
The certificate is successfully imported when the client_self.keystore,
client_trust.keystore, and dsware-api.properties files exist in the /opt/
huawei-data-protection/ebackup/vbstool/conf/cert/FSM floating IP
address/ directory.
13. Run the following command to add a file attribute.
chattr +i /opt/huawei-data-protection/ebackup/vbstool/
chattr +i -R /opt/huawei-data-protection/ebackup/vbstool/lib
chattr +i -R /opt/huawei-data-protection/ebackup/vbstool/conf
----End
Prerequisites
● Network connectivity is normal between servers and the FusionCompute
management plane.
● For servers, Accessibility Status is Accessible and Register Status is
Registered.
● The system has connected to FusionCompute and an interconnection account
has been created. For details about how to create an interconnection account,
go to 9.2 Creating a FusionCompute Interconnection Account.
Context
For details about FusionSphere protected environments, go to 10.4 Protected
Environments Supported by eBackup.
Procedure
Step 1 Log in to the eBackup backup management system using a browser.
Step 4 Enter the basic information of a FusionSphere protected environment. Table 3-3
describes related parameters.
Usernam User name of the eBackup Obtain it from 3.2 Preparing for
e backup management system and Backup (data preparation item
FusionCompute interconnection B2).
account.
NOTE
When the scanning succeeds, the icon next to the tier 1 node is , with the scanning
date and time displayed in the labels of the scanning job icon. If the scanning fails or is
in progress, the icon next to the tier 1 node is , with the latest scanning date and time
displayed in the labels of the scanning job icon.
● By default, the system scans for the environment information every hour. If the
information is changed, you can click or next to each tier 1 node to manually
trigger the scanning.
● After a successful scan, go to the Protected Environment area and click to refresh
the information in the navigation on the left.
----End
Follow-up Procedure
The VM that you want to protect can be backed up only after it is added to a
protected set. Select the VM that you want to protect and click Add to Existing
Protected Set or Add to New Protected Set to add it to a protected set.
Prerequisites
● Network connectivity is normal between eBackup servers and back-end
storage devices.
● You have planned and configured shared storage in advance. For details about
operations on the storage side, refer to the corresponding device manual.
● When the NAS shared storage is used, the client IP address of a NAS share is
the backup storage plane IP address of the eBackup server.
● To ensure data security, it is recommended that the shared directory be used
only by eBackup servers when NAS storage is used. For example, if NFS
storage is used, set the client IP address of the NFS share to the backup
storage plane IP address of the eBackup server. When the S3 storage is used,
the specified bucket is used only by eBackup. Otherwise, backup data may be
illegally obtained.
● If you select SAN(XFS) (volumes on the storage device are mapped to the
eBackup server and formatted into XFS file systems) as backup storage,
ensure that an iSCSI initiator has been configured on the eBackup server
before creating a storage unit. For details, see Configuring an iSCSI Initiator
on the eBackup Server. Then, map the volumes on the storage devices to the
backup server and backup proxy. For details about how to create volume
mappings, see Related Operations. The following uses OceanStor 5000,
5000F, 6000, 6000F V5 series and V500R007 version as an example. For details
about how to create volume mappings for other storage products, see the
desired product documentation.
NOTE
You are advised to use NAS or S3 storage units because SAN(XFS) storage units have
the following restrictions:
● SAN(XFS) storage units do not support capacity expansion. Plan the capacity
before using SAN(XFS) storage units.
● A SAN(XFS) storage unit can be bound to only one backup proxy at a time. All
backup and restore jobs of the storage unit are performed by one backup proxy. No
load balancing mechanism is available. If the backup proxy is faulty, the system
provides a failover mechanism to ensure normal service running.
Context
For details about storage units, go to 10.3 Backup Storage.
You are advised to configure an independent storage unit for each set of eBackup.
You are advised not to use the same storage unit for multiple sets of eBackup.
Otherwise, when the storage unit is restored, copies created by other eBackup will
be scanned to the faulty eBackup.
Procedure
Step 1 Log in to the eBackup backup management system using a browser.
Default account: admin. Default password: PXU9@ctuNov17!.
NOTICE
Backup storage of management data and backup storage for storing user VM data
cannot use the same NAS shared directory. Otherwise, the backup job may fail.
● NFS
Table 3-4 describes the related parameters.
Path Path for accessing the IPv4 path format: IP address or domain
NFS shared storage name:/share path or share name
IPv6 path format: [IP address] or
domain name:/share path or share
name
IP address and domain name indicate
the service IP address and domain
name of the NAS storage system,
respectively. If the backup storage is
OceanStor V300R006C00 or later, enter
share name in the path. For other
backup storage versions, enter share
path. The path contains 1 to 255
characters, including letters, digits, and
special characters .#%-=@{_}/:. It
cannot end with a slash (/).
Obtain the shared storage path from
the storage administrator.
NOTE
– An NFS share path can be used to create
only one storage unit.
– The client IP address of the NAS share is
the backup storage plane IP address of
the backup server. You can enter * to
represent all client IP addresses. You are
advised to enter the client IP address of
the NAS share. Otherwise, backup data
may be accessed illegally.
– Ensure that the storage side does not
limit the permissions of user root of the
eBackup server and that the user has full
permissions to the shared NAS directory.
For example, if you use the OceanStor
9000 WushanFS distributed file system,
choose no_all_squash and
no_root_squash when you configure
NFS parameters.
– If you use NFS storage, set the
permission to Read and write.
– The NFS management data backup
storage or NFS storage unit cannot use
the same file system as the FTP
management data backup storage.
Otherwise, the FTP management data
fails to be backed up.
● Table 3-5 describes basic information about S3 storage units and related
parameters.
NOTICE
Backup storage of management data and backup storage for storing user VM
data cannot use the same bucket. Otherwise, the backup job may fail.
Path Path for accessing the An IPv4 path format is IP address (or
S3 storage domain name):/Bucket name.
An IPv6 path format is [IP address] (or
domain name):/Bucket name.
IP address and domain name indicate
the service IP address and domain
name of the object storage service
system, respectively. The bucket name
consists of 3 to 255 characters,
including letters, digits, and special
characters .-_, for example,
192.168.10.10:/eBackup.123.
Obtain the shared storage path from
the storage administrator.
NOTE
– A bucket can be used to create only one
storage unit.
– S3 storage units do not support
deduplication.
– For details about the maximum number
of buckets supported by a storage unit,
see S3 in 6.7 Configuration Items.
● SAN(XFS)
Table 3-6 describes related parameters.
● After a storage unit is created, the system automatically mounts storage space.
● The Accessibility Status of the storage unit is Scanning after you create a storage unit
(the storage unit is connecting with backup proxies). Wait for the system to
automatically refresh the status. For details, see Viewing a storage unit in 5.2.1
Managing a Storage Unit.
Step 6 After a SAN(XFS) storage unit is created, if the storage system has multiple
Ethernet port IP addresses, configure multiple links to improve the availability of
the storage unit. Otherwise, skip this step.
1. Use PuTTY to log in to the backup proxy.
Default account: hcp. Default password: PXU9@ctuNov17!.
2. Run the su root command and enter the password of user root to switch to
user root.
The default password of user root is Cloud12#$.
3. Run the following command to discover the target:
iscsiadm -m discovery -t st -p iscsi_ip
iscsi_ip indicates the IP address of the Ethernet port that connects to eBackup.
4. Run the following command to scan disks:
upRescan
5. Run the following command to check whether multiple links exist:
upadmin show path
6. Log in to other backup proxies and repeat the preceding steps.
----End
Related Operations
This section uses OceanStor 5000, 5000F, 6000, 6000F V5 series V500R007 version
as an example to describe how to map volumes on a storage device to backup
server and backup proxies. For details about other storage products, see the
related product documentation. For details about supported backup storage types,
see the OceanStor BCManager 8.1.0 eBackup Compatibility List
(Virtualization).
After you run the preceding command, the system continues to run even when no
operation is performed, resulting in security risks. For security purposes, you are
advised to run the exit command to exit the system after completing your operations.
4. Run the following command to check whether UltraPath has been installed:
upadmin show version
Check whether information similar to the following is displayed:
[root@eBackup conf]# upadmin show version
Software Version : xx.xx.xx
Driver Version : xx.xx.xx
Because IP networks that the iSCSI technology uses to connect to remote targets do
not protect the data they transport, you must ensure connection security. One of the
protocols that iSCSI implements is the Challenge Handshake Authentication Protocol
(CHAP), which verifies the legitimacy of initiators that access targets on the network.
CHAP uses a three-way handshake algorithm to verify the identity of your host and, if
applicable, of the iSCSI target when the host and target establish a connection. CHAP
authentication includes unidirectional CHAP authentication in which storage systems
authenticate iSCSI initiators but iSCSI initiators do not authenticate storage systems
and bidirectional CHAP authentication in which an additional level of security enables
iSCSI initiators to authenticate storage systems.
Step 6 Create a mapping view and add host groups and LUN groups the mapping view.
----End
Prerequisites
Before creating a storage pool, create a storage unit.
Context
For details about storage pools, go to 10.3 Backup Storage.
Procedure
Step 1 Log in to the eBackup backup management system using a browser.
Step 4 Enter the basic information of a storage pool. Table 3-7 describes related
parameters.
----End
Prerequisites
Before creating a repository, 3.6 Creating a Storage Pool.
Context
For details about repositories, go to 10.3 Backup Storage.
Procedure
Step 1 Log in to the eBackup backup management system using a browser.
Default account: admin. Default password: PXU9@ctuNov17!.
Step 4 Enter the basic information of a storage pool. Table 3-8 describes related
parameters.
----End
Prerequisites
The protected environment where the backup objects to be protected reside has
been added to eBackup backup management system and the backup objects have
been detected.
Context
For details about protected sets, go to 10.5 Protected Set.
Procedure
Step 1 Log in to the eBackup backup management system using a browser.
Default account: admin. Default password: PXU9@ctuNov17!.
Step 4 Enter the basic information of a protected set. Table 3-9 describes related
parameters.
Available Backup objects that can be You can use either of the following
Objects added to the Selected methods to select backup objects: in
the navigation tree, select the
Objects list by clicking . required backup objects; set filtering
Backup objects that can be criteria and select the required
added to the Excluded backup objects that meet the filtering
criteria.
Objects . NOTE
● If a VM that is not bound to a CNA
host exists in the protected
environment and the VM is powered
on, the VM is displayed under a CNA
host on the FusionCompute page. On
the eBackup page, the VM is not
displayed under any CNA host and is
displayed in parallel with the CNA
host. The inconsistency does not
affect the backup and restore of the
VM.
● The users can select multiple backup
objects at the same time by hold
down Ctrl or Shift.
----End
Context
For details about policies, go to 10.6 Backup Policies.
Procedure
Step 1 Log in to the eBackup backup management system using a browser.
The default user name is admin, and the default password is PXU9@ctuNov17!.
Step 4 Set the basic information of the backup policy. Table 3-10 describes related
parameters.
One time Backup jobs to which a specific The backup policy execution time
backup policy is set are must be later than the current
executed only once. The system time.
backup policy execution time
needs to be set. The parameter
is valid only to full backup. This
parameter is available only
when Schedule is set to One
time.
Create After this option is selected, This function will affect backup
Verificati the system creates verification performance. If you have
on Data data for backup data. The demanding requirements on
verification data will be used to integrity and consistency of
verify the integrity and backup data and have no
consistency of the backup data. requirements on backup
If this option is not selected, performance, you are advised to
the system verifies only the enable this option to ensure data
consistency of the metadata of availability after data restore.
the backup data.
NOTE
Backup data is the real data of
users. Backup metadata is the
additional information about
location of data blocks and
number of disks.
----End
Prerequisites
Before creating a backup plan, create a repository, a protected set, and a backup
policy.
Context
● After configuring associated jobs for a backup plan, you can use the backup
plan wizard to select created objects and start backup jobs. This section
Procedure
Step 1 Log in to the eBackup backup management system using a browser.
Default account: admin. Default password: PXU9@ctuNov17!.
Step 4 On the General Info page, enter the basic information of a backup plan.
1. In Name, enter a backup plan name.
NOTE
The name contains 1 to 128 letters, digits, pluses (+), underscores (_), hyphens (-),
periods (.), and the at symbol (@).
2. In Description, describe the backup plan.
3. Click Next.
The Protected Set page is displayed.
Step 5 Select a protected set using either of the following methods:
● Select a protected set from the list.
● Query a required protected set in the upper right part of the list and select
the protected set.
NOTE
● If no protected sets are available in the list, click the Create Protected Set tab in the
upper right part of the page to create a protected set.
● If there is no VM or VM disk in the protected set, the system will not execute the
backup job.
If no backup policies are available in the list, click the Create Backup Policy tab in the
upper right part of the page to create a backup policy.
you can choose > Backup Plan to manually activate the backup task to be
executed.
NOTE
If the selected backup policy is set to One time and the creation time of the backup plan is
later than the execution time of the backup policy, the system immediately executes the
backup task after the backup plan is created (select Activate).
● If no repositories are available in the list, click the Create Repository tab in the upper
right part of the page to create a repository.
● If a backup job requires more storage capacity than the free capacity of its repository
while the storage pool of the repository has sufficient capacity, the backup job will be
executed. If the capacity of the repository is used up, no backup job will be executed.
NOTICE
You are advised not to run multi backup plans that contain one same VM at the
same time. Or the backup jobs may fail.
----End
Follow-up Procedure
After creating a backup plan, choose > Backup Plan and view information
about the created backup plan.
Prerequisites
The available storage capacity of the repository is sufficient for the backup plan to
execute backup jobs.
Context
Two methods to execute backup jobs are available:
● Automatic:
A backup job is automatically executed according to a backup policy.
● Manual:
A backup job is manually enabled by a user and is executed according to a
backup policy.
When a backup job is manually executed, eBackup backup management system
supports full backup and incremental backup. You can select a backup type based
on actual needs and available storage resources. Table 3-11 describes backup
types.
Full All data on a backup object is You can adopt full backup if you
backup backed up, no matter when data have high data protection
was changed or backed up last requirements and sufficient
time. According to the backup storage resources but have no
policy, the system initially requirements for backup and
executes full backup by default. restore time.
You can manually trigger full If the system has not executed
backup based on actual needs. any backup job before, you can
Full backup provides the most only select full backup to
complete backup protection; perform backup jobs. If the
however, full backup takes a system has performed backup
long time and occupies a large jobs before, you can select full
space. backup or incremental backup
to perform backup jobs.
Increment Data change since last full You can adopt full backup +
al backup backup or incremental backup is incremental backup if you have
backed up. The amount of high requirements for backup
backup data is small and the time and have sufficient storage
backup time is short. resources.
According to the backup policy,
the system initially executes full
backup by default. If the system
detects that the previous backup
is unavailable during the
backup, the system implements
full backup. If the backup is
available, incremental backup is
implemented.
Procedure
Step 1 Log in to the eBackup backup management system using a browser.
● Mouse over a backup plan where you want to execute backup and click in
the function pane.
● Click the backup plan and click in the preview area on the right.
NOTE
● If there is an ongoing backup job of the same protected object in the backup plan, the
system adds a backup job and set it in the Pending state.
● If backup jobs have been executed in the backup plan before, click . The system
automatically executes incremental backup.
● If backup jobs have not been executed in the backup plan before, click . The
system automatically executes full backup.
----End
Prerequisites
Backup jobs have been executed on the VMs to be backed up.
Procedure
Step 1 Log in to the eBackup backup management system using a browser.
Default account: admin. Default password: PXU9@ctuNov17!.
Users can set the types of backup job parameters that need to be displayed. Method: Click
in the upper right corner in the main window of jobs and select the types of backup job
parameters that need to be displayed.
Parameter Description
Parameter Description
Step 5 Click a backup job. In the preview area on the right, view its details.
NOTE
If a backup job fails, that is, Status of the backup job is Failed, you can rectify the fault by
viewing the error information in Details.
Step 6 Optional: Manually stop a backup job in either of the following ways when an
error occurs due to misoperation or when you do not need to execute the backup
job:
● Click the backup job and click in the preview area on the right.
● Mouse over the backup job and click in the button area on the right.
----End
User Requirements
An enterprise uses FusionSphere VMs to run critical services. To ensure data
security on the VMs, the enterprise needs to back up data. The backup data can
be used to recover VMs when VM failures occur. The backup requirements are as
follows:
● The total capacity of disks to be protected is 30 GB. The capacity of stead
data is 27 GB. The amount of changed data on each working day is 0.1%, and
the data is unchanged at weekends.
● It is required to use the same NAS share storage system to store VM data and
backup data.
● Backup cannot interrupt ongoing services on working days.
● When a VM fails, the backup system can restore VMs to a backup point in
time within the latest 7 days.
Data Planning
With appropriate data planning, the eBackup backup management system can
meet diverse users' backup requirements. Data planning is as follows:
● NAS share storage is required to serve as back-end storage. To ensure that the
NAS share storage provides sufficient capacity, use the following formula:
Total capacity of reserved backup data ≤ Storage unit capacity × Storage pool
capacity threshold × Repository capacity threshold, where Total capacity of
reserved backup data = Capacity of steady data + Capacity of steady data ×
Amount of daily changed data × (Retention days of backups - Data
unchanged days). Set the alarm thresholds of the storage pool capacity and
repository capacity to 80% and put data in to the preceding formula like 27
(GB) + 27 (GB) × 0.1% × (7-2) ≤ Storage unit capacity × 80% × 80%. From
the formula, you can calculate the storage unit capacity, which is 42.4 GB at
least. Considering unstable data changes and storage space occupation of
configuration files, set the storage unit capacity to 45 GB. In this way, the NAS
shared path provides 45 GB of storage capacity.
● The eBackup backup management system provides flexible policies to meet
different requirements. To avoid affecting normal services, it is planned to
perform one backup job for the protected VMs at 22:00 every working day.
● The eBackup backup management system provides three backup retention
policies: Permanent, By backup quantity, and By time. The user requires the
backup system to restore VMs to a backup point in time within the latest 7
days. Therefore, the backup policy is set to By time and the retention period
is set to 7 days.
Configuration Roadmap
1. Add a FusionSphere protected environment.
2. Add the protected VM to a protected set.
3. Create a backup policy based on data planning.
4. Configure the storage space and alarm threshold for backup data.
5. Create a backup plan and automate scheduling of the backup plan based on
the backup policy.
Procedure
Step 1 Add a FusionSphere protected environment.
1. Log in to the eBackup backup management system using a browser.
Default account: admin. Default password: PXU9@ctuNov17!.
5. Click OK.
Step 2 Add the protected VM to a protected set.
4. Click OK.
Step 3 Create a backup policy based on data planning.
4. Click OK.
Step 4 Configure the storage space and alarm threshold for backup data.
4. Click OK.
8. Click OK.
Step 5 Create a backup plan and automate scheduling of the backup plan based on the
backup policy.
By default, Activate is selected. After you select this option, the system automatically
executes the backup job based on the selected or new backup policy.
8. Click Next.
The Repository page is displayed.
9. Select the repository created in Step 4.
10. Click Completed.
----End
Verification
The backup plan will automatically schedule backup jobs based on the backup
policy. After backup jobs are completed, users can view the backup jobs and the
generated backups.
4 Restore
When the protected objects data is damaged or lost at the production end and
needs to be restored, eBackup backup management system restores the backup
data on the back-end storage to the production end using the backups generated
at a specific point in time.
4.1 Restoring FusionSphere VMs
4.2 (Optional) Viewing a Restore Job
4.3 Example for Restoring the FusionSphere VM Configuration
4.1.1 Restoring a VM
This section describes how to restore a VM that has been backed up to a specified
location.
Prerequisites
● The VM to be restored is a FusionCompute VM or a VDI VM.
● The VM that you want to restore has been fully backed up and the backup's
status is Valid.
Context
● A VM can be restored to a specified location. Full restore is performed. Backup
data is restored to a new specified path, that is, a new host or cluster and
datastore specified on the original or another VRM. A new VM is created in
the specified location, to which the backup data is restored.
● eBackup can connect to multiple sets of FusionCompute. If multiple sets of
FusionCompute are added to the protected environment, VMs can be
restored.
● For details about backups, go to 10.8 Backups.
Procedure
Step 1 Log in to the eBackup backup management system using a browser.
Step 3 In the Backed Up Environment area, click the protected environment where the
VM that you want to restore resides.
Step 4 Select the VM that you want to restore by performing either of the following
operations.
● Click the VM in the list.
● Find the VM by querying it on the upper right of the list. Then click the VM.
Step 5 In the preview area on the right, place the pointer on the backup required for
restoration and click .
● Before the restore, you can either perform a fast verification by selecting Quick
Verification or perform a full verification by selecting Full Verification. If the
verification status is Valid, the backup can be used to restore the VM.
● VMs whose type is FusionCompute VM or VDI VM support Restore VM to New
Location.
Paramet Description
er
Compute Compute resources that VMs use after restoration, including the
Resource clusters and hosts of the selected protected environment.
----End
Follow-up Procedure
After the restoration, you can log in to FusionCompute based on the target
location to view the information about the restored VM.
NOTE
After backup data of a FusionSphere Linux VM is restored to a new VM, the network
adapters on the new Linux VM may be in disorder. For details, see 7.3.4.3 Linux VM
Network Adapters Are in Disorder When Data Is Restored From a VM Or System Disks
to a New VM.
Prerequisites
● The VM to be restored is a FusionCompute VM or a VDI VM.
● The VM that you want to restore has been fully backed up and the backup's
status is Valid.
Context
● VMs can be batch restored either to specified locations. Full restore is
performed. Backup data is restored to new specified paths, that is, new hosts
or clusters and datastores specified on the original or other VRMs. New VMs
are created in the specified locations, to which the backup data is restored.
● You can batch restore only VMs of the same protected environment. You can
batch restore VMs to the same protected environment. Batch restored VMs
use the same Compute Resource and Datastore.
● For details about backups, go to 10.8 Backups.
● The latest backup of each VM is used by default to batch restore VMs.
● It is recommended that the length of the VM name is from 1 to 226. Or
unknown error may happen.
Procedure
Step 1 Log in to the eBackup backup management system using a browser.
Default account: admin. Default password: PXU9@ctuNov17!.
Step 4 Select the VMs that you want to restore by performing either of the following
operations.
● Click the VMs in the list.
● Find the VMs by querying them on the upper right of the list. Then click the
VMs.
Step 5 Batch restore VM to new location.
NOTE
Before the restore, you can either perform a fast verification by selecting Quick
Verification or perform a full verification by selecting Full Verification. If the verification
status is Valid, the backup can be used to restore the VM.
Protecte The name of the protected environment that the VMs are
d restored to.
Environ
ment
Name
Comput The computing resources that the VMs use after the restore,
e including the clusters and hosts of the selected Protected
Resourc Environment.
e
----End
Follow-up Procedure
After the restore, you can log in to FusionCompute based on the target locations
to view the information about the restored VMs.
Prerequisites
● The VM where the disk to be restored resides is a VM created on
FusionCompute, or a VDI VM.
● The VM disk that you want to restore has been fully backed up and the
backup's status is Valid.
Context
Disks on a VM can be restored to the original VM or a specified VM.
● Restoring a VM disk to the original VM
– If the original disk exists, the data on the disk will be overwritten or
replaced. Incremental restore is priority-ranked performed when the disk
is backed up using CBT.
– If you restore the system disk, the system disk on the original VM will be
replaced or overwritten.
– If the original disk is removed, full restore is performed. That is, a new
disk will be created and mounted in the original VM.
● Restoring a disk to the specified VM
Create a disk for full restore and mount the disk to the specified VM.
For details about backups, go to 10.8 Backups.
Procedure
Step 1 Log in to the eBackup backup management system using a browser.
Default account: admin. Default password: PXU9@ctuNov17!.
Step 6 You can restore VM disks to the original VM or a specified VM. Restore VM disks
to the original VM, go to Step 7; Restore VM disks to a specified VM, go to Step 8.
NOTE
Before the restore, you can either perform a fast verification by selecting Quick
Verification or perform a full verification by selecting Full Verification. If the verification
status is Valid, the backup can be used to restore the VM.
– Datastore provides storage space for restored disks. The drop-down menu lists all
datastores accessible by the target VM. You can select a datastore for the VM disk.
– You can click to select datastores for other VM disks on the VM so that the VM
disks are restored.
– If you want to restore the system disk to a specified VM and the system disk of the
specified VM exists, the datastore type must be the same as that of the system disk
of the specified VM.
4. Optional: Select Start VM after restore.
5. Click OK.
----End
Follow-up Procedure
After the restoration, you can log in to FusionCompute based on the target
location to view the information about the restored VM disk.
NOTE
When a disk (xfs file system) is repetitively recovered to a VM that has mounted multiple
disks (xfs file system), xfs file systems failed to be mounted. Refer to 7.3.4.1 xfs File
System in FusionSphere VMs Failed to Be Mounted.
After backup data of a FusionSphere Linux VM system disk is restored to a new VM, the
network adapters on the new Linux VM may be in disorder. For details, see 7.3.4.3 Linux
VM Network Adapters Are in Disorder When Data Is Restored From a VM Or System
Disks to a New VM.
Prerequisites
● The VM to be restored is a FusionCompute VM or a VDI VM.
● The VM disks that you want to restore have been fully backed up and their
backups' status is Valid.
Context
● If the original disk exists, the data on the disk will be overwritten or replaced.
Incremental restore is priority-ranked performed when the disk is backed up
using CBT. If you restore the system disk, the system disk on the original VM
will be replaced or overwritten. If the original disk is removed, full restore is
performed. That is, a new disk will be created and mounted in the original
VM. You can restore the disks to their original datastores. Alternatively, you
can migrate the disks to another datastore. If you migrate the disks to
another datastore, you can specify datastores for the system disk and other
disks separately.
● You can batch restore only VM disks of the same Protected Environment's
VMs.
● For details about backups, go to 10.8 Backups.
● The latest backup of each disk is used by default to batch restore disks.
Procedure
Step 1 Log in to the eBackup backup management system using a browser.
Step 3 In the Backed Up Environment area, click the protected environment where the
VM disk that you want to restore resides.
Step 4 Select the VM disks that you want to restore by performing either of the following
operations.
● Click the VMs where the VM disks reside in the list.
● Find the VMs by querying them on the upper right of the list.
NOTE
Before the restore, you can either perform a fast verification by selecting Quick
Verification or perform a full verification by selecting Full Verification. If the verification
status is Valid, the backup can be used to restore the VM.
All VM disks that can be created on a VM are selected by default. If a VM disk does not
exist, it is ignored automatically.
Step 7 Optional: Select the datastores that you want to restore the VM disks to.
NOTE
● Datastore provides storage space for restored disks. The drop-down menu lists all
datastores in the protected environment. When selecting a datastore, ensure that it can
be accessed by the original VMs; otherwise, the batch restore will fail.
● If you do not specify any datastore, all VM disks are restored to their original datastores.
● If there are system VM disks among the selected VM disks, to improve data security, you
can save the system VM disks in a separate datastore (the corresponding OS Disk) and
save other VM disks in another datastore of the same type (the corresponding Other
Disks).
----End
Follow-up Procedure
After the restore, you can log in to FusionCompute based on the target location to
view the information about the restored VM disk.
Prerequisites
● The VM where the disk files to be restored reside is a VM created on
FusionCompute.
● A full backup has been successfully performed for the VM disk where the files
to be restored reside, and the backup is in the Valid state.
● The CNA bound to the target VM must use the universal multipathing
software. If no CNA is bound to the target VM, all CNAs in the cluster must
use the universal multipathing software.
● The production storage plane of eBackup must be connected to the storage
plane of CNA over the Ethernet.
● You have imported the license file of the advanced edition.
NOTICE
Procedure
Before the restore, you can either perform a fast verification by selecting Quick
Verification or perform a full verification by selecting Full Verification. If the verification
status is Valid, the backup can be used to restore backup data.
NOTICE
Ensure that the OS type of the target VM is the same as that of the source VM.
If the newly bound disk is not displayed after you run the fdisk -l command, run the
echo 1 > /sys/bus/pci/rescan command to scan the PCI bus again. Run the fdisk -l
command again.
3. Run the pvscan command to scan for physical volumes.
Assume that /dev/xvdh and /dev/xvdi form the vg-flr volume group. When
you use other operating system with a UUID conflict issue, go to Step 9.4.
Otherwise, go to Step 9.5.
Found duplicate PV NBUng5IN8q2hGweLlYhqFBFM94W0zZph: using /dev/xvdh not /dev/xvdf
Found duplicate PV x9T42onhN59dWXal727jdN6Q9MdJxmvr: using /dev/xvdi not /dev/xvde
PV /dev/xvdi VG vg-flr lvm2 [20.00 GiB / 5.00 GiB free]
PV /dev/xvdh VG vg-flr lvm2 [20.00 GiB / 5.00 GiB free]
4. Run the following command to rename the volume group to resolve the UUID
conflict.
vgimportclone --basevgname Name of the new volume group Name of the
newly bound disk partition
For example, run the vgimportclone --basevgname vg-flr_snap /dev/
xvdh /dev/xvdi command to rename the volume group that consists of /dev/
xvdh and /dev/xvdi as vg-flr_snap.
NOTE
If file-level restore has been performed before the target VM is restored and the
volume group name has been changed, you can run the dmsetup remove /dev/New
volume group name/* command to delete the duplicate volume group before
performing this step to avoid volume group renaming failure caused by volume group
name conflicts, you can also use an unused name as the name of the new volume
group.
5. Run the vgchange -ay command to activate the volume group.
6. Run the lvdisplay command to display the logical volumes.
7. Run the mkdir Mounting directory command to create a mounting directory.
8. Run the mount -o ro Name of the newly bound logical volume Mounting
directory command to mount the newly bound logical volume to the specified
directory.
9. Run the cd Mounting directory command to go to the mounting directory and
copy files as required.
10. After the files are copied, run the umount Mounting directory command to
unmount the logical volume.
The following uses Windows Server 2008 R2 Enterprise 64bit as an example.
If the disk is a basic disk, the operation is the same as that for restoring the disk to
the original VM.
If the disk is a dynamic disk (containing only simple volumes), perform the
following operations:
1. Log in to FusionCompute and go to the VM that you want to restore.
2. Choose Start > Administrative Tools > Server Manager. The Server
Manager page is displayed.
3. Choose Storage > Disk Management to view the newly bound disk.
4. If the newly bound disk is in the offline state, set its state to online.
5. When the newly bound disk is online, right-click and select Import Foreign
Disks from the shortcut menu.
6. Go to the newly bound disk and copy files as required.
7. After the file copy is complete, set the newly bound disk to the offline state.
Step 10 Restore the disk to the original VM.
1. Select Restore to Original VM.
2. Click OK.
NOTE
If the newly bound disk is not displayed after you run the fdisk -l command, run the
echo 1 > /sys/bus/pci/rescan command to scan the PCI bus again. Run the fdisk -l
command again.
3. Run the mkdir Mounting directory command to create a mounting directory.
4. Run the mount -o ro Name of the newly bound disk partition Mounting
directory command to mount the newly bound disk to the specified directory.
NOTE
If the file system type of the volume is XFS and the volume is restored to the original
VM, run the mount -o ro,nouuid Name of the newly bound disk partition Mounting
directory command to mount the disk to avoid UUID conflicts.
5. Run the cd Mounting directory command to go to the mounting directory and
copy files as required.
6. After the files are copied, run the umount Mounting directory command to
unmount the disk.
If the disk is managed by the volume management software, perform the
following operations:
1. Log in to FusionCompute and go to the VM that you want to restore.
2. Run the fdisk -l command to view the newly bound disk.
NOTE
If the newly bound disk is not displayed after you run the fdisk -l command, run the
echo 1 > /sys/bus/pci/rescan command to scan the PCI bus again. Run the fdisk -l
command again.
3. Run the pvscan command to scan for physical volumes.
Assume that /dev/xvdh and /dev/xvdi form the vg-flr volume group. If other
OSs are used and no UUID conflict occurs, skip Step 13.4 and go to Step
13.5.
Found duplicate PV NBUng5IN8q2hGweLlYhqFBFM94W0zZph: using /dev/xvdh not /dev/xvdf
Found duplicate PV x9T42onhN59dWXal727jdN6Q9MdJxmvr: using /dev/xvdi not /dev/xvde
PV /dev/xvdi VG vg-flr lvm2 [20.00 GiB / 5.00 GiB free]
PV /dev/xvdh VG vg-flr lvm2 [20.00 GiB / 5.00 GiB free]
If file-level restore has been performed before the target VM is restored and the
volume group name has been changed, you can run the dmsetup remove /dev/New
volume group name/* command to delete the duplicate volume group before
performing this step to avoid volume group renaming failure caused by volume group
name conflicts, you can also use an unused name as the name of the new volume
group.
5. Run the vgchange -ay command to activate the volume group.
6. Run the lvdisplay command to display the logical volumes.
If the file system type of the volume is XFS and the volume is restored to the original
VM, run the mount -o ro,nouuid Name of the newly bound logical volume Mounting
directory command to mount the volume to avoid UUID conflicts.
9. Run the cd Mounting directory command to go to the mounting directory and
copy files as required.
10. After the files are copied, run the umount Mounting directory command to
unmount the logical volume.
NOTICE
If the connection fails, go to Step 14 to end the current task. Then, perform 6
to restore data to the new VM.
NOTE
7. After the file copy is complete, set the newly bound disk to the offline state.
If a disk is a dynamic disk, file-level restore to the original VM is not supported.
After this step is complete, go to Step 14.
Step 14 After the files are copied, end the task.
1. Shut down the target VM.
2. After that, you can perform either of the following operations to abort the
job.
– Click the file-level restore job and in the preview area on the right, click
.
– Move the mouse pointer to the file-level restore job and click in the
button area on the right.
----End
Prerequisites
At least one restore job has been started.
Procedure
Step 1 Log in to the eBackup backup management system using a browser.
Default account: admin. Default password: PXU9@ctuNov17!.
Users can set the types of restore job parameters that need to be displayed. Method: Click
in the upper right corner in the main window of jobs and select the types of restore job
parameters that need to be displayed.
Parameter Description
Parameter Description
Status The running status of the restore job, which can be any of the
following values:
● Aborted
Restore jobs have been aborted. Restore jobs can be stopped
only when its status is Pending or In progress.
● Aborting
Restore jobs are being aborted.
● Pending
In the event of multiple background jobs, the system sorts the
jobs in order of command deliver time and job priority. Jobs
waiting to be processed are set to the Pending state. Manual
restore jobs have a higher priority than automatic ones.
● In progress
The job is being performed, with its progress indicated by the
completed percentage.
● Completed
The job is completed.
● Failed
Restore job failed.
● Verifying
Verifying that the backup job can be scheduled.
Step 5 Click the job whose information you want to view. In the preview area on the
right, view the details about the job.
NOTE
If the job fails to be performed, that is, its Status is Failed, you can rectify the fault by
viewing the error information in Details.
Step 6 Optional: You can manually stop the job by performing either of the following
operations if you do not need the job.
● Click the job. In the preview area on the right, click .
● Place the pointer on the job. In the operation button area on the right, click
.
----End
User Requirements
After backing up a FusionSphere VM as instructed in 3.13 Example for Backing
Up the FusionSphere VM Configuration, the user has a FusionSphere VM whose
data is damaged and needs the eBackup backup management system to restore
the VM. Specifically, the user needs to restore the VM fully to four days ago on
Sunday. Backup data is restored to new specified new paths.
Procedure
Step 1 Log in to the eBackup backup management system using a browser.
Default account: admin. Default password: PXU9@ctuNov17!.
Step 5 Click Restore VM to New Location, and set the information of the new VM.
Step 6 Select Start VM after restore.
Step 7 Click OK.
----End
Verification
After the restore, you can go to > Job to view the recovery job and log in to
FusionCompute to view the VM information based on the target location.
About Users
After configuring users, you can configure system security policies, implement
rights-based service management, as well as monitor and manage online users in
real time.
Regular A regular user only has the rights to view system resources.
user
Related Operations
Operation Navigation Description Key Parameter
Path
If the value of
Number of
Attempts is
reached, the
system
automatically
locks the account.
If the account is
locked, the super
administrator can
manually unlock
it. Alternatively,
wait until the
account is
automatically
unlocked.
● Automatic Unlock
(minutes)
Automatic unlock
time after an
account is locked.
You can configure
this parameter when
Password Lock is
enabled and
Temporary is
selected.
– This parameter is
available to
temporary lock
only. This
parameter
becomes
unavailable if an
administrator or
a regular user is
manually locked
by the super
administrator. In
this case, the
administrator can
be manually
unlocked only.
– This parameter is
available to
administrators
and regular users.
The super
interconnection
user. The default
user name is
NBIUser. The
default password
is
Huawei@CLOUD
8!.
● Role
User role. For details
about role types and
permissions, see
Table 5-1.
NOTE
Administrator and
Regular user can
only search
themselves in the
upper right corner.
● Locked Status
Specifies whether a
user is automatically
locked or is locked
by the super
administrator.
identical
characters.
– Cannot be the
same as the user
name or the
reverse of the
user name.
– In addition, the
password cannot
be the same as
the passwords in
the following
path: /opt/
huawei-data-
protection/
ebackup/
microservice/
ebk_iam/conf
(case-insensitive).
● Max. Number of
User Connections
Indicates the
maximum number
of sessions per user.
If the value of this
parameter is OFF,
the number of
sessions per user is
unlimited.
a user as the
super
administrator.
The locked
user can be
used to log in
to the eBackup
system only
after the super
administrator
manually
unlock it.
storage is
NAS storage
and is
shared to
the backup
server and
backup
proxies using
NFS, the
type of the
storage unit
is NFS.
– S3
When the
back-end
storage is S3
storage and
is shared to
the backup
server and
backup
proxies using
S3, the type
of the
storage unit
is S3.
– SAN(XFS)
If the back-
end storage
is IP SAN,
map a
volume on
the storage
device to the
eBackup
server and
format the
volume into
the XFS file
system. The
volume can
be identified
by the
eBackup
server and
the storage
unit type is
SAN(XFS).
● Capacity
Total storage
unit capacity.
– When the
back-end
storage is
NAS storage,
the total
capacity of
the storage
unit is that
of the
shared
directory.
– When the
back-end
storage is S3
storage, the
total
capacity of
the storage
unit is that
of the
bucket.
– When the
back-end
storage is
SAN(XFS)
storage, the
total
capacity of
the storage
unit is the
total
capacity of
the volume.
● Path
Path for
accessing back-
end storage.
– When the
back-end
storage is
NAS storage,
the path is
used to
access an
NFS share.
– When the
back-end
storage is S3
storage, the
path is used
to access a
bucket.
– If the back-
end storage
is SAN(XFS),
the path for
accessing
the back-end
storage is IP
address of
the target
+WWN of
the volume.
Icon Description
After a FusionSphere protected environment is added to the eBackup backup
management system, the system automatically obtains VM information. Table 5-2
lists the related icons.
Related Operations
Operation Navigation Path Description Key Parameter
● If no
associated
backup
plans are
displayed in
the Backup
Plan area,
delete the
protected
set directly.
3. Use either of
the following
methods to
delete the
protected set:
● Move the
mouse
pointer to
the
protected
set that you
want to
delete and
click in
the button
area on the
right.
● Click the
protected
set that you
want to
delete and
click in
the preview
area on the
right.
to delete the
backup policy:
● Move the
mouse pointer
to the backup
policy that you
want to delete
and click in
the button area
on the right.
● Click the
backup policy
that you want
to delete and
click in the
preview area
on the right.
perform full
backup.
6 System Maintenance
Context
Table 6-1 describes task types of eBackup and their legends.
File-level The system delivers this job when users use backups to
restore restore specific files in VM disk. In file level restore,
larger file size indicates longer restore time.
Scan The system delivers this job when users manually scan
protected for objects in the protected environment.
environm
ent
Verify The system delivers this job when users add protected
credentia environments.
ls
Delete The system delivers this job when users delete specific
backup backups of specific protected objects.
Verify The system delivers this job when users verify the
backup integrity of specific backups of specific protected
objects.
Delete The system delivers this job when users delete specific
backup backup plans.
plan
Restore The system delivers this job when users restore specific
VM disk disks of specific VMs.
Procedure
Step 1 Log in to the eBackup backup management system using a browser.
Default account: admin. Default password: PXU9@ctuNov17!.
Step 3 Optional: In the upper right corner, set the search criteria and click , or click
Advanced to set search criteria and click OK to search for desired background
jobs.
Users can set the types of job parameters that need to be displayed. Method: Click in
the upper right corner in the main window of jobs and select the types of job parameters
that need to be displayed.
Parameter Description
Type Job type. Table 6-1 describes task types of eBackup and their
legends.
Parameter Description
– Background jobs can be aborted in the Pending state when the types are Verify
credentials, Scan environment, Delete backup and Delete backup plan.
– You can stop multiple jobs at the same time. To batch stop jobs, click Abort in the
upper left corner of the job list.
NOTE
If the backup policy associated with the backup job has enabled Dedupe and Compress or
either of them, the backup storage usage can be reduced. Snapshot Size indicates the
volume of data to be backed up. Backup Size indicates the volume of backup data. You can
view the space saving. If Dedupe and Compress are not enabled, 0% space saving will be
displayed for the backup job.
You can collect and analyze backup and restore data based on all or some of the
exported backup jobs, or analyze and locate problems.
● Click Export All in the upper left corner to export all jobs.
● Select a job in the left pane and click Export in the upper left corner to export
the selected job.
● In the upper right corner of the page, select a job based on the search criteria
and click Export List to export the task.
NOTE
The export time may be long. Do not close the current page. If you need to perform
operations, open a new page.
----End
Context
The alarm severity indicates the severity and importance of an alarm. The
management system classifies alarms into three severities: Critical, Major, and
Minor. Table 6-3 describes the definition and handling methods of different
severities of alarms.
Procedure
Step 1 Log in to the eBackup backup management system using a browser.
Step 3 Optional: In the upper right corner, set the search criteria and click , or click
Advanced to set search criteria and click OK to search for desired alarms.
Step 4 Click the alarms that you want to handle and follow instructions in Suggestions
to handle the alarm.
Some alarms in the system need to be manually recovered. If alarms have been
recovered but alarms still exist, or alarm objects have been deleted and related
alarms cannot be automatically cleared, system maintenance engineers can
manually clear alarms to prevent them from affecting follow-up maintenance.
1. After alarms are handled, select alarms that you want to clear and use either
of the following methods to clear them:
– Select the alarms that you want to clear and click Clear in the upper left
button area of the alarm list.
– Click the alarms that you want to clear and click in the preview area
on the right.
2. Click OK in the dialog box that is displayed.
Step 6 Optional: Export alarms. (This section uses Internet Explorer 11 as an example.)
You can click Export All to export all alarms to the local PC.
----End
Context
The similarities and differences of alarms and events are as follows:
● Similarity
Both the alarms and events reflect the changes detected by the management
system on the managed objects.
● Differences
– Alarms are special events. Alarms indicate that anomalies or faults occur
on the management system or its managed objects. Alarms must be
handled as soon as possible to protect services.
– Events only indicate changes to the managed objects. These changes may
not cause service exceptions.
– There are three alarms severities: Critical, Major, and Minor. There are
four event levels: Critical, Major, Minor, and Warning.
Procedure
Step 1 Log in to the eBackup backup management system using a browser.
Default account: admin. Default password: PXU9@ctuNov17!.
You can click Export All to export all events to the local PC.
----End
Context
HA refers to that active and standby modules work in hot or cold backup mode to
implement specific functions. When the active module is faulty, the standby
module automatically takes over the role of the active module to implement
system functions, improving system reliability.
To enable eBackup to support the HA function, plan at least two eBackup servers.
Initialize one as the backup server, and the other servers as backup proxies. By
default, eBackup does not support the HA function. You need to set HA
parameters to configure eBackup as an HA system. After the configuration, the
backup server and one backup proxy work in active/standby mode. After the
backup server fails, the backup proxy takes over the role of the backup server to
ensure normal system operation.
Procedure
Step 1 Log in to the eBackup backup management system using a browser.
Default account: admin. Default password: PXU9@ctuNov17!.
Parameter Description
Parameter Description
NTP Time Status of time consistency between the backup proxies and
Synchronizat backup server. The value can be Synchronized, Unsynchronized
ion Status or Unknown.
If the state of a backup proxy is Unsynchronized, users can click
the backup proxy and click Synchronize Time in the right
information pane to keep time consistency between the backup
proxy and backup server.
If the backup proxy is restarted or newly registered, the state
may become Unknown. In this case, users need to wait for the
system to automatically synchronize the time of the backup
proxy.
NOTE
The backup server functions as a backup proxy. To facilitate the user to view and manage
the detailed information about the backup server or backup proxy, the backup server and
backup proxy are displayed as independent information on the page.
You cannot register or deregister the backup server configured with HA or associated with
backup proxies.
● Registering a selected backup proxy
Select a backup proxy whose Accessibility Status is Accessible and Register
Status is Unregistered and use either of the following methods to register
the proxy:
– Click Register in the upper left area of the server list and click OK in the
Warning dialog box that is displayed.
– Click in the preview area on the right and click OK in the Warning
dialog box that is displayed.
● Registering all backup proxies
– Click in the preview area on the right and click OK in the Warning
dialog box that is displayed.
– Select multiple backup proxies and click Deregister to deregister them in
batches.
NOTICE
eBackup can be configured as an HA system only when there are at least two eBackup
servers in the system, that is, there is at least one independent backup proxy server.
----End
Procedure
Step 1 Log in to the eBackup backup management system using a browser.
Default account: admin. Default password: PXU9@ctuNov17!.
Step 2 In the navigation tree, choose > Configuration > Advanced Settings.
Step 3 Configure global system parameters. Table 6-5 describes related parameters.
Log Level Set the level of background run If you need detailed system run
logs. After this parameter is set, logs to locate faults, you are
the system prints logs of this advised to set the log level to a
level and higher levels and low level, for example, DEBUG.
saves the logs to the /opt/ The default level is INFO.
huawei-data-protection/
ebackup/logs directory or
microservice directory /opt/
huawei-data-protection/
ebackup/microservice/
ebk_xxx/logs on each server.
ebk_xxx indicates the
microservice name.
This parameter indicates the
importance of logs. eBackup
backup management system
classifies system run logs into
six levels: CRITICAL, ERROR,
WARNING, INFO, DEBUG, and
TRACE.
----End
Prerequisites
An SMTP server is available and has been configured.
Context
You need to input email addresses for sending remote alarm notification.
Therefore, you are obligated to take considerable measures, in compliance with
the laws of the countries concerned and the user privacy policies of your company,
to ensure that the personal data of users is fully protected.
Procedure
Step 1 Log in to the eBackup backup management system using a browser.
Default account: admin. Default password: PXU9@ctuNov17!.
Step 2 In the navigation tree, choose > Configuration > Email Notification.
SMTP Server Port number of the SMTP server. The parameter value must
Port be an integer from 1 to
65,535. The default value
is 25.
Interval for Interval at which sending alarm The parameter value must
Sending notification emails to recipients. be an integer from 1 to
Email 1440. The default value is
Notification 5.
(minutes)
A maximum of 30 recipient email addresses are supported and each alarm severity
can add 10 recipient email addresses.
----End
Prerequisites
Currently, only an external NTP server running Linux is supported.
Procedure
Step 1 If eBackup has been added to the Huawei distributed block storage cluster, the
Huawei distributed block storage cluster automatically synchronizes NTP
configurations to the backup server and backup proxy. Perform the following steps
to stop NTP synchronization of Huawei distributed block storage. Skip this step in
other scenarios.
1. Use PuTTY to log in to the eBackup server.
Default account: hcp. Default password: PXU9@ctuNov17!.
2. Run the su root command and enter the password of user root to switch to
user root.
The default password of user root is Cloud12#$.
3. Run the following command to enter the /conf directory and check whether
the value of configuration item IsEnableNtpService in configuration file
servercfg.cfg is TRUE.
cd /opt/dfv/oam/oam-u/nma/conf
– If yes, go to Step 1.4.
– If no, go to Step 2.
4. Run the following command to go to the /scripts directory and check
whether the nma_ctl.sh script exists:
cd /opt/dfv/oam/oam-u/nma/scripts/
– If yes, go to Step 1.5.
– If no, go to Step 2.
5. Run the following commands in sequence to stop the NTP synchronization of
Huawei distributed block storage:
bash /opt/dfv/oam/oam-u/nma/scripts/nma_ctl.sh stopNtpService
6. Run the following command to start NTP of eBackup:
systemctl start ntpd
systemctl enable ntpd
7. Repeat Step 1.1 to Step 1.6 on other eBackup nodes.
8. Restart the eBackup process.
If you only need to change the IP address of the NTP server, skip this step
because the eBackup process does not need to be restarted. After the eBackup
process is restarted, the active and standby eBackup servers are switched over.
After Step 1.1 to Step 1.7 are performed, NTP synchronization of Huawei
distributed block storage is disabled. The eBackup process is restarted to
disable the NTP service on the eBackup page. If the NTP service is enabled,
users cannot change the system time and time zone.
management system and choose > System Time & Zone. The NTP
service is disabled.
Step 2 If eBackup has been added to the Huawei distributed block storage cluster and
NTP synchronization of Huawei distributed block storage cannot be stopped by
performing the preceding steps, perform this step. Otherwise, skip this step.
NOTE
When you configure NTP on the eBackup GUI, only the NTP configurations of the active
and standby backup servers are modified. The NTP configurations of other backup proxies
are not automatically modified.
Step 4 On the navigation bar, choose > System Time & Zone.
Step 5 Configure the system time and time zone. Table 6-7 describes related parameters.
Parameter Description
Parameter Description
System Zone If you modify the system zone of the server not
supported by eBackup (for example, running
yast to modify the system zone in the control
center of the operating system), nothing will be
displayed on the system zone page. In such a
case, you must reconfigure the system zone to
ensure the normal operating of eBackup backup
management system.
----End
Context
The eBackup servers can be deployed in a physical server or VM, you need to
power on the eBackup servers according to the deployed environment and
scenarios.
NOTICE
If the HA function is enabled, power on the active node and then the standby
node. Otherwise, data within 10 minutes after the last power-off may be lost.
If the active and standby nodes are powered off and then powered on in the
specified sequences and if the interval between the power-off and power-on
exceeds 10 minutes, perform operations by following instructions in 7.3.5.5 In an
HA Scenario, the Active and Standby Nodes Are Correctly Configured.
However, Services on the Active Node Fail to Be Started.
Procedure
● Power on the eBackup physical server.
The backup server and backup proxy are deployed on the physical server.
Power on the eBackup server safely using iBMC.
● Power on the eBackup VM.
The following uses FusionCompute 8.x.x as an example.
a. Log in to FusionCompute.
Follow-up Procedure
Check whether eBackup server is successfully started. Run your browser, and enter
https://Management plane IP address or management plane floating IP address
of the backup server:8088, and log in to the backup server as user admin. If you
can log in, the backup server is successfully started.
Prerequisites
● When powering off the eBackup Server, make sure no running service on
eBackup Server.
● When powering off the eBackup Server, you cannot perform other operations
on it.
● You have prepared a cross-platform remote access tool, for example, PuTTY.
Context
After the eBackup Server is powered off, services are interrupted.
NOTICE
If the HA function is enabled, power off the standby node and then the active
node. Otherwise, data within 10 minutes after the last power-off may be lost.
Run the service hcp status command as user root. If AdminNode is running is
displayed in the command output, the node is the active node. Otherwise, the
node is the standby node.
Procedure
Step 1 Use PuTTY to log in to the eBackup server.
Step 2 Run the su root command and enter the password of user root to switch to user
root.
Step 3 Run TMOUT=0 to prevent the system from exiting due to timeout.
NOTE
After you run this command, the system continues to run when no operation is performed,
resulting in a risk. For security, run exit to exit the system.
Step 4 Run shutdown -h now command to power off the eBackup server.
----End
NOTE
For details about all the accounts of eBackup backup management system, see OceanStor
BCManager 8.1.0 eBackup Account List (Virtualization).
Prerequisites
● You have obtained the backup management plane IP address, user name, and
password of backup server.
● You have prepared a cross-platform remote access tool, for example, PuTTY.
Context
● Upon initial login to eBackup as user admin, you need to change the intial
password (PXU9@ctuNov17!) as prompted.
● You are asked to change your password if you are using a new account, or
your password expired, or you are logging in to eBackup for the first time
after the administrator resets your account.
● You can change the password of the eBackup login account in GUI or CLI.
Procedure
● Change the password in GUI.
a. Log in to the eBackup GUI as user admin.
b. In the upper right corner of the management page, click the drop-down
arrow next to the login user.
c. In the shortcut menu that is displayed, choose Change Password.
d. Enter the old password, a new password, and the confirm password in
Old Password, New Password, and Confirm Password respectively.
By default, a password:
▪ Contains 8 to 16 characters.
▪ Cannot be the same as the user name or the reverse of the user
name or contain consecutive characters of the user name.
After you run this command, the system continues to run when no operation is
performed, resulting in a risk. For security, run exit to exit the system.
d. Run cd /opt/huawei-data-protection/ebackup/cli to enter the CLI
command path.
e. Run sh hcpcli.sh admin and input the CLI login password to enter the CLI
mode.
If you log in for the first time, you need to change the initial password to
ensure account security.
To change the password of an account, log in using the account first.
NOTE
The password of admin used in the CLI is the same as that of admin used for
logging in to the eBackup GUI. If the password of admin is changed using the
CLI, the password of admin used for logging in to the GUI is also changed.
f. Run the management command.
The system enters the management view.
g. Run change user_password to change the login password.
Procedure
Step 1 Log in to the backup server GUI as user admin.
To prevent the account from being locked during password change, choose
Settings > Account > Security Policy, and deselect Password Lock before
changing the password. After changing the password, select Password Lock again.
Security risks exist if you deselect Password Lock. Select Password Lock again as
soon as possible after changing the password.
Step 4 Move the mouse pointer to the line where the NBIUser account resides and click
to change the password of the account.
In addition, the password cannot be the same as the passwords in the following
path: /opt/huawei-data-protection/ebackup/microservice/ebk_iam/conf (case-
insensitive).
----End
Prerequisites
● You have obtained the backup management plane IP address of the backup
server as well as user name and password used for login.
● You have prepared a cross-platform remote access tool, for example, PuTTY.
Procedure
Step 1 Log in to eBackup GUI as an administrator.
To prevent the account from being locked during password change, choose >
Account > Security Policy, and deselect Password Lock before changing the
password. After changing the password, select Password Lock again. Security risks
exist if you deselect Password Lock. Select Password Lock again as soon as
possible after performing operations in this section.
After you run the preceding command, the system continues to run even when no
operation is performed, resulting in security risks. For security purposes, you are advised to
run the exit command to exit the system after completing your operations.
Please enter the IAM user name of AdminNode and BackupNode. To use the default username (msuser)
press Enter.
Step 12 Enter the user name and password for accessing the IAM authentication
microservice, and press Enter.
You can use the default user name and press Enter.
The following command output is displayed:
Please enter the password of the IAM user:
Step 15 Run the service hcp restart command to restart the eBackup service so that the
change can take effect.
----End
Prerequisites
● You have prepared a cross-platform remote access tool, for example, PuTTY.
● You have obtained the backup management plane IP address of eBackup.
● You have obtained the passwords of the backup server's root and hcp
accounts.
Context
● Account hcp is an O&M account of the eBackup operating system used for
performing inspections and collecting logs. The initial password is
PXU9@ctuNov17!.
● You are advised to change the password before the password expires. To
query the password expiration time of the hcp account, perform the following
steps:
a. Log in to the server as user hcp.
b. Run the TMOUT=0 command to prevent the system from exiting due to
timeout.
Procedure
● Method one
a. Use PuTTY to log in to the eBackup server as user hcp.
b. Run su root, and input the password of the root account to switch to the
root account.
c. Run TMOUT=0 to prevent the system from exiting due to timeout.
NOTE
After you run this command, the system continues to run when no operation is
performed, resulting in a risk. For security, run exit to exit the system.
d. Run passwd hcp to change password of the hcp account.
The following information is displayed:
Changing password for hcp.
New password:
● Method Two
a. Use PuTTY to log in to the eBackup server as user hcp.
b. Run the TMOUT=0 command to prevent the system from exiting due to
timeout.
NOTE
After the preceding command is executed, the system remains running even
when no operation is performed, posing security risks. For security purposes, run
the exit command to exit the system after you finish performing operations.
c. Run passwd to change password of the hcp account.
The following information is displayed:
Changing password for user hcp.
Changing password for hcp.
(current) UNIX password:
d. Input the old password and press Enter.
The following information is displayed:
New password:
The recommended password rule is as follows:
Password Rule Example
Prerequisites
● You have prepared a cross-platform remote access tool, for example, PuTTY.
● You have obtained the backup management plane IP address of eBackup
server whose password you want to change.
● You have obtained the login password of the hcp account and the root
account.
Procedure
Step 1 Use PuTTY to log in to the eBackup server as user hcp.
Step 2 Run su root, and input the password of the root account to switch to the root
account.
Step 3 Run TMOUT=0 to prevent the system from exiting due to timeout.
NOTE
After the preceding command is executed, the system remains running even when no
operation is performed, posing security risks. For security purposes, run the exit command
to exit the system after you finish performing operations.
----End
Prerequisites
● You have prepared a cross-platform remote access tool, for example, PuTTY.
● You have obtained the backup management plane IP address of eBackup.
● The passwords of users root and hcp have been obtained.
Procedure
Step 1 Use PuTTY to log in to the eBackup server as user hcp.
Step 2 Run su root, and input the password of the root account to switch to the root
account.
Step 3 Run TMOUT=0 to prevent the system from exiting due to timeout.
NOTE
After you run this command, the system continues to run when no operation is performed,
resulting in a risk. For security, run exit to exit the system.
Step 4 Run the following command to generate a ciphertext for the grub password.
The command output returns the new password in ciphertext. Record the
ciphertext.
Step 7 Run the following command to open the file that contains grub boot parameters.
For the Euler operating system, replace the ciphertext next to the
password_pbkdf2 root parameter with that of the new password.
Step 10 Press Esc to exit editing mode, enter :wq, and press Enter.
----End
Prerequisites
● You have obtained the passwords of the GaussDB, eBkDbAdmin, eBkDbUser
and eBkDbUserSec database account.
● You have obtained the backup management plane IP address of eBackup
server.
● You have prepared a cross-platform remote access tool, for example, PuTTY.
Context
● The initial passwords of the GaussDB, eBkDbAdmin, eBkDbUser and
eBkDbUserSec account are Huawei@CLOUD8!.
● Log in to the database in an interactive way. For example, run ./gsql -d
admindb -U eBkDbAdmin -p 6432, and then input the password of the
database account. This avoids recording the password in files such
as .bash_history in case of password leakage.
Procedure
Step 1 Use PuTTY to log in to the backup server as user hcp.
If HA has been configured, perform the following operations on the active backup
server.
Step 2 Run su root, and input the password of the root account to switch to the root
account.
Step 3 Run TMOUT=0 to prevent the system from exiting due to timeout.
NOTE
After the preceding command is executed, the system remains running even when no
operation is performed, posing security risks. For security purposes, run the exit command
to exit the system after you finish performing operations.
NOTE
The database uses the dual account password mechanism. If you enter 2, in the second
item, eBkDbUserSec or eBkDbUser will be displayed as the equivalent account. If
eBkDbUserSec is displayed, the current used account is eBkDbUser. You can change only
the password of account eBkDbUserSec not used. After the modification is successful,
perform the following steps to switch to account eBkDbUserSec.
Step 12 The password is changed successfully. If you enter 2 in Step 8, change the
password of account eBkDbUserSec. Then, perform the following steps to switch
the user.
Step 13 Run the sh change_db_passwd.sh command to switch the active account to the
account whose password is changed.
The following information is displayed:
The operations you can execute are:
1. Change_db_password
2. Switch ebk user
Please choose the operator number that you want to execute:
----End
Context
● Certificate replacement only supports certificates in the X509v3 PEM text
format and does not support certificates in the DER binary format.
● The eBackup microservices support SSL certificates issued by multi-level CAs.
Prerequisites
● You have obtained the CA certificate file, microservice certificate file, and
private key file.
● A cross-platform remote access tool, such as PuTTY, is available.
Procedure
Step 1 Use PuTTY to log in to the eBackup server as user hcp.
Step 2 Run the su root command and enter the password of user root to switch to user
root.
The default password of user root is Cloud12#$.
Step 3 Run the TMOUT=0 command to prevent PuTTY from exiting due to session
timeout.
NOTE
After you run the preceding command, the system continues to run even when no
operation is performed, resulting in security risks. For security purposes, you are advised to
run the exit command to exit the system after completing your operations.
Step 4 Use hcp account through WinSCP to save new CA certificate files, microservice
certificate files, and private key files to path /tmp.
You can run the chmod 444 certificate file name command to allow account
hcpprocess to read CA certificate files, microservice certificate files, and private
key files.
Example: chmod 444 /tmp/cacert.pem
Step 5 Run the cd /opt/huawei-data-protection/ebackup/cli command to go to the CLI
command path.
Step 6 Select operations to perform based on the role:
NOTE
If you want to replace the eBackup Portal certificate, you only need to log in to the backup
server to perform the replacement.
● Backup server:
If HA has been configured, perform the following operations only on the
active backup server.
a. Run the following command, and enter the CLI login password to go to
the CLI mode.
sh hcpcli.sh admin
The default password is PXU9@ctuNov17!, which is the same as the
password of user admin for logging in to the eBackup GUI.
b. Run the following command. The system enters the setting view.
setting
c. Run the following command. The following command output is displayed:
change certification replace
The following command output is displayed:
WARN: This operation may restart nginx service.
Are you sure you want to continue. [yes/no]?
● Backup proxy:
Step 7 After reading the information that is displayed, type yes to confirm the
information and press Enter.
Step 8 Type the ID of the microservice whose certificate you want to replace, and press
Enter.
If you need to replace the eBackup Portal certificate, type the ID corresponding to
the ebk_lb microservice.
NOTICE
If HA has been configured for the backup server and backup proxy, do not select
the following microservices when replacing the certificate of the standby backup
server: ebk_governance, ebk_iam, ebk_license, ebk_alarm, ebk_lb, and all.
Step 9 Type the full path /tmp/** to the new CA certificate file, and press Enter.
Step 10 Type the full path /tmp/** to the new microservice certificate file, and press Enter.
Step 11 Type the full path /tmp/** to the new private key file, and press Enter.
Step 12 Type the password of the private key file, and press Enter.
After replacing the eBackup portal certificate, you need to import the certificate to
the browser if you want no insecure link prompt to be displayed when you access
the eBackup portal.
For example, on the Google Chrome browser, choose Settings > Advanced >
Manage certificates > Trusted Root Certification Authorities > Import, select
certificates, and click Finish. Restart the browser.
----End
Procedure
Step 1 Use PuTTY to log in to the eBackup server as user hcp.
Step 2 Run the su root command and enter the password of user root to switch to user
root.
Step 3 Run the TMOUT=0 command to prevent PuTTY from exiting due to session
timeout.
NOTE
After you run the preceding command, the system continues to run even when no
operation is performed, resulting in security risks. For security purposes, you are advised to
run the exit command to exit the system after completing your operations.
● Backup proxy:
If HA has been configured, perform the following operations on the standby
backup server and backup proxy.
a. Run the su -s /bin/sh hcpprocess -c "/opt/huawei-data-protection/
ebackup/cli/nginxcert_utilities.sh reset" command.
The following information is displayed:
WARN: This operation may restart nginx service.
Are you sure you want to continue. [yes/no]?
Step 7 Type the ID of the microservice whose certificate you want to reset, and press
Enter.
----End
6.4.2.3 Changing the SSL Certificate Key File Password of the eBackup
Microservices
This section explains how to change passwords of private key files of eBackup
microservices' SSL certificates.
Procedure
Step 1 Use PuTTY to log in to the eBackup server as user hcp.
Step 2 Run the su root command and enter the password of user root to switch to user
root.
The default password of user root is Cloud12#$.
Step 3 Run the TMOUT=0 command to prevent PuTTY from exiting due to session
timeout.
NOTE
After you run the preceding command, the system continues to run even when no
operation is performed, resulting in security risks. For security purposes, you are advised to
run the exit command to exit the system after completing your operations.
● Backup proxy:
If HA has been configured, perform the following operations on the standby
backup server and backup proxy.
a. Run the export LD_LIBRARY_PATH=/opt/huawei-data-protection/
ebackup/libs/ command.
b. Run the su -s /bin/sh hcpprocess -c "/opt/huawei-data-protection/
ebackup/cli/nginxcert_utilities.sh modify" command.
The following information is displayed:
WARN: This operation may restart nginx service.
Are you sure you want to continue. [yes/no]?
4.ebk_alarm
5.ebk_backup
6.ebk_restore
7.ebk_delete
8.ebk_copy
9.ebk_vmware
10.ebk_lb
11.ebk_accelerator
12.ebk_mgr
13.ebk_fsbackup
14.ebk_jobmanager
15.all
Step 7 Select the ID of the microservice whose password of the private key file needs to
be changed, and press Enter.
NOTICE
If HA has been configured for the backup server and backup proxy, do not select
the following microservices when changing the SSL certificate key file password of
the standby backup server microservices: ebk_governance, ebk_iam, ebk_license,
ebk_alarm, ebk_lb, and all.
----End
Context
● After adding an HA node, replace SSL certificates of eBackup OMMHA for
communication between the active and standby backup servers. New
certificates on both servers must be issued by the same CA certificate.
Otherwise, communication fails.
● When you replace the SSL certificate, the system automatically restarts the
OMMHA process.
● Certificate replacement only supports certificates in the X509v3 PEM text
format and does not support certificates in the DER binary format.
Prerequisites
● You have obtained the CA certificate file, OMMHA certificate file, and private
key file. To ensure system security, you need to delete the CA certificate file,
OMMHA certificate file, and private key file immediately after certificate
replacement.
● You have obtained the management plane IP address of eBackup server.
● A cross-platform remote access tool, such as PuTTY, has been prepared.
● A cross-platform file transfer tool, such as WinSCP, has been prepared.
Procedure
Step 1 Use PuTTY to log in to the active and standby backup servers as user hcp.
Step 2 Run the su root command and enter the password of user root to switch to user
root.
The default password of user root is Cloud12#$.
Step 3 Run the TMOUT=0 command to prevent PuTTY from exiting due to session
timeout.
NOTE
After you run this command, the system continues to run when no operation is performed,
resulting in a risk. For security purposes, you are advised to run the exit command to exit
the system after completing your operations.
Step 4 Use WinSCP to save the CA certificate file, OMMHA certificate file, and private
key file to path /tmp.
Step 5 Run the cd /opt/huawei-data-protection/ebackup/bin command to go to
the /bin directory.
Step 6 Run the sh cert_replace.sh ommha command.
The following command output is displayed:
WARN: This operation will restart OMMHA server and the link between primary node and standby node
may be disconnected for a while.
Are you sure you want to continue. [yes/no]?
Step 7 After reading the information that is displayed, enter yes to confirm the
information and press Enter.
The following command output is displayed:
Please enter CA certificate file:
Step 8 Enter the /tmp/** full path to the CA certificate file, and press Enter.
The following command output is displayed:
Please enter ommha certificate file:
Step 9 Enter the /tmp/** full path to the certificate file of OMMHA, and press Enter.
The following command output is displayed:
Please enter private key file:
Step 10 Enter the /tmp/** full path to the private key file, and press Enter.
The following command output is displayed:
Please enter pass phrase for key file:
Step 11 Enter the password of the private key file and press Enter.
If the following command output is displayed, the certificate file is successfully
replaced.
replace ommha certificate success!
----End
Context
● When you replace the SSL certificate of eBackup GaussDB, the system
automatically restarts GaussDB. To minimize the impact of the GaussDB re-
startup on services, you are advised to replace the certificate in off-peak
hours.
● Certificate replacement only supports certificates in the X509v3 PEM text
format and does not support certificates in the DER binary format.
● The eBackup GaussDB supports SSL certificates issued by multi-level CAs.
● If the HA function is not configured for the backup server, perform the
operations in this section on the backup server. If the HA function has been
configured for the backup server, replace the SSL certificate of eBackup
GaussDB by referring to 6.4.2.6 Replacing the SSL Certificate of eBackup
Prerequisites
● You have obtained the CA certificate file, DB certificate file, and private key
file. To ensure system security, you need to delete the CA certificate file, DB
certificate file, and private key file immediately after certificate replacement.
● Management plane IP addresses of the backup server have been obtained.
● The password of the private key file of the eBackup GaussDB certificate has
been obtained. The initial password is PXU9@ctuNov17!.
● A cross-platform remote access tool, such as PuTTY, is available.
● A cross-platform file transfer tool, such as WinSCP, is available.
Procedure
Step 1 Use PuTTY to log in to the backup server through a management IP address.
Step 2 Run the su root command and enter the password of user root to switch to user
root.
The default password of user root is Cloud12#$.
Step 3 Run the TMOUT=0 command to prevent PuTTY from exiting due to timeout.
NOTE
After the preceding command is executed, the system remains running even when no
operation is performed, which results in security risks. For security purposes, run the exit
command to exit the system after you finish performing operations.
Step 4 Use WinSCP to save the CA certificate file, DB certificate file, and private key file
to path /tmp.
Step 5 Run the cd /opt/huawei-data-protection/ebackup/bin command to go to
the /bin directory.
Step 6 Run the sh cert_replace.sh db command.
The following command output is displayed:
WARN: This operation will restart GaussDB server.
Are you sure you want to continue. [yes/no]?
Step 7 After reading the information that is displayed, enter yes to confirm the
information and press Enter.
The following command output is displayed:
Please enter CA certificate file:
Step 8 Enter the /tmp/** full path to the CA certificate file, and press Enter.
The following command output is displayed:
Please enter db certificate file:
Step 9 Enter the /tmp/** full path to the DB certificate file, and press Enter.
The following command output is displayed:
Step 10 Enter the /tmp/** full path to the private key file, and press Enter.
Step 11 Enter the password of the private key file and press Enter.
----End
Follow-up Procedure
● If the SSL certificate of the backup server GaussDB is replaced and is not
generated by the CA root certificate of eBackup, you need to perform the
following operations on the backup server and all the backup proxies:
a. Use PuTTY to log in to the backup server and backup proxies as user hcp.
b. Run the su root command and enter the password of user root to switch
to user root.
The default password of user root is Cloud12#$.
c. Run the TMOUT=0 command to prevent PuTTY from exiting due to
timeout.
d. If the SSL certificate is issued by multi-level CAs, place all CA information,
such as the root CA and level-2 CA into certificate file cacert.pem in
sequence.
e. Use WinSCP to copy CA certificate file cacert.pem to the following paths:
▪ /opt/huawei-data-protection/ebackup/microservice/ebk_backup/
conf
▪ /opt/huawei-data-protection/ebackup/microservice/ebk_copy/
conf
▪ /opt/huawei-data-protection/ebackup/microservice/ebk_delete/
conf
▪ /opt/huawei-data-protection/ebackup/microservice/ebk_restore/
conf
▪ /opt/huawei-data-protection/ebackup/microservice/ebk_vmware/
conf
NOTE
h. Run the service hcp restart command to restart the eBackup service
process.
Context
● After adding an HA node, replace SSL certificates of eBackup GaussBD for
communication between the active and standby backup servers. New
certificates on both servers must be issued by the same CA certificate.
Otherwise, communication fails.
● When you replace the SSL certificate of eBackup GaussDB for communication
between the active and standby backup servers, the system automatically
restarts the GaussDB. To minimize the impact of the GaussDB re-startup on
services, you are advised to replace the certificate in off-peak hours.
● Certificate replacement only supports certificates in the X509v3 PEM text
format and does not support certificates in the DER binary format.
● The communication between eBackup GaussDB on active and standby backup
nodes supports SSL certificates issued by multi-level CAs.
Prerequisites
● You have obtained the CA certificate file, DB certificate file, and private key
file. To ensure system security, you need to delete the CA certificate file, DB
certificate file, and private key file immediately after certificate replacement.
● A cross-platform remote access tool, such as PuTTY, has been prepared.
● A cross-platform file transfer tool, such as WinSCP, has been prepared.
Procedure
Step 1 Use PuTTY to log in to the active and standby backup servers as user hcp.
Step 2 Run the su root command and enter the password of user root to switch to user
root.
Step 3 Run the TMOUT=0 command to prevent PuTTY from exiting due to session
timeout.
NOTE
After the preceding command is executed, the system remains running even when no
operation is performed, posing security risks. For security purposes, run the exit command
to exit the system after you finish performing operations.
Step 4 Use WinSCP to save the CA certificate file, DB certificate file, and private key file
to path /tmp.
Step 5 Run the cd /opt/huawei-data-protection/ebackup/bin command to go to
the /bin directory.
Step 6 Run the sh cert_replace.sh db command.
The following command output is displayed:
WARN: This operation will restart GaussDB server.
Are you sure you want to continue. [yes/no]?
Step 7 After reading the information that is displayed, enter yes to confirm the
information and press Enter.
The following command output is displayed:
Please enter CA certificate file:
Step 8 Enter the /tmp/** full path to the CA certificate file, and press Enter.
The following command output is displayed:
Please enter db certificate file:
Step 9 Enter the /tmp/** full path to the DB certificate file, and press Enter.
The following command output is displayed:
Please enter private key file:
Step 10 Enter the /tmp/** full path to the private key file, and press Enter.
The following command output is displayed:
Please enter pass phrase for key file:
Step 11 Enter the password of the private key file and press Enter.
If the following command output is displayed, the certificate file is successfully
replaced.
replace db certificate success!
----End
Follow-up Procedure
● If the SSL certificate of the backup server GaussDB is replaced and is not
generated by the CA root certificate of eBackup, you need to perform the
following operations on the backup server and all the backup proxies:
a. Use PuTTY to log in to the backup server and backup proxies as user hcp.
b. Run the su root command and enter the password of user root to switch
to user root.
▪ /opt/huawei-data-protection/ebackup/microservice/ebk_backup/
conf
▪ /opt/huawei-data-protection/ebackup/microservice/ebk_copy/
conf
▪ /opt/huawei-data-protection/ebackup/microservice/ebk_delete/
conf
▪ /opt/huawei-data-protection/ebackup/microservice/ebk_restore/
conf
▪ /opt/huawei-data-protection/ebackup/microservice/ebk_vmware/
conf
NOTE
Context
● Certificate replacement only supports certificates in the X509v3 PEM text
format and does not support certificates in the DER binary format.
● IAM user authentication supports SSL certificates issued by multi-level CAs.
Prerequisites
● You have obtained the new CA certificate, IAM user authentication certificate
file, and private key file.
● A cross-platform remote access tool, such as PuTTY, is available.
● A cross-platform file transfer tool, such as WinSCP, is available.
Procedure
Step 1 Use PuTTY to log in to the backup server as user hcp.
If HA has been configured, perform the following operations on the active backup
server.
Step 2 Run the su root command and enter the password of user root to switch to user
root.
The default password of user root is Cloud12#$.
Step 3 Run the TMOUT=0 command to prevent PuTTY from exiting due to session
timeout.
NOTE
After you run the preceding command, the system keeps running even no operation is
performed, resulting in a risk. For security purposes, you are advised to run the exit
command to exit the system after completing your operations.
Step 4 Use WinSCP to save the CA certificate file, IAM user authentication certificate file,
and private key file to the /opt path.
Step 5 Run the cd /opt/** command to go to the path where the IAM certificate to be
replaced is located.
For example: Run the cd /opt/huawei-data-protection/ebackup/microservice/
ebk_iam/script/ command.
Step 6 Run the sh replace_iam_cert.sh replace command.
The command output example is as follows:
WARN: This operation will replace the IAM cert and key.
Are you sure you want to continue. [yes/no]?
Step 8 Enter the full path of the CA certificate /opt/**, and press Enter.
The following command output is displayed:
Please enter IAM certificate file:
Step 9 Enter the full path of the IAM certificate /opt/**, and press Enter.
The following command output is displayed:
Please enter private key file
Step 10 Enter the full path of the private key file /opt/**, and press Enter.
The following command output is displayed:
Please enter pass phrase for key file:
Step 11 Enter the password of the private key file, and press Enter.
If the following command output is displayed, the certificate file is successfully
replaced.
----End
6.4.2.8 Changing the Password of the Private Key File of the GaussDB,
OMMHA, or IAM User Authentication Certificate
This section describes how to change the password of the private key file of the
GaussDB, OMMHA, or IAM user authentication certificate. In the factory settings
of IAM, the password of a private key file is generated randomly. Therefore, you
need to replace the IAM user authentication certificate before performing
operations in this section.
Procedure
Step 1 Use PuTTY to log in to the eBackup server where the private key file is stored.
● When HA is not configured, you need to log in to the backup server to change
the password of the GaussDB private key file. When HA is configured, you
need to log in to the active and standby backup servers.
● To change the password of the OMMHA private key file, you need to log in to
the active and standby backup servers.
● When HA is not configured, you need to log in to the backup server to change
the password of the private key file of the IAM user authentication certificate.
When HA is configured, you need to log in to the active backup server.
Step 2 Run the following command to go to the directory where the private key file is
stored:
cd Directory where the private key file is stored
Example:
The private key file of the GaussDB certificate is stored in the /opt/huawei-data-
protection/ebackup/db/cert directory.
The private key file of the OMMHA certificate is stored in the /opt/huawei-data-
protection/ebackup/ha/local/cert/ directory.
The private key file of the IAM user authentication certificate is stored in the /opt/
huawei-data-protection/ebackup/microservice/ebk_iam/conf directory.
Step 3 Run the following command to copy the CA certificate file, certificate file, and
private key file to another directory, for example, /tmp:
cp CA certificate file Certificate file Private key file /tmp
Example:
OMMHA: cp cacert.pem server.crt server.pem /tmp
GaussDB: cp cacert.pem server.crt server.key /tmp
IAM: cp ebk_cacert.pem server.crt server.key /tmp
Step 5 Run the following command, enter the old and new passwords of the private key
file as prompted, and confirm the new password to change the password of the
private key file:
openssl rsa -in Private key file -out New private key file -aes256
In the preceding command, the name of New private key file is user-defined,
which must be different from the name of Private key file.
NOTE
● If OMMHA or GaussDB use the factory settings, the default password of the OMMHA
and GaussDB private key files are PXU9@ctuNov17!.
● In the factory settings of IAM, the password of a private key file is generated randomly.
Therefore, you need to replace the IAM user authentication certificate before performing
operations in this section.
● If IAM does not use the factory settings, the old password is provided by the user.
● The password of a private key file must meet the following complexity requirements:
– Contains 8 to 32 characters.
– Contains at least two types of the following characters: lowercase letters,
uppercase letters, digits, and special characters, including ~`!@#$%^&*()_+|{}:"<>?-
=\[];',./ and spaces.
During the replacement, set the paths of the certificate file, CA certificate file, and
private key file to the new path set in Step 3.
● If you want to change the password of the private key file of the GaussDB SSL
certificate, replace the private key file by referring to 6.4.2.5 Replacing the
SSL Certificate of the eBackup GaussDB.
● If you want to change the password of the private key file of the SSL
certificate of the OMMHA active and standby backup servers, replace the
private key file by referring to 6.4.2.4 Replacing the SSL Certificate of
eBackup OMMHA for Communication Between the Active and Standby
Backup Servers.
● If you want to change the password of the private key file of the SSL
certificate of the GaussDB active and standby backup servers, replace the
private key file by referring to 6.4.2.6 Replacing the SSL Certificate of
eBackup GaussDB for Communication Between the Active and Standby
Backup Servers.
● If you want to change the password of the IAM user authentication
certificate, replace the private key file by referring to 6.4.2.7 Replacing User
IAM Certificate.
----End
Procedure
Step 1 Log in to the eBackup backup management system using a browser.
Default account: admin. Default password: PXU9@ctuNov17!.
3. Click , select the certificate you want to import, and click Upload.
4. Click OK.
Step 4 View a certificate.
On the Certificate page, view imported certificates. Table 6-8 shows detailed
information.
----End
***********************************************
Master key info for ebk_jobmanager
***********************************************
Master key information:
Domain:0, Key ID:1, Key status:0, Today-Create time:3 days
Domain:0, Key ID:2, Key status:1, Today-Create time:0 days
Domain:1, Key ID:1, Key status:1, Today-Create time:0 days
----End
Step 1 Use PuTTY to log in to the eBackup server to which an eBackup key is to be
imported.
Default account: hcp. Default password: PXU9@ctuNov17!.
Step 2 Run the su root command and enter the password of user root to switch to user
root.
The default password of user root is Cloud12#$.
Step 3 Run the following commands in sequence in the directory where the key file is
stored to change the permission on the key file:
chmod 400 Key file name
chown root:root Key file name
Step 4 Run the following command to switch to the directory containing the eBackup key
script:
cd /opt/huawei-data-protection/ebackup/bin/
NOTE
----End
Step 1 Use PuTTY to log in to the eBackup server whose eBackup key validity period is to
be modified.
Default account: hcp. Default password: PXU9@ctuNov17!.
Step 2 Run the su root command and enter the password of user root to switch to user
root.
The default password of user root is Cloud12#$.
Step 3 Run the following command to switch to the directory containing the eBackup key
script:
cd /opt/huawei-data-protection/ebackup/bin/
Step 4 Run the following command to change the eBackup key validity period:
sh import_kmc_key.sh -change_expire_time
The following command output is displayed:
[root@eBackup:/opt/huawei-data-protection/ebackup/bin]sh import_kmc_key.sh -change_expire_time
/opt/huawei-data-protection/ebackup/bin
Current role is 0
Please enter the validity period of the master key. The validity period must be greater than or equal to 180
days and less than or equal to 36500 days:
Enter the validity period of the key as prompted. The validity period must range
from 180 days to 36500 days.
----End
Prerequisites
● A cross-platform remote access tool such as PuTTY has been installed.
● The IP address of the backup management plane and login passwords of the
hcp and root accounts have been obtained.
Context
The eBackup service must be restarted to disable the HTTP protocol. Stop the
eBackup service before disabling the HTTP protocol.
Procedure
Step 1 Use PuTTY to log in to the backup server.
If HA has been configured, perform the following operations on the active backup
server.
Step 2 Run the su root command and enter the password of user root to switch to user
root.
Step 3 Run TMOUT=0 to prevent the system from exiting due to timeout.
NOTE
After you run the preceding command, the system continues to run even when no
operation is performed, resulting in security risks. For security purposes, you are advised to
run the exit command to exit the system after completing your operations.
<VirtualHost *:8080>
ServerName 192.168.100.100:8080
<Directory />
AllowOverride None
Options None
Require all denied
</Directory>
<Directory "${DoCR}">
Options None
AllowOverride None
Require all denied
</Directory>
RewriteEngine on
RewriteOptions Inherit
RewriteCond %{SERVER_PORT} 8080$
RewriteRule ^(.*) https://%{SERVER_NAME}:8088$1 [R,END]
</VirtualHost>
NOTE
In the HA scenario, clear port configurations on both the active and standby backup
servers.
Step 7 Run the following command to make the configuration take effect:
● IPv4: iptables-restore /etc/sysconfig/iptables
● IPv6: ip6tables-restore /etc/sysconfig/ip6tables
Step 8 Run the service hcp restart command to restart the eBackup service.
NOTE
----End
Verification
Before performing operations in this section, you can access the eBackup GUI by
entering https://Floating IP address of the backup server or backup management
IP address of the backup server:port in the address box of a browser or entering
the IP address in the address box.
After performing the operations in this section, you can access the eBackup GUI
only by entering https://Floating IP address of the backup server or backup
management IP address of the backup server:8088.
Prerequisites
● The LDAP CA certificate, certificate, and private key files have been obtained.
● A cross-platform remote access tool, such as PuTTY, has been obtained.
● A cross-platform file transfer tool, such as WinSCP, has been prepared.
Procedure
Step 1 Use PuTTY to log in to the node where the IAM microservice resides, that is, active
backup server.
Step 2 Run the following command and enter the password of user root to switch to user
root.
su root
Step 3 Run the following command to prevent PuTTY from exiting due to timeout.
TMOUT=0
NOTE
After you run the preceding command, the system continues to run even when no
operation is performed, resulting in security risks. For security purposes, you are advised to
run the exit command to exit the system after completing your operations.
Step 4 Run the following command to go to the directory for configuring the IAM
microservice.
cd /opt/huawei-data-protection/ebackup/microservice/ebk_iam/conf
vi hcpconf.ini
NOTE
NOTE
Before you enable LDAPS, make sure that configurations in Step 7.4, Step 7.6, Step 7.7,
Step 7.8, and Step 7.9 have been performed. Otherwise, the LDAP server cannot be
correctly connected.
Step 8 Press Esc to exit the editing mode. Run the :wq! command to save the changes
and exit the CLI.
Step 9 Confirm the protocol selected in Step 7.4.
● If 1(LDAP) is selected in Step 7.4, go to Step 13.
● If 2(LDAPS) is selected in Step 7.4, go to Step 10.
Step 10 Use a file transfer tool, such as WinSCP, to upload the LDAP certificate file
LDAP_Cert.crt, CA certificate file LDAP_CACert.crt, and private key file
LDAP_PriKey.key to the /opt/huawei-data-protection/ebackup/microservice/
ebk_iam/conf directory of the IAM microservice server.
NOTE
Ensure that file names are the same as those in Step 10 to prevent faults in subsequent
operations.
Step 11 Run the following commands to change the owner of the LDAP certificate:
chown hcpprocess:hcpmgr LDAP_CACert.crt
Step 12 Run the following commands to change the permission of the LDAP certificate:
Step 13 After the configurations are performed, manually restart the IAM microservice to
make the corresponding LDAP configurations to take effect. You can perform the
following operations:
1. Run the following command to go to the /opt/huawei-data-protection/
ebackup/microservice/ebk_iam/script directory:
cd /opt/huawei-data-protection/ebackup/microservice/ebk_iam/script
2. Run the following command to stop the IAM microservice:
sh ebackup_stop.sh
3. Wait for the IAM microservice to restart automatically. After the server is
restarted, the configurations take effect.
Run the following commands in sequence to check whether the IAM
microservice is restarted successfully:
cd /opt/huawei-data-protection/ebackup/microservice/ebk_governance/
logs
ps -ef | grep ebk_iam
If information similar to the following is displayed, the IAM microservice is
restarted successfully:
[root@eBackup logs]# ps -ef | grep ebk_iam
hcpproc+ 23726 1 0 Nov17 ? 01:14:20 /opt/huawei-data-protection/ebackup/microservice/
ebk_iam/bin ebk_iam
----End
Prerequisites
You have prepared a cross-platform remote access tool, such as PuTTY.
Context
● After a private key is generated, it must be secured.
● The public key needs to be changed periodically. You can use the new public
and private key pair for login authentication to improve system security.
Procedure
Step 1 Generate a public and private key pair on the maintenance terminal.
1. Run the puttygen.exe.
2. In the Parameters area in the lower part of the page, set Type of key to
generate to SSH-2RSA and Number of bits in a generated key to an integer
from 2048 to 8192.
3. Click Generate and move the cursor over the blank area in the lower part of
the Key area to accelerate the public key generation.
The public key will be displayed in the area.
4. In Key passphrase, enter a password to encrypt the private key. In Confirm
passphrase, enter the password again.
NOTE
This step is optional. To protect the security of the private key file, you are advised to
configure a password to encrypt the private key file.
5. Click Save private key to save the private key file to the local computer.
Step 3 Run the su root command and enter the password of user root to switch to user
root.
After this command is executed, the system keeps running even when no operations are
performed, resulting in security risks. For security purposes, you are advised to run exit to
exit the system after completing your operations.
Step 5 Run cd ~ to enter the /home directory of the current login user.
Step 6 Run the ls -al command to check whether the .ssh file package exists in the
directory. If no, run mkdir .ssh to create the file package.
Step 8 Run ll to check whether authorized_keys exists in the file package. If no, run
touch authorized_keys to create the file.
Step 9 Copy the generated public key to the authorized_keys file on the eBackup server
and save the file.
NOTE
If content exists in the authorized_keys file, copy the public key to a new line.
Step 14 Click Open. Enter the user name and password of the private key (if configured)
to log in to the eBackup server.
----End
6.6 Inspection
By accessing databases, SmartKit checks the eBackup server comprehensively and
in real time, analyzes faults, and provides solutions for fault rectification.
Prerequisites
● You have obtained a SmartKit installation package of V200R007C00RC10 or a
later version. This section uses V200R007C00RC10 as an example. The
package name is SmartKit_V2R7C00RC10.zip. Obtain the installation
package as follows:
– For enterprise users: Click here.
– For carrier users: Click here.
● You have obtained the OceanStor BCManager
8.1.0_eBackup_Service_Euler_arm64.zip (for Euler, Arm architecture), or
OceanStor BCManager 8.1.0_eBackup_Service_Euler_x86_64.zip (for Euler,
x86 architecture) software package.
Obtain the software packages as follows:
– For enterprise users: Click here.
– For carrier users: Click here.
NOTE
● During the inspection, obtain the software package that is compatible with the
eBackup server. Otherwise, the inspection result will be incorrect. For example, you
cannot use the X86 software package to inspect the TaiShan server.
● The software package name changes with the actual software version, software
package must be the actual version in use.
● The eBackup server is normal.
● You have obtained the backup management plane IP address of the eBackup
and hcp account password. The initial password of user hcp is
PXU9@ctuNov17!. Change the password regularly for security purposes.
NOTE
To prevent the software package from being maliciously tampered with during transmission
or storage, download the corresponding digital signature file for integrity verification while
downloading the software package.
After the software package is downloaded from Huawei Support website, verify its PGP
digital signature by referring to OpenPGP Signature Verification Guide. If the verification
fails, do not use the software package, and contact Huawei technical support.
Before the software package is used for installation or upgrade, its digital signature also
needs to be verified by referring to the OpenPGP Signature Verification Guide to ensure
that the software package is not tampered with. To obtain this document, visit the
following link:
For carrier users, log in to http://support.huawei.com/carrier/digitalSignatureAction.
For enterprise users, log in to https://support.huawei.com/enterprise/en/tool/pgp-verify-
TL1000000054.
Context
eBackup supports inspection by SmartKit and built-in tools. For details about how
to use built-in tools to implement inspection, see the 6.8.6.5 Using the Inspection
Tool to View Desired Information.
Procedure
Step 1 Decompress OceanStor BCManager 8.1.0_eBackup_Service_Euler_arm64.zip or
OceanStor BCManager 8.1.0_eBackup_Service_Euler_x86_64.zip in the
maintenance terminal.
After the decompression, you obtain the following two files:
● OceanStor-eBackup-xxx-Collect.zip
● OceanStor-eBackup-xxx-Inspect.zip
Step 3 After you log in to SmartKit, if a message is displayed asking you to upgrade tools,
click Upgrade.
Step 4 On the home page, open Function Management.
Step 6 In the Verification and Installation window, select Inspection, and click Install.
Step 7 After the import is successful, Import succeeded message is displayed. Click OK.
Step 8 Select Storage and click Inspection.
2. If passwords are not used to log in to the eBackup server, click Customize
Authentication. In the dialog box that is displayed, select an authentication
mode, and click OK.
● Publickey authentication
Set Username to hcp, select a key file, enter the key password, and then click
Finish.
For details about how to obtain the key file and key password, see 6.5
Logging In to eBackup Server Using Public Key Authentication.
Step 16 By default, all inspection items are selected. You can select the items you want to
check, and click Next.
Step 17 Select a path for saving the inspection result file and click Next. The system
automatically starts the inspection task.
Step 18 When the inspection is completed, click Open the result directory or View the
report to view the inspection result.
If Not passed exist in the inspection report, go to the next step. Otherwise, the
inspection is completed.
Step 19 Log in to the eBackup backup management system using a browser as user
admin.
Step 20 On the navigation bar, choose Monitor > Event. View events whose severity
is warning and handle the events according to suggestions.
If the check items whose check results are Not passed are not displayed on the
eBackup GUI, contact technical support engineers.
----End
Follow-up Procedure
When viewing details about check items in an inspection report, pay special
attention to check items whose Result is Not passed. You need to follow
instructions in Suggestions to handle those items to ensure normal system
operation.
● You are advised not to change the configuration items not described in Table
6-10. Otherwise, the running of the eBackup service may be affected.
● After modifying some configuration items, you need to run the service hcp
restart command to restart the eBackup process.
● If the value of a configuration item is blank or falls without the range, the
system automatically restores the value to the default value.
● The hcpconf.ini configuration file where the AlarmEmailSendInterval,
OcAlarmPerformIP, OcAlarmPerformPort, OcAlarmPerformAccount,
AlarmType, and DonotAlarmEvent configuration items reside is stored in
the /opt/huawei-data-protection/ebackup/microservice/ebk_alarm/conf
path on the backup server.
one storage
unit x
Maximum
number of
buckets
supported by a
backup system
≤ Maximum
number of
connections
supported by
one S3 storage
unit
If either of the
preceding
requirements is
not met, backup
and restore jobs
may fail.
6.8.1 Installation
Script Function
Used to install, uninstall, and initially configure the software of eBackup.
Script Path
Installation package path customized by users.
Script Users
The script is executed by the root account.
Execution Method
Install eBackup:
~> sh ebackup_utilities.sh install virtual
Initially configure eBackup:
~> sh ebackup_utilities.sh config
uninstall eBackup:
~> sh ebackup_utilities.sh uninstall
Script Parameters
None
Precautions
You need to run service hcp stop to stop the eBackup services before executing
the sh ebackup_utilities.sh config script.
6.8.2 Uninstallation
Script Function
Used to uninstall the eBackup software.
Script Path
/opt/huawei-data-protection/ebackup/bin
Script Users
The script is executed by the root account.
Execution Method
~> sh uninstall.sh
Script Parameters
None
Precautions
None
6.8.3 Upgrade
Script Function
Used to establish a trust relationship between nodes
Script Path
/opt/huawei-data-protection/ebackup/bin
Script Users
The script is executed by the root account.
Execution Method
~> sh upgrade_tool.sh make_trust
Script Parameters
None
Precautions
The script is used in the upgrade of later versions. You can only execute this script
on the backup server.
Script Function
Used to clear a trust relationship between nodes
Script Path
/opt/huawei-data-protection/ebackup/bin
Script Users
The script is executed by the root account.
Execution Method
~> sh upgrade_tool.sh clean_trust
Script Parameters
None
Precautions
The script is used for upgrade in the later versions. You only can execute this script
on the backup server.
Script Function
Used to stop the backup services of all nodes in eBackup backup management
system
Script Path
/opt/huawei-data-protection/ebackup/bin
Script Users
The script is executed by the root account.
Execution Method
~> sh upgrade_tool.sh stop_all
Script Parameters
None
Precautions
The script is used in the upgrade of the later versions. You can only execute this
script on the backup server.
6.8.4 Process
Script Function
Used to start the eBackup process
Script Path
Any path
Script Users
The script is executed by the root account.
Execution Method
~> service hcp start or /etc/init.d/hcp start
NOTE
To forcibly start the eBackup process, run the service hcp start force or /etc/init.d/hcp start
force command.
Script Parameters
None
Precautions
None
Script Function
Used to stop the eBackup process
Script Path
Any path
Script Users
The script is executed by the root account.
Execution Method
~> service hcp stop or /etc/init.d/hcp stop
Script Parameters
None
Precautions
None
Script Function
Used to view the eBackup process
Script Path
Any path
Script User
The script is executed by the root account.
Execution Method
~> service hcp status or /etc/init.d/hcp status
Script Parameters
None
Precautions
None
Script Function
Used to restart the eBackup process
Script Path
Any path
Script Users
The script is executed by the root account.
Execution Method
~> service hcp restart or /etc/init.d/hcp restart
Script Parameters
None
Precautions
None
6.8.5 HA
Script Function
Used to stop the HA process and HA monitoring process
Script Path
/opt/huawei-data-protection/ebackup/ha/module/hacom/script
Script Users
The script is executed by the root account.
Execution Method
~> sh stop_ha.sh
Script Parameters
None
Precautions
None
Script Function
Used to start the HA process and HA monitoring process
Script Path
/opt/huawei-data-protection/ebackup/ha/module/hacom/script
Script Users
The script is executed by the root account.
Execution Method
~> sh start_ha.sh
Script Parameters
None
Precautions
None
Script Function
Used to stop the HA process
Script Path
/opt/huawei-data-protection/ebackup/ha/module/hacom/script
Script Users
The script is executed by the root account.
Execution Method
~> sh stop_ha_process.sh
Script Parameters
None
Precautions
After the HA process is stopped, the HA monitoring program will detect and
restart it after a while.
Script Function
Used to query the HA active/standby state
Script Path
/opt/huawei-data-protection/ebackup/ha/module/hacom/script
Script Users
The script is executed by the root account.
Execution Method
~> sh status_ha.sh
Script Parameters
None
Precautions
None
Script Function
Used to clear HA configuration information of a standby backup server that you
want to forcibly remove
Script Path
/opt/huawei-data-protection/ebackup/bin
Script Users
The script is executed by the root account.
Execution Method
~> sh ha_tool.sh clear
Script Parameters
clear: clears HA configuration information.
Precautions
None
Script Function
Used to monitor data synchronization between active and standby GaussDB
Script Path
/opt/huawei-data-protection/ebackup/bin
Script User
The script is executed by the root account.
Execution Method
~> sh db_sync_monitor.sh Parameter
Script Parameters
Parameter Description
Precautions
None
6.8.6 Others
Script Function
Used to restore a database by employing backup database files
Script Path
/opt/huawei-data-protection/ebackup/bin
Script Users
The script is executed by the root account.
Execution Method
~> sh hcp_admindb_restore.sh
Parameter Description
None
Precautions
None
Script Function
Used to restore a database by importing backups in a storage unit to the database
Script Path
Any path
Script Users
The script is executed by the root account.
Execution Method
~> service hcp recover or /etc/init.d/hcp recover
Parameter Description
None
Precautions
None
Script Function
When a backup or restoration job fails when the production storage is Huawei
distributed block storage, you can use this script to query and delete differential
bitmap volumes as prompted.
NOTE
The system compares two snapshots and generates incremental bitmap information.
Volumes that store the differential bitmap information are differential bitmap volumes.
Script Path
/opt/huawei-data-protection/ebackup/vbstool
Script User
The script is executed by the root account.
Execution Method
~> sh vrmVBSTool.sh --parameter name
Parameter Description
Parameter Description
Parameter Description
Script Function
Configures firewall rules for eBackup servers.
Script Path
/opt/huawei-data-protection/ebackup/bin
Script User
The script is executed by the root account.
Execution Method
~> sh iptablesHelper.sh parameter name
Parameter Description
Parameter Description
Parameter Description
Parameter Description
Script Function
Used to view desired information by employing the inspection tool
Script Path
/opt/huawei-data-protection/ebackup/bin
Script Users
The script is executed by the hcp account.
Execution Method
~> ./inspect.py parameter name
Parameter Description
Parameter Description
Precautions
The script can only be executed on the backup server. After the script is executed,
the inspection information about all servers is displayed.
Script Function
Used to enable CLI
Script Path
/opt/huawei-data-protection/ebackup/cli
Script Users
The script is executed by the hcp account.
Execution Method
~> sh hcpcli.sh user port
Parameter Description
Parameter Description
Precautions
None
Script Function
Used to manage open-iscsi
Script Path
Any path
Script Users
The script is executed by the root account.
Execution Method
~> service open-iscsi parameter name
Parameter Description
Parameter Description
Precautions
None
Script Function
Used to enable the log collection tool
Script Path
/opt/huawei-data-protection/ebackup/bin
Script User
The script is executed by the hcp account.
Execution Method
~> sudo ./make_report.py from_tools
Parameter Description
Parameter Description
Precautions
This script can be remotely invoked by Smartkit only. If the customer does not
have Smartkit onsite, run this script manually to collect logs. After the command
is manually executed, a file named HCP_Report_Timestamp.tar is generated in
the /opt/huawei-data-protection/ebackup/tmp directory (Run the tar xvf
command to decompress the file). You need to manually delete the file.
Script Function
On the backup server, this script is used to check whether the connection between
eBackup and S3 is set up successfully.
Script Path
/opt/huawei-data-protection/ebackup/sbin
Script Users
The script is executed by the root account.
Execution Method
1. Run OLD_LD_LIBRARY_PATH=$LD_LIBRARY_PATH
2. Run export LD_LIBRARY_PATH=/opt/huawei-data-protection/ebackup/
libs:/lib64.
3. Run ./uds_plug-in TestBucket <domain_name or ip_address> <bucket_name>
<access_key> <secret_access_key>.
4. Run export LD_LIBRARY_PATH=$OLD_LD_LIBRARY_PATH
Parameter Description
Parameter Description
access_key AK
secret_access_key SK
Precautions
● The connection is successful if the following information is displayed.
Test bucket success.
Script Function
Deletes residual differential bitmap volumes after data backup.
Script Path
/opt/huawei-data-protection/ebackup/sbin
Script User
The script is executed by the root account.
Execution Method
1. Log in to the active backup server as user root.
2. Run the TMOUT=0 command to prevent the system from exiting due to
timeout.
NOTE
After you run the preceding command, the system keeps running even when no
operation is performed, resulting in security risks. For security purposes, you are
advised to run the exit command to exit the system after completing your operations.
3. Run the cd /opt/huawei-data-protection/ebackup/sbin command to go to
directory /opt/huawei-data-protection/ebackup/sbin.
4. Run the sh deleteBitmapVolumes.sh query <Huawei distributed block
storage FloatIP> [PoolID] command to query residual differential bitmap
volumes.
6. Input the management plane IP address of a backup server, and press Enter.
Enter the password of user hcp:
7. Input the password of user hcp of the backup server, and press Enter.
Enter the password of user root:
8. Input the password of user root of the backup server, and press Enter.
Do you want to enter the backup management plane IP address of another eBackup node?(y/n)
(default:y)
9. Check whether you have input the preceding information of the backup server
interconnected with the Huawei distributed block storage system.
You must input information of all backup servers interconnected with the
Huawei distributed block storage system. Otherwise, whether residual
differential bitmap volumes are in use cannot be correctly determined, and
residual differential bitmap volumes may be mistakenly deleted.
– If you have not input information of all backup servers, perform the
following operations:
10. Input y, and press Enter.
The following command output is displayed:
Please enter the backup management plane IP address of an eBackup node:
11. Repeat 6 to 8 to input information of other backup servers.
After the eBackup server information is entered, the following information is
displayed:
Do you want to enter the backup management plane IP address of another
eBackup node?(y/n)(default:y)
12. Input n, and press Enter.
The following command output is displayed:
Total Nodes: 2 10.142.28.158 10.142.28.159 Do you want to enter the backup
management plane IP address of another eBackup node?(y/n)(default:y)
– If you have input information of all backup servers, input n, and press
Enter.
The following command output is displayed:
Total Nodes: 3
10.142.28.155
10.142.28.157
10.142.28.156
Do you want to enter the backup management plane IP address of another eBackup node?(y/n)
(default:y)
13. Check whether you have input information of all backup servers
interconnected with the Huawei distributed block storage system again.
If you have input information of all backup servers, input n, and press Enter.
If the following command output is displayed, residual differential bitmap
volumes are deleted:
Delete bitmap volume complete.
Parameter Description
Parameter Description
Precautions
None
Script Function
Deletes residual snapshots after backup.
Script Path
/opt/huawei-data-protection/ebackup/sbin
Script User
The script is executed by the root account.
Execution Method
1. Log in to the active backup server as user root.
2. Run the TMOUT=0 command to prevent the system from exiting due to
timeout.
NOTE
After you run the preceding command, the system keeps running even when no
operation is performed, resulting in security risks. For security purposes, you are
advised to run the exit command to exit the system after completing your operations.
3. Run the mkdir /opt/huawei-data-protection/ebackup/tmp/
deleteSnapshots command to create directory /opt/huawei-data-
protection/ebackup/tmp/deleteSnapshots.
Parameter Description
Parameter Description
Precautions
● FusionCompute can only be connected to one eBackup system. Otherwise,
whether snapshots are in use cannot be correctly determined, and snapshots
may be mistakenly deleted.
● You can only delete residual snapshots one day after they have been created.
● Storage units used by an eBackup system cannot be S3 and all of the storage
units can be accessed. Otherwise, deleting residual snapshots will fail.
Script Function
Clears residual data after the backup plans are deleted.
This script is applicable when storage units added on an eBackup node are only
used by the eBackup node. If the storage units are also used by other eBackup
nodes, running the script may delete backup data still needed in the environment.
Therefore, run the script cautiously.
Script Path
/opt/huawei-data-protection/ebackup/sbin
Script User
The script is executed by the root account.
Execution Method
1. Log in to the active backup server as user root.
2. Run the TMOUT=0 command to prevent the system from exiting due to
timeout.
NOTE
After you run the preceding command, the system keeps running even when no
operation is performed, resulting in security risks. For security purposes, you are
advised to run the exit command to exit the system after completing your operations.
3. Run the cd /opt/huawei-data-protection/ebackup/sbin command to go to
directory /opt/huawei-data-protection/ebackup/sbin.
4. Run the sh deleteResData.sh command to delete residual data in backups.
If information similar to the following is displayed, select the database
account and enter its password as prompted. The default password is
Huawei@CLOUD8!.
You are advised to select 3. If you enter incorrect passwords for the first two
accounts consecutively, services will be affected after the accounts are locked.
The users you can use to connect to db:
1. eBkDbAdmin
2. eBkDbUser
3. GaussDB
Please choose the user's number that you want to use to connect to db:
Parameter Description
None
Precautions
None
7 Troubleshooting
Step 1 Record the System messages (such as error codes and job details)
system that are displayed after a fault occurs can be used to
messages locate and rectify the fault.
when faults
occurred.
Step 3 Record all If no system messages are displayed, you can collect
information. alarms and logs. For details, see 7.2 Information
Collection.
Step 4 Rectify the After the fault is located, rectify the fault by following
fault. instructions in:
● System messages
● Alarms
● Logs
● 7.3 Troubleshooting Cases
Prerequisites
● You have obtained a SmartKit installation package of V200R007C00RC10 or a
later version. This section uses V200R007C00RC10 as an example. The
package name is SmartKit_V2R7C00RC10.zip. Obtain the installation
package as follows:
– For enterprise users: Click here.
– For carrier users: Click here.
● You have obtained the OceanStor BCManager
8.1.0_eBackup_Service_Euler_arm64.zip (for Euler, Arm architecture), or
OceanStor BCManager 8.1.0_eBackup_Service_Euler_x86_64.zip (for Euler,
x86 architecture) software package.
Obtain the software packages as follows:
– For enterprise users: Click here.
– For carrier users: Click here.
NOTE
● During the inspection, obtain the software package that is compatible with the
eBackup server. Otherwise, the inspection result will be incorrect. For example, you
cannot use the X86 software package to inspect the TaiShan server.
● The software package name changes with the actual software version, software
package must be the actual version in use.
● The eBackup server is normal.
● You have obtained the backup management plane IP address of the eBackup
and hcp account password. The initial password of user hcp is
PXU9@ctuNov17!. Change the password regularly for security purposes.
NOTE
To prevent the software package from being maliciously tampered with during transmission
or storage, download the corresponding digital signature file for integrity verification while
downloading the software package.
After the software package is downloaded from Huawei Support website, verify its PGP
digital signature by referring to OpenPGP Signature Verification Guide. If the verification
fails, do not use the software package, and contact Huawei technical support.
Before the software package is used for installation or upgrade, its digital signature also
needs to be verified by referring to the OpenPGP Signature Verification Guide to ensure
that the software package is not tampered with. To obtain this document, visit the
following link:
For carrier users, log in to http://support.huawei.com/carrier/digitalSignatureAction.
For enterprise users, log in to https://support.huawei.com/enterprise/en/tool/pgp-verify-
TL1000000054.
Context
Run logs of eBackup will be compressed and dumped. You can view the retention
policy of run logs in file /opt/huawei-data-protection/ebackup/conf/
hcplogrotate.conf on any eBackup server. Details are as follows:
● maxage indicates the retention period of compressed log files (unit: day).
● rotate indicates the number of retained compressed log files.
● size indicates the specified size of each log file. When a log file reaches the
value of size (unit: MB), the log file will be compressed and dumped.
Procedure
Step 1 Decompress OceanStor BCManager 8.1.0_eBackup_Service_Euler_arm64.zip or
OceanStor BCManager 8.1.0_eBackup_Service_Euler_x86_64.zip in the
maintenance terminal.
● OceanStor-eBackup-xxx-Collect.zip
● OceanStor-eBackup-xxx-Inspect.zip
Step 3 After you log in to SmartKit, if a message is displayed asking you to upgrade tools,
click Upgrade.
Step 6 In the Verification and Installation window, select Information Collection, and
click Install.
Step 7 After the import is successful, Import succeeded message is displayed. Click OK.
Step 8 Select Storage and click Storage Information Collection.
If you need to collect information about multiple eBackup nodes, fill in the
configuration page multiple times.
2. If passwords are not used to log in to the eBackup server, click Customize
Authentication. In the dialog box that is displayed, select an authentication
mode, and click OK.
● Publickey authentication
Set Username to hcp, select a key file, enter the key password, and then click
Finish.
For details about how to obtain the key file and key password, see 6.5
Logging In to eBackup Server Using Public Key Authentication.
----End
7.3.1.1 The Uninstallation Task Lasts for a Long Period After the uninstall.sh
Command Is Executed
Symptom
The uninstall.sh command is executed to uninstall eBackup. The uninstallation
task lasts for a long period.
Possible Causes
The storage mounted to the eBackup server is inaccessible.
Procedure
Step 1 Run the reboot command to restart the eBackup server OS.
Step 2 Go to the /opt/huawei-data-protection/ebackup/bin directory and run the sh
uninstall.sh command to uninstall eBackup.
Step 3 If the problem is not resolved, contact Huawei technical support.
----End
7.3.1.2 The Newly Added Backup Proxy Cannot Be Viewed on the Backup
Server Page
Symptom
After the backup proxy is configured, the newly added backup proxy cannot be
viewed by choosing Monitor > Server on the backup server page.
Possible Causes
The public key file between the backup server and the backup proxy is not paired.
As a result, the communication between the backup proxy and backup server fails.
Procedure
Step 1 Use PuTTY to log in to the backup proxy.
Default account: hcp. Default password: PXU9@ctuNov17!.
Step 2 Run the su root command and enter the password of user root to switch to user
root.
The default password of user root is Cloud12#$.
Step 3 Run the cd /opt/huawei-data-protection/ebackup/conf/cert/ command.
Step 4 Run the cat BackupNode.pub command to open the BackupNode.pub file and
record the content of the file.
Step 10 Enter add public_key <pubkey> to add the content of the BackupNode.pub file
of the backup proxy recorded in Step 4.
Step 13 Run the show server_public_key command to check the public key of the backup
server and copy the key.
Step 15 Run the su root command and enter the password of user root to switch to user
root.
Step 16 Run the cd eBackup software package decompression path command to go to the
directory where the eBackup software package is decompressed.
Step 17 Run the service hcp stop command to stop the service.
Step 19 Log in to the backup server GUI and choose Monitor > Server. The new proxy is
added.
----End
7.3.2 Login
Symptom
The eBackup GUI displays a message indicating "system is in restricted mode"
when I log in to eBackup.
Possible Causes
The database is abnormal, or the database memory is insufficient.
Procedure
Step 1 Possible cause 1: The database is abnormal, or the database memory is
insufficient.
1. Log in to the eBackup server using PuTTY.
Default account: hcp. Default password: PXU9@ctuNov17!.
2. Run the su root command and enter the password of user root to switch to
user root.
The default password of user root is Cloud12#$.
3. Run TMOUT=0 to prevent system timeout.
NOTE
After you run this command, the system continues to run even when no operation is
performed, posing a risk. For security purposes, you are advised to run exit to exit the
system after completing your operations.
4. Run df -h /opt to check whether the remaining capacity of the storage where
the database file resides is insufficient. If the capacity usage is higher than
96%, the remaining capacity is insufficient.
– If yes, run rm File name or rm -rf Folder name to delete unneeded files
or folders other than eBackup software.
– If no, go to Step 1.5.
----End
7.3.3 Backup
Symptom
A backup job may be in the In progress state and cannot be interrupted if the
network of an NFS storage unit is constantly or intermittently interrupted during
backup.
Possible Causes
Data is written into the storage unit. Wait for the system response. If the network
of the NFS storage unit is constantly or intermittently interrupted, the entire
network will be interrupted. As a result, the backup job enters the In progress
status and cannot be interrupted.
Procedure
Step 1 Run the reboot command to restart the backup proxy operating system.
● If the operating system is restarted successfully, no further action is required.
● If the operating system fails to be restarted, go to Step 2.
Step 2 Run the following two commands one by one to restart the backup proxy
operating system.
echo 1 > /proc/sys/kernel/sysrq
echo b > /proc/sysrq-trigger
NOTE
If the backup proxy operating system can be restarted normally, the problem is solved.
----End
7.3.3.2 A Backup Job May Be in the In progress State for a Long Time If
Networks of Production Storage Are Constantly or Intermittently
Interrupted During Backup
Symptom
A backup job may be in the In progress state for a long time and the backup
progress remains unchanged if networks of production storage are constantly or
intermittently interrupted during backup.
Possible Causes
When data is read from storage devices, if the networks of the production storage
are constantly or intermittently interrupted, read operations enter the waiting
state. As a result, the backup job is in the In progress state for a long time.
Procedure
Step 1 Use PuTTY to log in to the backup proxy that runs the backup task.
Step 2 Run the su root command and enter the password of user root to switch to user
root.
Step 3 Run the TMOUT=0 command to prevent the system from exiting due to timeout.
NOTE
After you run the preceding command, the system continues to run even when no
operation is performed, posing security risks. For security purposes, you are advised to run
the exit command to exit the system after completing your operations.
Step 4 Run the ping Storage service IP address command to check the network
connectivity.
● If the network is interrupted constantly or intermittently:
Check and reconnect networks between backup storage and eBackup hosts.
NOTE
After network connections become normal, execute the backup jobs again. If backup
jobs are not restored, go to Step 5.
● If the network connections are normal:
Contact technical support engineers.
Step 5 After the network connections are restored by performing the preceding
operations, if backup jobs are not restored, run the reboot command to restart the
operating system of the backup proxy. If the operating system fails to be restarted,
run the following command to forcibly restart it.
NOTICE
----End
Symptom
A VM fails to be backed up and a VM snapshot fails to be created on the task
details page.
Possible Causes
● Tools of the VM are not installed. You need to install Tools.
The job details are as follows:
Procedure
Step 1 Possible cause 1: Tools are not installed on the VM.
1. Use a browser to log in to the FusionCompute page.
2. Click the VM and view the Tools status of the VM on the Summary page.
3. If Tools on the VM is in the Not Running state, Tools is not installed on the
VM. Install Tools on the VM by referring to Installing Tools in
FusionCompute 8.1.0 Product Documentation.
4. Perform the backup job again.
Step 2 Possible cause 2: The VM is not restarted after its CPU or memory configuration is
modified.
1. Use a browser to log in to the FusionCompute page.
2. Click the VM and restart the VM on the VM page. Before the restart, ensure
that no service is running on the VM.
3. After the restart is complete, perform the backup job again.
Step 3 Possible cause 3: Failed to create a snapshot because the FusionCompute system is
abnormal.
1. On eBackup GUI, find the name of the protected object corresponding to the
failed job.
2. Use a browser to log in to the FusionCompute page.
3. Locate the VM that fails to be backed up.
4. Forcibly restart the VM and perform the backup job again.
Step 4 Possible cause 4: Failed to create a snapshot because the remaining storage
capacity of the VM is insufficient and the number of snapshots in the system has
reached the upper limit.
1. On eBackup GUI, find the name of the protected object corresponding to the
failed job.
2. Log in to the VM using PuTTY.
3. Delete unnecessary data from the VM to release storage space.
4. Search for the residual snapshot to be deleted.
----End
7.3.3.4 VM Backup Fails and the Disk Description Fails to Be Obtained in the
Task Details on the GUI
Symptom
The VM fails to be backed up on eBackup. The task details on the GUI show that
the disk description fails to be obtained.
Possible Cause
You have modified the disk attributes, added disks, or deleted disks at the VM
production site (FusionCompute), or performed a disk restore job on eBackup.
Procedure
Step 1 Log in to the eBackup GUI as user admin.
Step 3 Click on the right of the protected environment to scan the protected
environment again.
Step 4 Click OK. Wait until the scanning is complete.
Step 5 Perform the backup job again.
----End
Symptom
Disks of VMs cannot be selected when you create or modify a protected set on
eBackup.
Possible Causes
● The disk does not support backup. If the disk type is Shared or Non-shared
and the disk mode is Independent & persistent or Independent &
nonpersistent, backup is not supported.
● Disk properties have been modified or disks are added or deleted.
Procedure
Step 1 Possible cause 1: The disk does not support backup.
– If yes, the disk does not support backup. No further action is required.
– If no, click Modify Disk to view the disk mode.
● If the disk mode is Independent & persistent or Independent &
nonpersistent, the disk does not support backup. No further action is
required.
● If the disk mode is Dependent, go to Step 2.
Step 2 Possible cause 2: After you modify disk properties, add disks, or delete disks on the
VM production end (FusionCompute), the VM disk cannot be selected when you
create or modify a protected set.
1. Log in to the eBackup GUI as user admin.
5. On the navigation bar, choose Backup > Protected Set. Move the mouse
pointer to the protected set that you want to modify and click in the
button area on the right, or click the protected set that you want to modify
and click in the preview area on the right. Modify the disk of the protected
set where the VM is located.
----End
Symptom
An internal error is displayed in the job details of eBackup after a disk fails to be
opened, read, or closed during backup.
Possible Causes
1. The production management plane of eBackup fails to communicate with
CNA.
2. Multiple network adapters of eBackup are configured on the same network
segment.
3. After the IP address of eBackup is changed, the sh ebackup_utilities.sh
config command is not executed.
Fault Diagnosis
1. Check whether the production management plane of eBackup is connected to
the CNA network plane.
a. Check the production management plane IP address.
i. Use PuTTY to log in to the eBackup server.
Default account: hcp. Default password: PXU9@ctuNov17!.
ii. Run the following command to go to the conf directory:
cd /opt/huawei-data-protection/ebackup/conf
iii. Run the following command to query the production management
plane IP address of eBackup:
grep ProtectedEnvironmentManagementPlane privateconf.ini
The following command output is displayed:
[hcp@eBackup conf]$ grep ProtectedEnvironmentManagementPlane privateconf.ini
ProtectedEnvironmentManagementPlane=192.168.131.10|28:6e:d4:89:f0:3f
Procedure
Step 1 Possible cause 1: The production management plane of eBackup fails to
communicate with CNA.
Refer to 1.a to check whether the IP of the ProtectedEnvironmentStoragePlane
is the IP when planning.
If the configuration is incorrect, run the sh ebackup_utilities.sh config command
to reconfigure it. If the configuration is correct, check the network.
NOTE
Before running the sh ebackup_utilities.sh config command, you need to run the service
hcp stop command to stop the eBackup service.
Step 2 Possible cause 2: Multiple network adapters of eBackup are configured on the
same network segment.
● Solution 1: Configure the network adapters to different network segments.
● Solution 2: Retain only one network adapter on the network segment. Disable
other network adapters.
a. Run the following command to disable the network adapter:
ifdown the name of the network adapter to be disabled
b. Run the sh ebackup_utilities.sh config command to combine planes
corresponding to network adapters with that of the retained network
adapter.
NOTE
For example, if the first and second network adapters are in the same
network segment, the first network adapter is used as the backup
management plane, and the second network adapter is used as the
production management plane, disable the second network adapter and
run the sh ebackup_utilities.sh config command to configure the
backup management plane and production management plane to the
first network adapter.
NOTICE
For security purposes, you must isolate the following three groups of
planes:
▪ Storage plane
For details, see 9.4 Reconfigure eBackup Servers after Changing the IP Address.
----End
7.3.4 Restore
Symptom
When a disk (xfs file system) is repetitively recovered to a FusionSphere VM that
has mounted multiple disks (xfs file system), xfs file systems failed to be mounted.
Possible Causes
The superblock of an xfs file system stores a unique UUID about the file system. If
a VM has mounted multiple disks (xfs file system), multiple same UUIDs exist on
the VM, causing the file system mounting to fail.
Fault Diagnosis
When mounting xfs file systems, use parameters without UUID control or
reallocate a new UUID to ensure uniqueness of the UUIDs.
Procedure
Step 1 Log in to the VM that failed to mount xfs file systems.
Step 2 Troubleshoot the problem in either of the following ways:
● Use a parameter without UUID when mounting an XFS file system: Run
mount -o nouuid /dev/** /**.
● Reallocate a new UUID: Run xfs_admin -U generate /dev/**.
NOTE
----End
Symptom
After a restore job is successfully executed, restored non-system disks are not
displayed on the virtual machine running windows 7.
Possible Causes
Restricted by Windows 7.
Procedure
Step 1 On the desktop of the Windows 7 operating system, right-click the Computer
icon.
Step 2 Choose Manage from the shortcut menu.
The Computer Management window is displayed.
Step 3 In the left navigation tree, choose Storage > Disk Management.
Step 4 Right-click a restored disk and choose Online from the shortcut menu.
NOTE
----End
Symptom
After data is restored from a FusionSphere virtual machine (VM) or system disks
to a new VM, Linux VM network adapters are in disorder. IP addresses
disappeared.
Possible Causes
The configuration information for network adapters conflict in the Linux operating
system.
NOTE
When data is restored from a FusionSphere VM or system disks to a new VM, the IP address
and domain name on system disks are not modified. Instead, they are to be modified by the
customer.
Procedure
Step 1 Log in to a VM using VNC. Run the following command to delete a rule file whose
name contains persistent and net from the network rule directory. If the file does
not exist, go to Step 2.
rm /etc/udev/rules.d/XX-persistent-net.rules //XX varies with environments
Step 3 Log in to the VM again using VNC and run the following command to view
network configuration of the VM.
ifconfig -a
Step 4 Run the following command to check whether the XX-persistent-net.rules file
exists in the etc/udev/rules.d/ directory:
ls /etc/udev/rules.d/
● If no, go to Step 5.
● If yes, go to Step 6.
NOTE
● In the first command, the double quotation marks (" ") indicate the network adapter
name in the network adapter configuration information queried in Step 3.
● In the second command, the double quotation marks (" ") indicate the physical address
of the network adapter.
● When you run the third command for the first time, an error message may be displayed,
indicating that the file does not exist. Ignore the error message.
Repeat the preceding operations until the configuration information about all
network adapters queried in Step 3 is written into the XX-persistent-net.rules
file. Run the cat /etc/udev/rules.d/XX-persistent-net.rules command to verify
that the file content is correct.
Step 6 Run the following command to check whether the network adapter name in the
ifcfg-XXX network adapter configuration file is the same as that in the network
configuration information queried in Step 3.
ls /etc/sysconfig/network-script/
NOTE
The path of the network adapter configuration file varies according to the actual situation.
XXX in ifcfg-XXX is the name of each network adapter.
Step 7 Run the following command to use the VI editor to open the rule file whose name
contains persistent and net in the network directory.
vi /etc/udev/rules.d/XX-persistent-net.rules //XX varies with environments.
Step 9 In the XX-persistent-net.rules file, change the disordered network adapter names
to be the same as those in the network adapter configuration file.
Step 10 Press Esc, enter :wq, and press Enter to save the modification.
Step 11 Run the following command to open each network adapter configuration file in
the /etc/sysconfig/network-script/ directory:
vi /etc/sysconfig/network-script/ifcfg-XXX
NOTE
The path of the network adapter configuration file varies according to the actual situation.
XXX in ifcfg-XXX is the name of each network adapter.
Step 13 Set the IP address in the network adapter configuration file again.
NOTE
Ensure that the IP address to be configured is not used by other VMs or network adapters.
Otherwise, the configuration may fail.
Step 14 Press Esc, enter :wq, and press Enter to save the modification.
Step 15 Repeat Step 11 to Step 14 to ensure that the IP addresses in all network adapter
configuration files are correct.
----End
Symptom
After the file-level restore task fails, the disk remains on the target VM. The
eBackup clearing task fails to detach the disk. However, the task of disk detach
failure is displayed in the task list of FusionCompute.
Possible Causes
VIRTIO disks cannot be detached online after an exception occurs.
Procedure
Step 1 Log in to the FusionCompute management page.
Step 2 Locate the target VM and choose More > Power > Forcibly Stop to stop the VM.
Step 3 After the VM is shut down, choose Configuration > Disk. The disk management
page is displayed.
Step 4 Locate the disk whose name starts with HCP-FLR, and choose More > Detach to
detach the disk.
Step 6 The clearing task of eBackup automatically clears the residual disks and
datastores of the file-level restore task.
----End
7.3.5 Application
7.3.5.1 When a User Runs the rescan-scsi-bus.sh Command to Scan for the
New Mapped LUNs, the Task Keeps Running for a Long Time
Symptom
If an eBackup server is added to a Huawei distributed block storage cluster and
the system has new mapped LUNs, the task keeps running for a long time and
cannot stop when you run the rescan-scsi-bus.sh command to scan for the new
mapped LUNs.
Possible Causes
The Huawei distributed block storage agent version does not match the Huawei
distributed block storage version. As a result, the LUN scanning function on the
eBackup server is abnormal.
Procedure
Step 1 Restart the operating system of the eBackup server.
Step 2 For details about how to add the eBackup server to a Huawei distributed block
storage cluster again, see 3.4.1 Adding an eBackup Server to a Huawei
Distributed Block Storage Cluster (Applicable to Huawei Distributed Block
Storage 8.1.0/8.1.1).
----End
7.3.5.2 The eBackup Service Stops When the Capacity Usage of the /opt
Partition on the Backup Server Exceeds 96%
Symptom
The eBackup service stops when the capacity usage of the /opt partition on the
backup server exceeds 96%, and you cannot log in to eBackup.
Possible Causes
The capacity usage of the /opt partition is insufficient.
Procedure
Step 1 Log in to the backup server using PuTTY.
Step 2 Run su root and enter the password of the root account to switch to the root
account.
Step 3 Run TMOUT=0 to prevent the system from exiting due to timeout.
Step 4 Run df -h /opt to check the remaining space of /opt. When the capacity usage
exceeds 96%, run rm File name or rm -rf Folder name to delete unneeded files
or folders other than the eBackup software.
Step 5 Run the service hcp start command to start the eBackup service.
----End
Symptom
A standby node fails to be removed on the GUI when the HA function is being
used and the standby node is in the irrecoverable Inaccessible state.
Possible Causes
● An error occurs on the network between the active and standby nodes.
● A process on the active or standby node is faulty.
Procedure
Step 1 Log in to the standby node using PuTTY.
Step 2 Run the su root command and enter the password of account root to switch to
account root.
Step 3 Run the TMOUT=0 command to prevent the system from exiting due to timeout.
NOTE
After you run the preceding command, the system continues to run when no operation is
performed, posing a security risk. For security purposes, you are advised to run exit to exit
the system after completing your operations.
Step 4 Run the service hcp status command to check whether the eBackup service is
normal.
● If yes => Go to Step 5
● If no => Uninstall eBackup software. For details, see section 6.8.2.1
Uninstalling the eBackup Software.
Step 7 Run the su root command and enter the password of user root to switch to user
root.
Step 8 Run the TMOUT=0 command to prevent the system from exiting due to timeout.
NOTE
After you run the preceding command, the system continues to run when no operation is
performed, posing a security risk. For security purposes, you are advised to run exit to exit
the system after completing your operations.
Step 10 Stop the HA process. For details, see 6.8.5.3 Stopping the HA Process.
Step 11 Wait several minutes, and check whether the standby node has been removed on
the GUI. If the fault persists, contact technical support engineers.
----End
Symptom
In an HA scenario, after command sh status_ha.sh is executed on both active and
standby nodes, the command output indicates abnormal GaussDB resources. For
details about the command, see 6.8.5.4 Querying the HA Active/Standby State.
If the command output is not similar to that in the red rectangle in the preceding
figure, the resources are abnormal. The following figure is an example.
Possible Causes
Synchronization between active and standby databases is abnormal.
NOTICE
Procedure
Step 1 Log in to either of the active and standby nodes using PuTTY.
Step 2 Run the su root command and enter the password of account root to switch to
account root.
Step 3 Run the TMOUT=0 command to prevent PuTTY from exiting due to timeout.
NOTE
After you run the preceding command, the system continues to run when no operation is
performed, posing a security risk. For security purposes, you are advised to run exit to exit
the system after completing your operations.
Step 5 Run the sh db_sync_monitor.sh get_status command, and record the command
output.
DB last online role : Primary
DB last online time : 2016-04-14 16:38:31
Step 7 Run the su root command and enter the password of account root to switch to
account root.
Step 8 Run the TMOUT=0 command to prevent PuTTY from exiting due to timeout.
NOTE
After you run the preceding command, the system continues to run when no operation is
performed, posing a security risk. For security purposes, you are advised to run exit to exit
the system after completing your operations.
Step 11 Compare the preceding recorded command outputs to determine the active node.
● Choose the node whose DB last online role is Primary as the active node.
● If values of DB last online role for the two nodes both are Primary, choose
the node whose DB last online time is later as the active node.
Step 12 On the active node, run the service hcp restart force command to forcibly restart
the hcp process.
Step 13 Log in to the GUI and check whether node status is normal. For details, see 9.1
Logging In to the eBackup GUI and 6.1.4 Managing an eBackup Server. If the
fault persists, contact technical support engineers.
----End
Symptom
1. In a high availability (HA) scenario, services on the active node fail to be
started. The following command output is displayed after the service hcp
start command is executed on the active node:
eBackup: /opt/huawei-data-protection/ebackup/conf #service hcp start
Starting Huawei eBackup Service
This is primary node, but syncronized status is not correct.Restore the environment by seeing related
fault cases in the corresponding product documentation.
2. After the service hcp start command is executed on the standby node,
services on the standby node are started properly. About 2 minutes later, the
standby node becomes the active node because the original active node fails
to be started. The service hcp status command is executed again to check
the eBackup process. The command output indicates that AdminNode is not
running. As a result, the system login fails.
eBackup: /home #service hcp start
Starting Huawei eBackup Service
HCPProcessMonitor is running
OmmHaMonitor is running
Possible Causes
Services on the active node, standby node, and backup proxies are stopped or an
unexpected power outage occurs. Services on all nodes are restarted after more
than 10 minutes or when the time difference between the original system time
and modified system time is more than 10 minutes. As a result, the services on the
active node fail to be started.
Procedure
Step 1 Log in to the backup server using PuTTY.
Step 2 Run the su root command and enter the password of account root to switch to
account root.
Step 3 Run TMOUT=0 to prevent the system from exiting due to timeout.
NOTE
After you run this command, the system continues to run when no operation is performed,
posing a risk. For security, run exit to exit the system after completing your operations.
● If the role of one node is Primary, and that of the other node is Standby, the
node whose role is Primary is the active node.
● If roles of both nodes are Primary, the node that goes online later is the
active node.
Step 5 On the original active node, run the service hcp start force command to forcibly
start services.
----End
Symptom
The backup server and backup proxies are deployed on different nodes. After
disaster recovery is performed for the backup server or backup proxies are
incorrectly configured, the backup proxies cannot be registered on the backup
server.
Possible Causes
Public and private key information has changed after eBackup is reconfigured.
Procedure
Step 1 Log in to the backup proxy using PuTTY.
Default account: hcp; default password: PXU9@ctuNov17!
Step 2 Run the su root command and enter the password of account root to switch to
account root.
The default password of the root account is Cloud12#$.
----End
Symptom
The license becomes unavailable after HA is enabled and an active/standby
switchover is performed.
Possible Causes
After the switchover, the ESNs of the current active node do not exist in the license
file.
Procedure
Apply for a new license or change the ESN of the license (including the ESNs of
the active and standby nodes) and import the new license.
7.3.5.8 Backups Are Lost After the HA Function Is Enabled and an Active/
Standby Switchover Is Performed
Symptom
Backups are lost when the HA function is enabled and an active/standby
switchover is performed after the services on the standby node are stopped.
Possible Causes
After the switchover, database information is not synchronized.
Procedure
Step 1 Log in to the backup server using PuTTY.
Default account: hcp. Default password: PXU9@ctuNov17!.
Step 2 Run the su root command and enter the password of account root to switch to
account root.
The default password of user root is Cloud12#$.
Step 3 Run the TMOUT=0 command to prevent PuTTY from exiting due to timeout.
NOTE
After you run the preceding command, the system continues to run even when no
operation is performed, posing security risks. For security purposes, you are advised to run
the exit command to exit the system after completing your operations.
On the navigation bar, choose > All Backups, and check whether the backups
are retrieved.
----End
Symptom
After storage space is used up, backups fail to be deleted. In job details, message
"Failed to delete information of backup from database" is displayed.
Possible Causes
Space of storage units is used up.
Procedure
Step 1 Deactivate backup plans associated with faulty storage units.
1. Log in to eBackup backup management system.
Step 3 Run the su root command and enter the password of account root to switch to
account root.
Step 4 Run the TMOUT=0 command to prevent PuTTY from exiting due to timeout.
NOTE
After you run the preceding command, the system continues to run even when no
operation is performed, posing security risks. For security purposes, you are advised to run
the exit command to exit the system after completing your operations.
Step 5 Run the df -h command to query the mount point of the storage unit.
Example:
cd /opt/huawei-data-protection/ebackup/bricks/94500ea0-8273–
4015-9f07-3e75bf16e9ea
Step 7 Run the du -sk DummyFileForDisasteryRecovery.tmp command to check
whether the size of file DummyFileForDisasteryRecovery.tmp is 100 MB.
Example:
Step 10 The system will perform the delivered backup deletion job and backup expiration
job associated with the faulty storage unit within two hours, and the jobs will be
successfully executed.
Alternatively, you can delete backups on eBackup.
Step 11 Run the df -h command, and check whether the released storage unit space
exceeds 200 MB.
● If the released space exceeds 200 MB, go to Step 12.
----End
7.3.6 Maintenance
7.3.6.1 Large Time Difference Between the NTP Server and Backup Server
Symptom
There is a large time difference between the NTP server and backup server, and
the eBackup interface displays an alarm.
Possible Causes
If the network between the NTP server and backup server is disconnected or the
time of the NTP server is modified, there may be a time difference between the
NTP server and backup server. When the time difference is greater than 1 minute,
the eBackup interface displays an alarm.
The backup server attempts to synchronize time with the NTP server. If the time
difference is large, a large time change occurs on the backup server after time
synchronization. As a result, backup jobs are not executed as planned.
NOTE
If the impact is little according to your assessment, you may take no actions. Otherwise,
perform the following steps to resolve the problem. After you perform the following steps,
the eBackup service will restart, and the eBackup system cannot provide services externally
for a few seconds.
Procedure
Step 1 Log in to the eBackup system as the user admin.
Step 2 On the navigation bar, choose > System Time & Zone.
Step 3 Enter the local IP address of the backup server (127.0.0.1) in the NTP Server text
box, and click OK.
Step 4 In the Warning dialog box, click OK.
Step 5 Log in to the eBackup system again as the user admin.
Step 6 On the navigation bar, choose > System Time & Zone.
Step 7 Enter the IP address of the NTP server in the NTP Server text box, and click OK.
Step 8 In the Warning dialog box, click OK.
----End
7.3.6.2 The NTP Service of a Backup Proxy Is Abnormal, the Time of the
Backup Proxy Fails to Be Synchronized with that of the Backup Server, and
No Alarm Is Generated
Symptom
The time of a backup proxy is not synchronized with that of the backup server,
and no alarm is generated.
Possible Causes
A row starting with server in file /etc/ntp.conf does not exist. As a result, NTP
server configurations fail to be updated.
Procedure
Step 1 Log in to the backup proxy whose NTP service is abnormal using PuTTY.
Default account: hcp. Default password: PXU9@ctuNov17!.
Step 2 Run the su root command and enter the password of account root to switch to
account root.
The default password of user root is Cloud12#$.
Step 3 Run the TMOUT=0 command to prevent the system from exiting due to timeout.
NOTE
After you run the preceding command, the system continues to run even when no
operation is performed, posing security risks. For security purposes, you are advised to run
the exit command to exit the system after completing your operations.
Step 4 Run the cat /etc/ntp.conf | grep "^server*" command, and check whether any
command output is returned:
● If any command output is returned, contact Huawei technical support.
● Otherwise, go to Step 5.
Step 5 Log in to eBackup using the admin account.
● Non-HA scenario:
Query the IP address of the internal communication plane of the backup
server.
Step 8 Run the echo "server IP address prefer minpoll 4 maxpoll 5" >> /etc/ntp.conf
command to add an NTP server.
IP address is obtained in Step 7.
Step 9 Run the following commands in sequence to make the settings effective:
cd /etc/init.d
hwclock --systohc > /dev/null 2>&1
service ntp restart > /dev/null 2>&1
chkconfig ntp 3 > /dev/null 2>&1
chkconfig ntp 5 > /dev/null 2>&1
----End
8 Disaster Recovery
If the eBackup backup management system encounters an error, you can perform
disaster recovery to recover the eBackup backup management system and
applications. During initial system installation and configuration, backup of
management data is configured. Backup management data is used for system
restoration upon disasters.
8.1 Recovery Process
8.2 Collect Information
8.3 Installing a Backup Server
8.4 Configuring a Backup Server
8.5 Configuring Management Data Backup Storage
8.6 Restoring System Management Data and Storage Units
8.7 Restoring a Backup Proxy
NOTICE
● If the HA function is enabled, you need to remove the standby backup server
from the system before disaster recovery. Then perform disaster recovery by
following disaster recovery process. After the disaster recovery, add the
removed standby backup server to the system again.
● For details about how to remove and add a standby backup server, see step 5
in 6.1.4 Managing an eBackup Server.
● If a backup proxy fails to be registered with the backup server after disaster
recovery, rectify the fault as instructed in 7.3.5.6 Backup Proxies Fail to Be
Registered on the Backup Server Because Public and Private Key
Information Has Changed After eBackup Is Reconfigured.
● Perform the following operations when eBackup VMs or physical servers are
faulty, or when only the eBackup software is faulty:
Figure 8-1 shows the eBackup disaster recovery process. For details about
disaster recovery for backup proxies, see 8.7 Restoring a Backup Proxy.
NOTE
After disaster recovery is complete, all passwords in the system are restored to the default
passwords. For security purposes, you are advised to change them as soon as possible.
● Perform 8.6 Restoring System Management Data and Storage Units when
eBackup VMs, physical servers, and eBackup software are normal and only
management data is faulty.
Prerequisites
● At least one normal backup proxy exists.
● You have obtained the backup management plane IP address of the backup
server and the password of user root. The default password is Cloud12#$.
● You have obtained the login password of the hcp account, the default
password of the hcp account is PXU9@ctuNov17!.
NOTE
Procedure
Step 1 Collect internal communication plane IP address of the backup server.
The collected information is used to configure the backup server. The IP address of
the internal communication plane of the backup server must be same as that
before the failure occurs.
1. Log in to one normal backup proxy.
2. Run cd /opt/huawei-data-protection/ebackup/conf/.
3. View the CurrentLeaderIP information in the hcpconf.ini configuration file
(saved in/opt/huawei-data-protection/eBackup/conf/) to obtain the IP
address of the internal communication plane of the backup server.
----End
NOTICE
After the eBackup software is reinstalled, the system account passwords are
restored to default ones. To enhance system security, you are advised to change
passwords of the accounts described in OceanStor BCManager 8.1.0 eBackup
Account List (Virtualization).
Procedure
Step 1 Prepare for the installation.
For details, see 2.2 Preparing for Installation.
NOTICE
● If the original server is used, the network adapter corresponding to the backup
management plane IP address must be the same as that used before disasters.
Otherwise, you need to change the license ESN after disaster recovery.
● The IP addresses of the internal communication plane of the backup server
before and after disaster recovery must be the same. You can log in to any
backup proxy, view CurrentLeaderIP in configuration file hcpconf.ini in
path /opt/huawei-data-protection/ebackup/conf/ to obtain the IP address of
the internal communication plane of the backup server.
----End
NOTICE
● If the network adapter associated with the ESN fails or is changed, you need to
change the ESN by following instructions in 2.7 Importing a License.
● The IP addresses of the internal communication plane of the backup server
before and after the disaster recovery must be the same.
NOTICE
● Backup storage used during disaster recovery must be the same as that used
during initial installation and configuration before disasters.
● If you choose S3 storage as the backup storage of system management data,
the backup storage and the S3 bucket name before and after the disaster
recovery must be the same.
8.6.1 NFS
This section describes how to restore the eBackup management data and storage
units when the eBackup management data is lost or damaged and the backup
storage type of the management data is NFS.
Prerequisites
● New management data backup storage has been configured. Ensure that the
management data backup storage paths before and after restore are the
same and the identifiers are different. For details, see 2.5.1 NFS.
● Under path /opt/huawei-data-protection/ebackup/db_bak/Region-AZ-POD,
check whether configuration file storage_units.csv required for fault recovery
exists. Region-AZ-POD indicates eBackup identifier of the management data
backup. If the configuration file does not exist, contact Huawei technical
support.
● A cross-platform remote access tool, such as PuTTY, has been obtained.
● Backup and restore services of tenant data have been stopped (during
disaster recovery, the system automatically stops the eBackup process).
● If the HA function is configured, you need to remove the standby node from
the HA relationship before fault recovery. After the fault recovery is complete,
add the standby node to the HA relationship. Perform the following steps to
remove the standby node from the HA relationship:
a. Log in to the backup server GUI using a browser.
Context
● The file name of the backup data is [Backup data type][Backup type]
[Service name][Year][Month][Day][Hour][Minute][Second][Backup
period][No.].db. Backup data type can be F (full backup). Backup type can
NOTICE
Do not restore the system management data or storage units across versions.
Otherwise, the management data or storage units cannot be restored.
Procedure
Preparing data
Step 2 Run the following command, and enter the password of user root to switch to
user root.
su root
Step 3 Run the following command to prevent the system from exiting due to timeout.
TMOUT=0
NOTE
After you run this command, the system continues to run when no operation is performed,
resulting in a risk. For security purposes, you are advised to run the exit command to exit
the system after completing your operations.
Step 4 Run the following command to go to the save path of the restoration script.
cd /opt/huawei-data-protection/ebackup/bin
Step 5 Run the following command to restore the backup management data to the
running management data.
sh hcp_admindb_restore.sh
The following command output is displayed:
NOTE
Only main command outputs are displayed in the following operation procedures.
WARNING: Restore DB will stop eBackup service, are you sure to continue?(y/n)
Step 7 Enter the number before the subdirectory that stores the backup data of the
eBackup system management data before the fault occurs, and press Enter.
For example, if you choose subdirectory /opt/huawei-data-protection/ebackup/
db_bak/eBackup03 to store eBackup system management data, enter 1.
eBackup03 is the value of identifier set when the eBackup management data
backup storage is configured.
The following command output is displayed:
Backup Name Version
[1] FATEBACKUP20180128000125Y001.db xx
[2] FATEBACKUP20180129000125Y002.db xx
[3] FATEBACKUP20180130000125Y003.db xx
[4] FATEBACKUP20180130000127Y004.db xx
please select a backup file from the list above:
Performing a restore
Step 8 Select the backup file whose version is consistent with the version of the eBackup
backup management system, and press Enter. For details, see the backup file
naming rules in Context and the value of Version in the preceding command
output.
For example, select FATEBACKUP20160128000125Y001.db and enter 1.
● If the versions are inconsistent, the following information is returned. You
need to select backup data whose version is consistent with that of the
eBackup backup management system.
The system version don't match.
please select a backup file from the list above:
● The command output is as follows:
select backup name:FATEBACKUP20160128000125Y001.db
Checking data...
Backup data...Correct.
BackFileName is:1352B2A8F5934D8DA1356A22A5671DA3.tar.gz
BackFileName is:4AD4744C8775498AAD1389174EC14512.tar.gz
BackFileName is:C8F86F3249A047F188D81779E3685545.tar.gz
BackFileName is:D1D9A2EF865D41A184EF6F2A250F9E55.tar.gz
Shutting down Huawei eBackup Service
service hcp stop:completed done
This operation will drop the db, are you sure you want to continue?(y/n)
Step 10 Enter the password of database account admin, and press Enter.
NOTE
Step 11 Enter the password of database account license, and press Enter.
Step 12 Enter the password of database account alarm, and press Enter.
Step 13 Enter the password of database account IAM, and press Enter.
The default password is Huawei@CLOUD8!. The system begins to restore iamdb
data.
The following command output is displayed:
Checking database...Success.
Creating database...Success.
Restoring database...Success.
Dropping database...
Success.
Rename database...Success.
Grant privileges to dbuser...Success.
Operation finished.
Please enter GOVERNANCEDB database password for user eBkDbAdmin:
Step 14 Perform the following steps based on the role of the eBackup server:
Step 15 If the management role is the backup server, perform the following steps:
Enter the password of database account governance, and press Enter. The default
password is Huawei@CLOUD8!. The system begins to restore governancedb data.
Checking database...Success.
Creating database...Success.
Restoring database...Success.
Dropping database...
Success.
Rename database...Success.
Grant privileges to dbuser...Clean SERVICEINSTANCELIST in db.
Success.
Operation finished.
start restore datamoverdb
Please enter DATAMOVERDB database password for user eBkDbAdmin:
Step 16 If the management role is the backup server, enter the password of database
account datamover, and press Enter.
The default password is Huawei@CLOUD8!. The system begins to restore
datamoverdb data.
If the following command output is displayed, management data is restored
successfully.
Checking database...Success.
Creating database...Success.
Restoring database...Success.
Dropping database...
Success.
Rename database...Success.
Grant privileges to dbuser...Success.
Operation finished.
Restore DB success.
Starting Huawei eBackup Service
The service is starting, please wait for a moment...
serivce hcp start:completed
done
The ebk_governance agent of OceanStor BCManager eBackup was started successfully.
The ebk_license agent of OceanStor BCManager eBackup was started successfully.
The ebk_alarm agent of OceanStor BCManager eBackup was started successfully.
The ebk_iam agent of OceanStor BCManager eBackup was started successfully.
OLD_LD_LIBRARY_PATH=$LD_LIBRARY_PATH
2. Run the following command to copy the storage_units.csv file before the
fault to the new identifier after the fault occurs. Region-AZ-POD indicates the
backup data identifier of the eBackup system management data before the
fault occurs, and Region-AZ-POD02 indicates the backup data identifier of the
eBackup system management data created during fault recovery.
cp /opt/huawei-data-protection/ebackup/db_bak/Region-AZ-POD/
storage_units.csv /opt/huawei-data-protection/ebackup/db_bak/Region-
AZ-POD02
3. Run the following command to go to the path where configuration file
storage_units.csv resides. Region-AZ-POD02 indicates the backup data
identifier of the eBackup system management data created during fault
recovery.
cd /opt/huawei-data-protection/ebackup/db_bak/Region-AZ-POD02
4. Run the following command to restore a storage unit in the configuration file.
service hcp recover /opt/huawei-data-protection/ebackup/db_bak/Region-
AZ-POD02/storage_units.csv
The following command output is displayed:
WARNING: Recovery will stop services. Are you sure you want to continue?(y/n):
NOTE
Step 18 After performing the preceding steps, wait for about 5 minutes and log in to the
eBackup GUI. Click Backup Storage > Storage Unit. If Accessibility Status of the
storage unit is All accessible, the restore is successful.
Step 19 If backup proxies exist in the backup management system, power on the servers
where the backup proxies reside to ensure the normal running of eBackup
services.
Log in to the eBackup GUI, choose > Server, and check the status of backup
workflow servers or backup proxies. Ensure that the values of Accessibility Status
and Register Status for all backup workflow servers or backup proxies are
accessible and registered respectively.
----End
Follow-up Procedure
NOTE
After disaster recovery, replace the SSL certificate for communication between the active
and standby eBackup GaussDB nodes and the SSL certificate for communication between
the active and standby nodes of the eBackup OMMHA.
For details, see sections 6.4.2.6 Replacing the SSL Certificate of eBackup GaussDB for
Communication Between the Active and Standby Backup Servers and 6.4.2.4 Replacing
the SSL Certificate of eBackup OMMHA for Communication Between the Active and
Standby Backup Servers.
● If backup system management data fails to be restored in the first time,
perform the disaster recovery operations again.
● After disaster recovery, change the license ESN under either of the following
conditions:
– A VM template has been re-imported.
● After disaster recovery, if the original license cannot be used, obtain an ESN
again, obtain a new license through the ESN, and import the new license.
For details, see OceanStor BCManager 8.0.6 eBackup License Application
Guide.
● If the backup management plane floating IP addresses of the backup server
before and after the disaster are different, you need to reconfigure the
eBackup driver.
● If the backup server and backup proxy are deployed on different nodes, the
backup proxy may fail to be accessed after only the backup server is
recovered.
If a backup workflow server or backup proxy fails to be accessed, perform the
following operations:
a. Use PuTTY to log in to the backup server as user hcp.
b. Run the following command and enter the password of user root to
switch to user root.
The default password of user root is Cloud12#$.
su root
c. Run the following command to obtain the public key of the backup
server:
cat /opt/huawei-data-protection/ebackup/conf/cert/AdminNode.pub
d. Use PuTTY to log in to a backup proxy as user hcp.
e. Run the following command and enter the password of user root to
switch to user root.
The default password of user root is Cloud12#$.
su root
f. Run the following command to open the public key file:
vi /opt/huawei-data-protection/ebackup/conf/cert/AdminNode.pub
g. Delete the content in the file and write the public key of the backup
server obtained from c to the file.
h. Log in to the backup server node again and run the following command
to restart the eBackup process:
service hcp restart
8.6.2 S3
This section describes how to restore the eBackup management data and storage
units when the eBackup management data is lost or damaged and the backup
storage type of the management data is S3.
Prerequisites
● New management data backup storage has been configured. Ensure that the
management data backup storage paths before and after restore are the
same and the identifiers are different. For details, see 2.5.2 S3.
● Under S3 storage path /DBBakSubDir/ebackup/Region-AZ-POD, check
whether configuration file storage_units.csv required for fault recovery exists.
DBBakSubDir indicates the bucket of S3 storage, Region-AZ-POD indicates
the eBackup identifier of the management data backup. If the configuration
file does not exist, contact Huawei technical support.
● A cross-platform remote access tool, such as PuTTY, has been obtained.
● Backup and restore services of tenant data have been stopped (during
disaster recovery, the system automatically stops the eBackup process).
● If the HA function is configured, you need to remove the standby node from
the HA relationship before a disaster recovery. After the disaster recovery is
complete, add the standby node to the HA relationship. Perform the following
steps to remove the standby node from the HA relationship:
a. Log in to the backup server GUI using a browser.
Context
● The file name of the backup data is [Backup data type][Backup type]
[Service name][Year][Month][Day][Hour][Minute][Second][Backup
period][No.].db. Backup data type can be F (full backup). Backup type can
be AT (automatic) or MT (manual). Service name is fixed as EBACKUP.
Backup period can be H(hour), D (daily), W (weekly), M (monthly), Y
(yearly), or X (manual). Example: FATEBACKUP20160128000125Y001.db.
● If backup system management data exists, only data generated between the
backup point in time and the recovery point in time is lost.
● After a disaster recovery task is executed, the system may automatically
generates data records starting with Recover on the eBackup GUI (choosing
Backup > Backup Policy, Backup > Backup Plan or Backup Storage >
Repository to view the data records). These data records are necessary for
disaster recovery and are automatically generated by the system. After the
backup and restore, you are advised to delete the backup plans starting with
Recover on the eBackup GUI. When you delete the backup plans, the
associated backups are deleted to release the storage space. In addition, you
need to delete backup policies and repository starting with Recover on
eBackup.
● During the operation, you need to enter the database password. If you enter
the password incorrectly for three times, the system will automatically exit
from recovery program. In this case, perform this operation again.
● When you restore the system management data or a storage unit, ensure that
versions of the backup data and system are consistent. Run the showsys
command to view the current system version.
NOTICE
Do not restore the system management data or storage units across versions.
Otherwise, the management data or storage units cannot be restored.
Procedure
Preparing data
NOTE
After you run this command, the system continues to run when no operation is performed,
resulting in a risk. For security purposes, you are advised to run the exit command to exit
the system after completing your operations.
Step 4 Run the following command to go to the save path of the restoration script.
cd /opt/huawei-data-protection/ebackup/bin
Step 5 Run the following command to restore the backup management data to the
running management data.
sh hcp_admindb_restore.sh
The following command output is displayed:
NOTE
Only main command outputs are displayed in the following operation procedures.
WARNING: Restore DB will stop eBackup service, are you sure to continue?(y/n)
Step 7 Enter the number before the subdirectory that stores the backup data of the
eBackup system management data before the fault occurs, and press Enter.
eBackup03 is the value of identifier set when the eBackup management data
backup storage is configured.
Performing a restore
Step 8 Select the backup data that is consistent with the eBackup backup management
system version, and press Enter. For details, see Context.
Checking data...
Backup data...Correct.
BackFileName is:1352B2A8F5934D8DA1356A22A5671DA3.tar.gz
BackFileName is:4AD4744C8775498AAD1389174EC14512.tar.gz
BackFileName is:C8F86F3249A047F188D81779E3685545.tar.gz
BackFileName is:D1D9A2EF865D41A184EF6F2A250F9E55.tar.gz
Shutting down Huawei eBackup Service
service hcp stop:completed done
This operation will drop the db, are you sure you want to continue?(y/n)
Step 10 Enter the password of database account admin, and press Enter.
NOTE
Step 11 Enter the password of database account license, and press Enter.
Step 12 Enter the password of database account alarm, and press Enter.
Step 13 Enter the password of database account IAM, and press Enter.
Step 14 Perform the following steps based on the role of the eBackup server:
Step 15 If the management role is the backup server, perform the following steps:
Enter the password of database account governance, and press Enter. The default
password is Huawei@CLOUD8!. The system begins to restore governancedb data.
Checking database...Success.
Creating database...Success.
Restoring database...Success.
Dropping database...
Success.
Rename database...Success.
Grant privileges to dbuser...Clean SERVICEINSTANCELIST in db.
Success.
Operation finished.
start restore datamoverdb
Please enter DATAMOVERDB database password for user eBkDbAdmin:
Step 16 If the management role is the backup server, enter the password of database
account datamover, and press Enter.
The default password is Huawei@CLOUD8!. The system begins to restore
datamoverdb data.
If the following command output is displayed, management data is restored
successfully.
Checking database...Success.
Creating database...Success.
Restoring database...Success.
Dropping database...
Success.
Rename database...Success.
Grant privileges to dbuser...Success.
Operation finished.
Restore DB success.
Starting Huawei eBackup Service
The service is starting, please wait for a moment...
serivce hcp start:completed
done
The ebk_governance agent of OceanStor BCManager eBackup was started successfully.
The ebk_license agent of OceanStor BCManager eBackup was started successfully.
The ebk_alarm agent of OceanStor BCManager eBackup was started successfully.
The ebk_iam agent of OceanStor BCManager eBackup was started successfully.
Log in to the eBackup GUI, choose > Server, and check the status of backup
proxies. Ensure that the values of Accessibility Status and Register Status for all
backup proxies are accessible and registered respectively.
----End
Follow-up Procedure
NOTE
After disaster recovery, replace the SSL certificate for communication between the active
and standby eBackup GaussDB nodes and the SSL certificate for communication between
the active and standby nodes of the eBackup OMMHA.
For details, see sections 6.4.2.6 Replacing the SSL Certificate of eBackup GaussDB for
Communication Between the Active and Standby Backup Servers and 6.4.2.4 Replacing
the SSL Certificate of eBackup OMMHA for Communication Between the Active and
Standby Backup Servers.
● If backup system management data fails to be restored in the first time,
perform the disaster recovery operations again.
● After disaster recovery, change the license ESN under either of the following
conditions:
– A VM template has been re-imported.
● After disaster recovery, if the original license cannot be used, obtain an ESN
again, obtain a new license through the ESN, and import the new license.
For details, see OceanStor BCManager 8.0.6 eBackup License Application
Guide.
● If the backup management plane floating IP addresses of the backup server
before and after the disaster are different, you need to reconfigure the
eBackup driver.
● If the backup server and backup proxy are deployed on different nodes, the
backup proxy may fail to be accessed after only the backup server is
recovered.
If a backup workflow server or backup proxy fails to be accessed, perform the
following operations:
a. Use PuTTY to log in to the backup server as user hcp.
b. Run the following command and enter the password of user root to
switch to user root.
The default password of user root is Cloud12#$.
su root
c. Run the following command to obtain the public key of the backup
server:
cat /opt/huawei-data-protection/ebackup/conf/cert/AdminNode.pub
d. Use PuTTY to log in to a backup proxy as user hcp.
e. Run the following command and enter the password of user root to
switch to user root.
The default password of user root is Cloud12#$.
su root
f. Run the following command to open the public key file:
vi /opt/huawei-data-protection/ebackup/conf/cert/AdminNode.pub
g. Delete the content in the file and write the public key of the backup
server obtained from c to the file.
h. Log in to the backup server node again and run the following command
to restart the eBackup process:
8.6.3 FTP
This section describes how to restore the eBackup management data and storage
units when the eBackup management data is lost or damaged and the backup
storage type of the management data is FTP.
Prerequisites
● New management data backup storage has been configured. Ensure that the
management data backup storage paths before and after restore are the
same and the identifiers are different. For details, see 2.5.3 FTP.
● Under FTP storage path /DBBakSubDir/Region-AZ-POD, check whether
configuration file storage_units.csv for fault recovery exists. DBBakSubDir
indicates the directory of the backup storage on the FTP server, and Region-
AZ-POD indicates the identifier of the backup data of the eBackup
management data. If the configuration file does not exist, contact Huawei
technical support.
● A cross-platform remote access tool, such as PuTTY, has been obtained.
● Backup and restore services of tenant data have been stopped (during
disaster recovery, the system automatically stops the eBackup process).
● If the HA function is configured, you need to remove the standby node from
the HA relationship before a disaster recovery. After the disaster recovery is
complete, add the standby node to the HA relationship. Perform the following
steps to remove the standby node from the HA relationship:
a. Log in to the backup server GUI using a browser.
Context
● The file name of the backup data is [Backup data type][Backup type]
[Service name][Year][Month][Day][Hour][Minute][Second][Backup
period][No.].db. Backup data type can be F (full backup). Backup type can
be AT (automatic) or MT (manual). Service name is fixed as EBACKUP.
Backup period can be H(hour), D (daily), W (weekly), M (monthly), Y
(yearly), or X (manual). Example: FATEBACKUP20160128000125Y001.db.
● If backup system management data exists, only data generated between the
backup point in time and the recovery point in time is lost.
● After a disaster recovery task is executed, the system may automatically
generates data records starting with Recover on the eBackup GUI (choosing
Backup > Backup Policy, Backup > Backup Plan or Backup Storage >
Repository to view the data records). These data records are necessary for
disaster recovery and are automatically generated by the system. After the
backup and restore, you are advised to delete the backup plans starting with
Recover on the eBackup GUI. When you delete the backup plans, the
associated backups are deleted to release the storage space. In addition, you
NOTICE
Do not restore the system management data or storage units across versions.
Otherwise, the management data or storage units cannot be restored.
Procedure
Preparing data
NOTE
After you run this command, the system continues to run when no operation is performed,
resulting in a risk. For security purposes, you are advised to run the exit command to exit
the system after completing your operations.
Step 4 Run the following command to go to the save path of the restoration script.
cd /opt/huawei-data-protection/ebackup/bin
Step 5 Run the following command to restore the backup management data to the
running management data.
sh hcp_admindb_restore.sh
The following command output is displayed:
NOTE
Only main command outputs are displayed in the following operation procedures.
WARNING: Restore DB will stop eBackup service, are you sure to continue?(y/n)
Step 7 Enter the number before the subdirectory that stores the backup data of the
eBackup system management data before the fault occurs, and press Enter.
eBackup03 is the value of identifier set when the eBackup management data
backup storage is configured.
Performing a restore
Step 8 Select the backup file whose version is consistent with the version of the eBackup
backup management system, and press Enter. For details, see the backup file
naming rules in Context and the value of Version in the preceding command
output.
Checking data...
Backup data...Correct.
BackFileName is:1352B2A8F5934D8DA1356A22A5671DA3.tar.gz
BackFileName is:4AD4744C8775498AAD1389174EC14512.tar.gz
BackFileName is:C8F86F3249A047F188D81779E3685545.tar.gz
BackFileName is:D1D9A2EF865D41A184EF6F2A250F9E55.tar.gz
Shutting down Huawei eBackup Service
service hcp stop:completed done
This operation will drop the db, are you sure you want to continue?(y/n)
Step 10 Enter the password of database account admin, and press Enter.
NOTE
Step 11 Enter the password of database account license, and press Enter.
Step 12 Enter the password of database account alarm, and press Enter.
Step 13 Enter the password of database account IAM, and press Enter.
Step 14 Perform the following steps based on the role of the eBackup server:
Step 15 If the management role is the backup server, perform the following steps:
Enter the password of database account governance, and press Enter. The default
password is Huawei@CLOUD8!. The system begins to restore governancedb data.
Checking database...Success.
Creating database...Success.
Restoring database...Success.
Dropping database...
Success.
Rename database...Success.
Grant privileges to dbuser...Clean SERVICEINSTANCELIST in db.
Success.
Operation finished.
start restore datamoverdb
Please enter DATAMOVERDB database password for user eBkDbAdmin:
Step 16 If the management role is the backup server, enter the password of database
account datamover, and press Enter.
The default password is Huawei@CLOUD8!. The system begins to restore
datamoverdb data.
If the following command output is displayed, management data is restored
successfully.
Checking database...Success.
Creating database...Success.
Restoring database...Success.
Dropping database...
Success.
Rename database...Success.
Grant privileges to dbuser...Success.
Operation finished.
Restore DB success.
Starting Huawei eBackup Service
The service is starting, please wait for a moment...
serivce hcp start:completed
done
The ebk_governance agent of OceanStor BCManager eBackup was started successfully.
The ebk_license agent of OceanStor BCManager eBackup was started successfully.
The ebk_alarm agent of OceanStor BCManager eBackup was started successfully.
The ebk_iam agent of OceanStor BCManager eBackup was started successfully.
4. Run the following command to download file storage_units.csv from the FTP
storage to a local path on the backup server:
./SecurityTool DownloadFile /Region-AZ-POD/storage_units.csv /opt/
huawei-data-protection/ebackup/db_bak/Region-AZ-POD02
NOTE
Step 18 After performing the preceding steps, wait for about 5 minutes and log in to the
eBackup GUI. Click Backup Storage > Storage Unit. If Accessibility Status of the
storage unit is All accessible, the restore is successful.
Step 19 If backup proxies exist in the backup management system, power on the servers
where the backup proxies reside to ensure the normal running of eBackup
services.
Log in to the eBackup GUI, choose > Server, and check the status of backup
proxies. Ensure that the values of Accessibility Status and Register Status for all
backup proxies are accessible and registered respectively.
----End
Follow-up Procedure
NOTE
After disaster recovery, replace the SSL certificate for communication between the active
and standby eBackup GaussDB nodes and the SSL certificate for communication between
the active and standby nodes of the eBackup OMMHA.
For details, see sections 6.4.2.6 Replacing the SSL Certificate of eBackup GaussDB for
Communication Between the Active and Standby Backup Servers and 6.4.2.4 Replacing
the SSL Certificate of eBackup OMMHA for Communication Between the Active and
Standby Backup Servers.
● If backup system management data fails to be restored in the first time,
perform the disaster recovery operations again.
● After disaster recovery, change the license ESN under either of the following
conditions:
– A VM template has been re-imported.
● After disaster recovery, if the original license cannot be used, obtain an ESN
again, obtain a new license through the ESN, and import the new license.
For details, see OceanStor BCManager 8.0.6 eBackup License Application
Guide.
● If the backup management plane floating IP addresses of the backup server
before and after the disaster are different, you need to reconfigure the
eBackup driver.
● If the backup server and backup proxy are deployed on different nodes, the
backup proxy may fail to be accessed after only the backup server is
recovered.
If a backup workflow server or backup proxy fails to be accessed, perform the
following operations:
a. Use PuTTY to log in to the backup server as user hcp.
b. Run the following command and enter the password of user root to
switch to user root.
The default password of user root is Cloud12#$.
su root
c. Run the following command to obtain the public key of the backup
server:
cat /opt/huawei-data-protection/ebackup/conf/cert/AdminNode.pub
d. Use PuTTY to log in to a backup proxy as user hcp.
e. Run the following command and enter the password of user root to
switch to user root.
The default password of user root is Cloud12#$.
su root
f. Run the following command to open the public key file:
vi /opt/huawei-data-protection/ebackup/conf/cert/AdminNode.pub
g. Delete the content in the file and write the public key of the backup
server obtained from c to the file.
h. Log in to the backup server node again and run the following command
to restart the eBackup process:
8.6.4 SFTP
This section describes how to restore the eBackup management data and storage
units when the eBackup management data is lost or damaged and the backup
storage type of the management data is SFTP.
Prerequisites
● New management data backup storage has been configured. Ensure that the
management data backup storage paths before and after restore are the
same and the identifiers are different. For details, see 2.5.4 SFTP.
● A cross-platform remote access tool, such as PuTTY, has been obtained.
● Backup and restore services of tenant data have been stopped (during
disaster recovery, the system automatically stops the eBackup process).
● If the HA function is configured, you need to remove the standby node from
the HA relationship before a disaster recovery. After the disaster recovery is
complete, add the standby node to the HA relationship. Perform the following
steps to remove the standby node from the HA relationship:
Context
● The file name of the backup data is [Backup data type][Backup type]
[Service name][Year][Month][Day][Hour][Minute][Second][Backup
period][No.].db. Backup data type can be F (full backup). Backup type can
be AT (automatic) or MT (manual). Service name is fixed as EBACKUP.
Backup period can be H(hour), D (daily), W (weekly), M (monthly), Y
(yearly), or X (manual). Example: FATEBACKUP20160128000125Y001.db.
● If backup system management data exists, only data generated between the
backup point in time and the recovery point in time is lost.
● After a disaster recovery task is executed, the system may automatically
generates data records starting with Recover on the eBackup GUI (choosing
Backup > Backup Policy, Backup > Backup Plan or Backup Storage >
Repository to view the data records). These data records are necessary for
disaster recovery and are automatically generated by the system. After the
backup and restore, you are advised to delete the backup plans starting with
Recover on the eBackup GUI. When you delete the backup plans, the
associated backups are deleted to release the storage space. In addition, you
need to delete backup policies and repository starting with Recover on
eBackup.
● During the operation, you need to enter the database password. If you enter
the password incorrectly for three times, the system will automatically exit
from recovery program. In this case, perform this operation again.
● When you restore the system management data or a storage unit, ensure that
versions of the backup data and system are consistent. Run the showsys
command to view the current system version.
NOTICE
Do not restore the system management data or storage units across versions.
Otherwise, the management data or storage units cannot be restored.
Procedure
Preparing data
NOTE
After you run this command, the system continues to run when no operation is performed,
resulting in a risk. For security purposes, you are advised to run the exit command to exit
the system after completing your operations.
Step 4 Run the following command to go to the save path of the restoration script.
cd /opt/huawei-data-protection/ebackup/bin
Step 5 Run the following command to restore the backup management data to the
running management data.
sh hcp_admindb_restore.sh
The following command output is displayed:
NOTE
Only main command outputs are displayed in the following operation procedures.
WARNING: Restore DB will stop eBackup service, are you sure to continue?(y/n)
Step 7 Enter the number before the subdirectory that stores the backup data of the
eBackup system management data before the fault occurs, and press Enter.
The management data of the backup server is stored in
192.168.1.6_ebackup_server_bak.
For example, if you choose /opt/huawei-data-protection/ebackup/db_bak/
192.168.1.6_ebackup_server_bak to store eBackup system management data,
enter 3.
The following command output is displayed:
dir=/opt/huawei-data-protection/ebackup/db_bak/192.168.1.6_ebackup_server_bak
Performing a restore
Step 8 Select the backup file whose version is consistent with the version of the eBackup
backup management system, and press Enter. For details, see the backup file
naming rules in Context and the value of Version in the preceding command
output.
For example, select FATEBACKUP20190222100603H001.db and enter 1.
● If the versions are inconsistent, the following information is returned. You
need to select backup data whose version is consistent with that of the
eBackup backup management system.
The system version don't match.
please select a backup file from the list above:
● The command output is as follows:
select backup name:FATEBACKUP20190222100603H001.db
Checking data...
Backup data...Correct.
BackFileName is:DISRCVE421A714E8104AF8A37671DD045D7E92.tar.gz
BackFileName is:DISRCVDB80B43650B24DCB85004D117C619C86.tar.gz
BackFileName is:DISRCVB62185BC7E6B408684F337A1265B0C05.tar.gz
BackFileName is:DISRCVB755BBEC329F4522B1F31A5FE214F1BC.tar.gz
Shutting down Huawei eBackup Service
Shutting down CRON daemon done
Starting CRON daemon done
service hcp stop:completed done
This operation will drop the db, are you sure you want to continue?(y/n)
Step 10 Enter the password of database account admin, and press Enter.
The default password is Huawei@CLOUD8!. The system begins to restore
admindb data.
NOTE
Step 11 Enter the password of database account license, and press Enter.
Step 12 Enter the password of database account alarm, and press Enter.
Step 13 Enter the password of database account IAM, and press Enter.
Step 14 Perform the following steps based on the role of the eBackup server:
Step 15 If the management role is the backup server, perform the following steps:
Enter the password of database account governance, and press Enter. The default
password is Huawei@CLOUD8!. The system begins to restore governancedb data.
Checking database...Success.
Creating database...Success.
Restoring database...Success.
Dropping database...
Success.
Rename database...Success.
Grant privileges to dbuser...Clean SERVICEINSTANCELIST in db.
Success.
Operation finished.
start restore datamoverdb
Please enter DATAMOVERDB database password for user eBkDbAdmin:
Step 16 If the management role is the backup server, enter the password of database
account datamover, and press Enter.
The default password is Huawei@CLOUD8!. The system begins to restore
datamoverdb data.
If the following command output is displayed, management data is restored
successfully.
Checking database...Success.
Creating database...Success.
Restoring database...Success.
Dropping database...
Success.
Rename database...Success.
Grant privileges to dbuser...Success.
Operation finished.
Restore DB success.
Starting Huawei eBackup Service
The service is starting, please wait for a moment...
serivce hcp start:completed
done
The ebk_governance agent of OceanStor BCManager eBackup was started successfully.
The ebk_license agent of OceanStor BCManager eBackup was started successfully.
The ebk_alarm agent of OceanStor BCManager eBackup was started successfully.
The ebk_iam agent of OceanStor BCManager eBackup was started successfully.
Log in to the eBackup GUI, choose > Server, and check the status of backup
proxies. Ensure that the values of Accessibility Status and Register Status for all
backup proxies are accessible and registered respectively.
----End
Follow-up Procedure
NOTE
After disaster recovery, replace the SSL certificate for communication between the active
and standby eBackup GaussDB nodes and the SSL certificate for communication between
the active and standby nodes of the eBackup OMMHA.
For details, see sections 6.4.2.6 Replacing the SSL Certificate of eBackup GaussDB for
Communication Between the Active and Standby Backup Servers and 6.4.2.4 Replacing
the SSL Certificate of eBackup OMMHA for Communication Between the Active and
Standby Backup Servers.
● If backup system management data fails to be restored in the first time,
perform the disaster recovery operations again.
● After disaster recovery, change the license ESN under either of the following
conditions:
– A VM template has been re-imported.
● After disaster recovery, if the original license cannot be used, obtain an ESN
again, obtain a new license through the ESN, and import the new license.
For details, see OceanStor BCManager 8.0.6 eBackup License Application
Guide.
● If the backup management plane floating IP addresses of the backup server
before and after the disaster are different, you need to reconfigure the
eBackup driver.
● If the backup server and backup proxy are deployed on different nodes, the
backup proxy may fail to be accessed after only the backup server is
recovered.
If a backup workflow server or backup proxy fails to be accessed, perform the
following operations:
a. Use PuTTY to log in to the backup server as user hcp.
b. Run the following command and enter the password of user root to
switch to user root.
The default password of user root is Cloud12#$.
su root
c. Run the following command to obtain the public key of the backup
server:
cat /opt/huawei-data-protection/ebackup/conf/cert/AdminNode.pub
d. Use PuTTY to log in to a backup proxy as user hcp.
e. Run the following command and enter the password of user root to
switch to user root.
The default password of user root is Cloud12#$.
su root
f. Run the following command to open the public key file:
vi /opt/huawei-data-protection/ebackup/conf/cert/AdminNode.pub
g. Delete the content in the file and write the public key of the backup
server obtained from c to the file.
h. Log in to the backup server node again and run the following command
to restart the eBackup process:
Procedure
● When a backup proxy is faulty, perform the following operations:
a. Prepare for the installation.
For details, see 2.2 Preparing for Installation.
b. Use a browser to log in to the eBackup management system as user
admin.
c. Deregister the backup proxy. For details, see 6.1.4 Managing an eBackup
Server.
d. Installing the eBackup software.
After you run the preceding command, the system continues to run even when
no operation is performed, resulting in security risks. For security purposes, you
are advised to run the exit command to exit the system after completing your
operations.
e. Run the cd Directory storing the eBackup installation package command
to go to the directory where the initial configuration script resides.
f. Run the service hcp stop command to stop the eBackup services.
g. Uninstall the eBackup software.
For details, see 2.9 Uninstalling eBackup.
h. Install the eBackup software.
For details, see 2.3.2 Installing eBackup Using a Software Package.
i. Configure the backup proxy.
For details, see 2.4.2 (Optional) Configuring a Backup Proxy.
9 Common Operations
Procedure
Step 1 Run a web browser on your maintenance terminal.
NOTE
in the address bar of the browser, enter the management plane IP address of the
backup server, and press Enter.
Step 3 Configure a browser.
Step 4 Select a language and enter your user name and password.
● eBackup displays contents in your selected language.
● The default user name is admin and the default password is
PXU9@ctuNov17!.
If it is your first login, change the password as prompted.
● If you want to log in to eBackup as a Lightweight Directory Access Protocol
(LDAP) user, perform the following steps:
a. Configure LDAP server information in the system configuration file. For
details about the configuration, see 6.4.5 Configuring LDAPS.
b. After the configuration, you can log in to eBackup.
▪ You can use the LDAP user account created on the LDAP server to
log in to eBackup. (In such a scenario, eBackup automatically creates
a user whose role is regular user in the system.)
In the navigation tree, choose > Account > Users. Click Create
to create an LDAP user. The password of the LDAP user cannot
exceed 256 characters. After the user is created, log in to the system
as the user.
Step 5 Click Login.
NOTE
If the login page displays System Is in Restricted Mode, see 7.3.2.1 The eBackup GUI
Displays a Message Indicating "System Is in Restricted Mode" When I Log In to
eBackup.
----End
NOTE
● Select different Creating a User sections based on the permission management mode
(common mode and permission separation mode) of FusionCompute.
● When creating an interconnection account in common mode, set the following key
parameters:
● Set User Type to Interface interconnection.
● Set Role to administrator.
● Set Max. Concurrent Logins to Not limited.
● When creating an interconnection account in rights separation mode, set the following
key parameters:
● Set User Type to Interface interconnection.
● Set Max. Concurrent Logins to Not limited.
● Set User Type to System administrator.
● Set Role to sysadmin.
Prerequisites
● You have completed the network planning and installed eBackup.
● The Huawei distributed block storage agent is not installed.
● The following operation is performed based on this scenario: Only one
eBackup server is deployed in the eBackup system (If multiple eBackup
servers are deployed, configure routes for all the servers); the storage of the
VM to be backed up distributes on one Huawei distributed block storage
cluster.
● You have obtained the network addresses of the storage plane for Huawei
distributed block storage cluster, for example, 192.168.1.0/24.
● You have obtained the login password of user root of the eBackup server.
Change the password as soon as possible and log in to the server using the
new password. For password changing method, see 6.4.1.5 Changing the
Password of the root Account.
● If you have configured a network port name for the storage IP address of
Huawei distributed block storage, you need to change the network adapter
name of the storage plane of the eBackup server accordingly. If you have
configured only an IP address range for the storage IP address of Huawei
distributed block storage, such change is unnecessary. For details about the
configuration, log in to the Huawei distributed block storage management
node as user dsware, run cd /opt/dsware/client/bin to enter /opt/dsware/
client/bin. Run sh dswareTool.sh --op querySysPara -n sys_network_mark
(You need to enter the user name cmdadmin and the password, and the
default password is cmdHuawei@123).
NOTE
All nodes in the Huawei distributed block storage cluster include other compute nodes that
use Huawei distributed block storage.
Procedure
Step 1 Log in to the eBackup server.
Step 2 Run the TMOUT=0 command to prevent the user from logging out due to
timeout.
NOTE
After the preceding command is executed, the system remains running even when no
operation is performed, posing security risks. For security purposes, run the exit command
to exit the system after you finish performing operations.
– Before restarting the network, evaluate the possible impacts on ongoing services
on the server. Shut down some services before the restart if necessary.
– If you log in to the eBackup server remotely using a cross-platform remote access
tool, you will log out automatically after the restart. If this happens, log in to the
server again.
5. Run the route command to check the route information.
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 192.168.31.1 255.255.255.0 UG 0 0 0 eth2
----End
Prerequisites
● If you want to change the IP address of a backup server, ensure that no tasks
are running and the Accessibility Status of all backup server and backup
proxies are Accessible, Register Status of all backup server and backup
proxies are Registered. If you want to change the IP address of a backup
proxy, ensure that no associated tasks are running and the Accessibility
Status of the backup proxy is Accessible, Register Status of the backup
proxy is Registered. For details about how to check tasks associated with
backup proxies, refer to 6.1.1 Managing a Job. For details about the status of
the eBackup servers, refer to 6.1.4 Managing an eBackup Server.
● You have obtained the login password of user root of the eBackup server.
Change the password as soon as possible and log in to the server using the
new password. For password changing method, see 6.4.1.5 Changing the
Password of the root Account.
● You need to configure the route and the iptables rules if the new IP address
and the old IP address are not in the same network segment. When changing
the management plane IP address, you need to modify the route, add the
new iptables rules and delete the old iptables rules. When changing the
internal communication plane IP address, you need to modify the route, and
delete the old iptables rules. When changing the storage plane IP address, you
need to modify the route, add new iptables rules, and delete the old iptables
rules, unmount all storage units and associate them with the backup storage
again. For all the three situations above, you need to delete the rules within
one network segment when deleting the old iptables rules. Configure iptables
rules. For details, see 6.8.6.4 Auxiliary Scripts of iptables.
● If the HA function has been configured and an eBackup server needs to be
reconfigured, perform the following operations:
a. Remove an HA member.
If the HA function is enabled and the standby node is in irrecoverable
inaccessible state, see 7.3.5.3 A Standby Node Fails to Be Removed
When the HA Function Is Being Used and the Standby Node Is in the
Irrecoverable Inaccessible State.
i. Log in to the eBackup backup management system.
eBackup can be configured as an HA system only when there are at least two eBackup
servers in the system, that is, there is at least one independent backup proxy server.
Procedure
Step 1 If the production storage is Huawei distributed block storage, perform the
following operations before changing the management plane IP addresses or
production storage plane IP addresses of the backup server and backup proxy:
NOTE
a. Delete the backup server and backup proxy from the FusionStorage
cluster.
For details, see Removing a Node in the FusionStorage 8.0.1 Block
Storage Scaling Guide.
b. Log in to the eBackup server whose IP address needs to be changed to
uninstall FusionStorage block storage.
For details, see Uninstalling FusionStorage Block Storage in the
FusionStorage 8.0.1 Block Storage Product Documentation.
Step 2 If the production storage is Huawei distributed block storage, perform the
following operations before changing the management plane IP addresses or
production storage plane IP addresses of the backup server and backup proxy:
NOTE
OceanStor Pacific 9950 8.1.0 is used as an example. Obtain the document of the
corresponding version based on the site requirements.
● Before changing the management plane IP addresses of the backup server
and backup proxy, log in to the distributed storage management node to
change the eBackup management IP address.
a. Use PuTTY to log in to the distributed storage management node
through the floating IP address of the management plane.
Account: dsware
b. Modify the management plane IP address of the eBackup server.
For details, see Changing the Management IP Address of Distributed
Storage in the OceanStor Pacific Series 8.1.0 Product Documentation
(Huawei Engineers).
● Before changing the production storage plane IP address of the backup server
and backup proxy, delete VBS and delete the backup server and backup proxy
from the Huawei distributed block storage cluster.
a. Use a browser to log in to DeviceManager.
b. On the top navigation bar, choose Resources > Access > VBS.
c. Select VBS of the eBackup server whose IP address is to be changed and
delete it.
d. Delete the backup server and backup proxy from the Huawei distributed
block storage cluster.
For details, see Removing a Node from a Cluster in the OceanStor
Pacific Series 8.1.0 Capacity Expansion and Reduction Guide.
● Before changing the management plane IP addresses and production storage
plane IP addresses of the backup server and backup proxy, delete the backup
server and backup proxy from the Huawei distributed block storage cluster
and uninstall the Huawei distributed block storage.
a. Delete the backup server and backup proxy from the Huawei distributed
block storage cluster.
For details, see Removing a Node from a Cluster in the OceanStor
Pacific Series 8.1.0 Capacity Expansion and Reduction Guide.
b. Log in to the eBackup server whose IP address needs to be changed and
uninstall Huawei distributed block storage.
Step 4 If you want to change the IP address of a backup server, unregister all the backup
proxies. If you want to change the IP address of a backup proxy, unregister the
backup proxy. For details, see 6.1.4 Managing an eBackup Server.
Step 6 Run the TMOUT=0 command to prevent the user from logging out due to
timeout.
NOTE
After you run the preceding command, the system continues to run even when no
operation is performed, resulting in security risks. For security purposes, you are advised to
run the exit command to exit the system after completing your operations.
This step uses changing the IP address of the eBackup management plane as an
example. In this example, the network port configuration file corresponding to the
management plane IP address is ifcfg-bond0. Use the same method to change
the IP addresses of other planes.
1. Run the following command to switch to the network-scripts directory:
cd /etc/sysconfig/network-scripts
2. Change an eBackup IP address.
a. Run the following command to edit the configuration file:
vi Network port configuration file name
b. Press i to enter editing mode.
c. Modify the following parameter:
If Job for sshd.service failed because the control process exited with error code.
See "systemctl status sshd.service" and "journalctl -xe" for details., is displayed,
ignore it. This does not affect the restart of the SSHD service.
5. Run the following command to restart the network service.
service network restart
Step 10 If you want to change the IP address of a backup server, umount the shared disks.
If you want to change the IP address of a backup proxy, go to Step 13.
1. Run mount to check the shared disks on the server. For example, the
following information is displayed.
/dev/sda2 on / type ext3 (rw,acl,user_xattr)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
debugfs on /sys/kernel/debug type debugfs (rw)
udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,mode=1777)
devpts on /dev/pts type devpts (rw,mode=0620,gid=5)
fusectl on /sys/fs/fuse/connections type fusectl (rw)
securityfs on /sys/kernel/security type securityfs (rw)
configfs on /sys/kernel/config type configfs (rw)
ocfs2_dlmfs on /dlm type ocfs2_dlmfs (rw)
192.168.142.5:/nfs_database_94 on /opt/huawei-data-protection/ebackup/db_bak type nfs
(rw,retry=1,retrans=20,soft,nolock,timeo=60,addr=192.168.142.5)
none on /var/lib/ntp/proc type proc (ro,nosuid,nodev)
192.168.142.6:/NFS_94 on /opt/huawei-data-protection/ebackup/bricks/d94784aa-d51b-48cb-
b762-3c9c6c3c7814 type nfs (rw,retry=1,retrans=20,soft,nolock,timeo=60,addr=192.168.142.6)
/dev/sdb on /opt/huawei-data-protection/ebackup/bricks/bc5c5d05-868d-440e-97f8-3dc06b7e35e2
type ocfs2 (rw,_netdev,localalloc=2048,noacl,novdilock,heartbeat=local)
Step 12 Optional: You need to unregister the backup proxies whose Accessibility Status is
Inaccessible, Register Status is Registered when you change the internal
communication plane IP address of the backup server. For details, refer to 6.1.4
Managing an eBackup Server.
----End
Procedure
Step 1 Use PuTTY to log in to the eBackup server.
Step 2 Run the su root command and enter the password of user root to switch to user
root.
Step 3 Run the TMOUT=0 command to disable user logout upon system timeout.
NOTE
After you run the preceding command, the system continues to run even when no
operation is performed, resulting in security risks. For security purposes, you are advised to
run the exit command to exit the system after completing your operations.
Step 4 Run the vi /etc/resolv.conf command to add the IP address of a DNS server.
Press Esc to exit the editing mode. Type :wq, and press Enter.
----End
Context
● By default, eBackup generates mismatched certificate alarms. To ensure
security, enabling mismatched certificate alarms is recommended.
● After the certificate alarm function is disabled, existing alarms xxx has no
matching certificate. must be manually cleared.
Procedure
Step 1 Log in to the backup server as user hcp using PuTTY.
If HA has been configured, perform the following operations on the active backup
server.
Step 2 Run the su root command and enter the password of user root to switch to user
root.
The default password of user root is Cloud12#$.
Step 3 Run the TMOUT=0 command to prevent PuTTY from exiting due to session
timeout.
NOTE
After you run the preceding command, the system continues to run even when no
operation is performed, resulting in security risks. For security purposes, you are advised to
run the exit command to exit the system after completing your operations.
----End
Prerequisites
● You have obtained the user name and password for logging in to the
FusionCompute management console.
● You have obtained the backup management plane IP address of the eBackup
server and the password of user root.
Procedure
Step 1 If HA has been configured, remove the HA relationship first.
1. Log in to the eBackup backup management system using a browser.
Default account: admin. Default password: PXU9@ctuNov17!.
Step 2 Stop eBackup services and query the network plane configuration information of
the eBackup node.
1. Use PuTTY to log in to the eBackup server.
Default account: hcp. Default password: PXU9@ctuNov17!.
2. Run the su root command and enter the password of user root to switch to
user root.
The default password of the root user is Cloud12#$.
3. Run the TMOUT=0 command to prevent PuTTY from exiting due to timeout.
NOTE
After the preceding command is executed, the system remains running even when no
operation is performed, posing security risks. For security purposes, run the exit
command to exit the system after you finish performing operations.
4. Run the service hcp stop command to stop eBackup services.
If any job is running during this time, the job execution may fail.
5. Run the cd /opt/huawei-data-protection/ebackup/conf command to enter
the directory of the configuration file.
6. Run the find *.ini |xargs grep Plane command to query the network plane
configuration information of the eBackup node.
Record the configuration information about all network planes of the
eBackup node.
After the preceding command is executed, the system remains running even when no
operation is performed, posing security risks. For security purposes, run the exit
command to exit the system after you finish performing operations.
4. Run the following command to go to the network adapter configuration file
directory:
cd /etc/sysconfig/network-scripts/
5. Change the IP address of the eBackup server.
a. Run the following command to open and edit the configuration file of
the network adapter whose IP address needs to be changed:
vi NIC configuration file name
b. Press i to enter the editing mode and change the values of IPADDR,
NETMASK, and GATEWAY to the actual ones.
c. Press Esc and enter :wq to save the settings and exit.
6. Run the following command to restart the NIC:
service network restart
Step 10 Log in to eBackup GUI again and perform backup, restore, and backup deletion
jobs to verify that the functions are normal.
----End
Follow-up Procedure
After the MAC address is changed, the ESN changes. You must change the license
on the ESDP platform.
Procedure
Step 1 Log in to the OS remotely, and run the TMOUT=0 command to prevent the
system from exiting due to timeout.
NOTE
After you run the preceding command, the system continues to run even when no
operation is performed, resulting in security risks. For security purposes, you are advised to
run the exit command to exit the system after completing your operations.
Step 2 Run the ip a command to view the network port information of the physical
server:
This section uses network port names eno1, eno2, eno3, eno4, eno5, eno6, eno7,
and eno8 (eno1 and eno2 are management plane network ports, eno3 and eno4
are production storage plane network ports, eno5 and eno6 are backup storage
plane network ports, and eno7 and eno8 are internal communication plane
network ports.) as an example. If a reused network plane exists, skip the
procedure for configuring the corresponding NIC.
Step 3 Run the following commands in sequence to start the network ports:
ifconfig Network port name up
If the following information is displayed in the command output, check whether
the network cable is properly connected.
Step 4 Run the following commands in sequence to view the port status and network
port speed:
ethtool Network port name
Check whether the following information is displayed. If no, check whether the
network cable is properly connected.
Modify the network port configuration file name based on the site requirements.
ifcfg-bond0 DEVICE=bond0
IPADDR=eBackup management plane IP address
NETMASK=eBackup management plane subnet mask
ONBOOT=yes
BOOTPROTO=static
USERCTL=no
TYPE=Bonding
MTU=1500
BONDING_OPTS='mode=1 miimon=100'
BONDING_MASTER=yes
NM_CONTROLLED=no
GATEWAY=eBackup management plane gateway
DEFROUTE='no'
PEERDNS='no'
Name Content
ifcfg-eno1 DEVICE=eno1
BOOTPROTO=none
ONBOOT=yes
MASTER=bond0
SLAVE=yes
USERCTL=no
TYPE=Ethernet
NM_CONTROLLED=no
DEFROUTE='no'
ifcfg-eno2 DEVICE=eno2
BOOTPROTO=none
ONBOOT=yes
MASTER=bond0
SLAVE=yes
USERCTL=no
TYPE=Ethernet
NM_CONTROLLED=no
DEFROUTE='no'
3. Press Esc, enter :wq, and press Enter to save the settings and exit.
4. Run the service network restart command to restart the network adapter.
NOTE
If the service network restart command fails to be executed, check whether the
network adapter configuration is correct. If the configuration is incorrect, configure
the correct network adapter data and run the service network restart command
again to restart the network adapter.
Name Content
ifcfg-bond1 DEVICE=bond1
IPADDR=eBackup production storage plane IP address
NETMASK=eBackup production storage plane subnet mask
ONBOOT=yes
BOOTPROTO=static
USERCTL=no
TYPE=Bonding
MTU=1500
BONDING_OPTS='mode=1 miimon=100'
BONDING_MASTER=yes
NM_CONTROLLED=no
DEFROUTE='no'
PEERDNS='no'
ifcfg-eno3 DEVICE=eno3
BOOTPROTO=none
ONBOOT=yes
MASTER=bond1
SLAVE=yes
USERCTL=no
TYPE=Ethernet
NM_CONTROLLED=no
DEFROUTE='no'
ifcfg-eno4 DEVICE=eno4
BOOTPROTO=none
ONBOOT=yes
MASTER=bond1
SLAVE=yes
USERCTL=no
TYPE=Ethernet
NM_CONTROLLED=no
DEFROUTE='no'
3. Press Esc, enter :wq, and press Enter to save the settings and exit.
4. Run the service network restart command to restart the network adapter.
NOTE
If the service network restart command fails to be executed, check whether the
network adapter configuration is correct. If the configuration is incorrect, configure
the correct network adapter data and run the service network restart command
again to restart the network adapter.
This section uses bond2 as an example to describe how to configure bond2 as the
eBackup backup storage plane and network ports eno5 and eno6 as bond2.
1. Run the cd /etc/sysconfig/network-scripts command to go to the network-
scripts directory.
2. Run the vi Network port configuration file name command to open and
modify the network port information configuration file, as shown in Table
9-3.
NOTE
Table 9-3 Examples of network port configuration files of the backup storage
plane
Name Content
ifcfg-bond2 DEVICE=bond2
IPADDR=IP address of the eBackup backup storage plane
NETMASK=Subnet mask of the eBackup backup storage plane
ONBOOT=yes
BOOTPROTO=static
USERCTL=no
TYPE=Bonding
MTU=1500
BONDING_OPTS='mode=1 miimon=100'
BONDING_MASTER=yes
NM_CONTROLLED=no
DEFROUTE='no'
PEERDNS='no'
ifcfg-eno5 DEVICE=eno5
BOOTPROTO=none
ONBOOT=yes
MASTER=bond2
SLAVE=yes
USERCTL=no
TYPE=Ethernet
NM_CONTROLLED=no
DEFROUTE='no'
ifcfg-eno6 DEVICE=eno6
BOOTPROTO=none
ONBOOT=yes
MASTER=bond2
SLAVE=yes
USERCTL=no
TYPE=Ethernet
NM_CONTROLLED=no
DEFROUTE='no'
3. Press Esc, enter :wq, and press Enter to save the settings and exit.
4. Run the service network restart command to restart the network adapter.
NOTE
If the service network restart command fails to be executed, check whether the
network adapter configuration is correct. If the configuration is incorrect, configure
the correct network adapter data and run the service network restart command
again to restart the network adapter.
Modify the network port configuration file name based on the site requirements.
Table 9-4 Example of the network port configuration file of the internal
communication plane
Name Content
ifcfg-bond3 DEVICE=bond3
IPADDR=eBackup internal communication plane IP address
NETMASK=eBackup internal communication plane subnet mask
ONBOOT=yes
BOOTPROTO=static
USERCTL=no
TYPE=Bonding
MTU=1500
BONDING_OPTS='mode=1 miimon=100'
BONDING_MASTER=yes
NM_CONTROLLED=no
DEFROUTE='no'
PEERDNS='no'
ifcfg-eno7 DEVICE=eno7
BOOTPROTO=none
ONBOOT=yes
MASTER=bond3
SLAVE=yes
USERCTL=no
TYPE=Ethernet
NM_CONTROLLED=no
DEFROUTE='no'
ifcfg-eno8 DEVICE=eno8
BOOTPROTO=none
ONBOOT=yes
MASTER=bond3
SLAVE=yes
USERCTL=no
TYPE=Ethernet
NM_CONTROLLED=no
DEFROUTE='no'
3. Press Esc, enter :wq, and press Enter to save the settings and exit.
4. Run the service network restart command to restart the network adapter.
NOTE
If the service network restart command fails to be executed, check whether the
network adapter configuration is correct. If the configuration is incorrect, configure
the correct network adapter data and run the service network restart command
again to restart the network adapter.
----End
Procedure
Step 1 Log in to the OS remotely, and run the TMOUT=0 command to prevent the
system from exiting due to timeout.
NOTE
After you run the preceding command, the system continues to run even when no
operation is performed, resulting in security risks. For security purposes, you are advised to
run the exit command to exit the system after completing your operations.
Step 2 Run the ip a command to view the network port information of the physical
server:
This section uses network port names eno1, eno2, eno3, eno4, eno5, eno6, eno7,
and eno8 (eno1 and eno2 are management plane network ports, eno3 and eno4
are production storage plane network ports, eno5 and eno6 are backup storage
plane network ports, and eno7 and eno8 are internal communication plane
network ports.) as an example. If a reused network plane exists, skip the
procedure for configuring the corresponding NIC.
Step 3 Run the following commands in sequence to start the network ports:
ifconfig Network port name up
If the following information is displayed in the command output, check whether
the network cable is properly connected.
Step 4 Run the following commands in sequence to view the port status and network
port speed:
ethtool Network port name
Check whether the following information is displayed. If no, check whether the
network cable is properly connected.
Name Content
ifcfg-bond0 DEVICE=bond0
IPV6INIT=yes
IPV6ADDR=eBackup management plane IP address/Prefix length
ONBOOT=yes
BOOTPROTO=static
USERCTL=no
TYPE=Bonding
MTU=1500
BONDING_OPTS='mode=1 miimon=100'
BONDING_MASTER=yes
NM_CONTROLLED=no
STARTMODE=onboot
DEFROUTE=yes
PEERDNS=no
ifcfg-eno1 DEVICE=eno1
IPV6INIT=yes
BOOTPROTO=none
ONBOOT=yes
MASTER=bond0
SLAVE=yes
USERCTL=no
TYPE=Ethernet
NM_CONTROLLED=no
DEFROUTE=yes
PEERDNS=no
ifcfg-eno2 DEVICE=eno2
IPV6INIT=yes
BOOTPROTO=none
ONBOOT=yes
MASTER=bond0
SLAVE=yes
USERCTL=no
TYPE=Ethernet
NM_CONTROLLED=no
DEFROUTE=no
PEERDNS=no
3. Press Esc, enter :wq, and press Enter to save the settings and exit.
4. Run the service network restart command to restart the network adapter.
NOTE
If the service network restart command fails to be executed, check whether the
network adapter configuration is correct. If the configuration is incorrect, configure
the correct network adapter data and run the service network restart command
again to restart the network adapter.
This section uses bond1 as an example to describe how to configure bond1 as the
eBackup production storage plane and network ports eno3 and eno4 as bond1.
1. Run the cd /etc/sysconfig/network-scripts command to go to the network-
scripts directory.
2. Run the vi Network port configuration file name command to open and
modify the network port information configuration file, as shown in Table
9-6.
NOTE
Name Content
ifcfg- DEVICE=bond1
IPV6INIT=yes
bond1 IPV6ADDR=Production storage plane IP address/Prefix length
ONBOOT=yes
BOOTPROTO=static
USERCTL=no
TYPE=Bonding
MTU=1500
BONDING_OPTS='mode=1 miimon=100'
BONDING_MASTER=yes
NM_CONTROLLED=no
STARTMODE=onboot
DEFROUTE=no
PEERDNS=no
ifcfg- DEVICE=eno4
IPV6INIT=yes
eno4 BOOTPROTO=none
ONBOOT=yes
MASTER=bond1
SLAVE=yes
USERCTL=no
TYPE=Ethernet
NM_CONTROLLED=no
DEFROUTE=no
PEERDNS=no
3. Press Esc, enter :wq, and press Enter to save the settings and exit.
4. Run the service network restart command to restart the network adapter.
NOTE
If the service network restart command fails to be executed, check whether the
network adapter configuration is correct. If the configuration is incorrect, configure
the correct network adapter data and run the service network restart command
again to restart the network adapter.
Table 9-7 Examples of network port configuration files of the backup storage
plane
Name Content
ifcfg-bond2 DEVICE=bond2
IPV6INIT=yes
IPV6ADDR=Backup storage plane IP address/Prefix length
ONBOOT=yes
BOOTPROTO=static
USERCTL=no
TYPE=Bonding
MTU=1500
BONDING_OPTS='mode=1 miimon=100'
BONDING_MASTER=yes
NM_CONTROLLED=no
STARTMODE=onboot
DEFROUTE=no
PEERDNS=no
ifcfg-eno5 DEVICE=eno5
IPV6INIT=yes
BOOTPROTO=none
ONBOOT=yes
MASTER=bond2
SLAVE=yes
USERCTL=no
TYPE=Ethernet
NM_CONTROLLED=no
DEFROUTE=no
PEERDNS=no
Name Content
ifcfg-eno6 DEVICE=eno6
IPV6INIT=yes
BOOTPROTO=none
ONBOOT=yes
MASTER=bond2
SLAVE=yes
USERCTL=no
TYPE=Ethernet
NM_CONTROLLED=no
DEFROUTE=no
PEERDNS=no
3. Press Esc, enter :wq, and press Enter to save the settings and exit.
4. Run the service network restart command to restart the network adapter.
NOTE
If the service network restart command fails to be executed, check whether the
network adapter configuration is correct. If the configuration is incorrect, configure
the correct network adapter data and run the service network restart command
again to restart the network adapter.
Table 9-8 Example of the network port configuration file of the internal
communication plane
Name Content
ifcfg-bond3 DEVICE=bond3
IPV6INIT=yes
IPV6ADDR=Internal communication plane IP address/Prefix length
ONBOOT=yes
BOOTPROTO=static
USERCTL=no
TYPE=Bonding
MTU=1500
BONDING_OPTS='mode=1 miimon=100'
BONDING_MASTER=yes
NM_CONTROLLED=no
STARTMODE=onboot
DEFROUTE=no
PEERDNS=no
Name Content
ifcfg-eno7 DEVICE=eno7
IPV6INIT=yes
BOOTPROTO=none
ONBOOT=yes
MASTER=bond3
SLAVE=yes
USERCTL=no
TYPE=Ethernet
NM_CONTROLLED=no
DEFROUTE=no
PEERDNS=no
ifcfg-eno8 DEVICE=eno8
IPV6INIT=yes
BOOTPROTO=none
ONBOOT=yes
MASTER=bond3
SLAVE=yes
USERCTL=no
TYPE=Ethernet
NM_CONTROLLED=no
DEFROUTE=no
PEERDNS=no
3. Press Esc, enter :wq, and press Enter to save the settings and exit.
4. Run the service network restart command to restart the network adapter.
NOTE
If the service network restart command fails to be executed, check whether the
network adapter configuration is correct. If the configuration is incorrect, configure
the correct network adapter data and run the service network restart command
again to restart the network adapter.
----End
Prerequisites
● The eBackup server is connected to the storage device using network cables.
● An iSCSI initiator has been installed on the eBackup server.
● A cross-platform remote access tool, such as PuTTY, is available.
● The backup management plane IP address of the eBackup server and the
password of user root have been obtained. You are advised to change the
password regularly for security purposes.
Context
Take the service and management IP addresses of an OceanStor 5600 V3 storage
device 192.168.81.3 and 192.168.81.30 and storage plane IP address of the
eBackup server 192.168.18.40 as an example.
Procedure
Step 1 Use PuTTY to log in to the eBackup server.
● Template deployment environment
a. Log in to the server as user hcp.
b. Run the su root command and enter the password of account root to
switch to account root.
● Software package deployment environment
Log in to the server as user root.
Step 2 Run the TMOUT=0 command to prevent PuTTY from exiting due to timeout.
NOTE
After you run the preceding command, the system continues to run even when no
operation is performed, resulting in security risks. For security purposes, you are advised to
run the exit command to exit the system after completing your operations.
NOTE
– In scenarios where the initiator has been added to a host of the OceanStor V3
storage system:
During system running, if the name of the initiator has been changed, restart the
iSCSI service, log in to the OceanStor V3 storage system, remove the original
initiator, and add a new initiator.
– In scenarios where the initiator has not been added to any host of the OceanStor
V3 storage system:
During system running, if the name of the initiator has been changed, you must
restart the iSCSI service.
2. Restart the iSCSI service.
– For the SUSE operating system, run the service open-iscsi restart
command.
– For the Euler operating system, run the service iscsid restart command.
3. Run the iscsiadm -m discovery -t st -p 192.168.81.3 command to discover a
target.
NOTE
The IP address of the target is the service IP address of the storage device connected
to the service port of the eBackup server.
4. Run the iscsiadm -m node -p 192.168.81.3 -l command to log in to the
target.
----End
Context
Run the iscsiadm command to set the CHAP user name and password on the
eBackup server.
Procedure
Step 1 Use PuTTY to log in to the eBackup server.
● Template deployment environment
a. Log in to the server as user hcp.
b. Run the su root command and enter the password of account root to
switch to account root.
● Software package deployment environment
Log in to the server as user root.
Step 2 Run the TMOUT=0 command to prevent PuTTY from exiting due to timeout.
NOTE
After you run the preceding command, the system continues to run even when no
operation is performed, resulting in security risks. For security purposes, you are advised to
run the exit command to exit the system after completing your operations.
The IP address of the target is the service IP address of the storage system
connected to the service port of the eBackup server.
In this example, the IP address of the target is 192.168.81.3.
2. Configure the unidirectional CHAP user name and password.
Run the following command to configure the CHAP user name. For example:
iscsiadm -m node -o update -p 192.168.81.3 -n node.session.auth.username -v chaper-1
In this example, the IP address of the target is 192.168.81.3, and the CHAP
user name added for the eBackup server is chaper-1.
Run the following command to configure the CHAP password. For example:
iscsiadm -m node -o update -p 192.168.81.3 -n node.session.auth.password -v 12345678qwer
In this example, the IP address of the target is 192.168.81.3, and the password
of the CHAP user added for the eBackup server is 12345678qwer.
3. Optional: If the storage system (target) supports bidirectional CHAP
authentication, you need to configure the bidirectional CHAP user name and
password so that the iSCSI initiator can authenticate the storage system.
NOTE
The password for bidirectional CHAP authentication must be different from that for
unidirectional CHAP authentication.
Run the following command to configure the CHAP user name. For example:
iscsiadm -m node -o update -p 192.168.81.3 -n node.session.auth.username_in -v chaper-2
In this example, the IP address of the target is 192.168.81.3, and the CHAP user
name added for the eBackup server is chaper-2.
Run the following command to configure the CHAP password. For example:
iscsiadm -m node -o update -p 192.168.81.3 -n node.session.auth.password_in -v 87654321qwer
In this example, the IP address of the target is 192.168.81.3, and the password of
the CHAP user added for the eBackup server is 87654321qwer.
----End
Memory ≥ 16 GB
Number of network ports Plan a network port for each network plane based
on the network planes planned in 2.2.2 Network
Planning.
If you need to configure virtual NICs according to
9.8 Configuring Network Adapter Binding, plan
two network ports for each network plane for
which virtual NICs need to be configured.
Prerequisites
● Two physical servers are ready as required in 9.11.1 Software and Hardware
Configurations. One server will be used to be deployed as a backup server,
the other as a backup proxy.
● You have obtained the IP address, user name, and password of the iBMC
management network port.
● If RAID has been configured for the disks of the physical server, delete the
RAID to clear the disk partitions of the physical server.
● You have obtained the image file OceanStor_BCManager_EulerOS_X86.iso,
which can be obtained by decompressing OceanStor BCManager
xxx_EulerOS_X86.zip. xxx indicates the eBackup version.
How to obtain:
For enterprise users: Click here.
For carrier users: Click here.
Procedure
Step 1 Log in to the iBMC WebUI.
1. Open a browser. In the address box, type the IP address of the iBMC
management network port and press Enter. The address format is https://IP
address of the iBMC management network port.
2. Set User Name and Password, set Domain to Local iBMC, and click Log In.
The iBMC Web management page is displayed.
Step 2 Choose Remote Console > HTML5 Integrated Remote Console (Shared) to
access the remote control page of the physical server.
Step 3 Click > Forced System Reset to restart the physical server.
Step 4 When you see the following interface during the restart, press F11.
Step 5 In the following text box, enter your password and press Enter.
NOTE
----End
Procedure
Step 1 On the home page, press → and select Device Manager. The Device Manager
page is displayed.
Step 3 Press Enter. In the displayed menu, choose Main Menu > Configuration
Management > Clear Configuration to clear the system configuration.
Step 4 Select Confirm, press Enter, and then select Yes, and press Enter to confirm the
clearing operation.
Step 5 Press Esc to return to the configuration management menu and select Create
Virtual Drive.
Step 6 On the RAID configuration interface, move the cursor to locate Select RAID Level,
press Enter, and select RAID1.
Step 7 Press ↑ or ↓ to locate Select Drives, press Enter, select two disks of the same size
and type to form RAID 1, and select Apply Changes.
Step 8 Select Save Configuration to save the configuration. Select Confirm, press Enter,
and then select Yes, and press Enter to confirm the saving. Format the disks when
dividing RAID.
NOTICE
The capacity of RAID 1 ranges from 300 GB to 2 TB. Otherwise, the configuration
fails. If the capacity is greater than 2 TB, select Virtual Driver Size in this step to
change the capacity.
Step 9 Return to the configuration management menu and select View Drive Group
Properties to view the configured RAID information.
Step 10 Press Esc to return to the home page.
----End
Procedure
Step 1 In the main window, click > to select an image file, and click Connect to
open the image file.
Step 2 Press → to select Boot Manager. The Boot Manager page is displayed.
Step 3 Select the virtual DVD-ROM drive as the boot device and press Enter.
Step 4 On the following interface, press ↑ or ↓ to select Install EulerOS V2.0SP3 and
then press Enter to start installing the OS.
Step 5 If the physical server has a RAID controller card, perform the following steps to
partition the disk.
1. Select Installation Destination.
2. Select the RAID disk created in 9.11.2.2 Configuring RAIDs, select Custom on
the Storage Configuration page, and click Done.
a. Click .
b. Select /boot from the Mount Point drop-down list box.
c. Enter 512MiB in the Desired Capacity text box.
----End
Prerequisites
● The IP addresses of physical servers have been planned according to 2.2.2
Network Planning.
● You have obtained the mappings between the management plane, production
storage plane, backup storage plane, and internal communication plane and
the internal network ports of the system.
Procedure
Step 1 Log in to the OS remotely on iBMC, and run the TMOUT=0 command to prevent
the system from exiting due to timeout.
NOTE
After you run the preceding command, the system continues to run even when no
operation is performed, resulting in security risks. For security purposes, you are advised to
run the exit command to exit the system after completing your operations.
Step 2 Run the ip a command to view the network port information of the physical
server.
In this section, the network port names are eno1, eno2, eno3, and eno4. eno1 is
the management plane network port, eno2 is the production storage plane
network port, eno3 is the backup storage plane network port, and eno4 is the
internal communication plane network port. If a reused network plane exists, skip
the procedure for configuring the corresponding NIC. If multiple NICs need to be
bound as a virtual NIC, perform the configuration by referring to 9.8 Configuring
Network Adapter Binding. This section describes how to configure a single NIC.
Step 3 Run the following commands in sequence to start the network ports.
ifconfig Network port name up
If the following information is displayed in the command output, check whether
the network cable is properly connected.
Step 4 Run the following commands in sequence to view the port status and network
port speed.
ethtool Network port name
Check whether the following information is displayed. If no, check whether the
network cable is properly connected.
Modify the network port configuration file name based on the site requirements.
ifcfg-eno1 DEVICE=eno1
IPADDR=eBackup management plane IP address
NETMASK=eBackup management plane subnet mask
ONBOOT=yes
BOOTPROTO=static
GATEWAY=eBackup management plane gateway
DEFROUTE='yes'
PEERDNS='no'
3. Press Esc, enter :wq, and press Enter to save the settings and exit.
4. Run the service network restart command to restart the network adapter.
NOTE
If the service network restart command fails to be executed, check whether the
network adapter configuration is correct. If the configuration is incorrect, configure
the correct network adapter data and run the service network restart command
again to restart the network adapter.
ifcfg-eno2 DEVICE=eno2
IPADDR=eBackup production storage plane IP address
NETMASK=eBackup production storage plane subnet mask
ONBOOT=yes
BOOTPROTO=static
DEFROUTE='no'
PEERDNS='no'
3. Press Esc, enter :wq, and press Enter to save the settings and exit.
4. Run the service network restart command to restart the network adapter.
NOTE
If the service network restart command fails to be executed, check whether the
network adapter configuration is correct. If the configuration is incorrect, configure
the correct network adapter data and run the service network restart command
again to restart the network adapter.
Modify the network port configuration file name based on the site requirements.
ifcfg-eno3 DEVICE=eno3
IPADDR=IP address of the eBackup backup storage plane
NETMASK=Subnet mask of the eBackup backup storage plane
ONBOOT=yes
BOOTPROTO=static
DEFROUTE='no'
PEERDNS='no'
3. Press Esc, enter :wq, and press Enter to save the settings and exit.
4. Run the service network restart command to restart the network adapter.
NOTE
If the service network restart command fails to be executed, check whether the
network adapter configuration is correct. If the configuration is incorrect, configure
the correct network adapter data and run the service network restart command
again to restart the network adapter.
Modify the network port configuration file name based on the site requirements.
Table 9-14 Example of the network port configuration file of the internal
communication plane
Name Content
ifcfg-eno4 DEVICE=eno4
IPADDR=eBackup internal communication plane IP address
NETMASK=eBackup internal communication plane subnet mask
ONBOOT=yes
BOOTPROTO=static
DEFROUTE='no'
PEERDNS='no'
3. Press Esc, enter :wq, and press Enter to save the settings and exit.
4. Run the service network restart command to restart the network adapter.
NOTE
If the service network restart command fails to be executed, check whether the
network adapter configuration is correct. If the configuration is incorrect, configure
the correct network adapter data and run the service network restart command
again to restart the network adapter.
----End
Prerequisites
● The IP addresses of physical servers have been planned according to 2.2.2
Network Planning.
● You have obtained the mappings between the management plane, production
storage plane, backup storage plane, and internal communication plane and
the internal network ports of the system.
Procedure
Step 1 Log in to the OS remotely on iBMC, and run the TMOUT=0 command to prevent
the system from exiting due to timeout.
NOTE
After you run the preceding command, the system continues to run even when no
operation is performed, resulting in security risks. For security purposes, you are advised to
run the exit command to exit the system after completing your operations.
Step 2 Run the ip a command to view the network port information of the physical
server.
In this section, the network port names are eno1, eno2, eno3, and eno4. eno1 is
the management plane network port, eno2 is the production storage plane
network port, eno3 is the backup storage plane network port, and eno4 is the
internal communication plane network port. If a reused network plane exists, skip
the procedure for configuring the corresponding NIC. If multiple NICs need to be
bound as a virtual NIC, perform the configuration by referring to 9.8 Configuring
Network Adapter Binding. This section describes how to configure a single NIC.
Step 3 Run the following commands in sequence to start the network ports.
Step 4 Run the following commands in sequence to view the port status and network
port speed.
ethtool Network port name
Check whether the following information is displayed. If no, check whether the
network cable is properly connected.
Modify the network port configuration file name based on the site requirements.
Name Content
ifcfg-eno1 DEVICE=eno1
IPV6INIT=yes
IPV6ADDR=eBackup management plane IP address/Prefix length
ONBOOT=yes
BOOTPROTO=static
STARTMODE=onboot
DEFROUTE=yes
PEERDNS=no
3. Press Esc, enter :wq, and press Enter to save the settings and exit.
4. Run the service network restart command to restart the network adapter.
NOTE
If the service network restart command fails to be executed, check whether the
network adapter configuration is correct. If the configuration is incorrect, configure
the correct network adapter data and run the service network restart command
again to restart the network adapter.
This section uses network port eno2 as the production storage plane network port
as an example.
1. Run the cd /etc/sysconfig/network-scripts command to go to the network-
scripts directory.
2. Run the vi Network port configuration file name command to open and
modify the network port information configuration file, as shown in Table
9-16.
NOTE
Name Content
ifcfg- DEVICE=eno2
IPV6INIT=yes
eno2 IPV6ADDR=Production storage plane IP address/Prefix length
ONBOOT=yes
BOOTPROTO=static
STARTMODE=onboot
DEFROUTE=no
PEERDNS=no
3. Press Esc, enter :wq, and press Enter to save the settings and exit.
4. Run the service network restart command to restart the network adapter.
NOTE
If the service network restart command fails to be executed, check whether the
network adapter configuration is correct. If the configuration is incorrect, configure
the correct network adapter data and run the service network restart command
again to restart the network adapter.
Modify the network port configuration file name based on the site requirements.
ifcfg-eno3 DEVICE=eno3
IPV6INIT=yes
IPV6ADDR=Backup storage plane IP address/Prefix length
ONBOOT=yes
BOOTPROTO=static
STARTMODE=onboot
DEFROUTE=no
PEERDNS=no
3. Press Esc, enter :wq, and press Enter to save the settings and exit.
4. Run the service network restart command to restart the network adapter.
NOTE
If the service network restart command fails to be executed, check whether the
network adapter configuration is correct. If the configuration is incorrect, configure
the correct network adapter data and run the service network restart command
again to restart the network adapter.
Modify the network port configuration file name based on the site requirements.
Table 9-18 Example of the network port configuration file of the internal
communication plane
Name Content
ifcfg-eno4 DEVICE=eno4
IPV6INIT=yes
IPV6ADDR=Internal communication plane IP address/Prefix length
ONBOOT=yes
BOOTPROTO=static
STARTMODE=onboot
DEFROUTE=no
PEERDNS=no
3. Press Esc, enter :wq, and press Enter to save the settings and exit.
4. Run the service network restart command to restart the network adapter.
NOTE
If the service network restart command fails to be executed, check whether the
network adapter configuration is correct. If the configuration is incorrect, configure
the correct network adapter data and run the service network restart command
again to restart the network adapter.
----End
Symptom
Message Warning checking storage configuration or Custom partitioning
selected is displayed during the OS installation. Such as Figure 9-1, Figure 9-2.
Possible Cause
Historical partitions exist or no /swap partition exists in the target disk where the
OS is installed. You need to confirm whether to overwrite.
Procedure
----End
Symptom
During the OS installation, Error checking storage configuration is displayed.
Possible Causes
The target disk where the OS is to be installed uses the GPT mode to record
information of partitions. The /boot partition cannot be used, and the BIOS Boot
partition needs to be added.
Procedure
Step 3 The detailed error information and handling suggestions are displayed. Read the
information carefully and click Close.
If the error details are not the content in the following figure, rectify the fault
according to the handling suggestions in the details.
Step 5 Click , select biosboot from the drop-down list, and click Add mount point >
to add the partition.
----End
The chapter describes the basic concepts and principles about backup and restore,
helping you get familiar with backup and restore jobs before configuring them.
10.1 Backup
10.2 Restore
10.3 Backup Storage
10.4 Protected Environments Supported by eBackup
10.5 Protected Set
10.6 Backup Policies
10.7 Backup Plan
10.8 Backups
10.9 Common Concepts
10.1 Backup
This section describes backup-related basic terms such as snapshot and changed
block tracking (CBT), backup principles, deduplication and compression principles.
Basic Terms
Table 10-1 describes some backup-related basic terms.
Term Description
Term Description
Snapshot Two snapshots are compared and data differences of the two
comparis snapshots are displayed in the format of volume addresses. In
on incremental backup mode, only differential data is backed up.
Full ● For virtual disks, all data on the virtual disks is backed up.
backup ● For VMs, all disk data and VM configuration information are
backed up no matter when data was changed or backed up last
time.
No matter when data was changed or backed up last time, all data
is backed up. Full backup provides the most complete backup
protection. However, full backup takes a long time and occupies
large space.
Incremen ● For disks, the data changed since last full or incremental backup
tal for disks is backed up.
backup ● For VMs, the disk data and VM configuration information
changed since last full or incremental backup for VMs is backed
up.
The amount of incremental backup data is small and the backup
time is short.
Backup Principles
eBackup backup management system supports backup of VMs in the
FusionSphere environments. Table 10-2 lists application scenarios of different
backup modes.
NOTE
At the production end, when the storage type is virtualized storage, eBackup backup
management system can use CBT to back up VMs. When the VM storage type is Huawei
distributed block storage, eBackup backup management system can only use snapshot
compare to back up VMs.
CBT Snapshots are not reserved at the production end and do not occupy too
much storage space as a result. Using the CBT backup mode, eBackup
backup management system obtains changed data faster than using the
snapshot backup mode.
Sna Snapshots are reserved at the production end and occupy a large storage
psh space as a result. Using the snapshot backup mode, eBackup backup
ot management system obtains changed data slower than using the CBT
com backup mode.
pari
son
Deduplication
Deduplication is a data compression technology that searches for duplicate data,
saves only one copy of the data, and uses pointers that point to the unique copy
Compression
Data compression aims to reduce the storage space occupied by redundant data
and improve data transmission and processing efficiency. eBackup uses the LZ4
compression algorithm defines the size of the scanning window as M bytes and
the scanning moving size as N bytes. The M-byte data is used as the scanning
window for matching. After the duplicate data is found, the data is compressed.
N-byte data is removed for scanning each time.
10.2 Restore
This section describes restore-related terms such as backup, CBT, and restore
principles.
Basic Terms
Table 10-4 describes some discovery-related basic terms.
Term Description
Snapshot Two snapshots are compared and data differences of the two
comparis snapshots are displayed in the format of volume addresses. In
on incremental restore mode, the snapshot corresponding to a copy
used for restoration is compared with the target volume to be
restored, and only differential data is restored.
Full ● For disks, all disk backup data to which a backup corresponds is
restore restored.
● For VMs, all disk backup data and VM configuration information
to which a backup corresponds is restored.
It takes a longer time to restore a larger amount of data.
Incremen ● For disks, disk data changed between the backup point in time
tal and restore execution point in time is restored
restore ● For VMs, disk data changed between the backup point in time
and restore execution point in time and all VM configuration
information is restored.
NOTE
If snapshots exist, the system executes incremental restore. If snapshots do
not exist, the system executes full restore.
It takes a shorter time to restore a smaller amount of data.
Restore Principles
When FusionSphere and VMware VM data or data of LUNs in storage devices
needs to be restored, eBackup backup management system provides restore data
according to the backup that was created at a point in time specified by a user.
eBackup backup management system supports full restore and incremental
restore. For details about restore modes, see the background information in 4.1
Restoring FusionSphere VMs.
Users can specify any point-in-time backup saved in eBackup backup management
system to restore data. Restoring disk M is used as an example to illustrate the
principles of the two restore modes:
Full restore
When eBackup backup management system starts a restore job for disk M, if the
original disk on the target VM exists with capacity and location unchanged, obtain
all the backup data from the backup and write it onto disk M; if the original disk
on the target VM does not exist, create new disk M1 on the production end based
on the metadata of disk M in the backup, obtain all the backup data from the
backup and write it onto disk M1, and mount disk M1 to the target VM.
Incremental restore
eBackup backup management system starts a restore job for disk M and uses CBT
to obtain the data changed between the restore execution point in time of disk M
and the backup point in time of the backup. After receiving the changed data
from the backup, the system writes it to disk M at the production end.
Definition
As a global concept, backup storage refers to the back-end storage space for use
by eBackup backup management system, which consists of storage units, storage
pools, and repositories.
● Storage unit
A storage unit is the basic storage unit for backup data.
● Storage pool
A storage pool consists of one storage unit. A single storage pool forms an
abstraction layer to realize physical isolation. That is, the failure of one
storage pool does not affect the backup of other storage pools.
● Repository
A repository is a storage space divided from a storage pool. Storage
repositories are logically isolated from each other. A repository stores the
backups generated after a protected set is backed up. Repositories provide
storage space for backup and data source for recovery.
Logical Structure
Figure 10-2 shows the internal logical structure of backup storage.
1. After back-end storage devices map the storage space to backup server and
backup proxies, eBackup backup management system creates storage units
based on the storage space for use in data backup.
2. eBackup backup management system allocates the created storage units to
storage pools. Storage pools are physically isolated, that is, the failure of one
storage pool does not affect the backup of other storage pools.
3. Based on storage pools, eBackup backup management system creates one or
more repositories for storing backup data. If a protected object belongs to
only one backup plan, all its backups are stored in one repository instead of
spanning different repositories. If a protected object belongs to more than
one backup plan, its backups can be stored in different repositories.
Component Description
CNA CNAs are deployed on physical servers and manage local VMs
and corresponding virtual volumes.
Definition
A protected set defines backup objects, which can be one or more protected
objects. You can assign or exclude disks for all or specified VMs.
Functions
After a protected set is created, you can apply a backup policy for all backup
objects in a protected set to shorten the backup duration and improve backup
efficiency.
NOTE
A protected set, backup policy, and repository can all be used by multiple backup plans.
Scheduling Plan
After creating backup plans, users can manually start backup jobs at anytime
based on site requirements. However, as the number of backup jobs increases, it
becomes more and more difficult to manually track and execute backup jobs in
real time. eBackup backup management system provides a backup policy to
automatically schedule backup jobs. Besides, users can set retry policies to execute
failed backup jobs again. Note that retry policies are restricted by retry windows
and retry times.
The value can be Periodic or One time. When Schedule is set to Periodic, you
need to set scheduling plans for incremental backup. You can determine whether
to enable periodic full backup based on site requirements.
NOTE
If incremental backup and full backup are set to be executed at the same point in time, the
system will execute full backup first.
Weeks in Backup jobs are executed weekly The more frequently data is
a Month or in a specific week. backed up, the more thoroughly
data is protected; however, the
Days in a Backup jobs are not executed on backup time is also longer,
Week specific days. It is used together requiring a longer backup time
with Weeks in a Month. For and occupying larger space.
example, execute backup jobs on Choose a schedule based on
Wednesday and Sunday in the data importance and service
first week of each month. volume. Adopt a high backup
Excluded Execute backup jobs not in those frequency for important data.
Days in a specific days.
Month
One time Backup jobs to which a specific The backup policy execution
backup policy is set are executed time must be later than the
only once. The backup policy current system time.
execution time needs to be set.
The parameter is valid only to
full backup. This parameter is
available only when Schedule is
set to One time.
Create After this option is selected, This function will affect backup
Verificati the system creates verification performance. If you have
on Data data for backup data. The demanding requirements on
verification data will be used to integrity and consistency of
verify the integrity and backup data and have no
consistency of the backup data. requirements on backup
If this option is not selected, performance, you are advised to
the system verifies only the enable this option to ensure data
consistency of the metadata of availability after data restore.
the backup data.
NOTE
Backup data is the real data of
users. Backup metadata is the
additional information about
location of data blocks and
number of disks.
Retry Policy
A retry policy defines the number of retries and retry time window after a backup
job fails. The retry time window specifies the maximum time duration allowed for
the backup job to retry since its failure. The retry function can be enabled or
disabled based on site requirements. If the retry function is disabled, failed backup
jobs will not be performed again.
For example, backup job A is performed at 9:00. At 9:10, backup job A fails. In the
retry plan, the number of retries is set to 3 and the retry window is set to one
hour. By default, the system performs a failed backup job five minutes after the
backup job execution failure. Therefore, backup job A is performed again between
9:15 and 10:10.
● If backup job A still fails after three retries within the specified period or the
three retries cannot be completed within the specified period, the system will
not perform backup job A again.
● If backup job A successes within the specified period, the system will not
perform backup job A again.
Definition
Backup plans logically define backup boundaries. Backup plan consists of backup
policy, protected set, and repository. One backup plan is associated with one
backup policy, one protected set, and one repository only.
Function
Backup plans schedule backup jobs based on policies and store backups of
protected sets to repository.
NOTE
One backup policy, protected set, and repository can apply to multiple backup plans.
10.8 Backups
This section defines backups and explains their functions and relationship with
other modules.
Definition
A backup is backup data generated after a backup plan performs a backup job
based on a backup policy. Each backup is marked generation time. You can select
necessary backups to restore data according to timestamps.
The backup of an entire VM is named after the generation time of the backup.
The backup of a disk is named in the format of BUS number of the disk+Slot
number of the disk.
Functions
Verified backups are used to restore lost or damaged data at the production end.
11 FAQ
11.1 In What Configuration Modes Can Disks Not Be Restored by eBackup in LAN-
free Mode
11.2 Do VMs Created on FusionCompute Need to Be Restarted After Their CPUs
and Memory Are Adjusted
11.3 What Disk Modes are Not Supported by eBackup
11.4 Can Management Data Backup Storage and Backup Storage Storing User VM
Data Use One Shared Directory
11.5 No Backup Is Generated for VMs on FusionCompute
11.6 What Is the Impact of Removing an eBackup Server When the Production
Storage Is Huawei Distributed Block Storage
Answer
eBackup cannot restore the disks whose configuration modes are Thin
provisioning and Thick provisioning lazy zeroed in LAN-Free mode.
Answer
VMs created on FusionCompute need to be restarted after their CPUs and memory
are adjusted. Otherwise, backup may fail. Restarting VMs will interrupt services of
the VMs. You are advised to perform this operation when the service traffic is low.
Answer
Disk modes Independent & persistent and Independent & nonpersistent are
not supported by eBackup. Disk mode Dependent is supported.
Answer
Backup storage of management data and backup storage for storing user VM data
cannot use the same NAS shared directory or bucket. Otherwise, the backup task
may fail.
Answer
eBackup does not support the backup of shared disks of VMs on FusionCompute.
If only shared disks exist on the VM, no backup job will be generated.
Answer
When the production storage is Huawei distributed block storage, an exception
may occur in the Huawei distributed block storage cluster after the eBackup server
is removed. Therefore, before removing the eBackup server, delete the eBackup
server from the Huawei distributed block storage cluster. For details, see
Removing a Node in the Capacity Expansion and Reduction Guide of Huawei
distributed block storage.
A Glossary
A
AK See access key ID (AK).
API See application programming interface (API).
ASII American Standard Code for Information Interchange
access key ID (AK) An ID that confirms the identity of a user accessing the
object-based storage system. One access key ID belongs to
only one user, but one user can have multiple access key
IDs. The object-based storage system recognizes the users
accessing the system by their access key IDs.
security Security prevents computer systems and data from being
damaged and lost. Computer security is mainly ensured by
preventing access by unauthorized users to systems,
especially for systems that can be accessed by multiple
users or through communication lines.
application An application programming interface is a particular set of
programming rules and specifications that are used for communication
interface (API) between software programs.
B
B/S Browser/Server
BIOS See basic input/output system (BIOS).
whitelist A list or register of items that, for one reason or another,
are being provided a particular privilege, service, mobility,
access, or recognition.
protected object An object that is under DR protection. It can be a
database, VM, or storage LUN.
C
CHAP See Challenge Handshake Authentication Protocol
(CHAP).
storage type Storage resources are classified into different types based
on their attributes. For example, storage resources can be
classified into magnetic medium and solid state disks
(SSDs) in terms of the storage medium, and into common
I/O, high I/O, and ultra-high I/O storage resources in
terms of the I/O level.
D
DHCP See dynamic host configuration protocol (DHCP).
DNS See domain name server (DNS).
domain name A functional entity in the TCP/IP network. With
server (DNS) deployment of the DNS, subscribers can access related
servers using corresponding domain names. In the TCP/IP
network, a domain name maps an IP address. Domain
names are easier to remember but servers in the network
communicate with each other using IP addresses.
Therefore the DNS is used to convert domain names to
corresponding IP addresses.
multipathing A storage access mechanism. The multipathing provides
more than one physical path to access network storage
devices, the capabilities of error tolerance, I/O flow load
balance, I/O scheduling strategy with less granularity, and
high availability and performance for the network storage
system.
dynamic host A client-server networking protocol. A DHCP server
configuration provides configuration parameters specific to the DHCP
protocol (DHCP) client host requesting information the host requires to
participate on the Internet network. DHCP also provides a
mechanism for allocating IP addresses to hosts.
F
FC See Fibre Channel (FC).
G
GE Gigabit Ethernet
alarm A message reported when a fault is detected by a device
or by the network system during the device polling
process. Each alarm corresponds to a clearing alarm. After
a clearing alarm is received, the corresponding alarm is
cleared.
alarm dump A process of transferring the alarms stored in the system
memory to other external devices.
cutover A process of migrating the data of an application system
to another application system, which then provides
services.
root certificate An unsigned public key certificate or a self-signed
certificate that identifies the Root Certificate Authority
(CA). A root certificate is part of a public key
infrastructure scheme.
administrator A user who has authority to access all EMLCore product
management domains. This user has access to the entire
network and all management functions.
fault A failure to operate correctly. A fault does not include
failures caused by preventative maintenance, insufficient
external resources, or intentional settings.
I
I/O Input/Output
ICMP See Internet Control Message Protocol (ICMP).
IP SAN See Internet Protocol Storage Area Network (IP SAN).
J
encryption A function for converting data for the purpose of hiding
information and preventing unauthorized use.
K
clone 1. An independent VM that has the same resource
configuration, operating system, and application system
as the source VM but does not share any resources with
the source VM. It can be used and modified
independently. 2. A snapshot technology. The source data
is completely copied to generate a data duplicate;
therefore the duplicate needs the storage space as the
same size as the source data. In the VIS system, it is also
called third-mirror break-off snapshot.
L
LAN See local area network (LAN).
route A path that network traffic takes from its source to its
destination. Routes can change dynamically.
M
MD5 See message digest algorithm 5 (MD5).
message digest A hash function that is used in a variety of security
algorithm 5 (MD5) applications to check message integrity. MD5 processes a
variable-length message into a fixed-length output of
128 bits. It breaks up an input message into 512-bit
blocks (sixteen 32-bit little-endian integers). After a
series of processing, the output consists of four 32-bit
words, which are then cascaded into a 128-bit hash
number.
N
NFS See network file server (NFS).
network file server A distributed file system that allows remote file access
(NFS) across a network through the NFS protocol.
P
POD See point of delivery (POD).
configuration To set the basic parameters of an operation object.
Config Service A basic service provided by the IT PaaS platform for
providing the application configuration capabilities,
including centralized local configuration file
management and running status configuration
management. It supports the following for applications:
importing configuration models customized in
compliance with the configuration service specifications,
displaying configuration on the portal, changing
configuration, and sending configuration change
notifications.
point of delivery A minimum service unit in a data center, which is a
(POD) resource collection consisting of switches, firewalls, load
balancers, and servers. The resources collaborate to
provide network services or applications.
R
RAM See random access memory (RAM).
RESTful RESTful is a software architecture style rather than a
standard. It provides a set of software design guidelines
and constraints for designing software for interaction
between clients and servers. RESTful software is simpler
and more hierarchical, and facilitates the
implementation of the cache mechanism.
random access Semiconductor-based memory that can be read and
memory (RAM) written by the CPU or other hardware devices. The
storage locations can be accessed in any order.
S
SFTP See Secure File Transfer Protocol (SFTP).
SMTP See Simple Mail Transfer Protocol (SMTP).
SSH See Secure Shell (SSH).
Secure File Transfer A network protocol designed to provide secure file
Protocol (SFTP) transfer over SSH.
Secure Shell (SSH) A standard network protocol that allows users to
establish a secure channel between a local computer
and a remote computer. When a user remotely logs in
to an insecure network, the SSH feature provides secure
information protection and powerful authentication
functions to protect the network against attacks such as
IP address spoofing and simple password interception.
Simple Mail Transfer The TCP/IP protocol which facilitates the transfer of
Protocol (SMTP) electronic-mail messages, specifies how two systems are
to interact, and the format of messages used to control
the transfer of electronic mail.
power on To start up a computer; to begin a cold boot procedure;
to turn on the power
uplink In an access network, the direction that is far from the
subscriber end of the link.
data backup A method of copying key data to the backup storage
area to prevent data loss in case the original storage
area is damaged or a failure occurs.
data restoration A method for retrieving data that is lost due to damage
or misoperations.
digital signature A message signed with a sender's private key that can
be verified by anyone who has access to the sender's
public key. Digital signature gives the receiver the
reason to believe the message was sent by the claimed
sender. A proper implementation of digital signature is
computing a message digest for the message sent from
the sender to the receiver, and then signing the message
digest. The result is called digital signature and is sent
to the receiver together with the original message.
T
TLS Transport Layer Security
V
VBS See Volume Backup Service (VBS).
VNC virtual network controller
Volume Backup Volume Backup Service (VBS) allows a disk to be
Service (VBS) backed up and restored at specific time points. You can
use VBS to roll back a disk to a state when a backup
was created, or create a disk or image and restore data
on it using a backup, thereby preventing data loss.
W
WAN wide area network
network segment Part of a network on which all message traffic is
common to all nodes; that is, a message broadcast
from one node on the segment is received by all other
nodes on the segment.
gateway A device that connects two network segments using
different protocols. It is used to translate and convert
the data in the two network segments using different
protocols.
gateway IP address The IP address of a gateway. A gateway is a node that
forwards packets between networks. Packets are sent
to the gateway IP address when the destination
network address resides in a different network to the
sender.
X
system security policy A security policy for the system administrator to access
the system, including the password policy, login policy,
and session timeout.
power off An operation that switches off devices during upgrade
or expansion.
virtualization Virtualization is a technology that virtualizes a
computer into multiple logic computers. Multiple logic
computers can work on a computer. The operating
systems running on these logic computers can be
different, and the applications running on these
operating systems work independently. Therefore, the
working efficiency of the computer is significantly
improved. Software virtualization redefines IT resources
to implement dynamic allocation, flexible scheduling,
and cross-domain sharing of IT resources. This
improves IT resource usage, enables IT resources to
become social infrastructure, and serves flexible
application requirements in various industries.
virtual machine A VM file image that specifies VM compositions and
image basic configurations and can be used to create a VM. A
VM image contains an operating system, applications,
VM configurations (such as VM operating system,
disks, CPU kernel quantity, and network adapters) for
defining the entire set of virtual hardware, and other
software required for service running.
Y
Ethernet A LAN technology that uses the carrier sense multiple
access with collision detection (CSMA/CD) media
access control method. The speed of an Ethernet
interface can be 10 Mbit/s, 100 Mbit/s, 1000 Mbit/s, or
10000 Mbit/s. The Ethernet network is highly reliable
and easy to maintain.
remote notification A function with which remote maintenance personnel
are informed of alarms through Emails or short
messages.
Z
certificate A certificate, also known as the digital certificate,
associates the user identity information with the public
key. The certificate is issued by a third-party
organization and authenticates the identities of
communication parties.
automatic backup A periodic operation of storing data by the system.
subnet A type of smaller networks that form a larger network
according to a rule, for example, according to different
districts. This facilitates the management of the large
network. In a topology view, these smaller networks
are called subnets.
subnet mask The technique used by the IP protocol to determine
which network segment packets are destined for. The
subnet mask is a binary pattern that is stored in the
device and is matched with the IP address.
B Abbreviation
CA Certificate Authority
FC Fiber Channel
GE Gigabit Ethernet
IE Internet Explorer
IP Internet Protocol
OS Operating System
PC Personal Computer