Copy Data Lake
Copy Data Lake is the core architecture to realize massive copy data storage and management under multi-cloud architecture. It gathers massive copy data of backup, archive and test, and carries out the full lifecycle management of data in the lake. Based on the copy data lake, it provides rich copy data management capabilities, such as metadata management, data classification, data tagging, snapshot and cloning, to meet the needs of data management and use in different scenarios. Meanwhile it provides backup and recovery, migration, and disaster recovery management, to ensure data security and business continuity in all aspects.
• Unified management of multi-cloud data:
– Supports multiple storage services.
Each backup domain supports the deployment of one or more storage services to provide storage management capabilities. Data in different storage services under a unified backup domain can be managed in a unified way through AnyBackup Management Console. Data replication between different backup domains is supported.
– Supports unified management of multiple storage pools and physical isolation of storage resources under the same storage service.
– Supports data collection via high-performance backup and recovery APIs and standard storage protocols.
– Supports versioning and history of backup data to ensure that a recoverable copy of the data is available in the event of a required recovery of the production system.
– Supports unified management of heterogeneous disaster recovery systems: AnyBackup super administrator can be associated with NBU users to realize backup, recovery, policy and other disaster recovery management. A set of AnyBackup can manage multiple sets of NBUs to improve management efficiency.
NBU 8.2 and NBU 9.1 can be managed.
• Supports the deployment architecture of separating storage and computation, allowing the management console and storage services to be deployed separately. Both the management console and storage services can independently achieve horizontal scaling.
• Distributed computing, see [Distributed Computing].
• Distributed storage capabilities, see [Proplyd Distributed Storage].
Distributed Computing
Distributed computing uses multiple nodes to process backup tasks in parallel, which not only meets the increasing data size and backup requirements, but also builds a highly reliable backup architecture that can effectively withstand a variety of potential failures.
• Supports load balancing capabilities. Business requests are distributed evenly across all nodes to avoid performance bottlenecks at a single node, thereby improving data processing performance and availability.
• Supports horizontal scaling.
– The management console service supports horizontal scaling, with a maximum of 8 nodes.
– The storage service supports horizontal scaling, with a maximum of 10 storage services. For a service within a single storage service, up to 64 nodes are supported.
• Supports automatic failover. When the management service node fails, business requests are automatically transferred to a healthy node to ensure uninterrupted business.
• Supports three-copy redundancy to avoid service and data unavailability due to single node failures.
• Supports queuing system to realize efficient processing of massive tasks.
– Supports concurrency control at the storage service level.
– [Specifications] Global queuing quota and execution quota limits are 2,500.
Proplyd Distributed Storage
• Supports deployments of up to 64 nodes and provides horizontal and vertical scalability.
• Supports multiple storage media, including local devices, NAS storage, and SAN storage as storage pools.
• Supports single-copy, three-copy, EC, EC-folding data redundancy policies. Supports RAID+EC (2+1) deployment for 2U devices.
• Supports horizontal scaling of storage pools. The storage pool scaling does not affect the normal operation of the business.
• Supports data load balancing policies, see AnyBackup Family 8 White Paper for details.
• Supports multiple standard storage protocols, including NFS, iSCSI, FC SAN, S3, and more.
• Supports data copy capabilities, enabling cloning and mounting of backup data.
• Supports advanced features such as deduplication, data compression, flow control, data encryption, remote replication, and more.
• Supports D2D2T that replicates data to tapes.
• Supports ransomware protection for data storage with key technologies such as data immutability.
• Supports high availability capabilities.
– Local block storage pool: When a node fails, the tasks running at that time will fail. After restarting, they will switch to full backup, and the affected historical data cannot be restored.
– SAN/NAS storage pool: When a node fails, the external storage device of the faulty node will migrate to an available node for continued use. The current task can be restarted and continue running without affecting the recovery of historical data.
– Distributed storage pool (three-copy/EC): When a node fails, the current task can be restarted and continue running without affecting the recovery of historical data. The storage pool with three-copy or EC redundancy policy supports the replacement of faulty hard drives to ensure data reliability.
• Supports SSD accelerated I/O
– Local block storage pool: Index data and data blocks are automatically shunted. High-performance SATA SSDs are used to improve data indexing, fingerprint data access, and query performance.
– SAN/NAS storage pool: Currently local configuration of SSDs is not supported for I/O acceleration.
– Distributed storage pool (three-copy/EC): Supports three-copy distributed NVMe SSD write cache and single-node read-only cache, reducing small I/O read-write latency and improving data indexing, fingerprint data access, and query performance.
Backup and Recovery/Copy Data Management
Unified management of data protection and copy data is supported. It realizes data backup, recovery, data copy and data mount under the same application and the same engine. At the same time, unified monitoring of different types of tasks are supported.
• The following application modules are supported.
[Restrictions] Instant recovery is not supported if deduplication, data encryption or data compression is enabled.
Application |
Backup Capability |
Recovery Capability |
Copy Data Management |
File (in resource-centered and job-centered modes) |
Full Backup
Incremental Backup Incremental Forever Backup
Agent-based Backup |
Browse Recovery |
Copy Clone
Instant Recovery |
Object Storage |
Full Backup
Incremental Backup Incremental Forever Backup
Agentless Backup |
Browse Recovery |
Copy Clone
Instant Recovery |
Volume (regular) |
Full Backup
Incremental Forever Backup |
Browse Recovery |
Instant Recovery |
Volume (real-time) |
Full Backup
Incremental Forever Backup |
Browse recovery (Any Point in Time Recovery, latest IO recovery) |
Instant Recovery |
Entire machine |
Full Backup
Incremental Forever Backup |
Browse Recovery |
- |
Lustre |
Full Backup
Incremental Backup Incremental Forever Backup |
Browse Recovery |
Copy Clone
Instant Recovery |
Kingbase |
Full Backup
Log Backup
Incremental Backup Incremental Forever Backup |
Browse Recovery |
Copy Clone
Instant Recovery |
MySQL |
Full Backup
Differential Backup
Log Backup
Incremental Backup |
Browse Recovery
Any Point in Time Recovery |
Copy Clone
Instant Recovery |
Alibaba Cloud RDS for MySQL
(based on Generic APP backup framework) |
Full Backup
Log Backup |
Browse Recovery |
- |
Huawei Public Cloud RDS for MySQL
(based on Generic APP backup framework) |
Full Backup |
Browse Recovery |
- |
MariaDB |
Full Backup
Differential Backup
Log Backup
Incremental Backup |
Browse Recovery
Any Point in Time Recovery |
- |
TeleDB |
Full Backup
Differential Backup
Log Backup
Incremental Backup |
Browse Recovery
Any Point in Time Recovery |
- |
TDSQL |
Full Backup
Differential Backup
Log Backup
Incremental Backup |
Browse Recovery
Any Point in Time Recovery |
- |
SQL Server |
Full Backup
Differential Backup
Log Backup |
Browse Recovery
Any Point in Time Recovery |
- |
DB2 |
Full Backup
Differential Backup Incremental Backup |
Browse Recovery
Any Point in Time Recovery |
- |
Oracle |
Full Backup
Log Backup
Incremental Backup Incremental Forever Backup |
Browse Recovery
Any Point in Time Recovery |
Copy Clone
Instant Recovery |
PostgreSQL |
Full Backup
Incremental Backup |
Browse Recovery
Any Point in Time Recovery |
- |
MogDB |
Full Backup
Incremental Backup
Real-Time Log Backup
Log Backup |
Browse Recovery
Any Point in Time Recovery |
-
|
TelePG |
Full Backup
Incremental Backup |
Browse Recovery
Any Point in Time Recovery |
- |
openGauss |
Full Backup
Incremental Backup
Real-Time Log Backup
Log Backup |
Browse Recovery
Any Point in Time Recovery |
Instant Recovery |
Dameng |
Full Backup
Differential Backup Incremental Backup
Log Backup |
Browse Recovery
Any Point in Time Recovery |
- |
Informix |
Full Backup
Differential Backup Incremental Backup
Log Backup |
Browse Recovery
Any Point in Time Recovery |
- |
GBase 8s |
Full Backup
Differential Backup Incremental Backup
Log Backup |
Browse Recovery
Any Point in Time Recovery |
- |
SinoDB |
Full Backup
Differential Backup Incremental Backup
Log Backup |
Browse Recovery
Any Point in Time Recovery |
- |
TiDB |
Full Backup
Incremental Backup |
Browse Recovery |
- |
Exchange Server |
Full Backup
Incremental Backup |
Browse Recovery |
- |
Shentong |
Full Backup
Incremental Backup Differential Backup
Log Backup |
Browse Recovery
Any Point in Time Recovery |
- |
Caché |
Full Backup
Incremental Backup |
Browse Recovery |
- |
Sybase |
Full Backup
Incremental Backup |
Browse Recovery
Any Point in Time Recovery |
- |
Kingwow |
Full Backup
Incremental Backup |
- |
Copy Clone
Instant Recovery |
GoldenDB |
Full Backup
Incremental Backup |
Browse Recovery |
- |
GBase 8a |
Full Backup
Incremental Backup |
Browse Recovery |
- |
Generic APP Data Protection |
Full Backup
Incremental Backup Differential Backup
Log Backup |
- |
Copy Clone
Instant Recovery |
OceanBase |
Full Backup
Incremental Backup
Log Backup
Real-time Log Backup |
Browse Recovery |
- |
InterSystems IRISHealth Cluster |
Full Backup
Incremental Backup |
Browse Recovery |
- |
HighGo |
Full Backup
Log Backup |
Browse Recovery
Any Point in Time Recovery |
- |
Vastbase |
Full Backup
Incremental Backup
Log Backup |
Browse Recovery
Any Point in Time Recovery |
Copy Clone
Instant Recovery |
ArkDB |
Full Backup
Log Backup
|
Browse Recovery
Any Point in Time Recovery |
Copy Clone
Instant Recovery |
XenServer |
Full Backup
Incremental Backup |
Browse Recovery - New Recovery |
- |
FusionCompute |
Full Backup
Incremental Forever Backup |
Browse Recovery - New Recovery
Browse Recovery - Overwritten Recovery
Browse Recovery - Heterogeneous Recovery to VMware
Browse Files - Supports browsing and downloading of files inside the virtual machine |
Instant Recovery as a Virtual Machine
Instant Recovery to Hosts |
H3C CAS/UIS |
Full Backup
Incremental Forever Backup |
Browse Recovery - New Recovery
Browse Recovery - Heterogeneous Recovery to VMware/FusionCompute
Browse Files - Supports browsing and downloading of files inside the virtual machine |
Copy Clone
Instant Recovery to Hosts |
SmartX |
Full Backup
Incremental Forever Backup |
Browse Recovery - New Recovery
Browse Recovery - Heterogeneous Recovery to VMware |
- |
Nutanix AHV |
Full Backup
Incremental Forever Backup |
Browse Recovery - New Recovery
Browse Recovery - Heterogeneous Recovery to VMware
Browse Files - Supports browsing and downloading of files inside the virtual machine |
- |
InCloud Sphere |
Full Backup
Incremental Forever Backup |
Browse Recovery - New Recovery
Heterogeneous Recovery to VMware |
- |
OpenStack |
Full Backup
Incremental Forever Backup |
Browse Recovery - New Recovery
Browse Recovery - Heterogeneous Recovery to VMware/FusionCompute
Browse Files - Supports browsing and downloading of files inside the virtual machine |
Copy Clone
Instant Recovery to Hosts |
ZStack |
Full Backup
Incremental Forever Backup |
Browse Recovery - New Recovery
Browse Recovery - Heterogeneous Recovery to VMware |
- |
CNware |
Full Backup
Incremental Forever Backup |
Browse Recovery - New Recovery
Browse Files - Supports browsing and downloading of files inside the virtual machine |
Copy Clone
Instant Recovery to Hosts |
ProxmoxVE |
Full Backup |
Browse Recovery - New Recovery |
- |
Alibaba Cloud Apsara Stack |
Full Backup |
Browse Recovery - New Recovery |
- |
Huawei Cloud Stack |
Full Backup
Incremental Forever Backup |
Browse Recovery - Overwritten Recovery |
- |
QingCloud |
Full Backup
Incremental Forever Backup |
Browse Recovery - New Recovery |
- |
JDStack
|
Full Backup |
Browse Recovery - Overwritten Recovery |
- |
TCE |
Full Backup |
Browse Recovery - New Recovery |
- |
GaussDB |
Full Backup
Incremental Backup
Log Backup
Agentless Backup |
Browse Recovery Agentless Recovery |
- |
SAP HANA |
Full Backup
Incremental Backup Differential Backup
Log Backup |
Browse Recovery
Any Point in Time Recovery |
- |
HDFS |
Full Backup
Incremental Backup Differential Backup Agentless Backup |
Browse Recovery Agentless Recovery |
- |
Greenplum |
Full Backup
Incremental Backup |
Browse Recovery |
- |
MongoDB
(based on Generic APP backup framework) |
Full Backup
Incremental Backup |
Browse Recovery |
- |
Elasticsearch |
Full Backup
Incremental Backup |
Browse Recovery |
- |
Clickhouse |
Full Backup
Incremental Backup |
Browse Recovery |
- |
Kubernetes |
Full Backup
Incremental Forever Backup
Snapshot
Snapshot Backup |
Browse Recovery
Instant Recovery |
- |
Backup and Recovery supports the following public capabilities.
• Supports [Encryption in Transfer] to ensure that the data cannot be deciphered in the process of network transmission, so as to ensure data security.
• Supports [Data Encryption]
– Supports source or destination encryption.
– Supports AES256, SM4 and Blowfish encryption algorithms.
• Supports [Deduplication]
– Supports source-side deduplication or target-side deduplication.
– Supports fixed-length or variable-length data slices.
– Distributed deduplication architecture. Data and data fingerprints are evenly loaded to multiple nodes, making full use of multiple nodes to realize fingerprint checking and data storage. Scale-out linear horizontal scaling is supported.
– Supports dual hash fingerprints.
– Deduplication-enabled backup tasks support high availability of backup services: In case of failure of any node in the single-copy storage pool, incremental backups initiated by deduplication-enabled backup tasks will be automatically converted to full backups, and the data will be written to the healthy node of the original fingerprint library.
– The backup data after deduplication can be remotely replicated to the target, and the data in the process of remote replication still retains the deduplication effect. The deduplication range is the fingerprint database.
• Supports [Remote Replication]
– Supports point-in-time level data synchronization and reverse replication.
– Supports remote replication of data between different types of storage pools.
– Supports remote replication of encrypted, compressed and deleted data. The encryption, compression, and deduplication characteristics still retain after replication.
– Supports data block level resumable data transfer.
– Supports manual initiation and replication policy to initiate data synchronization.
– Supports copy retention policies for retention period and number of copies to be retained.
– Supports one-to-one, many-to-one, and one-to-many remote replication.
– Supports up to four levels of cascading replication.
– [Restrictions] The current version only supports data replication between different types of storage pools, such as distributed storage pools, local block storage pools, and SAN storage pools. It does not support cross-storage pool replication for NAS storage pools.
These capabilities are supported for the following applications.
Application |
Data Compression |
Data Encryption |
Encryption in Transfer |
Deduplication |
Remote Replication |
Remote Replication for Deduplicated Data |
File (in resource-centered and job-centered modes) |
✔ |
✔ |
✔ |
✔ |
✔ |
✔ |
Object Storage |
✔ |
- |
- |
✔ |
✔ |
- |
Volume |
- |
- |
- |
- |
- |
- |
Entire Machine |
✔ |
- |
✔ |
- |
- |
- |
Oracle |
✔ |
✔ |
✔ |
✔ |
✔ |
✔ |
MySQL |
✔ |
✔ |
✔ |
✔ |
- |
- |
SQL Server |
✔ |
✔ |
✔ |
✔ |
✔ |
- |
Exchange Server |
✔ |
✔ |
✔ |
✔ |
✔ |
✔ |
TiDB |
✔ |
✔ |
✔ |
✔ |
✔ |
- |
Caché |
✔ |
✔ |
✔ |
✔ |
✔ |
- |
Dameng |
✔ |
✔ |
✔ |
✔ |
✔ |
- |
Kingbase |
- |
- |
✔ |
- |
✔ |
- |
Kingwow |
- |
- |
✔ |
- |
✔ |
- |
Sybase |
✔ |
✔ |
✔ |
✔ |
✔ |
- |
GBase 8s |
- |
- |
✔ |
- |
- |
- |
GBase 8a |
- |
- |
✔ |
- |
- |
- |
Shentong |
✔ |
✔ |
✔ |
✔ |
✔ |
- |
PostgreSQL |
- |
- |
✔ |
- |
✔ |
- |
DB2 |
✔ |
✔ |
✔ |
✔ |
✔ |
- |
Informix |
- |
- |
✔ |
- |
- |
- |
SinoDB |
- |
- |
✔ |
- |
- |
- |
GoldenDB |
- |
- |
- |
- |
- |
- |
MogDB |
- |
- |
✔ |
- |
- |
- |
openGauss |
- |
- |
✔ |
- |
- |
- |
Generic APP |
- |
- |
✔ |
- |
✔ |
- |
OceanBase |
- |
- |
- |
- |
- |
- |
InterSystems IRISHealth Cluster |
✔ |
✔ |
✔ |
✔ |
✔ |
- |
HighGo |
- |
- |
✔ |
- |
✔ |
- |
Vastbase |
- |
- |
✔ |
- |
- |
- |
ArkDB |
✔ |
✔ |
✔ |
✔ |
- |
- |
TDSQL |
- |
- |
- |
- |
- |
- |
Alibaba Cloud RDS for MySQL
(based on Generic APP backup framework) |
- |
- |
- |
- |
- |
- |
Huawei Cloud Public Cloud RDS for MySQL
(based on Generic APP backup framework) |
- |
- |
- |
- |
- |
- |
VMware |
- |
- |
✔ |
✔ |
✔ |
✔ |
H3C CAS/UIS |
- |
- |
✔ |
- |
✔ |
- |
FusionCompute |
- |
- |
✔ |
✔ |
✔ |
✔ |
OpenStack |
- |
- |
✔ |
✔ |
✔ |
✔ |
Huawei Cloud Stack |
- |
- |
✔ |
✔ |
✔ |
✔ |
XenServer |
- |
- |
✔ |
- |
- |
- |
ZStack |
- |
- |
✔ |
- |
✔ |
- |
CNware |
- |
- |
✔ |
✔ |
✔ |
✔ |
SmartX |
- |
- |
✔ |
✔ |
✔ |
✔ |
InCloud Sphere |
- |
- |
✔ |
- |
✔ |
- |
Nutanix AHV |
- |
- |
✔ |
- |
✔ |
- |
Proxmox VE |
- |
- |
✔ |
- |
✔ |
- |
QingCloud |
- |
- |
✔ |
- |
- |
- |
Alibaba Cloud Apsara Stack |
- |
- |
✔ |
✔ |
✔ |
✔ |
JDStack |
- |
- |
✔ |
✔ |
✔ |
✔ |
TCE |
- |
- |
✔ |
✔ |
✔ |
✔ |
GaussDB |
✔ |
✔ |
✔ |
✔ |
✔ |
- |
SAP HANA |
✔ |
✔ |
✔ |
✔ |
✔ |
- |
HDFS |
✔ |
✔ |
✔ |
✔ |
✔ |
- |
Greenplum |
- |
- |
- |
- |
- |
- |
Elasticsearch |
- |
- |
- |
- |
- |
- |
Clickhouse |
- |
- |
- |
- |
- |
- |
MongoDB |
- |
- |
✔ |
- |
- |
- |
Kubernetes |
✔ |
- |
✔ |
✔ |
✔ |
✔ |
• Supports unified management of data protection policies
– SLA: It is a policy group for managing the data lifecycle, typically including policies such as data backup and data replication, to manage the entire process from data creation to eventual destruction. Additionally, the SLA can be reused, which simplifies the management and maintenance of tasks.
• Backup Policy: Supports triggers by minute, hour, day, week, month, quarter, and year schedules; supports configuring different backup types - full, incremental, incremental forever, log, and differential backups; supports GFS retention policy; supports backup windows, during which backup can be prohibited or limited in speed.
• Replication Policy: Supports intra-domain replication (i.e., replication to tape) and inter-domain replication (i.e., remote replication) policies; supports immediate replication after backup point in time is generated, as well as manual configuration of replication cycles such as day, week, month, quarter, and year schedules; supports copy retention policy; supports replication windows, during which replication speed can be limited.
• Snapshot Policy: Allows to configure snapshot cycles, snapshot initiation times, snapshot windows, and snapshot retention periods, as well as the number of snapshots to retain.
– Supports D2D2T (Disk to Disk to Tape), i.e., backing up the production data to a local storage pool and then replicating it to tape. During data recovery, the data in the tape storage pool can be directly restored to the production system or first replicated to any local storage pool for data thawing before restoring to the production system. This method of restoring data after thawing accelerates the data recovery efficiency and is suitable for full data recovery and large data volume recovery scenarios.
• Supports tape storage pools, including capabilities for creating, deleting, modifying, and querying the storage pool.
• The local storage pools can be local block storage pools, SAN storage pools, and NAS storage pools.
Currently only files can be replicated to tape.
Multi-Cloud Disaster Recovery and Migration
Multi-cloud disaster recovery is the capability of disaster recovery and migration for business systems under multi-cloud and hybrid cloud infrastructure architectures. It ensures the continuity of business systems while providing unified management of multiple clouds, simplifying management and operations. Meanwhile, drill is supported.
Disaster recovery and migration are supported for the following applications.
Application |
Disaster Recovery |
Migration |
Solution |
File |
✔ |
✔ |
Regular replication |
Volume |
✔ |
✔ |
Real-time replication |
Virtual Machine Replication to Huawei Public Cloud |
✔ |
✔ |
Real-time replication |
Virtual Machine Replication to Huawei Cloud Stack Version 8.x |
✔ |
✔ |
Real-time replication |
MySQL |
✔ |
✔ |
Logical data replication |
Alibaba Cloud RDS for MySQL |
✔ |
✔ |
Logical data replication |
Huawei Cloud RDS for MySQL |
✔ |
✔ |
Logical data replication |
Tencent Cloud RDS for MySQL |
✔ |
✔ |
Logical data replication |
China Unicom Cloud RDS for MySQL |
✔ |
✔ |
Logical data replication |
Huawei Cloud GaussDB (for MySQL) |
✔ |
✔ |
Logical data replication |
MongoDB |
✔ |
✔ |
Logical data replication |
Alibaba Cloud Cloud Database MongoDB Edition |
✔ |
✔ |
Logical data replication |
Huawei Cloud GaussDB (for MongoDB) |
✔ |
✔ |
Logical data replication |
Tencent Cloud TencentDB for MongoDB |
✔ |
✔ |
Logical data replication |
PostgreSQL |
✔ |
✔ |
Logical data replication |
Tencent Cloud Cloud Database TencentDB For PostgreSQL |
✔ |
✔ |
Logical data replication |
Huawei Cloud RDS For PostgreSQL |
✔ |
✔ |
Logical data replication |
Alibaba Cloud RDS For PostgreSQL |
✔ |
✔ |
Logical data replication |
SQL Server |
✔ |
✔ |
Logical data replication |
Huawei Cloud RDS For SQL Server |
✔ |
✔ |
Logical data replication |
Tencent Cloud RDS For SQL Server |
✔ |
✔ |
Logical data replication |
Alibaba Cloud RDS For SQL Server |
✔ |
✔ |
Logical data replication |
Microsoft Cloud RDS For SQL Server |
✔ |
✔ |
Logical data replication |
Disaster Recovery Management
Based on the open architecture of the platform, disaster recovery plans can be formulated for various business systems, and disaster recovery drills can be automated. This helps customers improve disaster response efficiency, enhance business continuity assurance capabilities, and ensure organizational security and compliance.
Functions and Features
• Recovery Resource Management
– Supports management of physical clients, virtual clients, and object storage recovery resources.
– Supports restoring application states and resource cleanup after disaster recovery and drills.
• Disaster Recovery Policy
– Supports a policy model for immediate recovery after backup completes, with retries available in case of execution failure.
– Supports periodic recovery policy models with weekly, monthly, quarterly, yearly, and excluding sensitive times policies, with retries available in case of execution failure.
– Supports adding multiple recovery policies to a disaster recovery and drill workflow as needed.
• Disaster Recovery Plan Management
– Supports configurations for disaster recovery, verification, cleanup, application, antivirus, and scripts. Workflow nodes can be configured by referencing disaster recovery configurations, and the execution of workflow nodes is completed by loading these configurations to achieve corresponding functions.
– An open, wizard-style workflow orchestration design that does not require manual dragging of nodes, without sequence restrictions on node types. It supports both serial and parallel orchestration models, allowing disaster recovery workflows to be arranged based on business scenarios.
– Supports group management of workflows for managing disaster recovery plans for different failure scenarios and failure levels of application systems.
• Disaster Recovery Drill
– Supports automatic orchestration of disaster recovery plans based on the application system architecture, with automated scheduling and recovery resource cleanup through disaster recovery policies, enabling cyclic automated disaster recovery drills and automatic report generation.
– Supports built-in antivirus library and engine updates, allowing parallel virus scanning, antivirus, and isolation for data recovery, instant recovery, and platform-level disaster recovery data.
– Supports deploying data sandboxes on the VMware virtualization platform to create a network-isolated environment. Application systems deployed on the VMware platform can directly use the application system during disaster recovery drills without modifying virtual machine IPs and application configurations, avoiding network conflicts with the production environment.
• Disaster Recovery Reports
– Disaster recovery report template management supports built-in report templates and custom report templates. It supports cloning built-in report templates to create custom report templates, with templates available for preview.
– Disaster recovery reports can be exported in PDF format, and report templates can be bound to workflows. Workflows can automatically generate disaster recovery reports based on the set report templates, which can be sent via emails.
– Disaster recovery report document contents include the disaster recovery plans used, the execution process and results of disaster recovery, and the results and process of virus scanning drills.
Compatibility
– The [Data Recovery and Drill, Workflow] compatibility is as follows.
Database: Oracle, Kingbase, MySQL, SQL Server, DB2, Dameng, Generic APP, TDSQL, GoldenDB, TiDB, GreenPlum.
Big Data Platform: SAP HANA, GaussDB A, GaussDB T.
Unstructured Data: File (NAS), Object Storage, Disaster Recovery and Migration - Platform Level Replication and Disaster Recovery.
Virtualization Platform: VMware.
– The [Antivirus] compatibility is as follows.
File, VMware, OSS Object Storage.
– The [Data Sandbox] compatibility is as follows.
VMware
Application-level Disaster Recovery
The production systems of enterprises and organizations can still run normally based on multi-level disaster recovery solutions after a disaster occurs.
Functions and Features
• Application-level Disaster Recovery Plan
Based on application topology architecture and business architecture, risk analysis is conducted to identify various potential physical fault and business fault scenarios. Combining fault scenarios, disaster recovery and workflow orchestration is configured for backup and disaster recovery data to specify customized disaster recovery plan for application systems.
• Application-level Disaster Recovery
Through automated disaster recovery drills, availability verification, and one-click application system takeover capabilities, the application system can be quickly and smoothly taken over during a disaster, reducing business interruption time.
Data Use
Test Data Management
Through steps such as data collection, data masking, and distribution, raw data with a certain level of complexity is used in the software development and testing process, realizing the reuse of backup data and unlocking its value.
Test Data Management has the following capabilities.
• Supports data desensitization
• Supports data mirroring
Data mirroring supports remote replication
• Supports automated workflows
• Supports data slimming
The following application system account systems and tenant account systems support data desensitization and mirror management.
Application Type |
Data Masking |
Mirror Management |
Oracle |
✔ |
✔ |
MySQL |
✔ |
✔ |
User System
System Account System
AnyBackup Family 8 currently supports three types of user roles.
• Super administrator
• Operator
• Inspector
[Restrictions] Inspectors are not supported in resource-centered management model.
Description of the various user roles.
User Role |
Permission |
Super Administrator |
Responsible for monitoring management, resource management, backup and recovery, disaster recovery and migration, copy management, disaster recovery management, data services, policy management, storage management, cluster management, user and organization management, system management. |
Operator |
Responsible for monitoring management, resource management, backup and recovery, disaster recovery and migration, copy management, disaster recovery management, data services, policy management, storage management. |
Inspector |
Only has viewing permissions, supports viewing of monitoring tasks, monitoring events or alarms, and tasks related to backup and recovery. |
• Operators are created by the super administrator. They can view and use the system resources allocated to them, as well as view and manage all business within their scope of permissions.
Operators are supported in the following application backup and recovery.
Oracle
|
MySQL
|
SQL Sever |
Caché |
Dameng |
Kingbase |
Sybase |
Shentong |
PostgreSQL |
DB2 |
MariaDB |
TeleDB |
TDSQL |
TelePG |
MongoDB
|
openGauss |
Informix |
GBase 8s |
SinoDB |
TiDB |
Exchange Server |
GaussDB T |
Kingwow |
SAP HANA |
GaussDB A |
HDFS |
VMware |
FusionCompute |
H3C CAS/UIS |
SmartX |
ZStack |
CNware |
OpenStack |
Alibaba Cloud Apsara Stack |
Huawei Cloud Stack |
JDStack |
TCE |
Nutanix AHV |
IncloudSphere |
ProxmoxVE |
MogDB |
Kubernetes |
Volume |
File (in job-centered mode) |
|
In resource-centered mode, file backup and recovery are only supported under super administrators.
The following application disaster recovery and migration are supported under operators.
File |
Volume |
Virtual Machine Replication to Huawei Public Cloud |
Virtual Machine Replication to Huawei Cloud Stack Version 8.x |
MySQL |
Alibaba Cloud RDS for MySQL |
Huawei Cloud RDS for MySQL |
Tencent Cloud RDS for MySQL |
China Unicom Cloud RDS for MySQL |
Huawei Cloud GaussDB (for MySQL) |
MongoDB |
Alibaba Cloud Cloud Database MongoDB Edition |
Huawei Cloud GaussDB (for MongoDB) |
Tencent Cloud TencentDB for MongoDB |
|
PostgreSQL, Tencent Cloud Cloud Database TencentDB For PostgreSQL, Huawei Cloud RDS For PostgreSQL, Alibaba Cloud RDS For PostgreSQL disaster recovery and migration are only supported by super administrators.
SQL Server, Huawei Cloud RDS For SQL Server, Tencent Cloud RDS For SQL Server, Alibaba Cloud RDS For SQL Server, Microsoft Cloud RDS For SQL Server disaster recovery and migration are only supported by super administrators.
Operators are supported for the following data services: data masking and mirror management.
• Supports inspectors: only have viewing permissions, supporting the viewing of monitoring tasks, monitoring events or alarms, and tasks related to backup and recovery.
Inspectors are supported in the following applications.
File (in job-centered mode) |
Volume |
Object Storage |
XenServer |
HDFS |
QingCloud |
Oracle |
MySQL |
SQL Sever |
Caché |
Dameng |
Kingbase |
Sybase |
Shentong |
PostgreSQL |
DB2 |
MariaDB |
TeleDB |
TDSQL |
TelePG |
Kingwow |
openGauss |
Informix |
GBase 8a |
SinoDB |
TiDB |
Exchange Server |
OceanBase |
SAP HANA |
GaussDB A |
GaussDB T |
|
|
|
|
Tenant Account System
Supports multi-tenant design. Tenants are created by the super administrator, who also creates user roles for tenant administrators to manage internal resources and disaster recovery business. Production resources and disaster recovery business resources are isolated between different tenants. Tenant administrators can access production resources independently. Super administrators cannot see tenant data but can assign quotas to tenants.
AnyBackup Family 8 currently supports 2 types of user roles.
• Tenant Administrator
• Tenant Operator
Description of the various user roles.
User Role |
Permission |
Tenant Administrator |
Responsible for monitoring management, resource management, backup and recovery, disaster recovery and migration, copy management, disaster recovery management, data services, policy management, storage management, user and organization management. |
Tenant Operator |
Responsible for monitoring management, resource management, backup and recovery, disaster recovery and migration, copy management, disaster recovery management, data services, policy management, storage management. |
The tenant account system is supported in the following application backup and recovery.
File (in job-centered mode) |
Object Storage |
Lustre |
SinoDB |
Sybase |
Kingbase |
MySQL |
MariaDB |
TeleDB |
TDSQL |
SQL Server |
DB2 |
Oracle |
PostgreSQL |
TelePG |
GaussDB T |
openGauss |
Dameng |
Informix |
GBase 8s |
MogDB |
TiDB |
Exchange Server |
Shentong |
Caché |
SAP HANA |
GaussDB A |
HDFS |
VMware |
FusionCompute |
H3C CAS/UIS |
SmartX |
ZStack |
CNware |
OpenStack |
Alibaba Cloud Apsara Stack |
Huawei Cloud Stack |
JDStack |
TCE |
Nutanix AHV |
IncloudSphere |
Proxmox VE |
MogDB |
Kubernetes |
Volume |
The tenant account system is supported in the following application disaster recovery and migration.
File |
Volume |
Virtual Machine Replication to Huawei Public Cloud |
Virtual Machine Replication to Huawei Cloud Stack version 8.x |
MySQL |
Alibaba Cloud RDS for MySQL |
Huawei Cloud RDS for MySQL |
Tencent Cloud RDS for MySQL |
China Unicom Cloud RDS for MySQL |
Huawei Cloud GaussDB (for MySQL) |
MongoDB |
Alibaba Cloud Cloud Database MongoDB Edition |
Huawei Cloud GaussDB (for MongoDB) |
Tencent Cloud TencentDB for MongoDB |
|
PostgreSQL, Tencent Cloud Database TencentDB For PostgreSQL, Huawei Cloud RDS For PostgreSQL, Alibaba Cloud RDS For PostgreSQL disaster recovery and migration are only supported by tenant administrators.
SQL Server, Huawei Cloud RDS For SQL Server, Tencent Cloud RDS For SQL Server, Alibaba Cloud RDS For SQL Server, Microsoft Cloud RDS For SQL Server disaster recovery and migration are only supported by tenant administrators.
The tenant account system is supported for the following data services: data desensitization, mirroring management.
Ransomware
Data Im mutability
– Immutable storage provides kernel-level data read and write protection capabilities. By strictly controlling I/O access and kernel program authentication for backup data storage paths, it blocks all illegal processes from reading and writing data to achieve protection purposes.
Air-Gap
– By planning an isolated recovery environment for users that is separated from the backup domain network, secure data is regularly replicated from the backup domain as a copy. After exceeding the replication window period, the isolated recovery environment automatically disconnects from the network plane, effectively blocking ransomware attack routes and preventing malicious data access and encryption tampering. If the production system and backup system are attacked by ransomware, a secure copy can be quickly obtained from the isolated recovery environment to restore the business system.
Two-Factor Authentication
– Ensures the security of user accounts through account password + SMS verification code or email verification code.
Data and Key Security
• Supports data encryption, encryption in transfer, and three-layer key system to ensure data storage and transmission security.
• Supports virus scanning and killing: Through the built-in or external virus database and antivirus engine in the disaster recovery management, the recovered data can be checked, killed and quarantined. Through this capability, whether the backup data is infected by viruses can be verified to ensure data security.
• Supports self-backup for management metadata.
Access Control
• Supports two-factor authentication via account password + SMS verification code or email verification code to ensure the account security.
• Provides role-based fine-grained access control and security policies such as password complexity detection, account expiration settings, IP whitelist and blacklist, login failure lockout, user disabling, and more, ensuring data usage security.
• Supports approval workflows, allowing for approval of actions such as manual backup, manual restore, manual cleanup, and creation, editing, deletion of SLAs by effective users (i.e., applicants). These actions can only be carried out after approval by the approver, ensuring data management security.
Specification
Number of Cluster Nodes
– In case of converged deployment: supports deployment of 3-64 nodes, supports single node deployment.
– In case of separated deployment:
n Management console: supports deployment of single node or 3-8 nodes.
n Storage Services:
A storage service supports deployment of a single node or 3-64 nodes.
The maximum total number of nodes for all storage services in a management console cannot exceed 64 nodes.
n The management console supports connecting up to 10 storage services.
Capacity
– Local Block Storage Pool 64 nodes
n Maximum storage capacity per node: 500TiB.
– Distributed storage pool (three copy, EC) 16 nodes * 4
n Maximum storage capacity per node: 165TiB
Performance Reference
– 4U Server, 32 HDD Groups RADI5, Local Block Storage Pools.
Single-node throughput: backup 2.9GiB/s, recovery 1.8GiB/s
Three-node cluster throughput: backup 6.8GiB/s, recovery 3.7GiB/s
– 4U server, each node consists of: 36 x 8TB HDDs + 4 x 3.2TB NVME SSDs + 25GE NICs
– Distributed storage pool (three copy): three-node cluster throughput: backup 3.8GiB/s, recovery 2.7GiB/s
– Distributed Storage Pool (EC 2+1): three-node cluster throughput: backup 4.4GiB/s, recovery 3.7GiB/s
– Distributed Storage Pool (EC 4+2:1): Three-node cluster throughput: Backup 4.72GiB/s Recovery 4.9GiB/s
Users
The default maximum total number of users is 20,000 (total number of users includes super administrators, operators, tenant administrators, and tenant operators).
See AnyBackup Family 8 Product Specification List for details.
Other
Performance Reference
Client supports on-demand deployment, push installations and remote upgrades
Alarm/Event Management
• Supports alarm rules: support the configuration of alarm rules for task failures, system resource anomalies, storage anomalies, and more.
• Supports event, alarm filtering: Specific filters based on user name, date, type, and level are supported.
• Supports event, alarm exporting: Supports exporting xls, txt, csv files.
• Alarm notification: Supports email, SMS, Enterprise WeChat, DingTalk, SNMP and Syslog push notifications.
Cluster and Node Management
• Supports node shutdown, restart, SSH management, details display, service information status display, and more.
• Supports displaying the topology diagram of the management console and storage service, displaying the list of storage services.
Network Plane
• Supports configuration of management network, storage network, backup network, and replication network, and supports modifying the backup network IP and replication network IP.
Network Environment
• Internal and External Networks
– Internal and external networks are supported for the following application backup and recovery
File |
Object Storage |
VMware |
FusionCompute |
H3C CAS/UIS |
SmartX |
CNware |
ZStack |
InCloud Sphere |
Nutanix AHV |
Proxmox VE |
OpenStack |
Huawei Cloud Stack |
Alibaba Cloud Apsara Stack |
JDStack |
TCE |
Oracle |
Kingbase |
MariaDB |
openGauss |
Exchange Server |
MySQL |
Sybase |
TeleDB |
Informix |
SQL Sever |
Shentong |
TDSQL |
GBase 8s |
GBase 8a |
Kingwow |
Caché |
PostgreSQL |
TelePG |
Dameng |
DB2 |
TiDB |
GoldenDB |
MogDB |
|
– Internal and external networks are supported for the following application disaster recovery and migration.
File (local file system/volume) |
Hosts |
Platforms |
• IPv4 single-stack network
AnyBackup supports IPv4 single-stack networks in all capabilities by default.
• IPv6 single-stack network
– The following capabilities are supported in IPv6 single-stack networks.
Oracle Backup and Recovery |
Oracle CDM |
File Backup and Recovery |
Object Storage Backup and Recovery |
Disaster Recovery Management |
GaussDB T Backup and Recovery |
SAP HANA Backup and Recovery |
HDFS Backup and Recovery |
Kubernetes Backup and Recovery |
|
SAN and NAS gateways are supported in IPv6 single-stack networks.
[Restrictions] Data Sandbox is not supported in IPv6 single-stack networks.
• [IPv4, IPv6 Dual Stack Network]
– The following capabilities are supported in IPv4, IPv6 dual-stack networks.
Oracle Backup and Recovery |
File Backup and Recovery |
Object Storage Backup and Recovery
|
GaussDB T Backup and Recovery |
Disaster Recovery Management |
SAP HANA Backup and Recovery |
HDFS Backup and Recovery |
Kubernetes Backup and Recovery |
|
|
[Restrictions]
- Data Sandbox does not support IPv4 and IPv6 dual-stack networks.
- SAN and NAS gateways are not supported in IPv4 and IPv6 dual-stack networks.
Task Center & Activity Center: Realizes unified management of user tasks and activities.
• Supports system-level, storage service-level, and tenant-level concurrency control, reducing user SLA planning costs. If the concurrency specification is exceeded, it will switch to queue waiting for execution.
• [Specifications]
– The default value for the global task concurrency and queue number is 300 * number of business nodes, with an upper limit of 2,500.
– The default value for task concurrency and queue number within a single storage service is 40 * number of storage nodes, with an upper limit of 200 * number of storage nodes within the storage service, and it cannot exceed the global quota