Overview

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. ZStack Cloud provides automated solutions on resuming all applications if a hardware or operating system failure occurs.

The Continuous Data Protection (CDP) service is a separate feature module. To use this service, purchase both the Base License and the Plus License of Continuous Data Protection (CDP). The Plus License cannot be used independently.

Concepts

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.
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.
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.

How CDP Works

ZStack Cloud provides block-level continuous data protection. You can restore CDP data according to a specified time point.

CDP backup
After continuous data protection is performed on a VM instance, the CDP server first performs a full copy of the VM data, continuously captures I/O data changes, and timestamps, and saves the I/O data of each change, thereby achieving continuous data backup.

Figure 1. CDP Backup
CDP recovery
When data recovery is performed, the CDP server exposes the CDP data as a block device and then restores the I/O data at a specified time to the disk or file system of a primary storage.

Figure 2. CDP recovery

Advantages

Simple:
- The software-defined solution we provide is hardware-independent and scalable.
- You can preview the backup files without restoring the system. Supported file formats: pictures (.png, .jpg, .bmp, .gif, etc.), PDF files, and text files (equal to or smaller than 10 MB).
- When you create a CDP task for the first time, the Cloud intelligently recommends the desired capacity required by a CDP task based on an algorithm, helping you to plan the backup space reasonably.
- You can restore data through a wizard-style process.
Strong:
- Agentless backup: To use the CDP service, you do not need to install agents for your VM instances or couple with other applications. This helps reduce the configuration complexity, lower the VM performance loss, and guarantee the business security.
- Second-level RPO: Provides second-level fine-grained continuous data protection for VM instances.
- Instant recovery: Supports instant recovery with the RTO in seconds, which helps to ensure the business continuity.
- Primary storage support: The CDP service applies to VM instances in different primary storage scenarios, including local storage, NFS, SharedBlock, Ceph, and CBD.
Flexible:
- Flexible RPO settings: Provides second/minute-level RPO settings.
- Multiple recovery levels: Supports entire recovery and file-level recovery.
  - Entire recovery: You can restore data to the original VM instance or to a newly-created VM instance.
  - File-level recovery: You can retrieve files without restoring the system. Both Windows and Linux file system formats are supported.
- Flexible data display and search:
  - The CDP data page displays hourly data changes of a VM instance, which provides a reference for backup capacity planning.
  - The CDP data page also provides a recovery point calendar, which identifies the dates with recovery points with colors. This helps you locate a recovery point quickly.
Reliable:
- Unified O&M: You can view the critical CDP information on the CDP overview page, including the CDP task status, recovery task status, backup server usage, and unread CDP alarms.
- You can restore CDP data to the original VM instance by creating a volume for the VM instance. All of the volumes before recovery can be retained and attached to the VM instance again, which ensures the data security to the maximum extent and facilitates post-fault analysis.
- The "Create VM instance" recovery policy allows you to create a new VM instance from the selected recovery point without affecting the original VM instance. You can finish the recovery after you confirm that the data is correct. This helps to meet the recovery drill requirements.
- You can mark and lock recovery points to retain the recovery point data in long term.
- The Cloud provides a list of recovery tasks, allowing you to view the recovery records and progress in a more friendly way.
- The RPO latency policy and alarm help to effectively relieve data transmission pressure of backup servers in heavy I/O scenarios.

Scenarios

The CDP service can be applied in the following scenarios:

Continuous protection of critical business data
You can use the CDP service to continuously back up and protect critical business data, such as banking system data and financial transaction data, minimizing data loss and ensuring your business continuity.
Anti-virus and data recovery
In case of virus invasion, such as a ransomware attack, you can use CDP to restore data to any point in time to reduce the loss caused by the virus.

Limits

Currently, if a VM instance has volumes not stored on the Ceph primary storage, you could not clone the VM instance or create snapshots or images for the VM instance during CDP.

Preparations

To use the Continuous Data Protection (CDP) service, you need to finish the following preparations:

Make sure that you have upgraded to the latest version of ZStack Cloud, and installed the Plus License of Continuous Data Protection (CDP).
Note: We recommend that you use ZStack Cloud 4.8.10 or later versions.
Make sure that you have an existing VM instance with no backup job created.
Make sure that you have prepared a storage server in local data center as the local backup server, and the storage server is not reused as a host.
Make sure that you have planned a storage network and a backup network. We recommend that you use at least 10 Gigabit NICs for your backup network.

Quick Start

The Continuous Data Protection (CDP) service allows you to back up and restore VM data in a local backup server, and retrieve files without restoring the system.

To quick start the Continuous Data Protection function, follow these steps:

CDP Backup:
1. Add a local backup server to ZStack Cloud.
2. Create a CDP task for VM instances.
3. Manage local CDP data.
CDP Recovery:
1. Restore CDP data of the VM instance to local.
2. View the recovery progress.
3. View the relevant resource that has been restored to local.

You can refer to the Local CDP Recovery Practice | Restore to the Original VM Instance and Local CDP Recovery Practice | Create a VM Instance chapters for CDP practice details.

CDP Practice

Local CDP Recovery | Restore to the Original VM Instance

About this task

Assume that the user has deployed the latest ZStack Cloud Private Cloud environment and installed the Continuous Data Protection (CDP) module. Now, the user plans to add a local backup server to back up a VM instance. After the data is backed up to the local backup server, important files are lost by mistake during business adjustment. Since the user's business application has hardware authorization, in order to quickly verify the availability of the service, the user needs to restore the data to the original VM instance to check whether the application is normal.

The following table lists the user's environment configuration.

Local Backup Server	Configuration
Backup Server IP	172.24.246.195
Mount Path	/cdp_store
SSH Port	22
User Name	root
Password	password
Management Network	172.24.246.195/16
Backup Network	192.168.1.0/24

The detailed steps are as follows:

Add a local backup server.
Create a CDP task.
View the CDP data of the VM instance, and lock the recovery point.
View the important file in the locked recovery point.
Delete the important file to simulate important data loss.
Find the locked recovery point, and restore data to the original VM instance.
View the recovery progress and relevant information.
Verify the restored data.

Procedure

Add a 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.
On the displayed page, set the following parameters:
- Addition Method: Select Add Server here.
- 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. In this scenario, enter 172.24.246.195.
- Mount Path: Enter the path to which the storage is mounted. In this scenario, enter /cdp_store.
- SSH Port: Enter the SSH port. Default: 22.
- User Name: Enter the user name. In this scenario, enter root.
- Password: Enter the password. In this scenario, enter password.
- Backup Network: Optional. Set the backup network. In this scenario, enter 192.168.1.0/24.
- Backup Data: Choose whether to scan the existing backup data. In this scenario, we do not need to scan the backup data.
Figure 3. Add Local Backup Server
Create a CDP task.
On the main menu of ZStack Cloud, choose Platform O&M > Backup Management > CDP Service > CDP Task. On the CDP Task page, click Create CDP Task. Then, the Create CDP Task page is displayed.
To create a CDP task, follow these three steps:
1. Set the basic information.
  On the displayed page, set the following parameters:
  
  Name: Enter a name for the CDP task.
  
  Description: Optional. Enter a description for the CDP task.
  
  VM Instance: Select the VM instance to be protected. In this scenario, select Business-VM-1.
  Note:
  
  You can create CDP tasks in bulk by choosing multiple VM instances.
  
  When you choose multiple VM instances, the name of CDP tasks will be followed by -1, -2, -3 and so forth to distinguish these tasks.
  
  One VM instance corresponds to one CDP task.
  
  After you create a CDP task for a VM instance, the Cloud performs a full backup for the VM instance.
  
  Shared volumes (if any) of a VM instance will not be backed up.
  
  You could not create a CDP task for VM instances with running backup jobs.
  
  You could not create a CDP task for VM instances with a scheduled snapshot job.
  
  If a VM instance is in the stopped state, the CDP task created for the VM instance is also in the stopped state and can start with the VM instance.
  
  You cannot create a CDP task for VM instances that use Vhost or ZBS (Vhost protocol) primary storage.
  
  Local Backup Server: In this scenario, select the added local backup server.
  Figure 4. Set Basic Information
2. Set the policy information.
  On the displayed page, set the following parameters:
  
  CDP Protection Policy: Set the CDP protection policy, including recovery point interval, recovery point retention policy, backup rate, and task running policy.
  
  Recovery Point Interval: Set the interval for generating recovery points. Unit: second, minute. By default, a recovery point is generated at an interval of 3 seconds. In this scenario, use the default value.
  
  Backup Aggregation Frequency: Set the interval for aggregating full backups. Valid range: 1-7 days, integer. By default, a full backup is aggregated every 7 days. In this scenario, use the default value.
  
  Recovery Point Retention Policy: Set the retention time and retention interval for recovery points. Up to 3 policies can be set.
  
  Backup Rate: Optional. You can limit the upstream bandwidth of each volume. Unit: Mbps/Gbps. In this scenario, select No limit.
  
  Task Running Policy: Set the desired size and RPO policy for a CDP task.
  
  Desired Size: Set the desired size for a CDP task. The CDP task will be stopped if the desired size is exceeded. In this scenario, use the suggested size.
  Note:
  
  The desired size must be greater than or equal to the total volume size and smaller than or equal to the total backup server size.
  
  The Cloud provides a recommended size according to the following formula:
  Recommended size = Maximum production data size X Number of full backups X 1.1 + Daily changed data size X Recovery point retention time X 1.5
  
  Maximum production data size: The maximum data size generated by your VM instance for one full backup. This value cannot exceed the total volume size of your VM instance.
  
  Number of full backups: Recovery point retention time ÷ Regular backup frequency.
  
  Daily changed data size: We recommend that you estimate the size of daily changed data based on your actual business scenario. For example, if the data of your VM instance increases by 1 GB per month, you can set the daily changed data size to 35 MB.
  
  Recovery point retention time: The maximum retention time you set on the UI.
  
  Maximum production data size X Number of full backups X 1.1: During the data retention period, the CDP task will perform more than one full backup. Some cases, such as VM restart, will also trigger a full backup. Therefore, the actual number of full backups will increase according to a certain proportion. (The coefficient here is 1.1, which can be adjusted according to the actual situation.)
  
  Daily changed data size X Recovery point retention time X 1.5: The size occupied by snapshot volumes is approximately 1.5 times the actual size of data changes.
  
  The formula above is for your reference in initial backup capacity planning. We recommend that you pay continuous attention to your backup server size changes, and expand the capacity in a timely manner according to the actual situation.
  
  RPO Policy: Set the CDP task running policy to deal with data replication latency in heavy I/O scenarios. By default, the CDP task will be stopped if the latency exceeds 10 minutes. After the data replication is synchronized, the CDP task will go back to the running status automatically. In this scenario, use the default value.
  Figure 5. Set Policy Information
3. Preview
  View the information about the CDP task. You can edit the information by clicking the Edit icon.
  
  Figure 6. Preview
View the CDP data of the VM instance, and lock the recovery point.
On the main menu of ZStack Cloud, choose Resource Center > Resource Pool > Virtual Resource > VM Instance. Then, the VM Instance page is displayed.
1. View the CDP data of the VM instance.
  On the displayed page, find VM-1, and enter its details page. On the CDP Data tab page, view the CDP data of the VM instance.
  
  Figure 7. View CDP Data
2. Lock the recovery point.
  Assume that the user plans to make a major business adjustment after 10:00:00, and the data before 10:00:00 needs to be marked.
  On the CDP Data tab page, choose one column (10:00:00 - 10:59:59), and click the corresponding arrow icon on the right of the list. Then, the recovery point list is displayed. On the recovery point list, choose one recovery point (10:00:00), and select the corresponding Lock Recovery Point checkbox. Then, enter a description for the locked recovery point.
  
  Figure 8. Lock Recovery Point
View the important file in the locked recovery point.

Assume the name of the important file is importantFile.

On the main menu of ZStack Cloud, choose Resource Center > Resource Pool > Virtual Resource > VM Instance. Then, the VM Instance page is displayed. Click the VM instance to enter its details page. On the CDP Data tab page, click the arrow icon beside the number of Locked Recovery Point. Then, the Locked Recovery Point List page is displayed. Find the recovery point that you locked before, and click Retrieve File. On the displayed Retrieve File page, enter importantFile in the search box to find it. You can find that the file is contained in the current locked recovery point.

Figure 9. View Important File in Locked Recovery Point
Delete the important file to simulate important data loss.

Assume that the user deleted the importantFile by mistake during business adjustment, and caused important data loss.

Figure 10. Delete File
Find the locked recovery point, and restore data to the original VM instance.
On the main menu of ZStack Cloud, choose Resource Center > Resource Pool > Virtual Resource > VM Instance. Then, the VM Instance page is displayed. Click the VM instance to enter its details page. On the CDP Data tab page, click the arrow icon beside the number of Locked Recovery Point. Then, the Locked Recovery List page is displayed.

Figure 11. Locked Recovery Point List
On the Locked Recovery Point List page, find the 2022-08-01 10:00:00 corresponding locked recovery point to perform data restoration. To restore data, follow these three steps:
1. Configure Recovery Policy.
  On the displayed page, set the following parameters:
  
  CDP Task: Display the CDP task corresponding to current locked recovery point.
  
  Recovery Point: Display the selected locked recovery point.
  
  Recovery Task Name: Restoring CDP data will automatically create a recovery task with a default task name. You can view the detailed recovery record in the recovery task list.
  Note: Recovery tasks created here are named in the format of VM Name-Recovery Point Time, for example, VM-1-2022-08-01-10:00:00.
  
  Recovery Policy: In this scenario, select Restore to Original VM Instance.
  Note:
  
  The Cloud supports two recovery policies: create VM instance and restore to original VM instance.
  
  After the recovery is performed, the original VM instance will quickly start up for business recovery.
  
  During the recovery, the original VM instance will be in the Restoring Data state. In this case, the VM instance can normally provide services and you can read data from and write data into this VM instance. However, the VM's own operations are limited to Launch Console only.
  
  Recovery Method: You can restore the CDP data to the original VM instance by creating new volumes or overwriting the current volumes. In this scenario, select Overwrite Current Volumes.
  
  Create Volumes:
  
  This method will create new volumes to replace the current volumes. Data in the current volumes will be retained.
  
  This method will detach the current volumes. You can view the newly created and detached volumes on the configuration tab page of the VM instance.
  
  After you confirm that the restored data is reliable, you can manually delete the detached volumes to release the storage space.
  
  Overwrite Current Volumes:
  
  This method will overwrite the original data in the VM instance. Please exercise caution.
  
  This method will keep the snapshots in the current volumes.
  
  Recovery Rate: Optional. You can limit the upstream bandwidth of each volume in CDP protection. Unit: Mbps/Gbps. In this scenario, select No limit.
  Figure 12. Configure Recovery Policy
2. Configure Target VM.
  By default, the name and description of the original VM instance are displayed.
  
  Figure 13. Configure Target VM
3. Preview.
  View the recovery task that will be created. You can edit the information by clicking the Edit icon.
  
  Figure 14. Preview
View the recovery progress and relevant information.

On the main menu of ZStack Cloud, choose Platform O&M > Backup Management > CDP Service > Recovery Task. Then, the Recovery Task page is displayed. On the Recovery Task main list, you can view the job status, target VM, time consumed, and other information.

Figure 15. View Recovery Progress
Verify the restored data.

Launch the VM console and run the ls command to view the file in the directory. You can find that the importantFile already exists in the directory.

Figure 16. Data Recovery Succeeded

What to do next

You can unlock the recovery point after a successful recovery to release storage space. So far, we have introduced the CDP scenario practice of restoring data to the original VM instance.

Local CDP Recovery | Create a VM Instance

About this task

Assume that the user has deployed the latest version of ZStack Cloud Private Cloud environment, and installed the Continuous Data Protection (CDP) module. The user plans to add a local backup server to backup a VM instance. After the data is backed up to the local backup server, important files are lost by mistake during business adjustment. Because not knowing the specific time when the problem occurred, the user is afraid to directly overwrite the original VM instance. Now the user needs to restore the data to a new VM instance to check whether the system is healthy.

The following table lists the user's environment configuration.

Local Backup Server	Configuration
Backup Server IP	172.24.246.195
Mount Path	/cdp_store
SSH Port	22
User Name	root
Password	password
Management Network	172.24.246.195/16
Backup Network	192.168.1.0/24

The detailed practice steps are as follows:

Add a local backup server.
Create a CDP task.
View the local CDP data of the VM instance and an important file.
Delete the important file to simulate the loss of the important data.
Restore to a new VM instance from current recovery point.
View the recovery progress and relevant information.
Verify the restored data.

Procedure

Add a 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.
On the displayed page, set the following parameters:
- Addition Method: Select Add Server here.
- 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. In this scenario, enter 172.24.246.195.
- Mount Path: Enter the path to which the storage is mounted. In this scenario, enter /cdp_store.
- SSH Port: Enter the SSH port. Default: 22.
- User Name: Enter the user name. In this scenario, enter root.
- Password: Enter the password. In this scenario, enter password.
- Backup Network: Optional. Set the backup network. In this scenario, enter 192.168.1.0/24.
- Backup Data: Choose whether to scan the existing backup data. In this scenario, we do not need to scan the backup data.
Figure 17. Add Local Backup Server
Create a CDP task.
On the main menu of ZStack Cloud, choose Platform O&M > Backup Management > CDP Service > CDP Task. On the CDP Task page, click Create CDP Task. Then, the Create CDP Task page is displayed.
To create a CDP task, follow these three steps:
1. Set the basic information.
  On the displayed page, set the following parameters:
  
  Name: Enter a name for the CDP task.
  
  Description: Optional. Enter a description for the CDP task.
  
  VM Instance: Select the VM instance to be protected. In this scenario, select Business-VM-1.
  Note:
  
  You can create CDP tasks in bulk by choosing multiple VM instances.
  
  When you choose multiple VM instances, the name of CDP tasks will be followed by -1, -2, -3 and so forth to distinguish these tasks.
  
  One VM instance corresponds to one CDP task.
  
  After you create a CDP task for a VM instance, the Cloud performs a full backup for the VM instance.
  
  Shared volumes (if any) of a VM instance will not be backed up.
  
  You could not create a CDP task for VM instances with running backup jobs.
  
  You could not create a CDP task for VM instances with a scheduled snapshot job.
  
  If a VM instance is in the stopped state, the CDP task created for the VM instance is also in the stopped state and can start with the VM instance.
  
  You cannot create a CDP task for VM instances that use Vhost or ZBS (Vhost protocol) primary storage.
  
  Local Backup Server: In this scenario, select the added local backup server.
  Figure 18. Set Basic Information
2. Set the policy information.
  On the displayed page, set the following parameters:
  
  CDP Protection Policy: Set the CDP protection policy, including recovery point interval, recovery point retention policy, backup rate, and task running policy.
  
  Recovery Point Interval: Set the interval for generating recovery points. Unit: second, minute. By default, a recovery point is generated at an interval of 3 seconds. In this scenario, use the default value.
  
  Backup Aggregation Frequency: Set the interval for aggregating full backups. Valid range: 1-7 days, integer. By default, a full backup is aggregated every 7 days. In this scenario, use the default value.
  
  Recovery Point Retention Policy: Set the retention time and retention interval for recovery points. Up to 3 policies can be set.
  
  Backup Rate: Optional. You can limit the upstream bandwidth of each volume. Unit: Mbps/Gbps. In this scenario, select No limit.
  
  Task Running Policy: Set the desired size and RPO policy for a CDP task.
  
  Desired Size: Set the desired size for a CDP task. The CDP task will be stopped if the desired size is exceeded. In this scenario, use the suggested size.
  Note:
  
  The desired size must be greater than or equal to the total volume size and smaller than or equal to the total backup server size.
  
  The Cloud provides a recommended size according to the following formula:
  Recommended size = Maximum production data size X Number of full backups X 1.1 + Daily changed data size X Recovery point retention time X 1.5
  
  Maximum production data size: The maximum data size generated by your VM instance for one full backup. This value cannot exceed the total volume size of your VM instance.
  
  Number of full backups: Recovery point retention time ÷ Regular backup frequency.
  
  Daily changed data size: We recommend that you estimate the size of daily changed data based on your actual business scenario. For example, if the data of your VM instance increases by 1 GB per month, you can set the daily changed data size to 35 MB.
  
  Recovery point retention time: The maximum retention time you set on the UI.
  
  Maximum production data size X Number of full backups X 1.1: During the data retention period, the CDP task will perform more than one full backup. Some cases, such as VM restart, will also trigger a full backup. Therefore, the actual number of full backups will increase according to a certain proportion. (The coefficient here is 1.1, which can be adjusted according to the actual situation.)
  
  Daily changed data size X Recovery point retention time X 1.5: The size occupied by snapshot volumes is approximately 1.5 times the actual size of data changes.
  
  The formula above is for your reference in initial backup capacity planning. We recommend that you pay continuous attention to your backup server size changes, and expand the capacity in a timely manner according to the actual situation.
  
  RPO Policy: Set the CDP task running policy to deal with data replication latency in heavy I/O scenarios. By default, the CDP task will be stopped if the latency exceeds 10 minutes. After the data replication is synchronized, the CDP task will go back to the running status automatically. In this scenario, use the default value.
  Figure 19. Set Policy Information
3. Preview
  View the information about the CDP task. You can edit the information by clicking the Edit icon.
  
  Figure 20. Preview
View the local CDP data of the VM instance and an important file.

Assume that the user made an important business adjustment on the day of 2022-08-01, and the user viewed the important data in the system before business adjustment.

On the main menu of ZStack Cloud, choose Resource Center > Resource Pool > Virtual Resource > VM Instance. Then, the VM Instance page is displayed. On the CDP Data tab page, view the data for any time period on 2022-08-01 (for example, 2022-08-01 10:00:00), and click Retrieve File. On the displayed Retrieve File page, enter importantFile in the search box to find it. You can find that the file is contained in the current recovery point.

Figure 21. View Important File in Recovery Point
Delete the important file to simulate important data loss.

Assume that the user deleted the importantFile by mistake during business adjustment, and caused important data loss.

Figure 22. Delete File
Restore to a new VM instance from current recovery point.
Assume that the user does not know the specific time when the mistake was made, and is afraid to overwrite the original VM instance. So, the user needs to create a new VM instance to verify the restoration.
On the main menu of ZStack Cloud, choose Resource Center > Resource Pool > Virtual Resource > VM Instance. Then, the VM Instance page is displayed. Click the VM instance to enter its details page. On the CDP Data tab page, select date 2022-08-01, and perform data restoration operation. To restore data, refer to the following three steps:
1. Configure Recovery Policy.
  On the displayed page, set the following parameters:
  
  CDP Task: Display the CDP task corresponding to current locked recovery point.
  
  Recovery Point: You can select a recovery point from the recovery point list (including locked recovery points) or from the locked recovery point list. In this scenario, select a recovery point corresponding to a certain time on 2022-08-01.
  Note:
  
  The recovery point list allows you to search for a recovery point by date, hour, and minute/second.
  
  When you search by hour, you can choose between hours with one hour as the interval.
  
  When you search by date, the Cloud provides a recovery point calendar, where dates with recovery points are marked in green for quick identification.
  
  When you search by minute/second, we recommend that you specify a time based on the recovery point interval you set before.
  
  The locked recovery point list displays all the locked recovery points by default, and allows you to search by date.
  
  Recovery Task Name: By default, restoring CDP data creates recovery task, and sets the default task name. You can view the detail recovery record in the recovery task list.
  Note: Recovery tasks created here are named in the format of VM Name-Recovery Point Time, for example, VM-1-2022-08-01-10:00:00.
  
  Recovery Policy: In this scenario, select Create VM Instance.
  Note:
  
  This method will create a VM instance from the current recovery point. The original one will not be affected.
  
  The newly created VM instance will quickly start up for business recovery.
  
  During the recovery, the newly created VM instance will be in the Restoring Data state. In this case, the VM instance can normally provide services and you can read data from and write data into this VM instance. However, the VM's own operations are limited to Launch Console only.
  
  Recovery Rate：Optional. You can limit the upstream bandwidth of each volume in CDP protection. Unit: Mbps/Gbps. In this scenario, select No limit.
  Figure 23. Configure Recovery Policy
2. Configure Target VM.
  On the displayed page, set the following parameters:
  
  Name: Enter a name for the new VM instance. For example, VM-from-CDP.
  
  Description: Optional. Enter a description for the new VM instance.
  
  Tag: Optional. Attach a tag for the new VM instance.
  
  Instance Offering: By default, we recommend that you use the same instance offering as the original VM instance.
  
  Network Configuration: By default, we recommend that you use the same network configuration as the original VM instance.
  
  Primary Storage: By default, we recommend that you use the same primary storage as the original VM instance.
  Note: If the VM instance has attached a SharedBlock volume, the provisioning type will set to thick provisioning by default when recovering data.
  
  Host: By default, we recommend that you use the same host as the original VM instance.
  Figure 24. Configure Target VM
3. Preview.
  View the recovery task that will be created. You can edit the information by clicking the Edit icon.
  
  Figure 25. Preview
View the recovery progress and relevant information.

On the main menu of ZStack Cloud, choose Platform O&M > Backup Management > CDP Service > Recovery Task. Then, the Recovery Task page is displayed. On the Recovery Task main list, you can view the job status, target VM, time consumed, and other information.

Figure 26. View Recovery Progress
Verify the restored data.

Launch the console of the newly created VM instance (VM-from-CDP). Then, run the ls command to view the file in the directory. You can find that the importantFile already exists in the directory.

Figure 27. Verify Restored Data

What to do next

So far, we have introduced the CDP scenario practice of restoring data by creating a new VM instance.

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)

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.

PreviousZStack Cloud NextZStack Cloud