OceanStor Dorado 6.1.x CloudBackup Feature Guide
OceanStor Dorado 6.1.x CloudBackup Feature Guide
6.1.x
Issue 06
Date 2023-10-31
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
Vulnerability
Huawei's regulations on product vulnerability management are subject to "Vul. Response Process". For
details about the policy, see the following website:https://www.huawei.com/en/psirt/vul-response-process
For enterprise customers who need to obtain vulnerability information, visit:https://
securitybulletin.huawei.com/enterprise/en/security-advisory
Purpose
This document describes the CloudBackup feature supported by the storage
system and provides the configuration and management methods.
The following table lists the product models to which this document is applicable.
NOTICE
This document is updated periodically with the software version. The operations
described in this document use the latest version as an example. Note that the
supported functions and features vary according to the software version. The
content in this document is for reference only.
Intended Audience
This document is intended for:
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Change History
Changes between document issues are cumulative. The latest document issue
contains all the changes made in earlier issues.
Issue 06 (2023-10-31)
This issue is the sixth official release.
Issue 05 (2023-04-20)
This issue is the fifth official release. The updates are as follows:
● Optimized descriptions about some operations.
● Added the support for deploying a CloudBackup containerized application
using DeviceManager.
● Added the support for importing the container image and Helm chart for
CloudBackup using DeviceManager.
Issue 04 (2022-11-15)
This issue is the fourth official release. The updates are as follows:
Optimized descriptions about some operations.
Issue 03 (2022-08-25)
This issue is the third official release.
Issue 02 (2022-04-15)
This issue is the second official release.
Issue 01 (2022-01-25)
This issue is the first official release.
Contents
2 Planning CloudBackup........................................................................................................... 9
3 Configuring CloudBackup....................................................................................................12
3.1 Configuration Process.......................................................................................................................................................... 12
3.2 Deploying CloudBackup on the Storage System........................................................................................................13
3.2.1 Importing the CloudBackup License........................................................................................................................... 13
3.2.2 Activating the Container Service.................................................................................................................................. 14
3.2.3 Configuring Interface Modules..................................................................................................................................... 16
3.2.3.1 Planning Interface Modules....................................................................................................................................... 16
3.2.3.2 Configuring the Front-End Container Mode......................................................................................................... 18
3.2.3.3 Configuring the Back-End Container Mode.......................................................................................................... 20
3.2.4 Configuring a Network Plane........................................................................................................................................23
3.2.4.1 Creating a Network Plane........................................................................................................................................... 23
3.2.4.1.1 Method 1: Using DeviceManager..........................................................................................................................23
3.2.4.1.2 Method 2: Using the CLI.......................................................................................................................................... 27
3.2.4.2 (Optional) Managing Routes..................................................................................................................................... 32
3.2.5 (Optional) Configuring DNS.......................................................................................................................................... 34
3.2.6 Importing the Container Image and Helm Chart for CloudBackup.................................................................35
3.2.6.1 Method 1: Using DeviceManager (Applicable to 6.1.6 and Later Versions)..............................................35
3.2.6.2 Method 2: Using the CLI.............................................................................................................................................. 36
3.2.7 Deploying the CloudBackup Containerized Application...................................................................................... 40
3.2.7.1 Method 1: Using DeviceManager (Applicable to 6.1.6 and Later Versions)..............................................40
3.2.7.2 Method 2: Using the CLI.............................................................................................................................................. 45
3.3 Establishing the Connection Between CloudBackup and the Backup Storage................................................50
4 Managing CloudBackup.......................................................................................................69
4.1 Managing the Local Storage............................................................................................................................................. 69
4.1.1 Viewing Local Storage Information.............................................................................................................................69
4.1.2 Configuring the Capacity Alarm Threshold of the Local Storage..................................................................... 70
4.1.3 Viewing Local Storage Authentication Information.............................................................................................. 71
4.1.4 Modifying Local Storage Authentication Information.......................................................................................... 71
4.2 Managing the Backup Storage......................................................................................................................................... 72
4.2.1 Viewing Backup Storage Information.........................................................................................................................72
4.2.2 Modifying the AK/SK of a Backup Storage...............................................................................................................74
4.2.3 Modifying the Capacity Alarm Threshold of a Backup Storage........................................................................ 75
4.2.4 Importing a Backup Storage Copy...............................................................................................................................75
4.2.5 Deleting a Backup Storage.............................................................................................................................................76
4.3 Managing SLAs...................................................................................................................................................................... 76
4.3.1 Viewing an SLA.................................................................................................................................................................. 76
4.3.2 Cloning an SLA................................................................................................................................................................... 77
4.3.3 Modifying an SLA.............................................................................................................................................................. 77
4.3.4 Deleting an SLA................................................................................................................................................................. 77
4.4 Managing File System Resources.................................................................................................................................... 78
4.4.1 Viewing File System Information................................................................................................................................. 78
4.4.2 Managing Protection Plans for File Systems........................................................................................................... 79
4.5 Managing Backup Copies................................................................................................................................................... 81
4.5.1 Viewing Backup Copies....................................................................................................................................................81
4.5.2 Modifying Copy Retention Policies.............................................................................................................................. 83
4.5.3 Deleting Copies.................................................................................................................................................................. 84
4.6 More Management Operations....................................................................................................................................... 84
C Glossary................................................................................................................................... 95
D Acronyms and Abbreviations........................................................................................... 111
1 Feature Description
1.1 Overview
This section describes the background, definition, and benefits of CloudBackup.
Background
Data backup is crucial in protecting data from losses or corruption caused by
human factors or physical faults in storage systems.
Definition
CloudBackup is a data protection technique deployed in storage system
containers. It backs up file system data from a storage system to the object
storage either in an on-premises data center or on the cloud, without the need for
extra backup servers.
In the event of data loss or corruption in the file system, CloudBackup can use the
backup copies to restore the data to the state at the specified point in time.
NAS backup of file CloudBackup scans for storage file systems and displays
systems them on the ProtectManager resource management
page. You can add protection measures for a file system
to back up its data.
The system uses file system snapshots to back up data
to the cloud through NAS sharing.
Periodic incremental A full backup is performed for the first backup, and
backup incremental backups are performed periodically to
improve backup efficiency. This applies to scenarios
where the backup bandwidth and backup storage
capacity are limited.
Periodic synthetic full You can set a synthesis full cycle in the periodic backup
backup policy to avoid long dependency paths for incremental
backups.
License Requirements
CloudBackup requires a license.
NOTE
To obtain a license, contact your local Huawei representative office or Huawei authorized
distributor.
Specifications
For the specifications of CloudBackup, refer to the Specifications Query (https://
info.support.huawei.com/storage/spec/#/home).
1.3.1 Backup
Basic Concepts
Full backup Backs up all data in the file system. By default, the first backup is
a full backup.
Full backup takes a long time and occupies a large space.
Backup Process
Figure 1-1 shows the data backup process with CloudBackup.
Storage system
Data backup to
FS 1 FS 2
the cloud
CloudBackup
Read-only Read-only
snapshot snapshot
...
Bucket
OceanStor Pacific/FusionStorage OBS
1.3.2 Recovery
In the event of data loss or corruption in the file system, you can select a backup
copy at a specified point in time to recover the data.
Recovery Process
Figure 1-2 shows the data recovery process with CloudBackup.
Storage system
FS 1 FS 2 Recovery
CloudBackup
Recovery
...
Bucket
OceanStor Pacific/FusionStorage
OBS
1. Select the local file system you want to recover and query the backup copies.
2. Select the backup copy you want to use for recovery. The backup copy can be
on the public cloud or in the object storage of the on-premises data center,
depending on how the backup system is deployed.
3. Determine whether to recover the entire file system using the selected copy
or recover specific files.
4. Determine whether to recover data to the original file system or a new file
system.
5. The system performs the recovery.
During recovery, CloudBackup reads data from the specified backup copy in
the object storage and writes the data to the share of the target file system.
NOTICE
During recovery, ensure that the target file system is not read or written by
any host service or other value-added features.
Application Restrictions
● CloudBackup supports backup and recovery of file systems but not LUNs.
● CloudBackup does not support backup and recovery of file systems with
HyperClone and HyperLock (WORM) configured.
● In the case of a split brain of HyperMetro, the file system at the losing side of
arbitration does not support backup and recovery with CloudBackup.
● The secondary file system of HyperMetro does not support backup and
recovery with CloudBackup.
● Recovery to the secondary file system of asynchronous remote replication is
not supported.
● When backing up data to the cloud, you can use only one of the IPv4 and
IPv6 networks.
● If the protected file system of CloudBackup is also the secondary file system
of remote replication, it is recommended that you set different time windows
for CloudBackup and remote replication. In addition, after the remote
replication synchronization is complete, the wait time must be greater than or
equal to 3 minutes. Otherwise, the backup task may fail.
On-premises DC
Storage system
FS 1 FS 2
CloudBackup
Read-only Read-only
snapshot snapshot
OceanStor Pacific/FusionStorage
OBS
Remote Backup
File system data of the storage system is backed up to the cloud storage of the
remote cloud data center. You do not need to purchase storage hardware,
reducing maintenance and procurement costs.
Storage system
FS 1 FS 2 Data backup
to the cloud
CloudBackup
......
Bucket
Storage system
Recovery
CloudBackup
FS 1 FS 2
Copy
Recovery
...
Bucket
OceanStor Pacific/FusionStorage OBS
2 Planning CloudBackup
Storage system
Recovery
Controller
enclosure 1
WAN
Switch Router
...
Controller
enclosure 2
Bucket
OceanStor Pacific/FusionStorage OBS
NOTE
If the CloudBackup containerized application has been deployed and you want to
deploy another feature (for example, FTP), you must change the license file from
CloudBackup to the desired feature (for example, FTP) and reactivate the container
service. After the container service is reactivated, the containerized application images,
Helm charts, and application data of CloudBackup are cleared by the storage system.
● The system resources (CPU and memory size) vary with product models. For
details, refer to Specifications Query (https://info.support.huawei.com/
storage/spec/#/home).
1. Capacity of the file system to be backed up. Assume that one file system
needs backup and its capacity is b.
2. Estimated data change amount between two incremental backups. Assume
that the amount is c.
3. Backup scheduling policy. Determine the frequency of incremental and
synthetic full backups. For example, incremental backup is performed every x
days, and synthetic full backup is performed after every y incremental
backups.
4. Backup retention policy, for example, z days.
5. Number of full copies (n) = z/[x * (y + 1)].
After m days (assume that m is greater than z), the required backup storage
capacity can be calculated as follows: Required backup storage capacity = [(Size of
the first full copy + Size of the last full copy)]/2 * Number of full copies + Size of
an incremental copy * Number of incremental copies = [b + c(m - n) + b + cm]/2 *
n + c * ny
Example:
Assume that the file system capacity is 10 GB (b = 10 GB); the data change
amount between two incremental backups is 2 GB (c = 2 GB); the backup policy is
once a day (x = 1); a synthetic full backup is performed after every five
incremental backups (y = 5); and the retention period of backup copies is 30 days
(z = 30). Then number of full copies (n) = z/[x * (y + 1)] = 30/[1 * (5 + 1)] = 5.
After 60 days (m = 60), the required backup storage capacity = [b + c(m - n) + b +
cm]/2 * n + c * ny = [10 + 2 * (60 - 5) + 10 + 2 * 60]/2 * 5 + 2 * 5 * 5 = 675 GB.
NOTE
1. The backup storage capacity plan may not be accurate. You are advised to plan
redundancy space (usually 20%) for the backup storage capacity.
2. If capacity expansion is considered at the production site, evaluate the capacity
expansion rate of the production site during backup planning and include the expanded
capacity in the preceding formula.
For example, if a backup plan is effective for one year and the production site capacity
is expanded by 20% within a year, the backup storage capacity should also be increased
by 20%.
3 Configuring CloudBackup
This chapter describes how to use CloudBackup to back up file system data.
3.1 Configuration Process
3.2 Deploying CloudBackup on the Storage System
3.3 Establishing the Connection Between CloudBackup and the Backup Storage
3.4 Configuring CloudBackup Protection
3.5 Recovering Backup Data
Log in to ProtectManager.
Import the container image
and Helm chart for
Authenticate the local storage CloudBackup.
system.
Establish the connection between
CloudBackup and the backup storage. Deploy the CloudBackup
(Optional) Import a CA
containerized application.
certificate.
End
Prerequisites
You have obtained the CloudBackup license.
Procedure
Step 1 Log in to DeviceManager.
NOTE
For details on how to log in to DeviceManager, see the Initialization Guide specific to your
product version.
1. Click .
2. Select the desired license file and click Open.
The button displayed in the dialog box varies with the browser.
3. Click Upload.
Step 5 In the middle function pane, check the differences between active and inactive
license files.
Step 6 Click Activate.
Confirm your operation as prompted.
----End
Follow-up Procedure
After importing the license, choose Settings > License Management. In the
middle function pane, verify that the Feature column includes CloudBackup.
Prerequisites
The CloudBackup license has been imported to the system.
Context
● If the storage system does not have the container service license before the
CloudBackup license is imported, you can use either of the following methods
to activate the container service:
– Using DeviceManager: See Procedure.
– Using the CLI: Run the change container_service active enabled=?
password=? command to activate the container service. For details, visit
Command/Event/Error Code Query.
● For details about how to reactivate the container service, see "Reactivating
the Container Service" in the Container User Guide specific to your product
model and version.
● After the CloudBackup license is imported and the container service is
activated, the system reserves fixed system resources (16 CPU cores and 32
GB memory per controller) for CloudBackup. For details, see Planning
Containerized Applications.
● You are advised to learn concepts related to the container service by referring
to Concepts Related to the Container Service.
● If more than two controller enclosures are configured with the container
service, contact Huawei technical support engineers to enable the container
function for multiple controller enclosures before activating the container
service.
Procedure
Step 1 Log in to DeviceManager as the super administrator.
Step 2 Before activating the container service, check whether the storage system
environment meets the requirements for activating the container service.
1. On the home page, view the storage system information. Ensure that the
overall running status of the storage system is normal and the capacity is
sufficient.
If a device is in the Faulty state, contact Huawei technical support to locate
and rectify the fault. After the device status becomes normal, activate the
container service.
2. In the Alarms area on the home page, check alarm information.
Click More. On the displayed Alarms and Events page, you can query
information about all alarms and events.
Clear all alarms and events by referring to suggestions. After all alarms and
events are handled, activate the container service.
Step 3 On the navigation bar, choose Settings > Container Settings.
Step 4 Activate the container service.
1. When you access the container setting page for the first time, you need to
enable Container Service. Read the description carefully and enter the login
password of the current user.
2. Select I have read and understood the consequences associated with
performing this operation.
3. Click OK to create an activation task.
NOTE
– If the kernel version is 1.1.6.0 or earlier, during the container service activation, all
controllers are restarted in batches, and the read and write performance may
deteriorate.
– If the kernel version is 1.1.7.0 or later, controllers will not be restarted in batches
during the container service activation. However, the read and write performance
may deteriorate, and the configuration may time out during the activation.
– After the container service is activated, IP addresses in the 172.16.x.x network
segment will be used for container management by default. As a result, services
that use the 172.16.x.x network segment, such as the NTP service, will become
invalid. Ensure that this network segment is not used by services.
– If allocating container resources fails and the failure cause is "the kernel version of
the current system does not support container service activation", run the create
upgrade session session=kernel configuration_data_path=? license_path=? ip=?
user=? command in developer mode to upgrade the kernel to the latest version.
For details about the command, visit Command/Event/Error Code Query. After
switching to the latest kernel version, activate the container service again.
– You can select the same storage pool for the image storage pool and application
storage pool.
– You can select multiple storage pools as application storage pools.
----End
Application Restrictions
● In 6.1.6 and earlier versions, after an interface module is set to the front-end
container mode or back-end container mode, it is exclusively occupied by the
container service and cannot serve for basic services.
● In 6.1.7 and later versions, after an interface module is set to the back-end
container mode, it is exclusively occupied by the container service and cannot
serve for basic services.
● The container service must be enabled first. Each controller that supports the
container service must have at least one idle interface module configured to
the front-end container mode and only one idle interface module configured
to the back-end container mode. The requirements of the interface modules
are as follows:
A
B
A C
B D
3.2.3.2 Configuring the Front-End Container Mode
To use the container service, you must configure the proper idle interface module
to be in the front-end container mode so that the created applications can provide
services for external systems.
Prerequisites
● The CloudBackup license has been imported.
● The container service has been activated.
Precautions
● The slots of the interface modules that can be configured to be in the front-
end container mode are the same as those supported by the front-end
interface modules of the corresponding product models. For details about
front-end interface modules, see "Interface Module" in the Product
Description specific to your product model.
NOTE
A front-end interface module connects a controller enclosure to the service side and
transmits service data.
● An administrator who has the interface_module read and write permissions
can configure interface modules to be in the front-end container mode, for
example, the built-in super administrator and administrator of the system.
● Before performing this operation, ensure that all services on the interface
module have been stopped.
● In 6.1.6 and earlier versions, after an interface module is configured to work
in front-end container mode, the interface module can only be used for
network communication of container front-end services and does not serve
for basic services of the storage system.
● 10GE electrical interface modules and SmartIO interface modules (with the
rate of 10 Gbit/s or 25 Gbit/s) can be configured to the front-end container
mode.
● Interface modules that work in front-end container mode do not support hot
swap. Before you replace, remove, or insert an interface module, power off
the interface module. For details, see section "Powering off an Interface
Module" in the Administrator Guide specific to your product model and
version.
Procedure
Step 1 Log in to DeviceManager as the super administrator.
Step 2 Choose Settings > Container Settings.
Step 3 In the Node Information area, click the number in the Container Front-End
Modules column.
The Container Front-End Module Details dialog box is displayed.
Step 6 Confirm the information in the dialog box, select I have read and understand the
consequences associated with performing this operation, and then click OK.
The interface module is configured to the front-end container mode.
----End
Prerequisites
● The CloudBackup license has been imported.
● The container service has been activated.
Precautions
● The slots of the interface modules that can be configured to be in the back-
end container mode are the same as those supported by the front-end
interface modules of the corresponding product models. For details about
A front-end interface module connects a controller enclosure to the service side and
transmits service data.
● An administrator who has the interface_module read and write permissions
can configure interface modules to be in the back-end container mode, for
example, the built-in super administrator and administrator of the system.
● Before performing this operation, ensure that all services on the interface
module have been stopped.
● After an interface module is configured to work in back-end container mode,
the interface module can only be used for network communication of
container back-end services and does not serve for basic services of the
storage system.
● 25 Gbit/s RoCE interface modules can be configured to the back-end
container mode.
● Interface modules that work in back-end container mode do not support hot
swap. Before you replace, remove, or insert an interface module, power off
the interface module. For details, see section "Powering off an Interface
Module" in the Administrator Guide specific to your product model and
version.
● During network planning, ensure that the logical port IP addresses of the
storage system and the front-end and back-end service IP addresses of the
container do not conflict with each other:
– Logical port IP addresses of the storage system cannot be used for front-
end container services.
– Front-end service IP addresses of the container cannot be used as logical
port IP addresses.
– Back-end service IP addresses of the container: When a pod is created,
the system randomly allocates IP addresses in the 172.16.x.x to 172.24.x.x
network segment for communication between the container and storage
system. The number of IP addresses increases with the specifications and
number of pods configured by the user.
NOTE
● If a conflict occurs when you configure the logical port IP addresses of the
storage system or front-end and back-end service IP addresses of the
container, the 0x40000613 alarm is reported. In this case, solve the issue
based on the preceding configuration requirements.
● If you need to change the default network segment of the container back-end
service, contact Huawei engineers for evaluation and modification.
Procedure
Step 1 Log in to DeviceManager as the super administrator.
Step 2 Choose Settings > Container Settings.
Step 3 In the Node Information area, click the number in the Container Back-End
Modules column.
Step 6 Confirm the information in the dialog box, select I have read and understand the
consequences associated with performing this operation, and then click OK.
The interface module is configured to the back-end container mode.
----End
Prerequisites
● The CloudBackup license has been imported.
● The container service has been activated.
● Interface modules have been configured for the container service.
Context
A network plane is a type of user-defined resources of a cluster. It provides
configuration items, such as the subnet, port, VLAN, and route, for the front-end
service network of a container.
Precautions
During network planning, ensure that the logical port IP addresses of the storage
system and the front-end and back-end service IP addresses of the container do
not conflict with each other:
● Logical port IP addresses of the storage system cannot be used for front-end
container services.
● Front-end service IP addresses of the container cannot be used as logical port
IP addresses.
● Back-end service IP addresses of the container: When a pod is created, the
system randomly allocates IP addresses in the 172.16.x.x to 172.24.x.x network
segment for communication between the container and storage system. The
number of IP addresses increases with the specifications and number of pods
configured by the user.
NOTE
● If a conflict occurs when you configure the logical port IP addresses of the storage
system or front-end and back-end service IP addresses of the container, the
0x40000613 alarm is reported. In this case, solve the issue based on the preceding
configuration requirements.
● If you need to change the default network segment of the container back-end
service, contact Huawei engineers for evaluation and modification.
Communication Mode
The container service of Huawei storage system implements a high-performance
container network based on interface modules. Single Root Input/Output
Virtualization (SR-IOV) allows an interface module to provide multiple virtual
functions (VFs). The Container Network Interface (CNI) plug-in is implemented
based on the VF. When a container is created, the CNI allocates a VF and directly
connects the VF to the container to provide a high-performance network.
Container
1 APP
APP
Service LUN LUN LUN
2
Kernel
Container
eth0
Storage resources
service 2
3
4 1
1. The interface module that works in the back-end container mode allocates
VFs to communicate with containerized applications.
2. The interface module that works in the back-end container mode allocates
VFs to communicate with storage resources of the storage system.
Procedure
Step 1 Log in to DeviceManager as the super administrator.
Step 2 Choose System > Container Service > Network Planes.
Step 3 Click Create.
The Create Network Plane page is displayed on the right.
Step 4 Set network plane parameters. Table 3-1 describes the parameters.
IP Address IP address type of the network plane. Possible values are IPv4
Type and IPv6.
Parameter Description
NOTE
VLAN, MTU (Bytes), Maximum Pods per Node, and IP Address Failover are hidden
options. You can click Advanced to display them.
Step 5 In Available Ports, select the desired ports. It is recommended that you select two
ports on each controller.
NOTICE
Ports added to the network plane must be connected to the object storage
network.
----End
Prerequisites
● The CloudBackup license has been imported.
● The container service has been activated.
● Interface modules have been configured for the container service.
Context
A network plane is a type of user-defined resources of a cluster. It provides
configuration items, such as the subnet, port, VLAN, and route, for the front-end
service network of a container.
Precautions
During network planning, ensure that the logical port IP addresses of the storage
system and the front-end and back-end service IP addresses of the container do
not conflict with each other:
● Logical port IP addresses of the storage system cannot be used for front-end
container services.
● Front-end service IP addresses of the container cannot be used as logical port
IP addresses.
● Back-end service IP addresses of the container: When a pod is created, the
system randomly allocates IP addresses in the 172.16.x.x to 172.24.x.x network
segment for communication between the container and storage system. The
number of IP addresses increases with the specifications and number of pods
configured by the user.
NOTE
● If a conflict occurs when you configure the logical port IP addresses of the storage
system or front-end and back-end service IP addresses of the container, the
0x40000613 alarm is reported. In this case, solve the issue based on the preceding
configuration requirements.
● If you need to change the default network segment of the container back-end
service, contact Huawei engineers for evaluation and modification.
Communication Mode
The container service of Huawei storage system implements a high-performance
container network based on interface modules. Single Root Input/Output
Virtualization (SR-IOV) allows an interface module to provide multiple virtual
functions (VFs). The Container Network Interface (CNI) plug-in is implemented
based on the VF. When a container is created, the CNI allocates a VF and directly
connects the VF to the container to provide a high-performance network.
Container
1 APP
APP
Service LUN LUN LUN
2
Kernel
Container
eth0
Storage resources
service 2
3
4 1
Procedure
Step 1 Log in to the CLI as an administrator or a super administrator.
Step 2 Create a network plane by running the following command:
create net_plane name=? [ vlanid=? ] [ mtu=? ] [ ipv4_subset_base=? ]
[ mask=? ] [ ipv4_subset_range=? ] [ ipv4_gateway=? ] [ ipv6_subset_base=? ]
[ prefix_length=? ] [ ipv6_subset_range=? ] [ ipv6_gateway=? ]
[ max_pods_per_node=? ] [ failover_enabled=? ]
Example:
admin:/>create net_plane name=backupNetPlane vlanid=1 ipv4_subset_base=192.168.128.0
mask=255.255.255.0 ipv4_subset_range=192.168.128.1-192.168.128.100 ipv4_gateway=192.168.128.110
max_pods_per_node=3 failover_enabled=yes
Command executed successfully.
Parameter Description
Parameter Description
ID Health Status Running Status Type IPv4 Address IPv6 Address MAC Role
Working Rate(Mbps)
-------------- ------------- -------------- ---- ------------ ------------ ----------------- ---- ------------------
CTE0.A.IOM1.P0 Normal Link Up -- -- -- 3a:72:c2:00:40:73 --
25000
CTE0.A.IOM1.P1 Normal Link Up -- -- -- 3a:72:c2:00:4a:fb --
25000
CTE0.B.IOM1.P0 Normal Link Up -- -- -- 3a:72:c2:00:3f:30 --
25000
CTE0.B.IOM1.P1 Normal Link Up -- -- -- 3a:72:c2:00:d7:1e -- 25000
----End
Procedure
Step 1 Choose System > Container Service > Network Planes.
Step 2 Select the network plane for which you want to manage routes and click Manage
Route.
NOTE
Alternatively, perform either of the following operations to go to the Manage Route page:
● Click More on the right of a desired network plane and select Manage Route.
● Click the name of the desired network plane. In the upper right corner of the page that
is displayed, select Manage Route from the Operation drop-down list.
Paramete Description
r
----End
Prerequisites
● A DNS server has been configured and is running properly.
● Port 53 for the TCP/UDP protocol between the storage system and the DNS
server is enabled.
● The latency of the network between the DNS server and the storage system is
less than or equal to the configured latency (200 ms by default).
Context
● A DNS server is used to resolve names of hosts in a domain.
● If you want to configure a standby DNS server, keep the domain names of the
active and standby servers consistent.
Procedure
Step 1 On DeviceManager, choose Settings > Basic Information > DNS Service.
Step 2 Click Modify in the upper right corner of the Management DNS area to configure
the DNS service for the management plane.
1. Set Active DNS IP Address.
2. (Optional) Set Standby DNS IP Address 1.
3. (Optional) Set Standby DNS IP Address 2.
NOTE
Set Standby DNS IP Address 1 first and then Standby DNS IP Address 2.
4. (Optional) Test the connectivity between the DNS server and the storage
system.
– You can click Test next to a DNS IP address to test its availability.
– You can click Test All to test the connectivity between the DNS server
and storage system.
5. Click Save.
----End
Follow-up Procedure
If you want to modify the DNS IP address, save the modification and run the
change container_application general name=dataprotect command on the CLI
to restart the CloudBackup service for the configuration to take effect. It takes
about 10 minutes to restart the CloudBackup service.
Prerequisites
● Before importing the container image and Helm chart, ensure that the
container service has been enabled.
● You have used the digital signature validation tool (PGP Verify) to verify the
integrity of the container image and Helm chart. If the verification fails,
obtain the container image and Helm chart again.
Context
● Container image: The container image is a template in standard format for
packaging containerized applications and is used to create iSulad containers.
● Helm chart: The chart is a packaging format used by Helm. It is a collection of
files that describe a group of Kubernetes resources.
Precautions
Only application images and charts that have passed Huawei digital signature
authentication can be imported. You can download the CloudBackup application
images and charts provided by Huawei in the following ways:
1. Log in to Huawei technical support website (https://support.huawei.com/
enterprise/en/index.html), enter the product model of the storage system in
the search box, and select the suggested path to the Documentation page of
the product model.
2. Select Release Documents on the left tree and download the version
mapping table of the current storage version.
3. Open the version mapping table and find the OceanProtect X8000 software
version that matches the current storage system version.
4. Go to the software download page and select the software version queried
in 3.
NOTE
If the queried software version has a patch version, obtain the container image and
Helm chart from the patch version.
5. Download the software packages named in the
XXX_Version_image_ARM_64.tgz and XXX_Version_chart_ARM_64.tgz
formats, which are the container image package and Helm chart package.
Procedure
Step 1 Log in to DeviceManager as the super administrator.
----End
Prerequisites
● Before importing the container image and Helm chart, ensure that the
container service has been enabled.
● You have used the digital signature validation tool (PGP Verify) to verify the
integrity of the container image and Helm chart. If the verification fails,
obtain the container image and Helm chart again.
Context
● Container image: The container image is a template in standard format for
packaging containerized applications and is used to create iSulad containers.
● Helm chart: The chart is a packaging format used by Helm. It is a collection of
files that describe a group of Kubernetes resources.
Precautions
Only application images and charts that have passed Huawei digital signature
authentication can be imported. You can download the CloudBackup application
images and charts provided by Huawei in the following ways:
1. Log in to Huawei technical support website (https://support.huawei.com/
enterprise/en/index.html), enter the product model of the storage system in
the search box, and select the suggested path to the Documentation page of
the product model.
2. Select Release Documents on the left tree and download the version
mapping table of the current storage version.
3. Open the version mapping table and find the OceanProtect X8000 software
version that matches the current storage system version.
4. Go to the software download page and select the software version queried in
3.
– For OceanStor Dorado 6.1.5 and earlier versions, go to the software
download page.
– For OceanStor Dorado 6.1.6 and later versions, go to the software
download page.
NOTE
If the queried software version has a patch version, obtain the container image and
Helm chart from the patch version.
5. Download the software packages named in the
XXX_Version_image_ARM_64.tgz and XXX_Version_chart_ARM_64.tgz
formats, which are the container image package and Helm chart package.
Procedure
Step 1 Log in to the CLI as an administrator or a super administrator.
Step 2 Import the container image by running the following command:
import container_image ip=? user=? password=? path=? [ port=? ] [ protocol=? ]
Example:
import container_image ip=192.168.1.1 user=admin password=******
path=OceanProtect_DataProtect_1.3.RC1_image_ARM_64.tgz
NOTE
● Ensure that the container image has been obtained and uploaded to the FTP or SFTP
server that can communicate with the management network port of the storage system.
● If the size of the container image exceeds 4 GB, you are advised to use FileZilla Server
to create a local FTP share to import the container image. For details about how to use
FileZilla Server to create a local FTP share, see "How Do I Create a Local FTP Share?" in
the Container User Guide.
Parameter Description
NOTE
Ensure that the Helm chart has been obtained and uploaded to the FTP or SFTP server that
can communicate with the storage system.
Parameter Description
----End
Prerequisites
● Before creating an application, ensure that the container image and Helm
chart have been imported to the storage system.
● Before creating an application, ensure that the container service has been
enabled.
Context
● Container image: The container image is a template in standard format for
packaging containerized applications and is used to create iSulad containers.
● Helm chart: The chart is a packaging format used by Helm. It is a collection of
files that describe a group of Kubernetes resources.
● When you deploy an application, the storage system automatically creates a
file system whose name starts with pvc_ to ensure the normal running of the
application.
Procedure
Step 1 Log in to DeviceManager as the super administrator.
Step 2 Choose System > Container Service > Applications.
Step 3 Click Deploy.
The Deploy Application page is displayed on the right.
Step 4 Set the parameters for deploying the CloudBackup containerized application.
Table 3-7 describes the parameters.
Parameter Description
Network Plane ID ID of the network plane. That is, the ID of the selected
network plane.
Parameter Description
----End
Prerequisites
● Before creating an application, ensure that the container image and Helm
chart have been imported to the storage system.
● Before creating an application, ensure that the container service has been
enabled.
Context
● Container image: The container image is a template in standard format for
packaging containerized applications and is used to create iSulad containers.
● Helm chart: The chart is a packaging format used by Helm. It is a collection of
files that describe a group of Kubernetes resources.
● When you deploy an application, the storage system automatically creates a
file system whose name starts with pvc_ to ensure the normal running of the
application.
Procedure
Step 1 Log in to the CLI as an administrator or a super administrator.
Step 2 Deploy an application and configure parameters such as the namespace and
storage resources for the application by running the following command:
create container_application general app=? version=? namespace=? name=?
dynamic_config=? net_plane_name=? description=?
Example:
create container_application general app=DataBackup version=1.X.X namespace=dpa name=dataprotect
dynamic_config="global.backupNetPlane=1,wait=true,timeout=1800,global.replicas=2,global.deploy_type=d3,
global.gaussdbpwd=R2F1c3NkYl8xMjM="
Parameter Description
Parameter Description
----End
Follow-up Procedure
● After deploying a CloudBackup containerized application:
In versions earlier than 6.1.5, run the show container_application general
name=? command to query the application details.
In 6.1.5 and later versions, run the show container_application general
name=? namespace=? command to query the application details.
NOTE
Name : dataprotect
Namespace : dpa
Revision : 1.X.X
Updated : 2023-03-07 22:30:33
Status : deployed
Chart Name : databackup
Description : databackup Software
Application Subscribe Capacity :
2.537TB
Application Image Name List : om:1.X.X,elasticsearch:1.X.X,kafka:1.X.X,pm-database-version-
migration:1.X.X
,pm-system-
base:1.X.X,dee_initcontainer:1.X.X,dee_global_search:1.X.X,dma_nginx:1.
X.X,dme_dns:1.X.X,pm-nginx:1.X.X,zookeeper:1.X.X,dee_nginx:1.X.X,pm-re
source-lock-manager:1.X.X,dee_indexer:1.X.X,dme_initcontainer:1.X.X,pm-
gui:1.X.X
,gaussdb:1.X.X,redis:1.X.X,dme_archive:1.X.X,dme_nginx:1.X.X,dee_db_anon
ymization:1.X.X,pm-protection-service:1.X.X
Net Plane List : backupNetPlane
PodList:
Pod Name Pod Status Pod Restart Times Pod Cpu Percent(%) Pod Memory
Percent(%) Pod Belong Node Pod Namespace Pod Is Ready
---------------------------- ---------- ----------------- ------------------ ---------------------
--------------- ------------- ------------
gaussdb-0 Running 0 14.29 4.82 node-0
dpa true
infrastructure-0 Running 0 -- -- node-0
dpa true
dataenableengine-server-1 Running 0 14.29 3.22
node-1 dpa true
dataenableengine-server-0 Running 0 14.29 3.22
node-0 dpa true
protectengine-e-dma-0 Running 0 1.43 0.63 node-0
dpa true
protectengine-1 Running 0 -- -- node-1
dpa true
protectengine-0 Running 0 -- -- node-0
dpa true
protectmanager-biz-service-1 Running 0 15.71 10.45
node-1 dpa true
protectmanager-biz-service-0 Running 0 15.71 10.45
node-0 dpa true
protectmanager-system-base-1 Running 0 15.00 7.55
node-0 dpa true
protectmanager-system-base-0 Running 0 15.00 7.55
node-1 dpa true
Dynamic Config :
Node Name Node Status Node Role Node Cpu Percent(%) Node Memory Percent(%)
--------- ----------- --------- ------------------- ----------------------
node-0 Ready master 6.49 27.21
node-1 Ready master 4.97 21.77
Prerequisites
The CloudBackup containerized application has been deployed on the storage
system.
Context
● ProtectManager is a management platform for data protection services. It
integrates the backup storage, SLA, and protection policies of CloudBackup.
● After the CloudBackup containerized application has been deployed on the
storage system, you can choose Data Protection > CloudBackup on
DeviceManager to navigate to the ProtectManager login page.
Procedure
Step 1 Log in to DeviceManager.
Step 2 Choose Data Protection > CloudBackup.
The ProtectManager login page is displayed.
NOTE
On the ProtectManager login page, the format of the address in the browser address box is
https://XXX.XXX.XXX.XXX:25080. XXX.XXX.XXX.XXX represents the management IP address
of the controller.
Step 3 Enter the user name sysadmin and password of ProtectManager to log in.
NOTE
For details about the user name and password, see the OceanStor Dorado Account List.
----End
For details about the user name and password, see the OceanStor Dorado Account List.
----End
Procedure
Step 1 On ProtectManager, choose System > Infrastructure > Local Storage.
The Local Storage page is displayed.
Step 2 Modify login authentication and service authentication.
1. Modify login authentication.
a. In the Authentication Information area, click Modify Login
Authentication.
b. Enter the user name and password of the super administrator of the
storage system, and click Save.
2. Modify service authentication.
a. In the Authentication Information area, click Modify Service
Authentication.
b. Enter the user name and password of the super administrator of the
storage system, and click Save.
NOTE
For details about the user name and password, see the OceanStor Dorado Account List.
----End
Procedure
Step 1 On ProtectManager, choose System > Security > Certificates.
Step 2 Click Add External Certificate.
The Add External Certificate page is displayed.
Parameter Description
Parameter Description
----End
Prerequisites
● You have prepared the object storage platform for storing backup data.
● You have obtained the endpoint, AK, and SK of the object storage.
● You have created a data bucket for storing backup data on the object storage
platform.
● Versioning has been disabled for the data bucket of the object storage.
Procedure
Step 1 On ProtectManager, choose System > Infrastructure > Backup Storage.
Step 2 Click Add Backup Storage.
The Add Backup Storage page is displayed on the right.
Parameter Description
Parameter Description
Use Proxy Server Determines whether to use a proxy for accessing the S3
storage.
NOTE
● Obtain the proxy information from the network administrator of
the enterprise data center.
● If Use Proxy Server is enabled, the Address, Username, and
Password parameters are displayed.
Alarm Threshold Alarm threshold for the backup storage capacity. When the
percentage of the used capacity to the total capacity of the
backup storage reaches the alarm threshold, an alarm is
generated, prompting you to expand the capacity or delete
unnecessary backup data to release storage space.
Otherwise, subsequent backup tasks may fail.
----End
Context
● In CloudBackup, a service level agreement (SLA) is a backup plan template to
meet various backup requirements.
● Multiple backup policies can be created, but each backup storage can be
associated with only one backup policy.
Procedure
Step 1 On ProtectManager, choose Protection > Protection Policies > SLAs.
Step 4 In the Configuration SLA area, click the icon for Step 1 Applications.
The Select Application page is displayed.
1. Select Local File System.
2. Click OK.
Step 5 In the Configuration SLA area, click Step 2 Backup Policy.
The Backup Policy page is displayed.
Step 6 Set basic backup policy parameters.
1. Specify an incremental backup plan. The default is Incremental 01
(Incremental). To add a plan, click Add Policy.
2. Specify the backup storage for the incremental backup plan.
3. Set incremental backup parameters.
NOTE
Set a proper backup interval, retention period, and backup window based on service
requirements. The recommended settings are as follows:
– If the protected file system in CloudBackup is also the secondary file system of
remote replication, it is recommended that you set different time windows for
CloudBackup and remote replication. Otherwise, the backup task may fail.
– The backup interval must be longer than the backup duration.
– It is recommended that the time of the initial backup should be the same as the
start time of the backup time window.
– The retention period must be longer than the backup interval.
▪ Configure the backup frequency and copy retention period for full
backup.
○ By Year
Configure the job to be executed once every year on XX (month)
XX (day), and copies are retained for XX days, weeks, months,
years, or permanently.
If the date does not exist in the year, no copy is generated.
○ By Month
Configure the job to be executed on xx (day) (multiple days can
be selected) or the last day of each month. Configure copies to
be retained for xx days, weeks, months, years, or permanently.
If the backup job is set to be executed once on the xxth day of
each month, no copy is generated when the date does not exist
in the current month.
○ By Week
Configure the job to be executed every Monday, Tuesday,
Wednesday, Thursday, Friday, Saturday, or Sunday (you can
select multiple options). Configure copies to be retained for xx
days, weeks, months, years, or permanently.
○ By day
Configure the job to be executed every xx days starting from xx
(year) xx (month) xx (day). Configure copies to be retained for
xx days, weeks, months, years, or permanently.
○ By Hour
Configure the job to be executed every xx hours starting from xx
(year) xx (month) xx (day). Configure copies to be retained for
xx days, weeks, months, years, or permanently.
▪ Set the time period for performing full backup. The full backup job
will not be scheduled beyond the time range.
NOTE
○ If the end time is earlier than or the same as the start time, the end
time is actually the end time of the next day.
○ If the backup job is not completed within the specified time window, the
system does not stop the backup job, but reports an event.
○ Once the retention period expires, the system automatically deletes the
expired copies.
Step 7 Set advanced parameters for the backup policy. Table 3-11 describes the
parameters.
Rate Limiting Select a proper rate limiting policy for the SLA to limit the
Policies maximum bandwidth during backup.
NOTE
To create a rate limiting policy, choose Protection > Protection
Policies > Rate Limiting Policies and click Create.
Parameter Description
----End
Prerequisites
● An SLA has been created.
● File system resources of the storage system have been discovered by
ProtectManager.
Context
File systems created on the storage system can be automatically discovered by
ProtectManager and displayed on the Local File System page.
NOTE
● New file systems on the storage system can be discovered by ProtectManager after a
period of time.
● NAS resources of only the System_vStore can be accessed using the container back-end
module. Therefore, only the file systems of the System_vStore can be discovered by
ProtectManager.
● File systems discovered by ProtectManager cannot be deleted on ProtectManager.
● Clone file systems are not displayed on ProtectManager.
Procedure
Step 1 On ProtectManager, choose Protection > Storage > Local File System.
Step 2 In the local file system list, select the file system that you want to protect and
choose More > Protect. The Protect page is displayed.
You can also select multiple local file systems for batch protection.
Step 3 In the Select SLA area, select a proper SLA for the file system.
If the current system time is later than the first backup start time of the SLA, you
can perform manual backup immediately after the SLA is associated or wait for
the next scheduling based on the backup policy set in the SLA.
----End
Follow-up Procedure
After a backup plan is configured for a file system, the system periodically creates
and executes backup tasks for the file system based on the scheduling policy.
Prerequisites
An SLA has been created for the file system you want to back up manually.
Context
● During manual backup, the parameters defined in the SLA (except Automatic
Retry), such as Rate Limiting Policies, are applied to the manual backup
task.
● Copies generated by manual backup are retained for the duration defined in
the SLA.
Procedure
Step 1 On ProtectManager, choose Protection > Storage > Local File System.
Step 2 In the local file system list, select the file system that you want to protect and
choose More > Manual Protect. The Manual Backup page is displayed on the
right.
You can also select multiple local file systems for batch manual backup.
----End
Prerequisites
A file system backup copy has been generated.
Precautions
● Restoration to a file system in WORM, CLONE, or non-UNIX security mode is
not supported.
● Restoration to a file system whose name starts with pvc_ is not supported.
● Restoration to the secondary file system of asynchronous remote replication is
not supported.
● After HyperMetro brain-split occurs, the end that fails arbitration does not
support restoration.
● After an entire copy is used for restoration to the original location, new files
added to the original file system after the copy is generated are not deleted. If
you want to restore the file system to a certain point in time, you need to
create a new file system on DeviceManager and specify the new file system
for restoration.
● Ensure that no other user is reading or writing the file system during the
restoration. Otherwise, data may be inconsistent or even damaged.
● The restoration operation is irreversible. If the restoration fails, data is not
rolled back and some data may be damaged.
Procedure
Step 1 On ProtectManager, choose Explore > Copy Data > Local File System.
NOTE
The system allows you to search for copies by resource or copy. This example searches for
copies by resource, which is the default method. To search by copy, click the Copy tab.
Step 2 Click the name of the file system that you want to recover.
Step 3 Click Copy Data and select the year, month, and day in sequence to find the copy.
Step 4 Choose More > Restore in the row where the copy is located.
b. Select the rule for overwriting the original location file. Table 3-12
describes the parameters.
Parameter Description
Skip existing files Existing files in the file system are not
processed. Only the files that do not exist are
recovered.
Only replace the files For existing files in the file system, only the
older than the files that are older than the recovered files
restoration file are replaced.
Parameter Description
Skip existing files Existing files in the file system are not
processed. Only the files that do not exist are
recovered.
Only replace the files For existing files in the file system, only the
older than the files that are older than the recovered files
restoration file are replaced.
Step 7 Read the warning carefully, select I have read and understand the consequences
associated with performing this operation and click OK.
----End
Prerequisites
The index status of the copy is Indexed.
Precautions
The files to be recovered are not being read or written.
Procedure
Step 1 On ProtectManager, choose Explore > Copy Data > Local File System.
NOTE
The system allows you to search for copies by resource or copy. This example searches for
copies by resource, which is the default method. To search by copy, click the Copy tab.
Step 2 Click the name of the file system that you want to recover.
The file system details page is displayed.
Step 3 Click Copy Data and select the year, month, and day in sequence to find the copy.
● File-level recovery is supported only when the index status of the copy is Indexed.
● If the name of a directory or file has garbled characters, file-level recovery is not
supported.
----End
4 Managing CloudBackup
Procedure
Step 1 On ProtectManager, choose System > Infrastructure > Local Storage.
Step 2 In the Basic Info and Available Capacity areas, view the basic information and
available capacity of the local storage.
Table 4-1 describes related parameters.
Parameter Description
----End
Procedure
Step 1 On ProtectManager, choose System > Infrastructure > Local Storage.
Set the upper threshold of the used capacity of the local storage. When the used
capacity reaches the threshold, an alarm is reported.
----End
Procedure
Step 1 On ProtectManager, choose System > Infrastructure > Local Storage.
Step 2 In the Authentication Information area, view the local storage authentication
information. Authentication information includes login authentication and service
authentication.
● Login authentication
– Username: used to redirect and log in to DeviceManager. The user must
have the super administrator permissions.
– Password: password of the login authentication user.
– Status: user authentication status. If the authentication status is
Abnormal, you need to modify the authentication information.
● Service Authentication
– Username: used by the backup system and storage system to perform
data protection operations. The user must have the super administrator
permissions.
– Password: password of the service authentication user.
– Status: user authentication status. If the authentication status is
Abnormal, you need to modify the authentication information.
----End
Procedure
Step 1 On ProtectManager, choose System > Infrastructure > Local Storage.
Step 2 In the Authentication Information area on the Local Storage page, click Modify
Login Authentication or Modify Service Authentication on the right.
Step 3 Modify the username and password for authentication between ProtectManager
and the local storage.
NOTE
Ensure that the user who logs in to DeviceManager from the current page has been logged
out.
----End
Prerequisites
You have added a backup storage.
Procedure
Step 1 On ProtectManager, choose System > Infrastructure > Backup Storage.
Step 2 Click the name of a backup storage. In the dialog box that is displayed on the
right, view its information.
Table 4-2 describes the parameters.
Parameter Description
Parameter Description
Use Proxy Server Determines whether to use a proxy for accessing the S3
storage.
NOTE
● Obtain the proxy information from the network administrator of
the enterprise data center.
● If Use Proxy Server is enabled, the Address, Username, and
Password parameters are displayed.
Alarm Threshold Alarm threshold for the backup storage capacity. When the
percentage of the used capacity to the total capacity of the
backup storage reaches the alarm threshold, an alarm is
generated, prompting you to expand the capacity or delete
unnecessary backup data to release storage space.
Otherwise, subsequent backup tasks may fail.
----End
Procedure
Step 1 On ProtectManager, choose System > Infrastructure > Backup Storage.
Step 2 Locate the row that contains the backup storage to be modified, and click More >
Modify Backup Storage.
Parameter Description
----End
Prerequisites
You have added a backup storage.
Procedure
Step 1 On ProtectManager, choose System > Infrastructure > Backup Storage.
Step 2 Locate the row that contains the backup storage to be modified, and click More >
Modify Backup Storage.
Step 3 Modify the capacity alarm threshold.
Set the upper threshold of the used capacity of a bucket. When the used capacity
reaches the threshold, an alarm is reported.
Step 4 Click OK.
----End
Prerequisites
A backup storage has been added.
Precautions
After a backup storage copy is imported, all metadata in the copy is imported into
the storage system. The copy generation mode is changed from Backup to
Import.
Procedure
Step 1 Choose System > Infrastructure > Backup Storage.
Step 2 Click More next to a backup storage and select Import Backup Storage Copies.
Step 3 In the dialog box that is displayed, click OK.
----End
Prerequisites
● You have added a backup storage.
● The backup storage has not been added to an SLA.
Precautions
A backup storage cannot be restored after deletion.
Procedure
Step 1 On ProtectManager, choose System > Infrastructure > Backup Storage.
Step 2 Locate the row that contains the backup storage to be deleted, and click More >
Delete.
Step 3 In the displayed dialog box, click OK.
----End
Procedure
Step 1 On ProtectManager, choose Protection > Protection Policies > SLAs.
Step 2 Click the name of an SLA.
Step 3 View the basic information and associated resources of the SLA.
----End
Procedure
Step 1 On ProtectManager, choose Protection > Protection Policies > SLAs.
Step 2 Locate the row that contains the SLA to be cloned, and click More > Clone.
Step 3 Set SLA parameters. For details about the parameters, see 3.4.1 Creating a NAS
Protection SLA.
----End
Procedure
Step 1 On ProtectManager, choose Protection > Protection Policies > SLAs.
Step 2 Locate the row that contains the SLA to be modified, and click More > Modify.
Step 3 Set SLA parameters. For details about the parameters, see 3.4.1 Creating a NAS
Protection SLA.
NOTE
----End
Precautions
● Deleted SLAs cannot be restored. Perform this operation only when necessary.
● An SLA that has been associated with resources cannot be deleted. To delete
the SLA, remove the resources associated with the SLA from protection first.
Procedure
Step 1 On ProtectManager, choose Protection > Protection Policies > SLAs.
Step 2 Locate the row that contains the SLA to be deleted, and click More > Delete.
NOTE
You can also select multiple SLAs and click Delete in the upper left corner to delete them in
batches.
Step 3 The Danger dialog box is displayed. Read the message carefully and perform
operations as required.
----End
Prerequisites
File system resources of the storage system have been discovered by
ProtectManager.
Context
File systems created on the storage system can be automatically discovered by
ProtectManager and displayed on the Local File System page.
NOTE
● New file systems on the storage system can be discovered by ProtectManager after a
period of time.
● Currently, only file systems of the System_vStore can be discovered on ProtectManager.
● File systems discovered by ProtectManager cannot be deleted on ProtectManager.
● ProtectManager does not display WORM or clone file systems, or file systems of non-
UNIX security style.
● File systems whose names start with pvc_ are not displayed on ProtectManager.
Procedure
Step 1 Choose Protection > Storage > Local File System.
Step 2 In the local file system list, view the file system information.
1. Table 4-4 describes the details of a file system.
2. Click the name of a local file system to view its Overview, Copy Data, and
Jobs.
– Overview
Displays the local file system name, SLA information, job execution time,
and total number of copies.
– Copy Data
You can search for copies by year, month, or day.
If is displayed below the time, a copy at that time exists.
– Jobs
Displays all jobs related to the local file system, including backup and
restore jobs. You can click Download to export the job list.
----End
Log in to ProtectManager, choose Protection > Storage > Local File System, and
locate the local file system to be operated.
Table 4-5 describes the operations.
Procedure
Step 1 On ProtectManager, choose Explore > Copy Data > Local File System.
● Click Copy to view all copy information by copy. When you must restore data
to the original location or a new location using a specified copy, you are
advised to click this icon and search for the copy. Table 4-7 describes the
parameters.
Parameter Description
----End
Precautions
● The modified copy retention period is calculated from the time the
modification takes effect.
● If the expiration time T of any copy (except the latest one) in a copy chain is
reached, the copy and its dependent copies whose expiration time is earlier
than T are deleted in sequence.
NOTE
● A copy chain refers to a full copy and all its dependent incremental copies. If the
full copy does not have any dependent incremental copy, the full copy
independently forms a copy chain.
● The expiration of the latest copy chain cannot be triggered.
Procedure
Step 1 On ProtectManager, choose Explore > Copy Data > Local File System.
Step 2 Click the Copy tab, locate the row that contains the target copy, and choose More
> Modify Retention Policy.
----End
Precautions
● Before deleting a copy, ensure that the copy is no longer used for restoration.
● Copies can be deleted when they are in the Invalid state, or in the Normal
state and are not indexed. Copies in other states cannot be deleted.
● After a copy is deleted, other copies that are dependent on the copy are also
deleted.
● Copies in the latest copy chain cannot be deleted (except that the latest copy
is the only copy).
NOTE
A copy chain refers to a full copy and all its dependent incremental copies. If the full
copy does not have any dependent incremental copy, the full copy independently
forms a copy chain.
Procedure
Step 1 On ProtectManager, choose Explore > Copy Data > Local File System.
Step 2 Click the Copy tab, locate the row that contains the target copy, and choose More
> Delete.
The Danger dialog box is displayed.
Step 3 Read the message carefully and perform operations as required.
----End
NOTICE
Prerequisites
The CloudBackup containerized application exists in the system.
Procedure
Step 1 Check whether controllers are available for expansion of the CloudBackup
containerized application. If yes, go to the next step. If no, no further action is
required.
1. Check the number of controllers on which the CloudBackup containerized
application is deployed.
– In versions earlier than 6.1.5, run the show container_application
general name=? command and find the value of the global.replicas
field in the command output. For example, if global.replicas is 2, the
CloudBackup containerized application is deployed on two controllers.
– In 6.1.5 and later versions, run the show container_application general
name=? namespace=? command and find the value of the
global.replicas field in the command output. For example, if
global.replicas is 2, the CloudBackup containerized application is
deployed on two controllers.
2. Check the total number of controllers in the system.
You can run the show controller general command to query all controllers
and obtain the number of controllers that support the container service.
3. Check whether controllers are available for expansion of the CloudBackup
containerized application.
– If the number of controllers on which the CloudBackup containerized
application has been deployed is less than the total number of controllers
that support the container service, there are controllers available for
expansion. In this case, go to step 2.
– If the number of controllers on which the CloudBackup containerized
application has been deployed is equal to the total number of controllers
that support the container service, no controller is available for
expansion. In this case, no further action is required.
Step 2 Configure interface modules for the controllers you want to use to expand the
CloudBackup containerized application.
This operation includes interface module planning and configuration of the front-
end and back-end container modes. For details, see 3.2.3 Configuring Interface
Modules.
Step 3 Add the front-end container Ethernet ports of the controllers to be used for
expansion to the backupNetPlane network plane.
1. Choose System > Container Service > Network Planes.
2. Click the name of backupNetPlane. On the displayed page, click Add in the
Port area.
The Add Port page is displayed on the right.
3. Select one or more ports whose Logical Type is Container front-end and
Running Status is Link up from the controllers to be used for expansion, and
click OK.
Step 4 Check whether the number of IP addresses on the network plane meets the
requirements.
● Each controller requires at least two IP addresses. If the number of IP
addresses in the IP address segment is greater than or equal to the total
number of controllers on which the containerized application has been and
will be deployed, the requirements are met. In this case, skip this step.
b. Check the Pod Status field in the command output to determine the
status of the CloudBackup containerized application. If Pod Status is
Running, the CloudBackup containerized application is running properly.
----End
Concept Description
Front-end container mode Mode of the interface module, which is used for
communication between the host and container.
Back-end container mode Mode of the interface module, which is used for
communication between the container and
storage system.
Concept Description
C Glossary
A
AC power module The module that transfers the external AC power
supply into the power supply for internal use.
Application server A service processing node (a computer device) on the
network. Application programs of data services run
on the application server.
Asynchronous remote A kind of remote replication. When the data at the
replication primary site is updated, the data does not need to be
updated synchronously at the mirroring site to finish
the update. In this way, performance is not reduced
due to data mirroring.
Air baffle It optimizes the ventilation channels and improves
the heat dissipation capability of the system.
Audit log guarantee A mode for recording audit logs. This mode
mode preferentially ensures that the audit log function is
normal and no audit log is missing.
Audit log non- A mode for recording audit logs. In this mode,
guarantee mode services are running properly. Audit logs may be
missing.
B
Backup A collection of data stored on (usually removable)
non-volatile storage media for purposes of recovery
in case the original copy of data is lost or becomes
inaccessible; also called a backup copy. To be useful
for recovery, a backup must be made by copying the
source data image when it is in a consistent state.
The act of creating a backup.
C
Cache hit ratio The ratio of the number of cache hits to the number
of all I/Os during a read task, usually expressed as a
percentage.
Captive screw Specially designed to lock into place on a parent
board or motherboard, allowing for easy installation
and removal of attached pieces without release of
the screw.
Challenge Handshake A password-based authentication protocol that uses a
Authentication challenge to verify that a user has access rights to a
Protocol system. A hash of the supplied password with the
challenge is sent for comparison so the cleartext
password is never sent over the connection.
Compliance mode A protection mode of WORM. In compliance mode,
files within their protection period cannot be changed
or deleted by either the file user or by the system
administrator. Files with expired protection periods
can be deleted but not changed by the file user or
the system administrator.
Controller The control logic in a disk or tape that performs
command decoding and execution, host data transfer,
serialization and deserialization of data, error
detection and correction, and overall management of
device operations. The control logic in a storage
subsystem that performs command transformation
and routing, aggregation (RAID, mirroring, striping, or
other), high-level error recovery, and performance
optimization for multiple storage devices.
Controller enclosure An enclosure that accommodates controllers and
provides storage services. It is the core component of
a storage system and generally consists of
components, such as controllers, power supplies, and
fans.
Copying A pair state. The state indicates that the source LUN
data is being synchronized to the target LUN.
Container root Space used to store the metadata for running
directory container images and container instances.
Container image An image is a special file system, which provides the
programs, libraries, resources, and configuration files
required for running containers. It also contains
configuration parameters, for example, for
anonymous disks, environment variables, and users.
The image does not contain dynamic data, and its
content will not be modified after construction.
Containerized An image can start multiple containers, and an
application application can contain one or a group of containers.
D
Data compression The process of encoding data to reduce its size. Lossy
compression (i.e., compression using a technique in
which a portion of the original information is lost) is
acceptable for some forms of data (e.g., digital
images) in some applications, but for most IT
applications, lossless compression (i.e., compression
using a technique that preserves the entire content of
the original data, and from which the original data
can be reconstructed exactly) is required.
Data flow A process that involves processing data extracted
from the source system. These processes include:
filtering, integration, calculation, and summary,
finding and solving data inconsistency, and deleting
invalid data so that the processed data meets the
requirements of the destination system for the input
data.
Data migration A movement of data or information between
information systems, formats, or media. Migration is
performed for reasons such as possible decay of
storage media, obsolete hardware or software
(including obsolete data formats), changing
performance requirements, the need for cost
efficiencies etc.
Data source A system, database (database user; database
instance), or file that can make BOs persistent.
Deduplication The replacement of multiple copies of data — at
variable levels of granularity — with references to a
shared copy in order to save storage space and/or
bandwidth.
Dirty data Data that is stored temporarily on the cache and has
not been written onto disks.
E
eDevLUN Logical storage array space created by a third-party
storage array.
Expansion module A component used for expansion.
Expansion Connects a storage system to more disk enclosures
through connection cables, expanding the capacity of
the storage system.
F
Field replaceable unit A unit or component of a system that is designed to
be replaced in the field, i.e., without returning the
system to a factory or repair depot. Field replaceable
units may either be customer-replaceable or their
replacement may require trained service personnel.
Firmware Low-level software for booting and operating an
intelligent device. Firmware generally resides in read-
only memory (ROM) on the device.
Flash Translation Layer Flash Translation Layer (FTL) organizes and manages
host data, enables host data to be allocated to NAND
flash chips of SSDs in an orderly manner, maintains
the mapping relationship between logical block
addresses (LBAs) and physical block addresses
(PBAs), and implements garbage collection, wear
leveling, and bad block management.
Front-end port The port that connects the controller enclosure to the
service side and transfers service data. Front-end port
types are Fibre Channel and iSCSI.
Front-end interconnect On a storage device, all controllers share the front-
I/O module (FIM) end interface modules.
G
Garbage collection The process of reclaiming resources that are no
longer in use. Garbage collection has uses in many
aspects of computing and storage. For example, in
flash storage, background garbage collection can
improve write performance by reducing the need to
perform whole block erasures prior to a write.
Gateway A device that receives data via one protocol and
transmits it via another.
H
Hard disk tray The tray that bears the hard disk.
Heartbeat Heartbeat supports node communication, fault
diagnosis, and event triggering. Heartbeats are
protocols that require no acknowledgement. They are
transmitted between two devices. The device can
judge the validity status of the peer device.
Hit ratio The ratio of directly accessed I/Os from the cache to
all I/Os.
Hot swap The substitution of a replacement unit (RU) in a
system for a defective unit, where the substitution
can be performed while the system is performing its
normal functioning normally. Hot swaps are physical
operations typically performed by humans.
HyperMetro A value-added service of storage systems.
HyperMetro means two datasets (on two storage
systems) can provide storage services as one dataset
to achieve load balancing among applications and
failover without service interruption.
HyperMetro domain A HyperMetro configuration object generally; made
up of two storage arrays and one quorum server.
HyperMetro services can be created on a HyperMetro
domain.
I
In-band management The management control information of the network
and the carrier service information of the user
network are transferred through the same logical
channel. In-band management enables users to
manage storage arrays through commands.
Management commands are sent through service
channels, such as I/O write and read channels. The
advantages of in-band management include high
speed, stable transfer, and no additional
management network ports required.
Initiator The system component that originates an I/O
command over an I/O interconnect. The endpoint
that originates a SCSI I/O command sequence. I/O
adapters, network interface cards, and intelligent I/O
interconnect control ASICs are typical initiators.
L
Load balance A method of adjusting the system, application
components, and data to averagely distribute the
applied I/Os or computing requests to physical
resources of the system.
Logical unit The addressable entity within a SCSI target that
executes I/O commands.
Logical unit number The SCSI identifier of a logical unit within a target.
Industry shorthand, when phrased as "LUN", for the
logical unit indicated by the logical unit number.
LUN formatting The process of writing 0 bits in the data area of the
logical drive and generating related parity bits so that
the logical drive can be in the ready state.
LUN mapping A storage system maps LUNs to application servers
so that application servers can access storage
resources.
LUN migration A method for the LUN data to migrate between
different physical storage spaces while ensuring data
integrity and uninterrupted operation of host
services.
LUN snapshot A type of snapshot created for a LUN. This snapshot
is both readable and writable and is mainly used to
provide a snapshot LUN from point-in-time LUN
data.
M
Maintenance terminal A computer connected through a serial port or
management network port. It maintains the storage
system.
Management interface The module that integrates one or more
module management network ports.
Management network An entity that provides means to transmit and
process network management information.
Management network The network port on the controller enclosure
port connected to the maintenance terminal. It is provided
for the remote maintenance terminal. Its IP address
can be modified with the change of the customer's
environment.
N
NVM Express A host controller interface with a register interface
and command set designed for PCI Express-based
SSDs.
NVMe SSD A solid state disk (SSD) with a non-volatile memory
express (NVMe) interface. Compared with other
SSDs, such SSDs can deliver higher performance and
shorter latency.
O
Out-of-band A management mode used during out-of-band
management networking. The management and control
information of the network and the bearer service
information of the user network are transmitted
through different logical channels.
P
Power failure When an external power failure occurs, the AC PEM
protection depends on the battery for power supply. This
ensures the integrity of the dirty data in the cache.
Pre-copy When the system monitors a failing member disk in a
RAID group, the system copies the data from the disk
to a hot spare disk in advance.
Palm-sized NVMe SSD A palm-sized NVMe SSD is a type of NVMe SSD of
which the dimensions (H x W x D) are 160 mm x 79.8
mm x 9.5 mm (neither 3.5-inch nor 2.5-inch).
Q
Quorum server A server that can provide arbitration services for
clusters or HyperMetro to prevent the resource access
conflicts of multiple application servers.
Quorum Server Mode A HyperMetro arbitration mode. When a HyperMetro
arbitration occurs, the quorum server decides which
site wins the arbitration.
R
RAID level The application of different redundancy types to a
logical drive. A RAID level improves the fault
tolerance or performance of the logical drive but
reduces the available capacity of the logical drive.
You must specify a RAID level for each logical drive.
Ransomware file When launching attacks, ransomware usually
interception generates encrypted files with special file name
extensions. In light of this, the system intercepts the
write to files with specific file name extensions to
block the extortion from known ransomware and
protect file systems in the storage system.
Real-time ransomware Ransomware has similar I/O behavior characteristics.
detection By analyzing file I/O behavior characteristics, the
system quickly filters out abnormal files and
performs deep content analysis on the abnormal files
to detect files attacked by ransomware. Then, secure
snapshots are created for file systems where files
have been attacked, and alarms are reported to
notify the data protection administrator, limiting the
impact of ransomware and reducing losses.
S
Script A parameterized list of primitive I/O interconnect
operations intended to be executed in sequence.
Often used with respect to ports, most of which are
able to execute scripts of I/O commands
autonomously (without policy processor assistance).
A sequence of instructions intended to be parsed and
carried out by a command line interpreter or other
scripting language. Perl, VBScript, JavaScript and Tcl
are all scripting languages.
Serial port An input/output location (channel) that sends and
receives data (one bit at a time) to and from the CPU
of a computer or a communications device. Serial
ports are used for serial data communication and as
interfaces for some peripheral devices, such as mouse
devices and printers.
Service data The user and/or network information required for the
normal functioning of services.
Service network port The network port that is used to store services.
Simple network An IETF protocol for monitoring and managing
management protocol systems and devices in a network. The data being
monitored and managed is defined by an MIB. The
functions supported by the protocol are the request
and retrieval of data, the setting or writing of data,
and traps that signal the occurrence of events.
Single point of failure One component or path in a system, the failure of
which would make the system inoperable.
Slot A position defined by an upper guide rail and the
corresponding lower guide rail in a frame. A slot
houses a board.
Small computer system A collection of ANSI standards and proposed
interface standards that define I/O interconnects primarily
intended for connecting storage subsystems or
devices to hosts through host bus adapters. Originally
intended primarily for use with small (desktop and
desk-side workstation) computers, SCSI has been
extended to serve most computing needs, and is
arguably the most widely implemented I/O
interconnect in use today.
Snapshot A point in time copy of a defined collection of data.
Clones and snapshots are full copies. Depending on
the system, snapshots may be of files, LUNs, file
systems, or any other type of container supported by
the system.
Snapshot copy A copy of a snapshot LUN.
Source LUN The LUN where the original data is located.
Static Priority Mode A HyperMetro arbitration mode. When a HyperMetro
arbitration occurs, the preferred site always wins the
arbitration.
Storage system An integrated system that consists of the following
parts: controller, storage array, host bus adapter,
physical connection between storage units, and all
control software.
Storage unit An abstract definition of backup storage media for
storing backup data. The storage unit is connected to
the actual storage media used to back up data.
T
Target The endpoint that receives a SCSI I/O command
sequence.
Target LUN The LUN on which target data resides.
Thin LUN A logic disk that can be accessed by hosts. It
dynamically allocates storage resources from the thin
pool according to the actual capacity requirements of
users.
Topology The logical layout of the components of a computer
system or network and their interconnections.
Topology deals with questions of what components
are directly connected to other components from the
standpoint of being able to communicate. It does not
deal with questions of physical location of
components or interconnecting cables. The
communication infrastructure that provides Fibre
Channel communication among a set of PN_Ports
(e.g., a Fabric, an Arbitrated Loop, or a combination
of the two).
U
User interface The space where users interact with a machine.
U-shaped bracket It is an optional structural part like letter "U". It is
located between the mounting ear of a chassis and
the mounting bar of a cabinet or bay and is used to
adjust the locations of the chassis and mounting bar
of the cabinet or bay.
W
Wear leveling A set of algorithms utilized by a flash controller to
distribute writes and erases across the cells in a flash
device. Cells in flash devices have a limited ability to
survive write cycles. The purpose of wear leveling is
to delay cell wear out and prolong the useful life of
the overall flash device.
Write amplification Increase in the number of write operations by the
device beyond the number of write operations
requested by hosts.
Write amplification The ratio of the number of write operations on the
factor device to the number of write operations requested
by the host.
Write back A caching technology in which the completion of a
write request is signaled as soon as the data is in the
cache. Actual writing to non-volatile media occurs at
a later time. Write back includes inherent risks: an
application will take action predicated on the write
completion signal, and a system failure before the
data is written to non-volatile media will cause
media contents to be inconsistent with that
subsequent action. For these reasons, sufficient write
back implementations include mechanisms to
preserve cache contents across system failures
(including power failures) and a flushed cache at
system restart time.
Write Once Read Many A type of storage, designed for fixed content, that
preserves what is written to it in an immutable
fashion. Optical disks are an example of WORM
storage.
Write through A caching technology in which the completion of a
write request is not signaled until data is safely
stored on non-volatile media. Write performance
equipped with the write through technology is
approximately that of a non-cached system. However,
if the written data is also held in a cache, subsequent
read performance may be dramatically improved.
Z
Zone A collection of Fibre Channel N_Ports and/or
NL_Ports (i.e., device ports) that are permitted to
communicate with each other via the fabric. Any two
N_Ports and/or NL_Ports that are not members of at
least one common zone are not permitted to
communicate via the fabric. Zone membership may
be specified by: 1) port location on a switch, (i.e.,
Domain_ID and port number); or, 2) the device's
N_Port_Name; or, 3) the device's address identifier;
or, 4) the device's Node_Name. Well-known
addresses are implicitly included in every zone.
A
AWS Amazon Web Services
C
CLI Command Line Interface
F
FC Fibre Channel
G
GUI Graphical User Interface
I
IP Internet Protocol
L
LUN Logical Unit Number
N
NAS Network Attached Storage
NFS Network File System
W
WWN World Wide Name
WWPN World Wide Port Name