Backup Service

ZStack 3.10.0>Product Manuals>Maintenance Manual>Advanced Function (Plus)>Backup Service

Backup Service, which is business-centered, integrates the scheduled incremental backup, scheduled full backup, and other backup technologies to ZStack Private Cloud. With Backup Service, multiple backup solutions are supported, such as local backup, remote backup, and Public Cloud backup solutions. Select an appropriate backup solution according to your own business needs.

Backup Service is a separate feature module. To use this service, purchase both the Base License and the Plus License of BareMetal Management. 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.

Local Backup
A local ImageStore backup storage can act as the Local Backup Storage to store scheduled backup data of the local VM instances, volumes, and management node databases. Meanwhile, the seamless switchover between the master local backup storage and the standby local backup storage 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 storage, 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 storage 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 Storage to store the scheduled backup data of the local VM instances, volumes, and databases. The backup data needs to be synchronized to the remote backup storage from the local backup storage.
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 storage, 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 storage 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 Storage 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 storage from the local backup storage.
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 storage, 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 storage to rebuild your data center and recover your business, as shown in Public Cloud Backup Scenario-2.

Figure 6. Public Cloud Backup Scenario-2

Backup Task

A backup task enables you to back up local VM instances, local volumes, or local MN database (database) on schedule to a specified local backup storage, and also to synchronize backup data to a specified remote backup storage (offsite backup storage or Public Cloud backup storage.

The backup task overview page displays backup task executions of VM instances, volumes, and database, where backup tasks within a time range are calculated and analyzed in visual graph. As a result, you can directly get a whole picture of all backup tasks.

A backup task enables you to back up local VM resources or local volume resources on schedule to a specified local backup storage, and also to synchronize backup data to a specified remote backup storage (offsite backup storage or Public Cloud backup storage).
- Make sure that you add a local backup storage to the Cloud in advance. If you specify two local backup storages, the active-standby seamless switchover between these two backup storages are supported.
- If you want to back up your data remotely, make sure that you add a remote backup storage to the Cloud in advance. Notice that you are only allowed to add one remote backup storage to the Cloud.
- Backup tasks of local VM instances or volumes:
  - A single backup task supports multiple resources.
  - Set the incremental backup strategy and the full backup strategy as needed.
  - Backup progress bars are provided to let you view resource backup states at any time.
  - Update a backup policy for a backup task as needed.
  - You can perform a one-time backup task immediately.
  - Set a network QoS or disk QoS for a backup task as needed.
  - When you create a backup task, the rich text mode is provided. Obtain help information at any time in the process.
  - After you create a backup task, you can perform a backup once immediately.
  - If the stopped VM instances skip backups, a one-time backup (technical preview) will be automatically performed after these VM instances start.
  - Currently, you are not allowed to perform a scheduled backup for shared volumes.
- A single VM instance or volume can be backed up immediately, where important businesses can be backed up at any time.
A backup task enables you to back up an MN database (database) on schedule to a specified local backup storage, and also to synchronize backup data to a specified remote backup storage (offsite backup storage or Public Cloud backup storage.
- Make sure that you add a local backup storage to the cloud in advance. If you specify two local backup storages, the active-standby seamless switching between these two backup storages are supported.
- If you want to back up your data remotely, make sure that you add a remote backup storage to the Cloud in advance. Note that you are only allowed to add one remote backup storage to the cloud.
The following are two types of backup policies:
- Incremental + default full policy:
  - With a backup task, you can perform incremental backups for your resources by defining the incremental policy.
  - After you perform 63 times of incremental backups (you can modify the incremental backup count on the terminal), the system defaults to execute a full backup once.
- Incremental + custom full policy:
  - With a backup task, incremental backups and full backups will be performed based on the user-defined incremental policy and full backup policy.
  - After you perform 63 times of incremental backups (you can modify the incremental backup count on the terminal), the system defaults to execute a full backup once.
- If an incremental backup and a full backup task are triggered simultaneously at a time, a backup sequence will be used.
- The corresponding incremental backups and full backups are all displayed on the list of the local backup data. If you have chosen to synchronize your local backup data to a remote backup storage, you can view the synchronized backup data on the list of the remote backup storage.

Notice

A backup task can be performed for the running VM instances.
To create the backup task for volumes, these volumes must be attached to the running VM instances.
If VM instances have attached shared volumes, these shared volumes cannot be not backed up when a backup task is performed for these VM instances.
One backup task can be specified to two local backup storages at most. When two local backup storages are specified, which of these two backup storages will be master or standby depends on their add sequence. The first to be added to the Cloud will be master, while the second or later will be standby.
When a local backup storage (Master) fails over, another local backup storage (Standby) will be automatically started to ensure your business continuity.
- When the local backup storage (Master) works properly, backup tasks will be performed directly on this local backup storage.
- When the local backup storage (Master) is stopped, deleted, or disconnected, backup tasks will be automatically performed on another local backup storage (Standby).
- When the local backup storage (Master) is restored to a normal working condition, the backup tasks will be automatically performed on this local backup storage (Master) again.

When backups are calculated by count, the retention count for backup data must be integer. The minimum allowed retention is one.
When backups are calculated by time, follow the rules below:
- The retention count for backup data must be integer. Unit: Day | Week | Month. The minimum allowed retention is one day.
- Retain X day (s), indicating that since backup tasks are performed for the first time, the backup data will be retained for 24 hours * day (s).
- Retain X week (s), indicating that since backup tasks are performed for the first time, the backup data will be retained for 7 days*week (s).
- Retain X month (s), indicating that since backup tasks are performed for the first time, the backup data will be retained for 30 days * month (s).

Run incrementalBackup.maxNum to set the default value to 64 globally, an indication that after 63 times of backup tasks are performed, a full backup will be performed once.

Run zstack-cli to update this global configuration value. For example,

[root@localhost ~]# zstack-cli  #Run CLI.  admin>>> LogInByAccount accountName=admin password=password #Log in to CLI. Default user name/password: admin/password.  admin >>>UpdateGlobalConfig category=volumeBackup name=incrementalBackup.maxNum value=10 #Modify the maximum incremental backups. {     "inventory": {         "category": "volumeBackup",         "defaultValue": "64",         "description": "the maximum numbers of continuous incremental backup",         "name": "incrementalBackup.maxNum",         "value": "10"     },     "success": true }

The updated backup policy will not affect the triggered backup tasks.
A new backup task will no longer be performed for the resource that has been backed up.
After deleting the backup task of this resource, you can create a new backup task for it.

Local Backup Data

A local backup data is the backup data (local VM instances, local volumes, or database) that are backed up on a local backup storage. On the Local Backup Data page, you can manage your local backup data.

Backup data can either be recovered to the local backup storage or synchronized to the remote backup storage.
When you recover database, the UI page will not work properly if you refresh your browser, which does not affect the database recovery process.
This feature module enables you to back up and recover the data that are saved on an MN database, while data of operation logs and monitoring information are not available for this operation.

You can perform the following operations on local backup data:

View details of the local backup data.
Restore the local backup data.
Synchronize the local backup data to a remote backup storage.
Delete the local backup data.
Scan the database backup.
Export the backup data of the local database.

Notice

When overwriting the original resources, ensure that VM instances are placed into the stopped state.
When synchronizing the local backup data remotely, ensure that you add a remote backup storage to ZStack Private Cloud in advance. Only one remote backup storage can be added.
When the local backup storage is deleted, only the local backup data will be deleted by default. To delete the backup data on the remote backup storage, select Sync Delete Remote Backup Data.
If the remote backup data is deleted simultaneously, its local records will be deleted, but the actual data are not affected.
Assume that you restore the backup data for a volume. If the volume resides on a SharedBlock primary storage, ensure that you select a provisioning method, including thin provisioning and thick provisioning.
- Thin provisioning: Allocate storage space to data volumes based on the actual usage to achieve higher storage utilization.
- Thick provisioning: Preallocate required storage space to provide sufficient storage capacity for data volumes, ensuring the storage performance.
After the database is restored, all resources on the Cloud will be changed to the state at a time when the backup task is created. Ensure that, in the local backup storage, select Scan Backup to obtain the information of the currently actual backup data.

Local Backup Storage

A local backup storage is a storage server located at your local data center for storing backup data of local VM instances, local volumes, or database.

An ImageStore backup storage that has been deployed in your local data center can serve as a local backup storage.
You can also deploy a new local backup storage on the Cloud.
The Cloud enables you to add multiple local backup storages.
When a backup task specifies multiple local backup storages, the active-standby seamless switchover between these local backup storages are supported.
Both the expunged, invalid backup data and expired, temporary data that have been expunged can be cleared up to release more storage spaces.
The backup data that have been backed up to a local backup storage can be viewed at the local backup storage details page.

You can perform the following operations on a local backup storage:

Add a local backup storage.
Enable the local backup storage.
Disable the local backup storage.
Reconnect the local backup storage.
Scan the backup data.
Clean up the data of the local backup storage.
Delete the local backup storage.
Modify the basic attributes of the local backup storage.
Manage the local backup storage.

Notice

Add an existing ImageStore backup storage to act as a local backup storage. The Name option will automatically detect and use the name of this ImageStore backup storage. Also, after addition, you can modify the name by going to the details page of the local backup storage.
Assume that you specify a local backup storage for a backup task. If you disable this local backup storage, the backup task will fail.
Assume that you specify multiple local backup storages for a backup task. If you disable one of these local backup storages, the backup task will be automatically switched to another local backup storage (Standby).
If the local backup storage is an existing ImageStore backup storage, deleting the local backup storage will not delete the local records (of the backup data) and the actual data on this local backup storage. When you add this local backup storage again, the local records of the backup data will be restored in real time.
If the local backup storage is a newly added storage server, deleting this local backup storage will delete the local records of the backup data on the local backup storage, but the actual data is not affected. Exercise caution when you add this local backup storage again, the local records of the backup data cannot be automatically restored.
Data can be cleaned. If you clean both the expunged, valid backup data and the expired, temporary data on the local backup storage, you can release more storage spaces.
Note:
For example, assume that you expunge the local backup data of a VM instance or volume, and expunge this VM instance or volume restored from this backup data. At this time, performing the clear data button will release the storage space for this local backup storage.

Next Chapter:Migration Service

Backup Service

Typical Backup Scenarios

Backup Task

Notice

Local Backup Data

Notice

Local Backup Storage

Notice

Products

Solutions

Help & Support

Contact Us