Backup management integrates multiple disaster recovery
technologies such as incremental backup and full backup that are suitable for
multiple business scenarios. You can implement local backup and remote backup based
on your business needs.
Backup Service is a separate feature module. To use this service, purchase both the Base
License and the Plus License of Backup Service. The Plus License cannot be used
independently.
Typical Backup Scenarios
Backup Service can be applied to the following three typical scenarios: local backup,
remote backup, and Public Cloud backup.
Note: If
you have the Tenant Management Plus license at the same time, the project
members (project managers, project admins, and general project members) can
perform local backup for VM instances, elastic baremetal instances, and data
volumes in the project.
Local Backup
A local ImageStore image storage can act as the Local
Backup Server to store scheduled backup data of the local VM
instances, elastic baremetal instances, data volumes, and management node
databases. Meanwhile, the seamless switchover between the primary local
backup server and the secondary local backup server is supported, which
effectively ensures your business continuity.
If your local data is
mistakenly deleted, or data in the local primary storage is damaged, you can
recover the backup data from the local backup server, as shown in Local Backup
Scenario-1
Figure 1. Local Backup Scenario-1
If you encounter a disaster in your local data center, you can rely
totally on your local backup server to rebuild your data center and recover
your business, as shown in Local Backup Scenario-2.
Figure 2. Local Backup Scenario-2
Remote Backup
A storage server in a remote data center can act as the
Remote Backup Server to store the scheduled backup data of the
local VM instances, elastic baremetal instances, volumes, and databases. The
backup data needs to be synchronized to the remote backup server from the
local backup server.
If your local data is mistakenly deleted, or data
in the local primary storage is damaged, you can recover the backup data
from the remote backup server, as shown in Remote Backup
Scenario-1
Figure 3. Remote Backup Scenario-1
If you encounter a disaster in your data center, you can rely totally on
your remote backup server to rebuild your data center and recover your
business, as shown in Remote Backup Scenario-2.
Figure 4. Remote Backup Scenario-2
Public Cloud Backup
The storage server in the
Public Cloud can act as the Public Cloud Backup Server to store the scheduled
backup data of the local VM instances, volumes, and databases. The backup
data can be synchronized to the Public Cloud backup
server from the local backup server.
Note: The Public Cloud backup feature does not apply to elastic
baremetal instances.
If your local data is mistakenly
deleted, or data in the local primary storage is damaged, you can recover
the backup data from the Public Cloud backup server, as
shown in Public Cloud Backup Scenario-1.
Figure 5. Public Cloud Backup Scenario-1
If you encounter a disaster in your data center, you can rely totally on
your Public Cloud backup server to rebuild your data
center and recover your business, as shown in Public Cloud
Backup Scenario-2.
Figure 6. Public Cloud Backup Scenario-2
ZStack Cloud allows you to integrate 3rd-party backup
services via CBT interfaces. For details, contact the official technical
support.
Preparations
Before you can use Backup Service, you need to install ZStack Cloud as the admin and deploy resources necessary for VM
instances, elastic baremetal instances, or data volumes.
In addition, you need to purchase the Plus License of Backup Service as the admin.
Quick Start
Backup management module integrates multiple disaster recovery scenarios such as local
backup, remote backup, and Public Cloud backup. You can choose
different backup methods that are suitable to your business needs.
Local Backup
Local backup allows you to backup and recover the data of the local VM instances,
elastic baremetal instances, data volumes, and management node databases.
Backup:
Backup the data of the local VM instances/elastic baremetal
instances/data volumes/databases to a specified local backup server
as scheduled.
If you specify two local backup servers, the failover mechanism is
supported.
For backup jobs of local VM instances/elastic baremetal
instances/data volumes, you can configure incremental backup and
full backup according to your business needs.
Recover:
If your local data is mistakenly deleted, or data in the local
primary storage is damaged, you can recover the backup data from the
local backup server.
If you encounter a disaster in your local data center, you can rely
totally on your local backup server to rebuild your data center and
recover your business.
Local backup practice covers the following two parts:
Backup Practice:
Add one or more local backup servers to the Cloud. To add a local
backup server, see Local Backup Server.
Create backup jobs of local VM instances/elastic baremetal
instances/data volumes/databases. To create a backup job, see Backup Job.
Manage local backup data. For more information, see Local Backup Data.
Recover Practice:
Recover the backup data of local VM instances/elastic baremetal
instances/data volumes/databases from the local backup server. To
recover local backup data, see Local Backup Data.
Remote backup allows you to backup and recover the data of the local VM instances,
elastic baremetal instances, data volumes, and management node databases to/from the
remote backup server.
Backup:
Backup the data of the local VM instances/elastic baremetal
instances/data volumes/databases to a specified remote backup server
as scheduled.
The backup data needs to be synchronized to the remote backup server
from the local backup server.
For backup jobs of local VM instances/elastic baremetal
instances/data volumes, you can configure incremental backup and
full backup according to your business needs.
Recover:
If your local data is mistakenly deleted, or data in the local
primary storage is damaged, you can recover the backup data from the
remote backup server.
If you encounter a disaster in your local data center, you can rely
totally on your remote backup server to rebuild your data center and
recover your business.
Before recovering the data of VM instances/elastic baremetal
instances/data volumes, you need to synchronize the data from the
remote backup server to local.
You can directly recover the backup data of databases to local.
Remote backup practice covers the following two parts:
Backup Practice:
Add a remote backup server to the Cloud. To add a remote backup
server, see Remote Backup Server.
Add one or more local backup servers to the Cloud. To add a local
backup server, see Local Backup Server.
Create backup jobs of local VM instances/volumes/databases. To
create a backup job, see Backup Job.
Manage remote backup data. Form more information, see Remote Backup Data.
Recover Practice:
Recover the backup data of local VM instances/elastic baremetal
instances/data volumes/databases from the remote backup server. To
recover the remote backup data, see Remote Backup Data.
Public Cloud backup allows you to backup and recover the data of
the local VM instances, elastic baremetal instances, data volumes, and management
node databases to/from the Public Cloud backup server.
Backup:
Backup the data of the local VM instances/elastic baremetal
instances/data volumes/databases to a specified Public Cloud backup server as scheduled.
The backup data needs to be synchronized to the Public Cloud backup server from the local backup
server.
For backup jobs of local VM instances/elastic baremetal
instances/data volumes, you can configure incremental backup and
full backup according to your business needs.
Recover:
If your local data is mistakenly deleted, or data in the local
primary storage is damaged, you can recover the backup data from the
Public Cloud backup server.
If you encounter a disaster in your local data center, you can rely
totally on your Public Cloud backup server to
rebuild your data center and recover your business.
Before recovering the data of VM instances/elastic baremetal
instances/data volumes, you need to synchronize the data from the
Public Cloud backup server to local.
You can directly recover the backup data of databases to local.
Public Cloud backup practice covers the following two parts:
Backup Practice:
Add a Public Cloud backup server to the Cloud.
To add a Public Cloud backup server, see Remote Backup Server.
Add one or more local backup servers to the Cloud. To add a local
backup server, see Local Backup Server.
Create backup jobs of local VM instances/volumes/databases. To
create a backup job, see Backup Job.
Manage Public Cloud backup data. For more
information, see Remote Backup Data.
Recover Practice:
Recover the backup data of local VM instances/volumes/databases from
the Public Cloud backup server. To recover
Public Cloud backup data, see Remote Backup Data.
You can create backup jobs to back up VM instances, volumes, and
databases on your local data center to specified local storage servers and sync the
backup data to specified remote backup servers or backup servers on the public
cloud.
The following describes how to create backup jobs for local VM instances and volumes and
the management node database.
Overview
The backup job overview visually displays the backup job overview,
resource overview, and backup job statistics of core resources on the Cloud.
On the main menu of ZStack Cloud, choose Platform O&M > Backup Management > Backup Service > Backup Job. On the Backup Job page, the
Overview tab is displayed by default.
Figure 7. Backup Job Overview
Job Overview
Job overview displays backup job number and state on a card.
Total jobs: The total number of backup jobs on the Cloud, as well as the number
of VM instance, elastic baremetal instance, data volume, and database backup
jobs.
State: The state of backup jobs. Green indicates enabled, while red indicates
disabled.
Resource Overview
Resource overview displays the backup and protection
information about available VM instances/elastic baremetal instances/datavolumes on
the Cloud.
VM Instance:
Backup Job: The number of VM instances that have backup jobs on the
Cloud.
CDP Task: The number of VM instances that have CDP tasks
on the Cloud.
No Task: The number of VM instances that have no backup jobs or CDP tasks on the Cloud.
Elastic Baremetal Instance:
Backup Job: The number of elastic baremetal instances that have backup
jobs in the Cloud.
No Task: The number of elastic baremetal instances that have no backup
jobs in the Cloud.
Data Volume:
Backup Job: The number of volumes that have backup jobs on the
Cloud.
Other: The number of volumes attached by VM instances with CDP tasks or VM instances/elastic baremetal
instances with backup jobs on the Cloud.
No Task: The number of volumes that have no backup jobs or CDP tasks on the Cloud.
Backup Job Statistics
Backup job statistics displays the execution of backup jobs in a line chart with time
period as the horizontal axis and job number as the vertical axis.
You can set a time filter to the view the execution of backup jobs within the
selected time period (by year/month/day).
Blue: The number of executed backup jobs within the selected time
period.
Green: The number of succeeded backup jobs within the selected time
period.
Yellow: The number of partially succeeded backup jobs within the selected
time period. You can view the specific backup job result in the job
details.
Red: The number of failed backup jobs within the selected time period.
Grey: The number of backup jobs that are scheduled to implement within the
selected time period.
Note:
The time filter applies to both the line chart (backup job statistics)
and list (backup record).
Allows you to view the execution of a backup job on the current date in
hover.
Backup Record
Backup record displays the execution record of all backup jobs within the current
time period, including execution time, name, backup resource, resources, backup
mode, backup capacity, task result and time consumed. You can view the job details
of a backup job.
Figure 8. Backup Job Details
Additional Information
The backup job overview displays static data that will be updated every time
you enter the page.
Allows you to set an event alarm for a backup job, which triggers an alarm
when a backup job fails.
Create a Backup Job
On the main menu of ZStack Cloud, choose Platform O&M > Backup Management > Backup Service > Backup Job. Then the Backup Job page appears. On the page,
choose a resource type to be backed up and click Create Backup
Job. Then, the Create Backup Job page appears.
You can create the following types of backup jobs:
Backup jobs for VM instances/elastic baremetal instances/data volumes
Backup jobs for the management node database
Create Backup Job for VM Instance/Elastic Baremetal Instance/Data Volume
Follow these four steps to create a backup job for VM instances/elastic baremetal
instances/volumes:
Set basic information.
Name: Enter a name for the backup
job.
The name must be 1 to 128 characters in length and can
contain Chinese characters, letters, digits, spaces, hyphens (-), underscores
(_), periods (.), parenthesis (), colons (:), and plus signs (+) and cannot
begin or end with spaces.
Description: Optional. Enter a
description for the backup job.
Local Backup Server:
Specify one or more local backup servers.
Note:
You can specify up to two local backup servers for a
backup job.
Before you can specify a local backup server, you
need to add the server to ZStack CloudPrivate Cloud. For more
information, see Add a Local
Backup Server.
If you specify two local backup
servers, by default, the first server added to the
Cloud is the primary backup server and the second is
the secondary backup server.
If you specify two local backup
servers, these two servers apply the fail-over
mechanism.
When the primary backup server works as
expected, data is backed up on the primary backup
server.
If the primary backup server is disabled,
removed, or disconnected, data is backed up on the
secondary backup server.
When the primary backup server resumes working
as expected, data backup is auto-switched to the
primary backup server.
Sync to Remote Backup
Server: Choose whether to sync local backup data
to a remote backup server. By default, the checkbox is not selected.
Note:
Before you can sync backup data to a remote backup
server, you need to add a remote backup server to
the Cloud. Note that you can add only one remote
backup server to the Cloud. For more information,
see Add a
Remote Backup Server.
You can sync VM instance/data volume backup data to
a server that is in another data canter or from a
public cloud.
You can sync elastic baremetal instance backup data
to a server that is in another data center.
Remote Backup Server:
Select a remote backup server if you want to sync data to a
remote server.
Set QoS: Optional.
You can set network QoS and disk QoS for the backup job.
Downstream Bandwidth: Set the
maximum downstream bandwidth. Unit: Kbps, Mbps, and
Gbps. Valid values: 8 Kbps to 30 Gbps. If you do not
specify the downstream bandwidth, this bandwidth is
unlimited.
Upstream Bandwidth: Set the
maximum upstream bandwidth. Unit: Kbps, Mbps, and Gbps.
Valid values: 8 Kbps to 30 Gbps. If you do not specify
the upstream bandwidth, this bandwidth is
unlimited.
Disk Read Speed: Set the maximum
read speed. Unit: MB/s and GB/s. Valid values: 1MB/s to
100GB/s. If you do not specify the disk read speed, this
speed is unlimited.
Disk Write Speed: Set the maximum
write speed. Unit: MB/s and GB/s. Valid values: 1MB/s to
100GB/s. If you do not specify the disk write speed,
this speed is unlimited.
Note: We recommend that you set a QoS
based on your physical network environments and the
concurrent number of implemented backup jobs.
Figure 9. Set Basic Information
Select backup resource.
Select VM instances/elastic baremetal
instances/data volumes that you need to back up.
VM Instance/Elastic Baremetal Instance/Data
Volume: Select the resources that you need to
back up.
Note:
VM Instance:
You can only back up running VM
instances.
You cannot back up a VM instance with a CDP
task.
Volumes on ZBS primary storage over the CBD protocol can be backed up. You cannot create backup jobs for a VM instance that uses Vhost primary storage or has any volume over the Vhost protocol attached, including a ZBS volume over the Vhost protocol.
You can select multiple VM instances that do
not exceed the authorized quota of the backup
service.
If the selected VM instance has backup data,
creating a backup job for it does not occupy any
additional quota of the backup service.
Elastic Baremetal Instance:
You can only back up running elastic baremetal
instances.
You can only back up elastic baremetal
instances that use block storage volume as system
volumes.
You can select multiple elastic baremetal
instances that do not exceed the authorized quota
of the backup service.
If the selected elastic baremetal instance has
backup data, creating a backup job for it does not
occupy any additional quota of the backup
service.
Data Volume:
You can only back up data volumes attached to
running VM/elastic baremetal instances.
You cannot back up data volumes attached to VM
instances with CDP tasks.
Back up Volume: You can back up all
volumes that are attached to the selected VM/elastic baremetal
instances. By default, this switch is turned on.
Note: You cannot
back up shared volumes that are attached to a VM/elastic
baremetal instance.
Figure 10. Select Backup Resource
Set backup policy.
You can create a backup job in one of the following
three backup modes:
Incremental Backup + Default Full Backup:
You only need to customize the incremental backup
policy, and the full backup policy is set by default by
system.
The Cloud performs incremental backup based on the
custom incremental backup policy.
After the incremental backup is executed 63 times or a
customized number of times, the Cloud will implement a
full backup, which will delete the incremental backup
records without affecting the data security.
Incremental Backup + Custom Full Backup:
You need to customize the incremental backup policy and
the full backup policy.
The Cloud performs incremental backup and full backup
based on the custom incremental backup policy and full
backup policy.
After the incremental backup is executed 63 times or a
customized number of times, the Cloud will implement a
full backup, which will delete the incremental backup
records without affecting the data security.
Full Backup Policy:
You need to customize the full backup policy.
The Cloud performs full backup based on the custom full
backup policy.
On the displayed page, set the following parameters:
Backup Mode: Select a backup mode for a
backup job, including Incremental Backup + Default Full
Backup, Incremental Backup + Custom Full
Backup.
Incremental Backup + Default Full Backup:
Incremental Backup
Policy: Customize an incremental
backup policy.
Backup Cycle: Select a
backup cycle. Options: Backup by Month,
Backup by Week, Backup by Day,
Backup by Hour, and Backup by
Minute.
If you select Backup by
Month, Backup by Week, or Backup by
Day, you can set the backup execution time and
schedule the effective time of the backup job to
the accuracy of a second.
Execution Time:
If you select Backup by Month and set
the execution time to 00:00:00 of the first day of
each month, the incremental backup job is executed
at 00:00:00 of the first day of each
month.
Note: If you set the execution time to the
31th day of each month, the incremental backup job
is executed only in the month that has 31
days.
If you select Backup by Week and set
the execution time to 00:00:00 of Sunday and
Tuesday of each week, the incremental backup job
is executed at 00:00:00 of Sunday and Tuesday of
each week.
If you select Backup by Day and set the
execution time to 00:30:00, the incremental backup
job is executed at 00:30:00 of each day.
Schedule Effective
Time: Choose whether to schedule the
time when the backup job takes effect.
If you
specify data backup by month, week, or day, you
can schedule the time when the backup job takes
effect. After the backup job takes effect, data
backup is executed based on the specified cycle
and time.
If you select Backup by Hour or
Backup by Minute, you can set a
finer-grained incremental backup cycle.
Start Time to
Implement:
If you choose to back up data every 6 hours
and set the start time to 2020-12-30 00:00:00,
incremental backup is implemented starting from
00:00:00, Dec 30, 2020 at an interval of 6
hours.
If you choose to back up data every 30 minutes
and the start time to 2020-12-30 00:00:00,
incremental backup is implemented starting from
00:00:00, Dec 30, 2020 at an interval of 30
minutes.
Note: The minimum backup interval is 15
minutes.
Incremental Backup + Custom Full Backup:
Incremental Backup
Policy: Customize an incremental
backup policy.
Backup Cycle: Select a
backup cycle. Options: Backup by Month,
Backup by Week, Backup by Day,
Backup by Hour, and Backup by
Minute.
If you select Backup by
Month, Backup by Week, or Backup by
Day, you can set the backup execution time and
schedule the effective time of the backup job to
the accuracy of a second.
Execution Time:
If you select Backup by Month and set
the execution time to 00:00:00 of the first day of
each month, the incremental backup job is executed
at 00:00:00 of the first day of each
month.
Note: If you set the execution time to the
31th day of each month, the incremental backup job
is executed only in the month that has 31
days.
If you select Backup by Week and set
the execution time to 00:00:00 of Sunday and
Tuesday of each week, the incremental backup job
is executed at 00:00:00 of Sunday and Tuesday of
each week.
If you select Backup by Day and set the
execution time to 00:30:00, the incremental backup
job is executed at 00:30:00 of each day.
Schedule Effective
Time: Choose whether to schedule the
time when the backup job takes effect.
If you
specify data backup by month, week, or day, you
can schedule the time when the backup job takes
effect. After the backup job takes effect, data
backup is executed based on the specified cycle
and time.
If you select Backup by Hour or
Backup by Minute, you can set a
finer-grained incremental backup cycle.
Start Time to
Implement:
If you choose to back up data every 6 hours
and set the start time to 2020-12-30 00:00:00,
incremental backup is implemented starting from
00:00:00, Dec 30, 2020 at an interval of 6
hours.
If you choose to back up data every 30 minutes
and the start time to 2020-12-30 00:00:00,
incremental backup is implemented starting from
00:00:00, Dec 30, 2020 at an interval of 30
minutes.
Note: The minimum backup interval is 15
minutes.
Full Backup
Policy: Customize a full backup
policy.
Backup Cycle: Select a
backup cycle. Options: Backup by Month and
Backup by Week.
If you select Backup
by Month or Backup by Week, you can set
the backup execution time and schedule the
effective time of the backup job to the accuracy
of a second.
Execution Time: Set the
time when the backup job is implemented.
If you select Backup by Month and set
the execution time to 00:00:00 of the first day of
each month, the full backup job is executed at
00:00:00 of the first day of each month.
Note: If
you set the execution time to the 31th day of each
month, the full backup job is executed only in the
month that has 31 days.
If you select Backup by Week and set
the execution time to 00:00:00 of Sunday and
Tuesday of each week, the full backup job is
executed at 00:00:00 of Sunday and Tuesday of each
week.
Schedule Effective
Time: Choose whether to schedule the
time when the backup job takes effect.
You can
schedule the time at which the backup job takes
effect. After the backup job takes effect, data
backup is executed based on the specified cycle
and time.
Full Backup Policy:
Full Backup
Policy: Customize a full backup
policy.
Backup Cycle: Select a
backup cycle. Options: Backup by Month and
Backup by Week.
If you select Backup
by Month or Backup by Week, you can set
the backup execution time and schedule the
effective time of the backup job to the accuracy
of a second.
Execution Time: Set the
time when the backup job is implemented.
If you select Backup by Month and set
the execution time to 00:00:00 of the first day of
each month, the full backup job is executed at
00:00:00 of the first day of each month.
Note: If
you set the execution time to the 31th day of each
month, the full backup job is executed only in the
month that has 31 days.
If you select Backup by Week and set
the execution time to 00:00:00 of Sunday and
Tuesday of each week, the full backup job is
executed at 00:00:00 of Sunday and Tuesday of each
week.
Schedule Effective
Time: Choose whether to schedule the
time when the backup job takes effect.
You can
schedule the time at which the backup job takes
effect. After the backup job takes effect, data
backup is executed based on the specified cycle
and time.
Backup Immediately: Choose whether to
back up data immediately after the backup job is created. By
default, this option is not selected.
Local Retention Policy: Set the policy
how the local backup data is reserved. The data can be reserved
by count or by time (day/week/month).
If by count, a minimum of 1 local backup can be
reserved.
If by time, a minimum of 1 day of local backup can be
reserved.
Remote Retention Policy: Set the policy
how the remote backup data is reserved. The data can be reserved
permanently, by count, or by time (day/week/month).
If permanently, the remote backup data will not be
cleared automatically.
If by count, a minimum of 1 remote backup can be
reserved.
If by time, a minimum of 1 day of remote backup can be
reserved.
Figure 11. Set Backup Policy
Preview.
Preview the backup job. You can click the Edit icon to
modify the job.
Figure 12. Preview
Create Backup Job for Management Node Database
On the main menu of ZStack Cloud, choose Platform O&M > Backup Management > Backup Service > Backup Job. Then the Backup Job page appears. On the page,
choose Database > Create Backup Job. Then the Create Backup Job page appears.
On the displayed page, set the following parameters:
Name: Enter a name for the backup job.
Description: Optional. Enter a description for the
backup job.
Backup Resource: The management node database is
displayed
Local Backup Server:
Specify one or more local backup servers.
Note:
You can specify up to two local backup servers for a
backup job.
Before you can specify a local backup server, you
need to add the server to ZStack CloudPrivate Cloud. For more
information, see Add a Local
Backup Server.
If you specify two local backup
servers, by default, the first server added to the
Cloud is the primary backup server and the second is
the secondary backup server.
If you specify two local backup
servers, these two servers apply the fail-over
mechanism.
When the primary backup server works as
expected, data is backed up on the primary backup
server.
If the primary backup server is disabled,
removed, or disconnected, data is backed up on the
secondary backup server.
When the primary backup server resumes working
as expected, data backup is auto-switched to the
primary backup server.
Sync to Remote Backup
Server: Choose whether to sync local backup data
to a remote backup server. By default, the checkbox is not selected.
Note:
Before you can sync backup data to a remote backup
server, you need to add a remote backup server to
the Cloud. Note that you can add only one remote
backup server to the Cloud. For more information,
see Add a
Remote Backup Server.
You can sync VM instance/data volume backup data to
a server that is in another data canter or from a
public cloud.
You can sync elastic baremetal instance backup data
to a server that is in another data center.
Remote Backup Server:
Select a remote backup server if you want to sync data to a
remote server.
Backup Policy: Set the backup policy for the backup
job.
Backup Cycle: Select a backup cycle.
Options: Backup by Week, Backup by Day, and
Backup by Hour.
If you select Backup by Week,
Backup by Day, you can set the backup execution time
of the full backup job to the accuracy of a second.
Execution Time: Set the time when
the backup job is implemented.
If you select Backup by Week and set the
execution time to 00:00:00 of Sunday and Tuesday
of each week, the full backup job is executed at
00:00:00 of Sunday and Tuesday of each week.
If you select Backup by Day and set the
execution time to 00:30:00, the full backup job is
executed at 00:30:00 of each day.
If you select Backup by Hour, you can set
finer-grained full backup job cycle to the accuracy of a
second.
Interval:
Backup by the hour, with an interval of 2 hours. The
full backup job is executed at an interval of 2
hours.
Note:
The minimum interval between backup jobs is 1
hour.
If you select Backup by Hour, you can
back up on the hour from the moment the backup
task is created.
Data Retention Policy: Specify how the local backup
data and remote backup data is reserved.
Local Retention Policy: Set the retention
policy for local backup data. Options: by count and by time
(day/week/month).
If by count, a minimum of 1 local backup can be
reserved.
If by time, a minimum of 1 day of local backup can be
reserved.
Remote Retention Policy: Set the retention
policy for remote backup data. Options: permanent, by count, and by
time (day/week/month).
If permanent, the remote backup data will not be cleared
automatically.
If by count, a minimum of 1 remote backup can be
reserved.
If by time, a minimum of 1 day of remote backup can be
reserved.
Figure 13. Create Backup Job for Management Node Database
Notes
By default, the value of incrementalBackup.maxNum is 64. This
value indicates that the Cloud will implement a full backup after the
incremental backup is executed 63 times. You can also use zstack-cli to modify the
value:
[root@localhost ~]# zstack-cli
admin>>> LogInByAccount accountName=admin password=password //Log into the system.The default username and password combination is admin/password.
admin >>>UpdateGlobalConfig category=volumeBackup name=incrementalBackup.maxNum value=10 //Update the maximum times of incremental backup.
{
"inventory": {
"category": "volumeBackup",
"defaultValue": "64",
"description": "the maximum numbers of continuous incremental backup",
"name": "incrementalBackup.maxNum",
"value": "10"
},
"success": true
}
After you set a data retention policy, only records are deleted for data outside
the retention policy, which does not affect data security.
If a full backup and incremental backup are triggered at the same time, the two
backups are executed in queue.
You can check the incremental backup data and full backup data on the
Local Backup Data page. If you have selected Sync to
Remote Backup Server, you can check the backup data on the remote backup
server.
Manage a Backup Job
On the main menu of ZStack Cloud, choose Platform O&M > Backup Management > Backup Service > Backup Job. Then the Backup Job page appears.
The following table lists the actions that you can perform on a backup job for VM
instances and volumes.
Action
Description
Edit Backup Job
Edit the name and description of a backup
job.
Enable Backup Job
Enable a backup job.
Disable Backup Job
Disable a backup job. If you disable a backup
job, data backup will not be implemented for the associated
resources. In addition, you cannot create new backup jobs for the
resources.
Set Backup Policy
Update the backup policy of the backup job. You
can edit the backup mode, backup retention policy, incremental
backup policy, and full backup policy.
Note: New backup policies do
not affect backup jobs that have been triggered.
Set Backup Server
Configure local backup servers and remote backup
servers for the backup job.
Backup Now
Implementing a backup job right now will generate
a new backup in the backup chain.
Note:
If the backup mode of the backup job is Incremental
Backup + Default Full Backup, the manual backup is
implemented in the mode the same as the next backup.
Full backup is not supported.
If the backup mode of the backup job is Incremental
Backup + Custom Full Backup, you can choose whether to
implement full backup. If you do not choose to implement
full backup, the manual backup is implemented in the
mode the same as the next backup. Full backup is not
supported.
If the backup mode of the backup job is Full Backup
Policy, a full backup will be implemented. By default,
the Full Backup switch is enabled and cannot be
disabled.
After you successfully perform manual execution, you can
view the ongoing backup job on the
Auto-Scheduling Task tab.
If the manual execution fails, you can view the task
record on the Cloud Operation Logs
tab or the Overview tab on the
Backup Job page.
Delete Backup Job
Delete a backup job. If you delete a backup job,
data backup is terminated for the associated resources. You can
create new backup jobs for the resources.
Note:
If you have already created a backup job for a resource,
you cannot create another backup job for the
resource.
After you delete a backup job for a resource, you can
create a new backup job for the resource.
The following table lists the actions that you can perform on a backup job for the
database.
Action
Description
Edit Backup Job
Edit the name and description of a backup job.
Enable Backup Job
Enable a backup job.
Disable Backup Job
Disable a backup job. If you disable a backup job, data backup
will not be implemented for the associated resources. In addition,
you cannot create new backup jobs for the resources.
Backup Now
Implementing a backup job right now will generate a new backup in
the backup chain.
Delete Backup Job
Delete a backup job. If you delete a backup job, data backup is
terminated for the associated resources. You can create new backup
jobs for the resources.
Note:
If you have already created a backup job for a resource,
you cannot create another backup job for the
resource.
After you delete a backup job for a resource, you can
create a new backup job for the resource.
Local Backup Data
The local backup data is the data of local VM instances, elastic
baremetal instances, data volumes, and databases backed up in the local backup server.
You can manage the local backup data on the Local Backup Data
page.
You can restore the backup data to your local server or synchronize the data to
a remote backup server.
When you restore a database, refreshing the browser will make the UI display
improperly without affecting the restoring process.
With the Backup Service, you can back up or restore the data stored in the
management node database. Note that the operation logs and monitoring
information cannot be backed up or restored.
The following lists the actions that you can perform on the local
backup data:
View the local backup data.
Restore the local backup data.
Synchronize the local backup data to a remote backup server.
Delete the local backup data.
Scan the database backup.
Export the backup data of the local database.
View the Local Backup Data
On the main menu of ZStack Cloud, choose Platform O&M > Backup Management > Backup Service > Local Backup Data. On the Local Backup Data page, you can manage
the local backup data.
Figure 14. Local Backup Data
This page includes three tab pages: VM Instance,
Elastic Baremetal Instance, Data
Volume, and Database. Each tab page displays
the backup data generated based on the backup jobs.
The backup data is displayed as a folder by resource or database.
Under each resource or database folder, the backup data of the resource or
database is arranged in order based on the latest creation date.
Restore the Local Backup Data
You can restore the local backup data of the local VM instances, volumes, or
databases to your local server.
Restore a local VM instance
On the Local
Backup Data page, select the backup data of a VM instance and
choose Restore from the
Actions column. Then, the Recover
Backup Data page is displayed.
On the displayed page,
set the following parameters:
Recovery Policy: Select a recovery
policy.
The following two policies are available:
New Resource:
If you choose
this policy, set the following parameters:
Name: Set a name for
the VM instance.
Description: Optional.
Enter a description for the VM instance.
Instance Offering:
Select an instance offering for the VM
instance.
Network Configuration:
Select a network for the VM instance.
Recover Volume Data:
Choose whether to recover the volume data.
Note: If
the selected backup data is the whole backup data
of the VM instance, you can restore the VM
instance with its volumes to the local server.
This helps ensure the data consistency.
Advanced Settings:
Primary Storage:
Optional. Specify a primary storage for the root
volumes of the VM instance.
Note:
When you restore the backup data of a VM
instance that uses a SharedBlock primary storage,
you need to choose a provisioning method,
including thin provisioning and thick
provisioning.
Thin provisioning: Allocates storage spaces to
VM instances according to the actual usage to
achieve higher storage utilization.
Thick provisioning: Pre-allocates the required
storage space, providing sufficient storage
capacity to VM instances and ensures the storage
performance.
Host: Optional. Specify
a host on which the VM instance is started.
Figure 15. New Resource
Overwrite Original Resource:
If
you choose this policy, set the following
parameters:
Name: The name of the
original resource is displayed.
Description: The
description (if any) of the original resource is
displayed.
Recover Volume Data:
Choose whether to recover the volume data.
Figure 16. Overwrite Original Resource
Note:
Before you can overwrite the original
resource, stop the VM instance first.
If the selected backup data is the whole
backup data of the VM instance, you can restore
the VM instance with its volumes to the local
server. This helps ensure the data
consistency.
Restore an elastic baremetal instance
On the Local Backup
Data page, select the backup data of an elastic baremetal
instance and choose Restore from the
Actions column. Then, the Recover
Backup Data page is displayed.
On the displayed page,
set the following parameters:
Recovery Policy: Select a recovery
policy.
The following two policies are available:
New Resource:
If you choose
this policy, set the following parameters:
Name: Set a name for
the elastic baremetal instance.
Description: Optional.
Enter a description for the elastic baremetal
instance.
Elastic Baremetal
Cluster: Select a cluster where the
instance resides. If left blank, the system
automatically assign a cluster,
Creation Mode: Select
an instance creation mode. Supports Add By
Baremetal Node and Add By Baremetal
Offering.
Baremetal Node/Baremetal
Offering: According to the selected
creation mode, select a baremetal node or offering
to create the instance.
Power Off to Release Baremetal
Node: If enabled, when the elastic
baremetal instances is stopped, the baremetal node
will be automatically released and then can be
used by another elastic baremetal instance to
avoid idle resources.
Primary Storage: Select
a primary storage for the instance.
Recover Volume Data:
Choose whether to recover the volume data.
Note: If
the selected backup data is the whole backup data
of the elastic baremetal instance, you can restore
the instance with its volumes to the local server.
This helps ensure the data consistency.
Advanced Settings:
Gateway Node Allocation
Policy: Select a gateway node
allocation policy.
First Assigned Gateway
Node: Optional. Select a gateway node
for the first startup of the elastic baremetal
instance. If you do not specify a gateway node,
the gateway node selected based on the gateway
node allocation policy is used. This option takes
effect only on the first start-up of the elastic
baremetal instance. Afterwards, gateway nodes are
assigned based on the gateway node allocation
policy.
Figure 17. New Resource
Overwrite Original Resource:
If
you choose this policy, set the following
parameters:
Name: The name of the
original resource is displayed.
Description: The
description (if any) of the original resource is
displayed.
Recover Volume Data:
Choose whether to recover the volume data.
Note:
Before you can overwrite the original
resource, stop the elastic baremetal instance
first.
If the selected backup data is the whole
backup data of the instance, you can restore the
VM instance with its volumes to the local server.
This helps ensure the data consistency.
Restore a volume
On the Local Backup
Data page, select the backup data of a volume and choose
Restore from the Actions
column. Then, the Recover Backup Data page is
displayed.
On the displayed page, set the following parameters:
Recovery Policy: Select a recovery
policy.
The following two policies are available:
New Resource:
If you choose
this policy, set the following parameters:
Name: Set a name for
the volume.
Description: Optional.
Enter a description for the volume.
VM Instance: Select a
VM instance to which the volume is to be attached.
Note:
When you restore the backup data of a volume
that uses a SharedBlock primary storage, you need
to choose a provisioning method, including thin
provisioning and thick provisioning.
Thin provisioning: Allocates storage spaces to
volumes according to the actual usage to achieve
higher storage utilization.
Thick provisioning: Pre-allocates the required
storage space, providing sufficient storage
capacity to volumes and ensures the storage
performance.
Primary Storage: The
primary storage used by the VM instance is
displayed.
VirtIO SCSI: Choose
whether to create VirtIO SCSI data volumes. By
default, this checkbox is not selected.
Note: If
you are using a LocalStorage primary storage, we
recommend that you do not use VirtIO SCSI data
volumes.
Figure 18. New Resource
Overwrite Original Resource:
If
you choose this policy, you do not need to make any
settings.
Name: The name of the
original resource is displayed.
Description: The
description (if any) of the original resource is
displayed.
Figure 19. Overwrite Original Resource
Restore a database
Assume that the original ZStack CloudPrivate Cloud exists and you want to restore the
database from the local backup data to overwrite the original one.
Make sure that the global setting
Database Recovery from Backup Data is enabled.
On
the main menu of ZStack Cloud, choose Settings > Global Setting > Advanced > Platform O&M > Backup Management and set Database Recovery from Backup
Data to true. This allows you to restore a
database from the backup data.
On the Database tab page, select the
specified backup data and choose Restore
from the Actions column.
In the displayed Recover Database dialog
box, enter the root password. The initial password is
zstack.mysql.password.Figure 20. Recover Database
Note:
Restoring the database restarts the management node,
during which time the management interface cannot be
used.
This process usually takes a few minutes without
affecting your business resources.
If you deleted a resource (such as a VM instance or
volume) after the backup point, the deleted resource
will become invalid and its data cannot be restored.
You can clean up the invalid data manually.
The system restores the database.Figure 21. Restoring Database
The database is restored successfully. You
can click Relogin to log in to the Cloud
again.Figure 22. Database Restored Successfully
Note: After the database is restored, all resources of the
Cloud are back to the original state before the backup. You
can click Scan Backup Data in the
local backup server page to obtain the actual backup data
information.
Assume that the original ZStack CloudPrivate Cloud does not exist and you want to restore
the database from the local backup data to build a new Cloud.
Log in to the system. Then, the
Welcome to use our Cloud page is
displayed. Choose Restore Backup Data > Restore.
Figure 23. Restore Backup Data
Prepare the server.
On the Prepare Server
page, set the following parameters:
Backup Server IP: Enter the
IP address of the local backup server.
URL: Enter the URL of the
storage mounted to the local backup server. For
example, /mnt/xxx_ds.
Note: The
backup data of the database is stored in the
storage of the URL.
SSH Port: Enter the SSH port.
Default: 22.
User Name: Enter the user
name. Default: root.
Password: Enter the
password.
Figure 24. Prepare Server
Prepare backup data.
On the
Prepare Backup Data page, set the
following parameters:
Database Backup Data: Select
the backup data of the database to restore.
Figure 25. Prepare Backup Data
Note:
The system will detect the number of the licensed
hosts (CPU cores). You need to select the
appropriate database backup data to restore. You can
also update the license to increase the licensed
quota to avoid the management node start failure due
to insufficient licensed quota.
In the displayed Recover
Database dialog box, enter the root password. The
initial password is zstack.mysql.password.
Figure 26. Restore Database
Note:
Restoring the database restarts the management node,
during which time the management interface cannot be
used.
This process usually takes a few minutes without
affecting your business resources.
If you deleted a resource (such as a VM instance or
volume) after the backup point, the deleted resource
will become invalid and its data cannot be restored.
You can clean up the invalid data manually.
The system restores the database.Figure 27. Restoring Database
The database is restored successfully. You
can click Relogin to log in to the Cloud
again.Figure 28. Database Restored Successfully
Note: After the database is
restored, all resources of the Cloud are back to the
original state before the backup. You can click
Scan Backup Data in the local
backup server page to obtain the actual backup data
information.
Note:
If the management node fails to start due to insufficient
licensed quota, a pop up window will be displayed, prompting
you to increase the licensed quota and then restore the
database.
Here are some notices on the business recovery in a
newly-built data center:
If the network topology and storage architecture of
the new data center are the same as those of the
original one, the business will be recovered after
all hardware resources (such as hosts and primary
storages) are successfully reconnected.
If the network topology and storage architecture of
the new data center are different from those of the
original one, you can recover your business by
adding a new host and rebuilding a network
topology.
Synchronize Local Backup Data to a Remote Server
You can synchronize the backup data of local VM instances, volumes, and databases to
a remote backup server.
Note: Before you can synchronize data to a remote server, add
a remote backup server to ZStack CloudPrivate Cloud. Note that you can add only one remote backup
server. For information about how to add a remote backup server, see Remote Backup Server.
Delete Local Backup Data
You can delete the local backup data of local VM instances, volumes, and
databases.
Note: By default, only the local backup data is deleted. To delete the
backup data in the remote backup server, select Delete Also Data on Remote
Backup Server.
Scan Database Backup
You can scan the local backup server to obtain the database backup data on the local
backup server.
Note: For a newly added local backup server, you can manually scan the
database backup to ensure that the records of the local backup data of the
database in the local backup server are consistent with the local
records.
Export Backup Data of a Local Database
On the Local Backup Data page, select a backup data and choose
Export from the Actions column.
Then, you can export the backup data of the database.Figure 29. Database Backup Exported Successfully
Local Backup Server
On the main menu of ZStack Cloud, choose Platform O&M > Backup Management > Backup Server > Local Backup Server. On the Local Backup Server page, click
Add Local Backup Server. Then, the Add Local Backup
Server page is displayed.
You can add a local backup server by using one of the following
methods:
Use an existing image storage.
Add a new server.
Use an Existing Image Storage
On the displayed page, set the following parameters:
Zone: By default, the current zone is displayed.
Addition Method: Select
Existing Image Storage.
Image Storage: Add an image storage. Only ImageStore
image storage are supported.
Note: Make sure that the image storage uses an
operating system consistent with that of the management
node.
Backup Network: Enter the backup
network CIDR.
Note:
If you deployed a network dedicated to local backup, you can add
the network to the Cloud directly.
In local backup scenarios, this backup network is used for VM,
volume, and database backing up and recovery, CDP task creation,
and CDP data recovery.
Using a dedicated network can avoid network congestions and
improve the transmission efficiency.
Backup Data: Optional. Choose whether to scan the
existing backup data.
Note: Deleted backup data cannot be restored by this
operation.
Figure 30. Add Existing Image Storage
Add a New Server
On the displayed page, set the following parameters:
Zone: By default, the current zone is displayed.
Addition Method: Select
Add Server to add a new server.
Name: Enter a name for the local
backup server.
The name must be 1 to 128 characters in length and can
contain Chinese characters, letters, digits, spaces, hyphens (-), underscores
(_), periods (.), parenthesis (), colons (:), and plus signs (+) and cannot
begin or end with spaces.
Description: Optional. Enter a
description for the local backup server.
Backup Server IP: Enter the IP
address of the local backup server.
Note:
You need to prepare a new storage server in the local data
center as a local backup server.
Make sure that the backup server uses an operating system
consistent with that of the management node.
Mount Path: Enter the path to
which the storage is mounted, for example,
/mnt/xxx_ds.
SSH Port: Enter the SSH port.
Default: 22.
User Name: Enter the user name.
Default: root.
Password: Enter the
password.
Backup Network: Enter the backup
network CIDR.
Note:
If you deployed a network dedicated to local backup, you can add
the network to the Cloud directly.
In local backup scenarios, this backup network is used for VM,
volume, and database backing up and recovery, CDP task creation,
and CDP data recovery.
Using a dedicated network can avoid network congestions and
improve the transmission efficiency.
Backup Data: Choose whether to
scan the existing backup data.
Note: Deleted backup data cannot be restored
by this operation.
Figure 31. Add Server
Manage a Local Backup Server
On the main menu of ZStack Cloud, choose Platform O&M > Backup Management > Backup Server > Local Backup Server. Then, the Local Backup Server page is
displayed.
The following table lists the actions that you can perform on a local
backup server.
Action
Description
Add Local Backup Server
Use an existing image storage (ImageStore only)
as the local backup server or add a new server as the local backup
server.
Enable Local Backup Server
Enable a disabled local backup server.
Disable Local Backup Server
Disable an enabled local backup server.
Note:
If you specify only one local backup server for a backup
job, disabling the local backup server will make the
backup job fail.
If you specify more than one local backup server for a
backup job, when you disable the active one, the backup
job will be implemented on the standby one.
Reconnect Local Backup Server
Reconnecting a local backup server will update
the records of the backup data on the local backup server.
Scan Backup Data
Scan the existing backup data in the local backup
server and display the backup data records on the Cloud
platform.
Note: Deleted backup data cannot be restored by the
scan action.
Cleanup Data
Clean up the invalid backup data and expired
temporary data that have been completely deleted from the local
backup server to free up the storage space.
Update Password
Change the password of a local backup
server.
Delete Local Backup Server
Delete a local backup server.
Note: Deleting a
local backup server will stop the backup jobs and CDP tasks on the server. Please exercise
caution.
Remote Backup Server
On the main menu of ZStack Cloud, choose Platform O&M > Backup Management > Backup Server > Remote Backup Server. On the Remote Backup Server page, click
Add Remote Backup Server. Then, the Add Remote
Backup Server page is displayed.
You can add a remote backup server by using one of the following
methods:
Add a remote backup server.
Add an Alibaba Cloud backup server.
Add a remote backup server
On the displayed page, set the following parameters:
Name: Enter a name for the remote backup server. The name must be 1 to 128 characters in length and can
contain Chinese characters, letters, digits, spaces, hyphens (-), underscores
(_), periods (.), parenthesis (), colons (:), and plus signs (+) and cannot
begin or end with spaces.
Description: Optional. Enter a description for the
remote backup server.
Type: select Remote Backup
here.
Zone: Select the zone to which the remote backup
server is mounted.
Backup Server IP: Enter the IP address of the remote
backup server.
Note:
You need to prepare a new storage server in the remote data
center as a remote backup server.
Make sure that the backup server uses an operating system
consistent with that of the management node of ZStack Cloud.
Mount Path: Enter the path to which the storage is
mounted, for example, /mnt/remote_ds.
SSH Port: Enter the SSH port. Default: 22.
User Name: Enter the user name. Default: root.
Password: Enter the password.
Figure 32. Add Remote Backup Server
Add an Alibaba Cloud backup server
On the displayed page, set the following parameters:
Name: Enter a name for the Alibaba Cloud backup
server.
The name must be 1 to 128 characters in length and can
contain Chinese characters, letters, digits, spaces, hyphens (-), underscores
(_), periods (.), parenthesis (), colons (:), and plus signs (+) and cannot
begin or end with spaces.
Description: Optional. Enter a description for the
remote backup server.
Type: select Alibaba Cloud
Backup here.
Zone: Select the zone to which the Alibaba Cloud
backup server is mounted.
Backup Server IP: Enter the IP address of the Alibaba
Cloud backup server.
Note:
You need to prepare a new storage server in the Alibaba Cloud as a
remote backup server. Method:
Download the standard backup service image from the official
website of ZStack Cloud.
Create an ECS instance based on the standard image. Note
that a public IP address is required.
Purchase the NAS storage in the Alibaba Cloud console.
Mount the NAS storage to the ECS instance.
Enter the public IP address of the ECS instance as the IP
address of the Alibaba Cloud backup server.
Mount Path: Enter the path to which the NAS storage
is mounted, for example, /mnt/remote_ds.
SSH Port: Enter the SSH port. Default: 22.
User Name: Enter the user name. Default: root.
Password: Enter the password.
Figure 33. Add Alibaba Cloud Backup Server
Remote Backup Data
The remote backup data is the data of the local VM instances, elastic baremetal
instances, volumes, and databases backed up in the remote backup server. You can manage
the remote backup data on the Backup Data tab page of the
Remote Backup Server details page.
The following lists the actions that you can perform on the remote backup data:
View the remote backup data.
Synchronize the remote backup data to a local server.
Delete the remote backup data.
Restore the remote backup data.
Scan the database backup.
Export the backup data of the remote database.
View the Remote Backup Data
On the main menu of ZStack Cloud, choose Platform O&M > Backup Management > Backup Server > Remote Backup Server. Then, the Remote Backup Server page is
displayed. Click on the name of a remote backup server to expand its details page.
On the Backup Data tab page, you can manage the remote backup
data.
Synchronize the Remote Backup Data to a Local Server
You can synchronize the remote backup data of the local VM instances, elastic
baremetal instances, data volumes, and databases to a local server.
Note:
If you added only one local backup server, the remote backup data will
be synchronized to this local backup server.
If you added multiple local backup servers, you need specify a local
backup server and then synchronize the remote backup data to the local
server.
Delete Remote Backup Data
You can delete the remote backup data of local VM instances, elastic baremetal
instances, data volumes, and databases.
Note: Deleting the remote backup data also
deletes the local records of the remote backup data. The actual data is not
affected.
Restore the Remote Backup Data
You can restore the remote backup data of the local VM instances, elastic baremetal
instances, data volumes, or databases to your local server.
Before you can restore the remote backup data to a local server, synchronize
the remote data of the local VM instances, elastic baremetal instances, and
data volumes to the local backup server.
The remote backup data of the database is directly restored to the local
server.
Restore a local VM instance
On the Backup Data tab page of the Remote
Backup Server details page, select the remote backup data
of a VM instance and choose Sync to Local from
the Actions column.
Click on the backup data to expand its details page and choose
Restore from the
Actions column. Then, the Recover
Backup Data page is displayed.
On the Recover Backup Data page, set the following
parameters:
Recovery Policy: Select a recovery
policy.
The following two policies are available:
New Resource:
If you choose
this policy, set the following parameters:
Name: Set a name for
the VM instance.
Description: Optional.
Enter a description for the VM instance.
Instance Offering:
Select an instance offering for the VM
instance.
Network Configuration:
Select a network for the VM instance.
Recover Volume Data:
Choose whether to recover the volume data.
Note: If
the selected backup data is the whole backup data
of the VM instance, you can restore the VM
instance with its volumes to the local server.
This helps ensure the data consistency.
Advanced Settings:
Primary Storage:
Optional. Specify a primary storage for the root
volumes of the VM instance.
Note:
When you restore the backup data of a VM
instance that uses a SharedBlock primary storage,
you need to choose a provisioning method,
including thin provisioning and thick
provisioning.
Thin provisioning: Allocates storage spaces to
VM instances according to the actual usage to
achieve higher storage utilization.
Thick provisioning: Pre-allocates the required
storage space, providing sufficient storage
capacity to VM instances and ensures the storage
performance.
Host: Optional. Specify
a host on which the VM instance is started.
Figure 34. New Resource
Overwrite Original Resource:
If
you choose this policy, set the following
parameters:
Name: The name of the
original resource is displayed.
Description: The
description (if any) of the original resource is
displayed.
Recover Volume Data:
Choose whether to recover the volume data.
Figure 35. Overwrite Original Resource
Note:
Before you can overwrite the original
resource, stop the VM instance first.
If the selected backup data is the whole
backup data of the VM instance, you can restore
the VM instance with its volumes to the local
server. This helps ensure the data
consistency.
Restore an elastic baremetal instance
On the Backup Data tab page of the Remote
Backup Server details page, select the remote backup data
of an elastic baremetal instance, and choose Sync to
Local from the Actions
column.
Click on the backup data to expand its details page, and choose
Restore from the
Actions column. Then, the Recover
Backup Data page is displayed. On the displayed page, set
the following parameters:
Recovery Policy: Select a recovery
policy.
The following two policies are available:
New Resource:
If you choose
this policy, set the following parameters:
Name: Set a name for
the elastic baremetal instance.
Description: Optional.
Enter a description for the elastic baremetal
instance.
Elastic Baremetal
Cluster: Select a cluster where the
instance resides. If left blank, the system
automatically assign a cluster,
Creation Mode: Select
an instance creation mode. Supports Add By
Baremetal Node and Add By Baremetal
Offering.
Baremetal Node/Baremetal
Offering: According to the selected
creation mode, select a baremetal node or offering
to create the instance.
Power Off to Release Baremetal
Node: If enabled, when the elastic
baremetal instances is stopped, the baremetal node
will be automatically released and then can be
used by another elastic baremetal instance to
avoid idle resources.
Primary Storage: Select
a primary storage for the instance.
Recover Volume Data:
Choose whether to recover the volume data.
Note: If
the selected backup data is the whole backup data
of the elastic baremetal instance, you can restore
the instance with its volumes to the local server.
This helps ensure the data consistency.
Advanced Settings:
Gateway Node Allocation
Policy: Select a gateway node
allocation policy.
First Assigned Gateway
Node: Optional. Select a gateway node
for the first startup of the elastic baremetal
instance. If you do not specify a gateway node,
the gateway node selected based on the gateway
node allocation policy is used. This option takes
effect only on the first start-up of the elastic
baremetal instance. Afterwards, gateway nodes are
assigned based on the gateway node allocation
policy.
Figure 36. New Resource
Overwrite Original Resource:
If
you choose this policy, set the following
parameters:
Name: The name of the
original resource is displayed.
Description: The
description (if any) of the original resource is
displayed.
Recover Volume Data:
Choose whether to recover the volume data.
Note:
Before you can overwrite the original
resource, stop the elastic baremetal instance
first.
If the selected backup data is the whole
backup data of the instance, you can restore the
VM instance with its volumes to the local server.
This helps ensure the data consistency.
Restore a volume
On the Backup Data tab page of the Remote
Backup Server details page, select the remote backup data
of a data volume, and choose Sync to Local from
the Actions column.
Click on the backup data to expand its details page, and choose
Restore from the
Actions column. Then, the Recover
Backup Data page is displayed. On the displayed page, set
the following parameters:
Recovery Policy: Select a recovery
policy.
The following two policies are available:
New Resource:
If you choose
this policy, set the following parameters:
Name: Set a name for
the volume.
Description: Optional.
Enter a description for the volume.
VM Instance: Select a
VM instance to which the volume is to be attached.
Note:
When you restore the backup data of a volume
that uses a SharedBlock primary storage, you need
to choose a provisioning method, including thin
provisioning and thick provisioning.
Thin provisioning: Allocates storage spaces to
volumes according to the actual usage to achieve
higher storage utilization.
Thick provisioning: Pre-allocates the required
storage space, providing sufficient storage
capacity to volumes and ensures the storage
performance.
Primary Storage: The
primary storage used by the VM instance is
displayed.
VirtIO SCSI: Choose
whether to create VirtIO SCSI data volumes. By
default, this checkbox is not selected.
Note: If
you are using a LocalStorage primary storage, we
recommend that you do not use VirtIO SCSI data
volumes.
Figure 37. New Resource
Overwrite Original Resource:
If
you choose this policy, you do not need to make any
settings.
Name: The name of the
original resource is displayed.
Description: The
description (if any) of the original resource is
displayed.
Figure 38. Overwrite Original Resource
Restore a database
Assume that the original ZStack CloudPrivate Cloud exists and you want to restore the
database from the remote backup data to overwrite the original one.
Make sure that the global setting
Database Recovery from Backup Data is enabled.
On
the main menu of ZStack Cloud, choose Settings > Global Setting > Advanced > Platform O&M > Backup Management and set Database Recovery from Backup
Data to true. This allows you to restore a
database from the backup data.
On the Backup Data tab page of the
Remote Backup Server details page,
select the remote backup data of a database, and choose
Restore from the
Actions column. In the displayed
Recover Database dialog box, enter the
root password. The initial password is
zstack.mysql.password.Figure 39. Recover Database
Note:
Restoring the database restarts the management node,
during which time the management interface cannot be
used.
This process usually takes a few minutes without
affecting your business resources.
If you deleted a resource (such as a VM instance or
volume) after the backup point, the deleted resource
will become invalid and its data cannot be restored.
You can clean up the invalid data manually.
The system restores the database.Figure 40. Restoring Database
The database is restored successfully. You
can click Relogin to log in to the Cloud
again.Figure 41. Database Restored Successfully
Note: After the database is restored, all resources of the
Cloud are back to the original state before the backup. You
can click Scan Backup Data in the
local backup server page to obtain the actual backup data
information.
Assume that the original ZStack CloudPrivate Cloud does not exist and you want to restore
the database from the remote backup data to build a new Cloud.
Log in to the system. Then, the
Welcome to use our Cloud page is
displayed. Choose Restore Backup Data > Restore.
Figure 42. Restore Backup Data
Prepare the server.
On the Prepare Server
page, set the following parameters:
Backup Server IP: Enter the
IP address of the remote backup server.
Note: Make
sure that the backup data of the database in the
remote backup server is intact.
URL: Enter the URL of the
storage mounted to the remote backup server. For
example,
/mnt/remote_ds.
Note: The
backup data of the database is stored in the
storage of the URL.
SSH Port: Enter the SSH port.
Default: 22.
User Name: Enter the user
name. Default: root.
Password: Enter the
password.
Figure 43. Prepare Server
Prepare backup data.
On the
Prepare Backup Data page, set the
following parameters:
Database Backup Data: Select
the backup data of the database to restore.
Figure 44. Prepare Backup Data
Note:
The system will detect the number of the licensed
hosts (CPU cores). You need to select the
appropriate database backup data to restore. You can
also update the license to increase the licensed
quota to avoid the management node start failure due
to insufficient licensed quota.
In the displayed Recover
Database dialog box, enter the root password. The
initial password is zstack.mysql.password.
Figure 45. Restore Database
Note:
Restoring the database restarts the management node,
during which time the management interface cannot be
used.
This process usually takes a few minutes without
affecting your business resources.
If you deleted a resource (such as a VM instance or
volume) after the backup point, the deleted resource
will become invalid and its data cannot be restored.
You can clean up the invalid data manually.
The system restores the database.Figure 46. Restoring Database
The database is restored successfully. You
can click Relogin to log in to the Cloud
again.Figure 47. Database Restored Successfully
Note: After the database is restored, all resources of the
Cloud are back to the original state before the backup. You
can click Scan Backup Data in the
local backup server page to obtain the actual backup data
information.
Note:
If the management node fails to start due to insufficient
licensed quota, a pop up window will be displayed, prompting
you to increase the licensed quota and then restore the
database.
Here are some notices on the business recovery in a
newly-built data center:
If the network topology and storage architecture of
the new data center are the same as those of the
original one, the business will be recovered after
all hardware resources (such as hosts and primary
storages) are successfully reconnected.
If the network topology and storage architecture of
the new data center are different from those of the
original one, you can recover your business by
adding a new host and rebuilding a network
topology.
Scan Database Backup
You can scan the remote backup server to obtain the database backup data on the
remote backup server.
Note: For a newly added remote backup server, you can manually
scan the database backup to ensure that the records of the remote backup data of
the database in the remote backup server are consistent with the local
records.
Typical Practices
This chapter includes scenarios of local backup practice, remote backup practice, and
Public Cloud backup practice.
Local Backup Practice
About this task
Assume that you have deployed the latest ZStack Cloud
environment on local and purchased both the Base License and the Plus License of
Backup Service. Now, you plan to add a local backup server to backup VM instances
with non-shared volumes. Assume that the data is backed up to a local backup server,
and the service VM instance is mistakenly expunged, causing Web service interruption
(http://192.168.1.1) and data loss. After you have recovered the data
from the local backup server, the service and data are both back to normal.
The following table lists an example of a local backup server configurations.
Local Backup Server
Configuration
Backup Server IP
192.168.0.1
Mount Path
/local_ds
SSH Port
22
User Name
root
Password
password
Backup Network
192.168.0.0/24
Follow these steps to run your local backup practice:
Add a local backup server.
Create a backup job.
Check the local backup data and the service state.
Expunge the VM instance by mistake.
Recover the backup data of VM instance and volume to local.
Validate whether the service is recovered.
Procedure
Add a local backup server.
On the main menu of ZStack Cloud,
choose Platform O&M > Backup Management > Backup Server > Local Backup Sever. On the Local Backup Sever page, click
Add Local Backup Sever. Then, the Add
Local Backup Sever page is displayed.
On the displayed page, set the following parameters:
Zone: By default, the current zone is
displayed.
Addition Method: In this
scenario, select Add Server.
Name: Enter a name for the local backup
server.
Description: Optional.
Enter a description for the local backup server.
Backup Server IP: Enter the IP address of the
local backup server. In this scenario, enter
192.168.0.1.
Note: Make sure that the backup server uses
an operating system consistent with that of the management
node.
Mount Path: Enter the path to which the
storage is mounted. In this scenario, enter
/local_ds.
SSH Port: Enter the SSH
port. Default: 22.
User Name: Enter the user
name. Default: root.
Password: Enter the
password of the corresponding user. In this scenario, enter
password.
Backup Network: Optional. Set the backup
network. In this scenario, enter 192.168.0.0/24.
Backup Data: Choose whether to scan the
existing backup data. In this scenario, unselect the checkbox.
Figure 48. Add Local Backup Server
Create a backup job.
On the main menu of ZStack Cloud,
choose Platform O&M > Backup Management > Backup Service > Backup Job. Then the Backup Job page appears. On
the page, choose VM Instance > Create Backup Job. Then, the Create Backup Job page is
displayed.
To create a backup job, follow these four steps:
Set basic information.
Name: Enter a name for the backup
job.
Description: Optional. Enter a
description for the backup job.
Local Backup Server:
Specify one or two local backup servers. In this scenario,
select a local backup server that you added in step1.
Sync to Remote Backup
Server: Choose whether to sync local backup data
to a remote backup server. In this scenario, we do not enable
this option.
Set QoS: Optional. You can set network
QoS and disk QoS for the backup job. In this scenario, we do not
set QoS for the backup job.
Figure 49. Set Basic Information
Select backup resource.
VM Instance: Select one or more VM
instances that you need to back up. In this scenario, select
your service VM instance.
Back up Attached Volume: You can back up
all volumes that are attached to the selected VM instances. In
this scenario, enable this option.
Figure 50. Select Backup Resource
Set backup policy.
Backup Mode: Select a backup mode for a
backup job. In this scenario, select Incremental
Backup + Default Full Backup.
Incremental Backup
Policy: Customize an incremental backup
policy.
Backup Cycle: Select
Backup by Week and
Mon in this scenario.
Execution Time: Set
00:00:00 in this
scenario.
Schedule Effective Time: Choose
whether to schedule the time when the backup job takes
effect. In this scenario, we do not enable this
option.
Backup Immediately: Choose whether to
back up data immediately after the backup job is created. In
this scenario, select the checkbox.
Local Retention Policy: Set the policy
how the local backup data is reserved. In this scenario, retain
only the latest 5 backups generated.
Figure 51. Set Backup Policy
Preview.
Preview the backup job. You can modify the configuration of the
backup job by clicking the Edit icon.
Figure 52. Preview
Check the local backup data and the service state.
Check the local backup data of the VM instance.
On the main menu of ZStack Cloud, choose Platform O&M > Backup Management > Backup Service > Local Backup Data. Then, the Local Backup Data
page is displayed. You can check the service VM instance backup
data.
Figure 53. VM Instance Backup Data
Check the service state.
Use a browser to access to the Web service URL and confirm that the
VM instance can normally provide Web service and the data is
normal.
Figure 54. Web Service
Expunge the VM instance by mistake.
Assume that you mistakenly expunge the service VM instance causing Web
service interruption.
Figure 55. Web Service Interruption
Recover the backup data of VM instance and volume to local.
On the main menu of ZStack Cloud,
choose Platform O&M > Backup Management > Backup Service > Local Backup Data. On the Local Backup Data page, locate
the backup data of the mistakenly expunged VM instance and click Actions > Restore. Then, the Recover Backup Data page is
displayed.
On the displayed page, set the following parameters:
Recover Policy: In this scenario, select
New Resource.
Name: Enter a name for the new resource.
Description: Optional. Enter a description
for the new resource.
Instance Offering: Select an existing
instance offering.
Network Configuration: Configure the network
resources and network services for the VM instance.
Network: Select an L3 network for the
VM instance. In this scenario, select flat network.
Make Default: Set one of the networks
as the default network of the VM instance.
Specify IP:
Optional. Choose whether to specify an IP address to the VM
instance. In this scenario, specify 192.168.1.1.
Specify MAC Address: Optional. Choose
whether to customize a MAC address for the VM instance.
Security Group: Optional. Associate
an existing security group with the VM instance.
Recover Volume Data: Optional. Choose whether
to recover the data of the volume that attached to the VM instance.
In this scenario, enable this option.
Advanced Settings: Optional. Configure
advanced policies for recovering backup data. In this scenario, we
do not specify advanced settings.
Figure 56. Recover Backup Data
Validate whether the service is recovered.
Use a browser to access to the Web service URL and confirm that the VM
instance can normally provide Web service and the data is normal.
Figure 57. Web Service
What to do next
So far, we have introduced the typical practice of the local backup scenario.
Remote Backup Practice
About this task
Assume that you have deployed the latest ZStack Cloud
environment on local and purchased both the Base License and the Plus License of
Backup Service. Now, you plan to add a local backup server and a remote backup
server to backup a service VM instance with non-shared volumes. The data is backed
up to the local backup server and synced to the remote backup server in Zone-1.
Assume that you have mistakenly expunged a service VM instance causing Web service
interruption (http://192.168.1.1) and data loss. In addition, the local
backup server is destroyed, so you have to recover backup data from the remote
backup server. After data is recovered, both the service and data are back to
normal.
Figure 58. Remote Backup Scenario Typology
The following tables list the examples of a local backup server and remote backup
server configurations.
Local Backup Server
Configuration
Backup Server IP
192.168.0.1
Mount Path
/local_ds
SSH Port
22
User Name
root
Password
password
Backup Network
192.168.0.0/24
Remote Backup Server
Configuration
Backup Server IP
172.20.0.1
Mount Path
/remote_ds
SSH Port
22
User Name
root
Password
password
Follow these steps to run your remote backup practice:
Add backup servers.
Create a backup job.
Check the state of local backup data, remote backup data, and the
service.
Expunge the VM instance by mistake.
Recover VM instance/volume backup data.
Validate whether the service is recovered.
Procedure
Add backup servers.
Add a local backup server.
On the main menu of ZStack Cloud,
choose Platform O&M > Backup Management > Backup Server > Local Backup Sever. On the Local Backup Sever page, click
Add Local Backup Sever. Then, the Add
Local Backup Sever page is displayed.
On the displayed page, set the following parameters:
Zone: By default, the current zone is
displayed.
Addition Method: In this
scenario, select Add Server.
Name: Enter a name for the local backup
server.
Description: Optional.
Enter a description for the local backup server.
Backup Server IP: Enter the IP address of the
local backup server. In this scenario, enter
192.168.0.1.
Note: Make sure that the backup server uses
an operating system consistent with that of the management
node.
Mount Path: Enter the path to which the
storage is mounted. In this scenario, enter
/local_ds.
SSH Port: Enter the SSH
port. Default: 22.
User Name: Enter the user
name. Default: root.
Password: Enter the
password of the corresponding user. In this scenario, enter
password.
Backup Network: Optional. Set the backup
network. In this scenario, enter 192.168.0.0/24.
Backup Data: Choose whether to scan the
existing backup data. In this scenario, unselect the checkbox.
Figure 59. Add Local Backup Server
Add a remote backup server.
On the main menu of ZStack Cloud, choose Platform O&M > Backup Management > Backup Server > Remote Backup Sever. On the Remote Backup Sever
page, click Add Remote Backup Sever. Then, the
Add Remote Backup Sever page is
displayed.
On the displayed page, set the following
parameters:
Name: Enter a name for the remote
backup server.
Description: Optional. Enter a
description for the remote backup server.
Type: Select Remote
Backup in this scenario.
Zone: Select the zone to which the
remote backup server is mounted. In this scenario, select
ZONE-1.
Backup Server IP: Enter the IP
address of the remote backup server. In this scenario, enter
172.20.0.1.
Note: Make sure that the backup server
uses an operating system consistent with that of the
management node of ZStack Cloud.
Mount Path: Enter the path to which
the storage is mounted. In this scenario, enter
/remote_ds.
SSH Port: Enter the SSH port.
Default: 22.
User Name: Enter the user name.
Default: root.
Password: Enter the password. In this
scenario, enter password.
Figure 60. Add Remote Backup Server
Create a backup job.
On the main menu of ZStack Cloud,
choose Platform O&M > Backup Management > Backup Service > Backup Job. Then the Backup Job page appears. On
the page, choose VM Instance > Create Backup Job. Then, the Create Backup Job page is
displayed.
To create a backup job, follow these four steps:
Set basic information.
Name: Enter a name for the backup
job.
Description: Optional. Enter a
description for the backup job.
Local Backup Server:
Specify one or two local backup servers. In this scenario,
select a local backup server that you added in step1.
Sync to Remote Backup
Server: Choose whether to sync local backup data
to a remote backup server. In this scenario, enable this
option.
Remote Backup Server: Select the remote
backup server that you added in step 1.
Set QoS: Optional. You can set network
QoS and disk QoS for the backup job. In this scenario, we do not
set QoS for the backup job.
Figure 61. Set Basic Information
Select backup resource.
VM Instance: Select one or more VM
instances that you need to back up. In this scenario, select
your service VM instance.
Back up Attached Volume: You can back up
all volumes that are attached to the selected VM instances. In
this scenario, enable this option.
Figure 62. Select Backup Resource
Set backup policy.
Backup Mode: Select a backup mode for a
backup job. In this scenario, select Incremental
Backup + Default Full Backup.
Incremental Backup
Policy: Customize an incremental backup
policy.
Backup Cycle: Select
Backup by Week and
Mon in this scenario.
Execution Time: Set
00:00:00 in this
scenario.
Schedule Effective Time: Choose
whether to schedule the time when the backup job takes
effect. In this scenario, we do not enable this
option.
Backup Immediately: Choose whether to
back up data immediately after the backup job is created. In
this scenario, select the checkbox.
Local Retention Policy: Set the policy
how the local backup data is reserved. In this scenario, retain
only the latest 5 backups generated.
Remote Retention Policy: Set the policy
how the remote backup data is reserved. In this scenario, retain
only the latest 5 backups generated.
Figure 63. Set Backup Policy
Preview.
Preview the backup job. You can modify the configuration of the
backup job by clicking the Edit icon.
Figure 64. Preview
Check the state of local backup data, remote backup data, and the
service.
Check the local backup data of the VM instance.
On the main menu of ZStack Cloud, choose Platform O&M > Backup Management > Backup Service > Local Backup Data. Then, the Local Backup Data
page is displayed. You can check the service VM instance backup
data.
Figure 65. VM Instance Backup Data
Check the remote backup data of the VM instance.
On the main menu of ZStack Cloud, choose Platform O&M > Backup Management > Backup Server > Remote Backup Server. On the Remote Backup Server
page, click the name of the remote backup server and enter its
details page. On the details page, click Backup
Data. Then, the Backup Data tab
is displayed. You can check the service VM instance backup data.
Figure 66. Remote Backup Server Backup Data
Check the service state.
Use a browser to access to the Web service URL and confirm that the
VM instance can normally provide Web service and the data is
normal.
Figure 67. Web Service
Expunge the VM instance by mistake.
Assume that you mistakenly expunge the service VM instance causing Web
service interruption.
Figure 68. Web Service Interruption
Recover VM instance/volume backup data.
Synchronize backup data from remote backup server to local backup
server.
On the main menu of ZStack Cloud, choose Platform O&M > Backup Management > Backup Server > Remote Backup Server. On the Remote Backup Server
page, click the name of the remote backup server and enter its
details page. On the details page, click Backup
Data. Then, the Backup Data tab
is displayed. On the displayed tab, locate the backup data and click Actions > Sync to Local. On the Select Local Backup
Server drawer, select a local backup server.
Figure 69. Sync to Local
Recover the backup data of VM instance and volume to local.
On the main menu of ZStack Cloud,
choose Platform O&M > Backup Management > Backup Service > Local Backup Data. On the Local Backup Data page, locate
the backup data of the mistakenly expunged VM instance and click Actions > Restore. Then, the Recover Backup Data page is
displayed.
On the displayed page, set the following parameters:
Recover Policy: In this scenario, select
New Resource.
Name: Enter a name for the new resource.
Description: Optional. Enter a description
for the new resource.
Instance Offering: Select an existing
instance offering.
Network Configuration: Configure the network
resources and network services for the VM instance.
Network: Select an L3 network for the
VM instance. In this scenario, select flat network.
Make Default: Set one of the networks
as the default network of the VM instance.
Specify IP:
Optional. Choose whether to specify an IP address to the VM
instance. In this scenario, specify 192.168.1.1.
Specify MAC Address: Optional. Choose
whether to customize a MAC address for the VM instance.
Security Group: Optional. Associate
an existing security group with the VM instance.
Recover Volume Data: Optional. Choose whether
to recover the data of the volume that attached to the VM instance.
In this scenario, enable this option.
Advanced Settings: Optional. Configure
advanced policies for recovering backup data. In this scenario, we
do not specify advanced settings.
Figure 70. Recover Backup Data
Validate whether the service is recovered.
Use a browser to access to the Web service URL and confirm that the VM
instance can normally provide Web service and the data is normal.
Figure 71. Web Service
What to do next
So far, we have introduced the typical practice of the remote backup scenario.
Public Cloud Backup Practice
About this task
Assume that you have deployed the latest ZStack Cloud
environment on local, purchased both the Base License and the Plus License of Backup
Service, and owned an ECS instance on Alibaba Cloud. Now, you plan to add a local
backup server and an ECS instance as the Public Cloud backup
server. The data is backed up to the local backup server and synced to the Public Cloud backup server in Zone-1. Assume that the VM instance
data is mistakenly changed causing Web service data error
(http://192.168.1.1). In addition, the local backup server is destroyed, so
you have to recover data from the Public Cloud backup server.
After data is recovered, both the service and data are back to normal.
Figure 72. Public Cloud Backup Scenario
The following tables list the examples of a local backup server and Public Cloud backup server configurations.
Local Backup Server
Configuration
Backup Server IP
192.168.0.1
Mount Path
/local_ds
SSH Port
22
User Name
root
Password
password
Backup Network
192.168.0.0/24
Public Cloud
Backup Server
Configuration
Backup Server IP
172.20.0.1
Mount Path
/public_ds
SSH Port
22
User Name
root
Password
password
Follow these steps to run your Public Cloud backup practice:
Configure an Alibaba Cloud ECS instance as the Public Cloud backup server.
Add backup servers.
Create a backup job.
Check the state of local backup data, Public Cloud
backup data, and the service.
Mistakenly change the original data.
Recover VM instance backup data.
Validate whether the service is recovered.
Procedure
Configure an Alibaba Cloud ECS instance as a Public Cloud
backup server.
Download a standard backup service image (DR image) from the official
website.
Prepare an Alibaba Cloud VPC. Create an ECS instance with a public
network IP based on the vSwitch in the VPC.
Purchase an NAS storage on Alibaba Cloud Console.
On Alibaba Cloud Console, choose Product and Services > > File Storage NAS and click Buy Now. Set Region,
Zone, Storage Type, Protocol Type, and other information. Then, purchase
the NAS storage.
Attach the NAS storage to the VM instance manually.
Log on to the console of the ECS instance and run following commands
to attach the NAS
storage:
[root@localhost ~]# mkdir /cloud_bs
#Create a mount directory
[root@localhost ~]# mount -t nfs4 xxxxxxxxxx-snp66.cn-shanghai.nas.aliyuncs.com:/ /zstack_bs
#Query the mount path of the NAS on Alibaba Cloud Console. For example, xxxxxxxxxx-snp66.cn-shanghai.nas.aliyuncs.com
#Attach the NAS storage to /cloud_bs
[root@localhost ~]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/vda1 40G 3.7G 34G 10% /
devtmpfs 488M 0 488M 0% /dev
tmpfs 497M 0 497M 0% /dev/shm
tmpfs 497M 50M 447M 11% /run
tmpfs 497M 0 497M 0% /sys/fs/cgroup
tmpfs 100M 0 100M 0% /run/user/0
xxxxxxxxxx-snp66.cn-shanghai.nas.aliyuncs.com:/ 1.0P 292G 1.0P 1% /cloud_bs
Add backup servers.
Add a local backup server.
On the main menu of ZStack Cloud,
choose Platform O&M > Backup Management > Backup Server > Local Backup Sever. On the Local Backup Sever page, click
Add Local Backup Sever. Then, the Add
Local Backup Sever page is displayed.
On the displayed page, set the following parameters:
Zone: By default, the current zone is
displayed.
Addition Method: In this
scenario, select Add Server.
Name: Enter a name for the local backup
server.
Description: Optional.
Enter a description for the local backup server.
Backup Server IP: Enter the IP address of the
local backup server. In this scenario, enter
192.168.0.1.
Note: Make sure that the backup server uses
an operating system consistent with that of the management
node.
Mount Path: Enter the path to which the
storage is mounted. In this scenario, enter
/local_ds.
SSH Port: Enter the SSH
port. Default: 22.
User Name: Enter the user
name. Default: root.
Password: Enter the
password of the corresponding user. In this scenario, enter
password.
Backup Network: Optional. Set the backup
network. In this scenario, enter 192.168.0.0/24.
Backup Data: Choose whether to scan the
existing backup data. In this scenario, unselect the checkbox.
Figure 73. Add Local Backup Server
Add a Public Cloud backup server.
On the main menu of ZStack Cloud, choose Platform O&M > Backup Management > Backup Server > Remote Backup Sever. On the Remote Backup Sever
page, click Add Remote Backup Sever. Then, the
Add Remote Backup Sever page is
displayed.
On the displayed page, set the following parameters:
Name: Enter a name for the remote
backup server.
Description: Optional. Enter a
description for the remote backup server.
Type: Select Alibaba Cloud
Backup in this scenario.
Zone: Select the zone to which the
Alibaba Cloud backup server is mounted. In this scenario,
select ZONE-1.
Backup Server IP: Enter the IP
address of the Alibaba Cloud backup server. In this
scenario, enter 172.20.0.1.
Mount Path: Enter the path to which
the Alibaba Cloud backup server is mounted. In this
scenario, enter /public_ds.
SSH Port: Enter the SSH port.
Default: 22.
User Name: Enter the user name.
Default: root.
Password: Enter the password. In this
scenario, enter password.
Figure 74. Add Alibaba Cloud Backup Server
Create a backup job.
On the main menu of ZStack Cloud,
choose Platform O&M > Backup Management > Backup Service > Backup Job. Then the Backup Job page appears. On
the page, choose VM Instance > Create Backup Job. Then, the Create Backup Job page is
displayed.
To create a backup job, follow these four steps:
Set basic information.
Name: Enter a name for the backup
job.
Description: Optional. Enter a
description for the backup job.
Local Backup Server:
Specify one or two local backup servers. In this scenario,
select a local backup server that you added in step1.
Sync to Remote Backup
Server: Choose whether to sync local backup data
to a remote backup server. In this scenario, enable this
option.
Remote Backup Server: Select the Alibaba
Cloud backup server that you added in step 1.
Set QoS: Optional. You can set network
QoS and disk QoS for the backup job. In this scenario, we do not
set QoS for the backup job.
Figure 75. Set Basic Information
Select backup resource.
Backup Resource: Select the type of
resource that you need to back up. In this scenario, select
VM Instance.
VM Instance: Select one or more VM
instances that you need to back up. In this scenario, select
your service VM instance.
Back up Attached Volume: You can back up
all volumes that are attached to the selected VM instances. In
this scenario, disable this option.
Figure 76. Select Backup Resource
Set backup policy.
Backup Mode: Select a backup mode for a
backup job. In this scenario, select Incremental
Backup + Default Full Backup.
Incremental Backup
Policy: Customize an incremental backup
policy.
Backup Cycle: Select
Backup by Week and
Mon in this scenario.
Execution Time: Set
00:00:00 in this
scenario.
Schedule Effective Time: Choose
whether to schedule the time when the backup job takes
effect. In this scenario, we do not enable this
option.
Backup Immediately: Choose whether to
back up data immediately after the backup job is created. In
this scenario, select the checkbox.
Local Retention Policy: Set the policy
how the local backup data is reserved. In this scenario, retain
only the latest 5 backups generated.
Remote Retention Policy: Set the policy
how the remote backup data is reserved. In this scenario, retain
only the latest 5 backups generated.
Figure 77. Set Backup Policy
Preview.
Preview the backup job. You can modify the configuration of the
backup job by clicking the Edit icon.
Figure 78. Preview
Check the state of local backup data, Public Cloud backup
data, and the service.
Check the local backup data of the VM instance.
On the main menu of ZStack Cloud, choose Platform O&M > Backup Management > Backup Service > Local Backup Data. Then, the Local Backup Data
page is displayed. You can check the service VM instance backup
data.
Figure 79. VM Instance Backup Data
Check the Public Cloud backup data of the VM
instance.
On the main menu of ZStack Cloud, choose Platform O&M > Backup Management > Backup Server > Remote Backup Server. On the Remote Backup Server
page, click the name of the Alibaba Cloud backup server and enter
its details page. On the details page, click Backup
Data. Then, the Backup Data tab
is displayed. You can check the service VM instance backup data.
Figure 80. Public Cloud Backup Server Backup
Data
Check the service state.
Use a browser to access to the Web service URL and confirm that the
VM instance can normally provide Web service and the data is
normal.
Figure 81. Web Service
Mistakenly change the original data.
Assume that you have changed the Web data of the service VM instance by
mistake and delete the backup data in local backup server, which resulting
in abnormal Web display.
Figure 82. Error Data
Recover VM instance backup data.
Synchronize backup data from Alibaba Cloud backup server to local
backup server.
On the main menu of ZStack Cloud, choose Platform O&M > Backup Management > Backup Server > Remote Backup Server. On the Remote Backup Server
page, click the name of the Alibaba Cloud backup server and enter
its details page. On the details page, click Backup
Data. Then, the Backup Data tab
is displayed. On the displayed tab, locate the backup data and click Actions > Sync to Local. On the Select Local Backup
Server drawer, select a local backup server.
Stop service VM instance.
On the main menu of ZStack Cloud, choose Resource Center > Resource Pool > VM Instance. On the VM Instance page, locate
the service VM instance and click Actions > Power > Stop.
Recover VM instance backup data.
On the main menu of ZStack Cloud, choose Platform O&M > Backup Management > Backup Service > Local Backup Data. On the Local Backup Data page,
locate the backup data of the service VM instance and click Actions > Restore. Then, the Recover Backup Data
page is displayed.
On the displayed page, set the following parameters:
Recovery Policy: In this scenario,
select Overwrite Original
Resource.
Name: By default, the original VM
instance name is displayed.
Description: By default, the original
VM instance description is displayed.
Figure 83. Recover Backup Data
Validate whether the service is recovered.
Use a browser to access to the Web service URL and confirm that the VM
instance can normally provide Web service and the data is normal.
Figure 84. Web Service
What to do next
So far, we have introduced the typical practice of the Public Cloud backup scenario.
Glossary
Instance
An instance is a virtual machine or server that runs the images of operating
systems in Cloud, such as VM instance and elastic baremetal
instance.
VM Instance
A VM instance is a virtual
machine instance running on a host. A VM instance has its own IP address and can
access public networks and run application services.
Volume
A volume provides storage space for a VM instance. Volumes
are categorized into root volumes and data volumes.
Root Volume
A root volume provides support for the system operations
of a VM instance.
Data Volume
A data volume provides extended storage space for a VM
instance.
Image
An image is a template file used to create a VM instance
or volume. Images are categorized into system images and volume
images.
Instance Offering
An instance offering defines the number of vCPU cores,
memory size, network bandwidth, and other configuration settings of VM
instances.
Disk Offering
A disk offering defines the capacity and other
configuration settings of volumes.
GPU Specification
A GPU specification defines the frame per second (FPS),
video memory, resolution, and other configuration settings of a physical or virtual
GPU. GPU specifications are categorized into physical GPU specifications and virtual
GPU specifications.
vNUMA Configuration
vNUMA uses CPU pinning to passthrough the topology of
associated host physical NUMA (pNUMA) nodes to a VM instance, generating a topology
of virtual NUMA (vNUMA) nodes for the VM instance. This topology enables a vCPU on a
vNUMA node to primarily access the local memory and thus improves VM
performance.
NUMA (Non-Uniform Memory Access)
Non-uniform memory access (NUMA) is a computer memory
design where the memory access time depends on the memory location relative to the
CPU. Under NUMA, a processor can access its own local memory faster than non-local
memory and thus improves VM performance.
pNUMA Node (physical NUMA Node)
A pNUMA node (physical NUMA node) is a host NUMA node
predefined based on the host NUMA architecture. It is used to manage the CPUs and
memory of the host.
pNUMA Topology (physical NUMA Topology)
A pNUMA topology (physical NUMA topology) is the topology
of the host NUMA nodes predefined by the CPU vendor based on the host NUMA
architecture.
vNUMA Node (virtual NUMA Node)
A vNUMA node (virtual NUMA node) is generated by
passing-through associated pNUMA nodes via CPU pinning. It is used to manage the
CPUs and memory of a VM instance.
vNUMA Topology (virtual NUMA Topology)
A vNUMA topology (virtual NUMA topology) is the topology
of VM NUMA nodes generated by passing-through associated pNUMA nodes via CPU
pinning.
Local Memory
Local memory is the memory that a CPU (pCPU or vCPU)
accesses through the Uncore iMC (Integrated Memory Controller) of the same NUMA
(pNUMA or vNUMA) node. Compared with accessing non-local memory, accessing local
memory has lower latencies.
CPU Pinning
CPU pinning assigns the virtual CPUs (vCPUs) of a VM
instance to specific physical CPUs (pCPUs) of the host, which improves VM
performance.
EmulatorPin Configuration
EmulatorPin assigns all other threads than virtual CPU
(vCPU) threads and IO threads of a VM instance to physical CPUs (pCPUs) of the host
so that these threads run on assigned pCPUs.
Auto-Scaling Group
An auto-scaling group is a group of VM instances that are
used for the same scenarios. An auto-scaling group can automatically scale out or in
based on application workloads or health status of VM instances in the
group.
Snapshot
A snapshot is a point-in-time capture of data status in a
volume.
Affinity Group
A VM scheduling policy is a resource orchestration policy
based on which VM instances are assigned hosts to achieve the high performance and
high availability of businesses.
Zone
A zone is a logical group of resources such as clusters,
L2 networks, and primary storage. Zone is the largest resource scope defined in the
Cloud.
Cluster
A cluster is a logical group of hosts (compute
nodes).
Host
A host provides compute, network, and storage resources
for VM instances.
Primary Storage
A primary storage is one or more servers that store volume
files of VM instances. These files include root volume snapshots, data volume
snapshots, image caches, root volumes, and data volumes.
Image Storage
An image storage is a storage server that stores VM image
templates, including ISO image files.
iSCSI Storage
iSCSI storage is an SAN storage that uses the iSCSI
protocol for data transmission. You can add an iSCSI SAN block as a Shared Block
primary storage or pass through the block to a VM instance.
FC Storage
FC storage is an SAN storage that uses the FC technology
for data transmission. You can add an FC SAN block as a Shared Block primary storage
or pass through the block to a VM instance.
NVMe Storage
A type of storage implemented via the NVMe-oF (NVMe over
fabrics) protocol. You can add a block device configured from an NVMe storage as
SharedBlock primary storage.
L2 Network
An L2 network is a layer 2 broadcast domain used for layer
2 isolation. Generally, L2 networks are identified by names of devices on the
physical network.
VXLAN Pool
A VXLAN pool is a collection of VXLAN networks established
based on VXLAN Tunnel Endpoints (VTEPs). The VNI of each VXLAN network in a VXLAN
pool must be unique.
L3 Network
An L3 network includes IP ranges, gateway, DNS, and other
network configurations that are used by VM instances.
Public Network
Generally, a public network is a logical network that is
connected to the Internet. However, in an environment that has no access to the
Internet, you can also create a public network.
Flat Network
A flat network is connected to the network where the host
is located and has direct access to the Internet. VM instances in a flat network can
access public networks by using elastic IP addresses.
VPC Network
A VPC network is a private network where VM instances can
be created. A VM instance in a VPC network can access the Internet through a VPC
vRouter.
Management Network
A management network is used to manage physical resources
in the Cloud. For example, you can create a management network to manage access to
hosts, primary storage, image storage, and VPC vRouters.
Flow Network
A flow network is a dedicated network for port mirror
transmission. You can use a flow network to transmit the mirrors of data packets of
NIC ports to the target ports.
VPC vRouter
A VPC vRouter is a dedicated VM instance that provides
multiple network services.
VPC vRouter HA Group
A VPC vRouter HA group consists of two VPC vRouters.
Either VPC vRouter can be a primary or secondary VPC vRouter for the group. If the
primary VPC vRouter does not work as expected, the VPC vRouter becomes the secondary
VPC vRouter in the group to ensure high availability of business.
vRouter Image
A vRouter image encapsulates network services and can be
used to create VPC vRouters.
Dedicated-Performance LB Image
A dedicated-performance load balancer (LB) image
encapsulates dedicated-performance load-balancing services and can be used to create
load balancer instances. However, a dedicated-performance load balancer image cannot
be used to create VM instances.
vRouter Offering
A vRouter offering defines the number of vCPU cores,
memory size, image, management network, and public network configuration settings of
VPC vRouters. You can use a vRouter offering to create VPC vRouters that can provide
network services for public networks and VPC networks.
LB Instance Offering
A load balancer (LB) instance offering defines the CPU,
memory, image, and management network configuration settings used to create LB
instances. LB instances provide load balancing services for the public network, flat
network, and VPC network.
SDN Controller
The SDN controller is the core of the SDN architecture,
responsible for centralized management and control of network
devices.
SDN Cluster
A cluster of dedicated VM instances designed to provide highly available SDN capabilities.
SDN Instance
A dedicated VM instance designed to provide SDN network
capabilities.
SDN Image
An SDN image encapsulates an SDN software and can be used
to create SDN instances.
SDN Instance Offering
An SDN instance offering defines the CPU, memory, SDN
image, and management network configuration used for creating SDN
instances.
Security Group
A security group provides security control services for VM
NICs. It filters the ingress or egress TCP, UDP, and ICMP packets of VM NICs based
on the specified security rules.
VIP
In bridged network environments, a virtual IP address
(VIP) provides network services such as serving as an elastic IP address (EIP), port
forwarding, load balancing, IPsec tunneling. When a VIP provides the preceding
network services, packets are sent to the VIP and then routed to the destination
network where VM instances are located.
EIP
An elastic IP address (EIP) functions based on the NAT
technology. IP addresses in a private network are translated into an EIP that is in
another network. This way, private networks can be accessed from other networks by
using EIPs.
Port Forwarding
Port forwarding functions based on the layer-3 forwarding
service of VPC vRouters. This service forwards traffic flows of the specified IP
addresses and ports in a public network to specified ports of VM instances by using
the specified protocol. If your public IP addresses are insufficient, you can
configure port forwarding for multiple VM instances by using one public IP address
and port.
Load Balancer
A load balancer distributes traffic flows of a virtual IP
address to backend servers. It automatically inspects the availability of backend
servers and isolates unavailable servers during traffic distribution. This way, the
load balancer improves the availability and service capability of your
business.
Listener
A listener monitors the frontend requests of a load
balancer and distributes the requests to a backend server based on the specified
policy. In addition, the listener performs health checks on backend
servers.
Forwarding Rule
A forwarding rule forwards the requests from different
domain names or URLs to different backend server groups.
Backend Server Group
A backend server group is a group of backend servers that
handles requests distributed by load balancers. It is the basic unit for traffic
distribution by load balancer instances.
Backend Server
A backend server handles requests distributed by a load
balancer. You can add a VM instance on the Cloud or a server on a third-party cloud
as a backend server.
Frontend Network
A frontend network is a type of network that is associated
with a load balancer. Requests from the network are distributed by the load balancer
to backend servers based on a specified policy.
Backend Network
A backend network is a type of network that is associated
with a load balancer. Requests from frontend networks are distributed by the load
balancer to servers in the backend network.
Load Balancer Instance
A load balancer instance is a custom VM instance used to
provide load balancing services.
Certificate
If you select HTTPS for a listener, associate it with a
certificate to make the listener take effect. You can upload either a certificate or
certificate chain.
Firewall
A firewall is an access control policy that monitors
ingress and egress traffic of VPC vRouters and decides whether to allow or block
specific traffic based on the associated rule sets and rules.
Firewall Rule Set
A firewall rule set is a set of rules that a firewall uses
to defend against network attacks. You need to associate a rule set with the egress
or ingress flow direction of VPC vRouter NICs to make the rule set take
effect.
Firewall Rule
A firewall rule is an access control entry associated with
the egress or ingress flow direction of VPC vRouter NICs to defend against network
attacks. A firewall rule includes rule priority, match condition, and
behavior.
Rule Template
A rule template is a template that you can select when you
add rules to a rule set or a firewall.
IP/Port Set
An IP or port set is a set of IP addresses or ports that
you can select when you add rules to a rule set or a firewall.
IPsec Tunnel
An IPSec tunnel encrypts and verifies IP packets that
transmit over a virtual private network (VPN) from one site to
another.
OSPF Area
An Open Shortest Path First (OSPF) area is divided from an
autonomous system based on the OSPF protocol. This simplifies the hierarchical
management of vRouters.
NetFlow
A NetFlow monitors the ingress and egress traffic of the
NICs of VPC vRouters. The supported versions of data flows are V5 and
V9.
Port Mirroring
Port mirroring mirrors the traffic data of VM NICs and
sends the traffic data to the target ports. This allows for the analysis of data
packets of ports and simplifies the monitoring and management of data traffic and
makes it easier to locate network errors and exceptions.
Route Table
A route table contains information about various routes
that you configure. Route entries in a route table must include the destination
network, next hop, and route priority.
CloudFormation
CloudFormation is a service that simplifies the management
of cloud resources and automates deployment and O&S. You can create a stack
template to configure cloud resources and their dependencies. This way, resources
can be automatically configured and deployed in batches. CloudFormation provides
easy management of the lifecycle of cloud resources and integrates automatic O&S
into API and SDK.
Resource Stack
A resource stack is a stack of resources that are
configured by using a stack template. The resources in the stack have dependencies
with each other. You can manage resources in the stack by managing the resource
stack.
Stack Template
A stack template is a UTF8-encoded file based on which you
can create resource stacks. The stack template defines the resources that you want,
the dependencies between the resources, and the configuration settings of the
resources. When you use a stack template to create a resource stack, CloudFormation
parses the template and the resources are automatically created and
configured.
Sample Template
A sample template is a commonly used resource stack. You
can use a sample template provide by the Cloud to create resource
stacks.
Designer
A designer is a CloudFormation tool that allows you to
orchestrate cloud resources. You can drag and drop resources on a canvas and use
lines to establish dependencies between the resources.
Baremetal Cluster
A baremetal cluster consists of baremetal chassis. You can
manage baremetal chassis by managing a baremetal cluster where the chassis
reside.
Deployment Server
A deployment server is a server that provides PXE service
and console proxy service for baremetal chassis.
Baremetal Chassis
A baremetal chassis is used to create a baremetal instance
and is identified based on the BMC interface and IPMI configuration
setting.
Preconfigured Template
A preconfigured template is used to create a preconfigured
file that allows for unattended batch installation of an operating system for
baremetal instances.
Baremetal Instance
A baremetal instance is an instantiated baremetal chassis.
Elastic Baremetal Management
Elastic Baremetal Management provides dedicated physical
servers for your applications to ensure high performance and stability. In addition,
this feature allows elastic scaling. You can apply for and scale resources based on
your needs.
Provision Network
A provision network is a dedicated network for PXE boot
and image downloads while creating elastic baremetal instances in a gateway proxy
cluster.
Elastic Baremetal Cluster
Provides a separated cluster to manage baremetal
nodes.
Gateway Node
A gateway node is a node where the ingress and egress
traffic of the Cloud and elastic baremetal instances in gateway proxy clusters is
forwarded.
Baremetal Node
A baremetal node is used to create a baremetal instance
and is identified based on the BMC interface and IPMI configuration
setting.
Elastic Baremetal Instance
An elastic baremetal instance has the same performance as
physical servers and allows elastic scaling. You can apply for and scale resources
based on your needs.
Elastic Baremetal Offering
An elastic baremetal offering defines the number of vCPU
cores, memory size, CPU architecture, CPU model, and other configuration settings of
elastic baremetal instances.
vCenter
The Cloud allows you to take over vCenter and manage
resources on the vCenter.
VM Instance
A VM instance is an ESXi virtual machine instance running
on a host. A VM instance has its own IP address to access public networks and can
run application services.
Network
A vCenter network defines the network settings of VM
instances on vCenter, such as IP range, gateway, DNS, and network
services.
Volume
A volume provides storage space for a VM instance on
vCenter. A volume attached to a VM instance can be used as a root volume or data
volume. A root volume provides support for the system operations of a VM instance. A
data volume provides extended storage space for a VM instance.
Image
An image is a template file used to create a VM instance
or volume on vCenter. Images are categorized into system images and volume
images.
Event Message
Event Message displays event alarm messages of vCenter
that is took over by the Cloud. This feature allows you to locate errors and
exceptions efficiently.
Network Topology
A network topology visualizes the network architecture of
the Cloud. It allows for efficient planning, management, and improvement of network
architecture. Network topologies can be categorized into global topologies and
custom topologies.
Performance Analysis
Performance Analysis displays the performance metrics of
key resources monitored externally or internally in the Cloud. You can view the
performance analysis or export the analysis report as needed to improve the O&M
efficiency.
Capacity Management
Capacity Management visualizes the capacities and usages
of key resources in the Cloud. You can use this feature to improve O&S
efficiency.
MN Monitoring
Management Node (MN) monitoring allows you to view the
health status of each management node when you use multiple management nodes to
achieve high availability.
Alarm
An alarm is used to monitor the status of time-series data
and events and respond to the status change. Alarms can be categorized into resource
alarm, event alarm, and extended alarm.
One-Click Alarm
A one-click alarm integrates multiple metrics of a
resource. You can create one-click alarms for multiple resources to monitor these
resources.
Alarm Template
An alarm template is a template of alarm rules. If you
associate an alarm template with a resource group, an alarm is created to monitor
the resources in the group.
Resource Group
A resource group consists of resources grouped based on
your business needs. If you associate an alarm template with a resource group, the
alarm rules specified by the template take effect on all the resources in the
group.
Message Template
A message template specifies the text template of a
resource alarm message or event alarm message sent to an SNS system.
Message Source
A message source is used to take over extended alarm
messages. If you configure alarms for message sources, extended alarm messages can
be sent to various endpoints.
Endpoint
An endpoint is a method that users obtain subscribed
messages. Endpoints are categorized into system endpoints, email, DingTalk, HTTP
application, short message service, and Microsoft Teams.
Alarm Message
An alarm message is a message sent the time when an alarm
is triggered.
Current Task
A current task is an ongoing operation performed in the
Cloud. You can perform centralized management over ongoing
operations.
Operation Log
An operation log is a chronological record of operations
on the specified objects and their operation results.
Audit
Audit monitors and records all activities on the Cloud.
You can use this feature to implement operation tracking, cybersecurity classified
protection compliance, security analysis, troubleshooting, and automatic
O&M.
Log Collection
Allows you to collect with one click the log data from the
Cloud and various nodes on the Cloud generated in the specified time period and
download the log data.
One-Click Inspection
Comprehensively inspects the health status of key
resources and services of the Cloud and scores their healthiness based on the
inspection results. In addition, the one-click inspection service provides O&M
suggestions and inspection reports.
Backup Management
Backup management integrates multiple disaster recovery
technologies such as incremental backup and full backup that are suitable for
multiple business scenarios. You can implement local backup and remote backup based
on your business needs.
Backup Job
You can create a backup job to back up local VM instances,
volumes, or databases to a specified storage server on a regular
basis.
Local Backup Data
Local backup data of VM instances, volumes, and databases
is stored in the local backup server.
Local Backup Server
A local backup server is located at the local data center
and is used to store local backup data.
Remote Backup Server
A remote backup server is located at a remote data center
or a public cloud and is used to store remote backup
data.
Continuous Data Protection (CDP)
Continuous Data Protection (CDP) provides second-level and
fine-grained continuous backups for important business systems in VM instances,
allowing users to restore VM data to a specific time state, and retrieve files
without restoring the system.
CDP Task
You can create a CDP task to continuously back up your VM
data to a specified backup server to achieve continuous data protection and
recovery.
CDP Data
The backup data generated from continuous data protection
on VM instances is stored in local backup servers.
Recovery Point
A recovery point is a data point generated during
continuous data protection. A recovery point corresponds to a data record within the
recovery point interval specified by the user.
Locked Recovery Point
You can lock or unlock a recovery point as needed. After a
recovery point is locked, data of the recovery point will not be automatically
cleared or deleted.
Recovery Task
A recovery task helps you quickly restore data by
specifying a CDP task and recovery point, and allows you to view the recovery
progress and logs in a more friendly way.
Cryptography Security Compliance
The Cryptography Security Compliance service provides
applications with cloud security capabilities based on commercial cryptography,
meeting the requirements of commercial cryptography application security
assessments.
HSM Pool
An HSM pool is a logical group of hardware security
modules (HSMs) and is used to provide unified cryptography services such as
signature validation and encryption.
HSM
A hardware security module (HSM) is a dedicated device
that encrypts, decrypts, and authenticates information by using the cryptographic
technology.
Platform Cryptography Security Compliance
Enables the Cloud to meet the requirements of Cryptography
Security Compliance through the cryptography capabilities provided by HSM
pools.
Certificate Login
Authenticates the identity of a user by using a UKey
device.
Data Protection
Protects important data on the Cloud to ensure the data
confidentiality and integrity.
Scheduled Job
A scheduled job defines that a specific action be
implemented at a specified time based on a scheduler.
Scheduler
A scheduler is used to schedule jobs. It is suitable for
business scenarios that last for a long time.
Tag
A tag is used to mark resources. You can use a tag to
search for and aggregate resources.
Migration Service
The Cloud provides V2V migration service that allows you
to migrate VM instances and data from other virtualized platform to the current
cloud platform.
ZMigrate Migration Service
A migration service installed from
Application Market that migrates VM instances and their data from VMware environments
to the current cloud platform.
V2V Migration
V2V Migration allows you to migrate VM instances from the
VMware or KVM platform to the current cloud platform.
V2V Conversion Host
A V2V conversion host is a host in the destination cluster
that you need to specify during V2V migration to cache VM instances and data when
you implement V2V migration. After the VM instances and data are cached in the
V2Vconversion host, they are migrated to the destination primary
storage.
User
A user is a natural person that constructs the most basic
unit in Tenant Management.
User Group
A user group is a collection of natural persons or a
collection of project members. You can use a user group to grant
permissions.
Role
A role is a collection of permissions that can be granted
to users. A user that assumes a role can call API operations based on the
permissions specified by the role. Roles are categorized into platform roles and
project roles.
Single Sign-On
The Single Sign-On service provided by the Cloud. It supports seamless access to SSO systems. Through the service, related users can directly log in to the Cloud and manage cloud resources.
Project
A project is a task that needs to be accomplished by
specific personnel at a specified time. In Tenant Management, you can plan resources
at the project granularity and allocate an independent resource pool to a project.
The word Tenant in Tenant Management mainly refers to projects. A project is
a tenant.
Project Member
A project member is a member in a project who is granted permissions on
specific project resources and can use the resources to accomplish tasks. Project
members include the project admin, project managers, and normal project
members.
Process Management
Process management is part of ticket management that
manages the processes related to the resources of projects. Processes can be
categorized into default processes and custom processes.
My Approvals
In the Cloud, only the administrator and project
administrators are granted approval permissions. the administrator and project
administrators can approve or reject a ticket. If a ticket is approved, resources
are automatically deployed and allocated to the specified project.
Bills
A bill is the expense of resources totaled at a specified
time period. Billing is accurate to the second. Bills can be categorized into project bills, department bills, and account
bills.
Pricing List
A pricing list is a list of unit prices of different
resources. The unit price of a resource is set based on the specification and usage
time of the resource.
Console Proxy
Console proxy allows you to log in to a VM instance by
using the IP address of a proxy.
AccessKey Management
An AccessKey pair is a security credential that one party
authorizes another party to call API operations and access its resources in the
Cloud. AccessKey pairs shall be kept confidential.
IP Allowlist/Blocklist
An IP allowlist or blocklist identifies and filters IP
addresses that access the Cloud. You can create an IP allowlist or blocklist to
improve access control of the Cloud.
Application Center
Application Market allows you to add applications to the
Cloud and then access the applications with one click. It extends the functionality
of the Cloud. You can add default applications through the built-in installation
package or add more applications through URLs.
Sub-Account Management
A sub-account can be created by the admin or synced from
an SSO authentication system and is managed by the admin. Resources created under a
sub-account are managed by the sub-account.
Theme and Appearance
You can customize the theme and appearance of the
Cloud.
Email Server
If you select Email as the endpoint of an alarm, you need
to set an email server. Then alarm messages are sent to the email
server.
Log Server
A log server is used to collect management node logs or
the platform operation logs. You can add a log server to the cloud and use the
collected logs for operation trace or troubleshooting. This makes your O&M more
efficient.
Global Setting
Global Setting allows you to configure settings that take
effect on the whole platform.
Scenario Template
Scenario Template provides multiple templates that
encapsulate scenario-based global settings. You can apply a template globally with
one click based on your business needs. This improves your O&M
efficiency.
HA Policy
HA Policy is a mechanism that ensures sustained and stable
running of the business if VM instances are unexpectedly stopped or are errored
because of errors occurring to compute, network, or storage resources associated
with the VM instances. By enabling this feature, you can customize VM HA policies to
ensure your business continuity and stability.
Time Management
Manages the Cloud system time and allows you to configure
time servers for the Cloud. After you configure NTP time servers for the Cloud, the
clock of the time servers is synced with all nodes of the Cloud.
GPU Device
A GPU device is a powerful microprocessor with high
computational capabilities. You can use a GPU device to handle intricate graphics
rendering and parallel computing jobs, thus improving the efficiency of businesses
such as graphic production, video processing, and machine learning.
Script Library
The script library stores and manages script files
centrally. By executing scripts on VM instances, you can complete complex O&M
operations and automated jobs.
XML Hook
An XML Hook is a script that can flexibly insert or modify
parameters in XML files of VM instances. By attaching an XML Hook to a VM instance,
you can customize VM configurations and enable specialized
functionalities.
Container Service
A simple and user-friendly container management service,
providing features like GPU management & scheduling, multi-tenancy,
multi-cluster, quota configuration, CI/CD. and microservice. The service reduces the
container using complexity and aligns well with traditional user's habits, helping
you easily manage and deploy your container cluster, and enjoy the benefits of
cloud-native technologies in a quick and convenient way.
Advanced Monitoring Server
An advanced monitoring server is a dedicated VM instance
used to receive advanced monitoring data of load balancers and other
resources.
Advanced Monitoring Server Image
An advanced monitoring server image encapsulates the
advanced monitoring service and can be used to create advanced monitoring
server.
Advanced Monitoring Server Offering
An advanced monitoring server offering defines the CPU
cores, memory size, image, management network, and public network configurations of
advanced monitoring server. You can use an advanced monitoring server offering to
create advanced monitoring servers.
Plugin Management
You can package extended resources or tools into
standardized plugins for quick installation and integration, expanding the Cloud
capabilities.
Region Management
A region is a self-contained cloud environment with
independent management node(s), networks, hardware, and cloud resources. ZStack IAM
enabled user synchronization and SSO across multiple regions.
Note: If
you have the Tenant Management Plus license at the same time, the project
members (project managers, project admins, and general project members) can
perform local backup for VM instances, elastic baremetal instances, and data
volumes in the project.
