No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

OceanStor BCManager 6.5.0.1 eBackup Product Description 01

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Restrictions

Restrictions

This section describes restrictions on the eBackup software in public cloud backup scenarios.

Note the following restrictions when deploying the eBackup software:

  • In one eBackup system, the eBackup software must be deployed on only VMs or physical machines.
  • File systems using common Internet file system (CIFS) and SAN storage cannot serve as backup storage of the eBackup system's management data.

Backup System

  • eBackup nodes can be deployed on both VMs and physical machines. To deploy eBackup on physical machines, the production storage must adopt InfiniBand (IB) networking.
  • One eBackup system (consisting of backup servers and backup proxies) responsible for data migration corresponds to one IaaS OpenStack system at the cascaded layer. If one IaaS OpenStack system at the cascading layer contains n IaaS OpenStack systems at the cascaded layer, n eBackup systems need to be deployed.
  • Only S3 storage can be used as backup storage to save tenants' data on EVS disks.
  • The eBackup software supports backup and restore in scenarios when only one IaaS BlockStorage system (containing multiple resource pools) is deployed in one IaaS OpenStack system.
  • Licenses support capacity authorization only.

Backup Function

  • Only EVS disks and ECSs in scenarios where the production storage is IaaS BlockStorage can be backed up.
  • If the backup image generated in the last backup job is deleted or damaged, full backup will be performed in the next backup job.
  • If the storage snapshot corresponding to the backup image generated in the last backup job is deleted, full backup will be performed in the next backup job.
  • Deduplication is not supported for backup data.
  • If no CBT information is returned by the production end during the execution of a full backup job, no data will be backed up. In this case, when the generated backup image is used for restore, no data will be written into the disks of the production end. That is, the data in such disks remains consistent with that before the restore.
  • If EVS disks of an ECS are from multiple IaaS BlockStorage systems, the ECS cannot be backed up.
  • Only EVS disks whose status are available or in use can be backed up.
  • Only ECSs whose status are ACTIVE, HARD_REBOOT, PASSWORD, PAUSED, REBOOT, SHUTOFF, or SUSPENDED can be backed up.
  • ECSs with no mounted EVS disks cannot be backed up.
  • Local disks of BMSs cannot be backed up.
  • Supports backup of the relational database service (RDS) instance.

Restore Function

  • If an EVS disk is to be created by using backup data of an existing EVS disk, the capacity of the EVS disk to be created must be greater than or equal to that of the existing EVS disk.
  • If only a part of EVS disks that have undergone volume management (such as logical volume management on Linux or dynamic volume management on Windows) on ECSs are restored, data on these EVS disks cannot be properly accessed.
  • During restore, disk space where no backup data is written will not be zeroed out or reclaimed.
  • During ECS restore, data of data volumes cannot be restored to system volumes.
  • Local disks of BMSs cannot be restored.
  • Supports restore of the relational database service (RDS) instance.
  • Only EVS disks whose status are available or in use can be restored.
  • Only ECSs whose status are ACTIVE, HARD_REBOOT, PASSWORD, PAUSED, REBOOT, SHUTOFF, or SUSPENDED can be restored.
  • If the cross-AZ restore feature is used, information about the S3 storage interconnected with the two eBackup drivers in the two AZs must be the same.
  • When the disk-level backup is used, the data of the unselected disks will not be backed up. When this copy is used to restore data, the data in these disks is inconsistent with the data in the copy at the same time point. As a result, services may be abnormal.
Download
Updated: 2019-04-26

Document ID: EDOC1100079909

Views: 945

Downloads: 29

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next