Hot Disaster Recovery (HDR)

It supports same-city active-active, active-standby switchover, two sites in three centers, and other disaster recovery architectures, meeting different levels of RPO/RTO requirements.

It supports automated disaster recovery switchover orchestration and regular disaster recovery drills, ensuring the disaster recovery plan is always available while meeting industry compliance audit requirements.

It fully meets Classified Protection 2.0 and industry compliance requirements related to disaster recovery and backup, providing full-process monitoring and alerting.

No additional recovery host is required. The backup system can create its own emergency takeover virtual hosts and provide services externally without integrating or configuring a third-party virtualization platform. It also supports starting multiple virtual machines simultaneously from the same backup point, with each virtual machine configurable with different IP addresses, different CPU counts, and different memory sizes to meet different functional and performance requirements such as copy usage and system failure emergency response.

Yes, it can be rate-limited. During backup, the backup and recovery system supports network bandwidth usage rate limiting and disk read/write usage rate limiting to ensure that the impact of backup on production is small and within a controllable range. At the same time, source-side global deduplication technology is used, reducing the amount of transmitted data by more than 90%.

Yes. Big data components cover HDFS, HBase, Hive, ElasticSearch, Redis, and ClickHouse, and support fine-grained backup and recovery: HDFS single-file and directory level, HBase single-table and NameSpace level, Hive table level, ElasticSearch index level, and ClickHouse table level. For data warehouses, it supports online backup of DWS databases and applications, supports agentless deployment without installing clients, and supports deduplication and compression. The entire backup task configuration process is graphical, with no need to write scripts.

Yes, both. Global search has built-in support for global searching of the copy contents of files, virtual machines, and HDFS, supports fuzzy matching search by file name and directory name, and supports fine-grained recovery of individual files after search. Data masking has built-in support for masking database backup copy data, with preset masking policies that meet the regulatory requirements of PCI-DSS, PII, and HIPAA, and also supports custom masking policies.

Yes, it supports delegated administration. Users of the backup system can be managed hierarchically, such as system administrators, ordinary users, and other different roles, and all user operations are recorded to meet operation audit requirements.

The drill target machine does not need any preconfigured drill environment to immediately carry out drill reconstruction — the target machine may have no operating system, an operating system inconsistent with the original machine, no application system, and no database. In addition, for X86 and C86 production environments, an isolated private virtualization verification environment can be self-built. Regardless of whether the backup task is stopped, multiple backup points of one backup task can be selected at the same time to perform virtualization verification, validating the consistency and reliability of backup data; when a disaster occurs, the binary search method is used to quickly locate the best historical point for data recovery.