Constraints
General
- A vault can be associated with only one backup policy.
- A vault can be associated with only one replication policy.
- A vault can be associated with a maximum of 256 resources.
- A maximum of 32 backup policies and 32 replication policies can be created.
- Only backups in the Available or Locked vaults can be used to restore data.
- Backups in a Deleting vault cannot be deleted.
- Backups cannot be downloaded to a local PC or uploaded to OBS.
- A vault and its associated servers or disks must be in the same region.
- Concurrent data restoration is not supported.
- Auto capacity expansion does not take effect if it is enabled after the vault is full.
Cloud Disk Backup
- Only disks in the Available or In-use state can be backed up.
- Frozen disks in the retention period cannot be backed up.
- A new disk must be at least as large as the backup's source disk.
- Cloud disk backups cannot be replicated to other regions.
- Backup and restoration of local disks are not supported.
Cloud Server Backup
- A maximum of 10 shared disks can be backed up with a cloud server.
- Only backups in the Available or Locked vaults can be used to create images and be replicated to different regions.
- Frozen servers in the retention period cannot be backed up.
- Cloud servers support crash-consistent backup, whereas database servers support application-consistent backup in addition to crash-consistent backup.
- You can back up specific disks on a server, but such a backup must be restored as a whole. File- or directory-level restoration is not supported.
- Images cannot be created from backups if the amount of resources associated with a server backup vault exceeds the quota.
- You are advised not to back up a server whose disk size exceeds 4 TB.
- Backups can be replicated only to regions that have replication capabilities.
- A backup can be replicated only when it meets all of the following conditions:
- It is an ECS backup.
- It contains system disk data.
- It is in the Available state.
- Only backups can be replicated. Backup replicas cannot be replicated again but can be used to create images.
- A backup can be replicated to multiple regions but can have only one replica in each destination region. The replication rule varies with the replication method:
- Manual replication: A backup can be replicated to the destination region as long as it has no replica in that region. A backup can be replicated again if its replica in the destination region has been deleted.
- Policy-based replication: A backup can only be automatically replicated to a destination region once. It cannot be automatically replicated to that region again, even if its replica has been deleted.
- Only replication-supported regions can be selected as destination regions.
- A backup can be replicated only when it meets all of the following conditions:
SFS Turbo Backup
- Only file systems in the Available state can be backed up.
- An SFS Turbo file system backup cannot be used to restore data to the original file system.
- Backups can be replicated only to regions that have replication capabilities.
- A backup can be replicated only when it meets all of the following conditions:
- It is generated for an SFS Turbo file system.
- It is in the Available state.
- Only backups can be replicated. Backup replicas cannot be replicated again but can be used to create SFS Turbo file systems.
- A backup can be replicated to multiple regions but can have only one replica in each destination region. The replication rule varies with the replication method:
- Manual replication: A backup can be replicated to the destination region as long as it has no replica in that region. A backup can be replicated again if its replica in the destination region has been deleted.
- Policy-based replication: A backup can only be automatically replicated to a destination region once. It cannot be automatically replicated to that region again, even if its replica has been deleted.
- Only replication-supported regions can be selected as destination regions.
- A backup can be replicated only when it meets all of the following conditions:
Hybrid Cloud Backup - Storage Backup
- See OceanStor Dorado V3 Series V300R002 CloudBackup Feature Guide for the constraints on storage devices.
- Backups synchronized to the cloud cannot be used to create cloud servers.
- Synchronized backups can only be restored to data disks on cloud servers.
Hybrid Cloud Backup - VMware Backup
- VM backups from the following VMware vSphere versions can be restored to cloud servers: 5.1, 5.5, 6.0, 6.5. If you do not need to restore the backups to cloud servers, there is no restriction on the VMware version.
- To obtain better performance and operation experience, you are advised to use the OSs listed in Table 1, which have passed the compatibility test.
- The VDDK version of VMware 6.5 VMs must be 6.0.3.
- Backups synchronized to the cloud cannot be used to create cloud servers.
- Backups synchronized to the cloud can only be restored to other cloud servers, and can be restored to system disks or data disks.
- Before the restoration, configure security groups according to the procedure. Otherwise, the restoration may fail.
Table 1 OSs that support restoration to the cloud OS
Supported Version
Windows
Windows 7
Windows Server 2008 R2
Windows Server 2012
Windows Server 2012 R2
Windows Server 2016
Windows Server 2019
CentOS
CentOS 6.4
CentOS 6.5
CentOS 7.2
CentOS 7.3
CentOS 7.4
CentOS 7.5
CentOS 7.6
CentOS 7.7
Red Hat
Red Hat 6.4
Red Hat 6.5
Red Hat 7.2
Desktop Backup
- Only desktops in the Available or In-use state can be backed up.
File Backup
- Before backing up a file, ensure that the file is not being used or changed by an application, and the backup client has the read permissions on this file. Otherwise, the backed-up data will be incomplete.
- Before backing up a file, ensure that the file is not being used or changed by a process, and the backup client has the read permissions on this file. Otherwise, the backed-up data will be incomplete.
- You are advised not to restore file backups when applications are running. Stop the applications and then restore files.
- One backup client can have a maximum of 8 files and directories added.
- Each resource can only have one Agent installed.
- The number of resources where the Agent can be installed is not limited.
- A single directory can contain a maximum of 500,000 files, and you are advised to reserve at least 4 GB of memory on each backup client to perform file backups.
- One path can contain a maximum of 200 characters.
- The maximum bandwidth allowed for file backup data transmission is 16 Gbit/s. If the maximum bandwidth is reached, flow control will be triggered.
- File backup cannot back up the files stored in SFS file systems that are mounted to cloud servers.
- Backup may fail on directories with frequent file writes in Windows.
- At least 50 Mbit/s network bandwidth is required in cross-cloud or cross-region scenarios.
Application-Consistent Backup
Database |
OS |
Version |
---|---|---|
SQL Server 2008/2012/2019 |
Windows |
Windows Server 2008, 2008 R2, 2012, 2012 R2, and 2019 for x86_64 |
SQL Server 2014/2016/Enterprise Edition |
Windows |
Windows Server 2014, 2014 R2, and 2016 Datacenter for x86_64 |
MySQL 5.5/5.6/5.7 |
Red Hat |
Red Hat Enterprise Linux 6 and 7 for x86_64 |
SUSE |
SUSE Linux Enterprise Server 11, 12, 15 SP1, 15 SP2 for x86_64 |
|
CentOS |
CentOS 6 and 7 for x86_64 |
|
EulerOS |
EulerOS 2.2 and 2.3 for x86_64 |
|
HANA 1.0/2.0 |
SUSE |
SUSE Linux Enterprise Server 12 for x86_64 |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot