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

• Restore a local VM instance
  1. 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.
  2. 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.
  3. 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.

         
         
         

       • 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 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 a volume
  1. 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.
  2. 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.

         
         
         

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

         
         
         

• Restore a database
  • Assume that the original ZStack Cloud Private Cloud exists and you want to restore the database from the remote backup data to overwrite the original one.
    1. 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.

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

       
       
       

       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.
    3. The system restores the database.

       
       
       

    4. The database is restored successfully. You can click Relogin to log in to the Cloud again.

       
       
       

       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 Cloud Private Cloud does not exist and you want to restore the database from the remote backup data to build a new Cloud.
    1. Log in to the system. Then, the Welcome to use our Cloud page is displayed. Choose Restore Backup Data > Restore.

       
       
       

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

       
       
       

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

       
       
       

       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.
    4. In the displayed Recover Database dialog box, enter the root password. The initial password is zstack.mysql.password.

       
       
       

       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.
    5. The system restores the database.

       
       
       

    6. The database is restored successfully. You can click Relogin to log in to the Cloud again.

       
       
       

       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.