Introduction
This document provides last-minute information about AnyBackup Family 7.0.18.3. New features, new compatibilities and enhancements of AnyBackup Enterprise, AnyBackup CDM, AnyBackup Express and AnyBackup Disaster Recovery Management can be found in the following sections of this document.
The release version of AnyBackup Family 7.0.18.3 is available from May 11, 2024. If you are upgrading from previous versions, please review the upgrade guide closely before performing the upgrade.
See next:
- New Major Features
- New Features
- New Compatibilities
- Enhancements
AnyBackup Family 7
【New Major Features】
· [Server Deployment] New feature:
- External KingBase V8 is added as the database of AnyBackup management console, so that the need for replacing modules with domestic ones can be satisfied.
【New Features】
Backup and Recovery
· New Application [HuaWei Cloud GaussDB]:
- Full backup, incremental backup, and recovery are supported.
- Concurrent backup for multiple clients is supported, so that backup efficiency is improved.
- Advanced features like Deduplication, Data Compression, Data Encryption, and Auto Retry are supported.
· [MongoDB] New features:
- Slave nodes can be configured for backing up MongoDB replica set clusters.
· [Object Storage] New features:
- Backup data sources can be filtered. You can filter out unwanted objects by file name, file format, directory, or time.
· [Hyper-V] New features:
- D2D2T (tape archive) is supported.
- Hyper-V backup data can be restored to Huawei public cloud heterogeneously.
· [CTCloud] New features:
- Full backup, incremental backup and recovery of ECS (Elastic Cloud Server) are supported.
- Advanced features like Deduplication, Data Compression, Data Encryption, and Auto Retry are supported.
· [HUAWEI Cloud Stack] New features:
- For ECS using OceanStor Pacific storage, iSCSI backup solution is supported, so that the compatibility limitations of VBS backup solution can be lifted.
- Huawei Cloud Stack platform can be backed up without using an operation administrator account.
- ECS backup data can be restored to Huawei public cloud heterogeneously.
- Backup and recovery of volume granularity is supported.
· [Alibaba Apsara Stack] New features:
- The original IP address can be kept after the ECS (Elastic Cloud Server) is restored.
· [CNware] New features:
- Business Group is added to the data source type when you browse backup data sources, to adapt the user's habit of using production system.
· [VMware] New features:
- Virtualization platforms with the same address can be added repeatedly.
- Virtual machines with user snapshots can be backed up.
- Disks can be backed up and restored concurrently, so that the backup performance of virtual machines can be improved.
· [FusionCompute] New features:
- Data backup can be performed by adopting consistent snapshot, which is used to deal with the issue that the virtual machine snapshot is stuck or fails in some scenarios.
· [H3C CAS] New features:
- Snapshots can be unretained after VM backups to save production storage space.
· [OpenStack] New features:
- Backup and recovery on OpenStack platforms under the scenario of accessing multiple Ceph storages are supported, so that the deployment scenario of a single cloud host across multiple production storages can be met.
- Backup and recovery in the scenario where the network of production platform is IPv6 are supported.
· [SANGFOR HCI] New features:
- Agentless backup and recovery are supported (that is, the backup and recovery agent does not need to be installed on the production node).
· [SmartX] New features:
- D2D2T (tape archive) is supported.
· [Virtualization/Cloud Platform Management] New features:
- Non-built-in clients can be chosen when you create or edit platforms. (Supported applications: ZStack, FusionCompute, XenServer, Huawei Cloud Stack, and OpenStack)
· [Backup Data Retention Policy] New features:
- The Strict Retention option is added to the policy of Data Retention Period. If any point in time in the copy does not exceed the retention period, the copy is retained, to ensure that users have data available within the retention period.
· [MySQL] New features:
- A specified node can be configured for backup, reducing the impact on production.
- In MySQL cluster failover scenario, whether the backup job switches from incremental backup, differential backup or log backup to full backup can be specified via configuring the file, to minimize the impact on business.
- Lock Tables timeout can be configured. If the lock time exceeds the configured time, the backup will fail to give priority to the user's production business.
- Query timeout can be configured. When a long-running query exists and the query time exceeds the configured time, the backup will fail to give priority to the user's production business.
- When continuous log backup is started manually, data and logs can be backed up at the same time. It can meet the requirements of performing log backup, or performing log backup and data backup simultaneously at any time.
- In the data backup scenario, the redo caching method can be converted into pipeline method without occupying the user's local production space.
- In the data recovery scenario, the default binglog log path can be changed to the installation directory to prevent the system space from being too full.
- MySQL log paths can be customized, and related logs can be downloaded from the console.
· [openGauss] New features:
- Whether the backup job switches to full backup can be specified via configuring the file, to minimize the impact on user's business.
- In the data backup scenario, the continuity of log backup can be detected and the backup serial number can be obtained, to facilitate users to troubleshoot issues.
· [KingBase] New Features:
- KingBase databases started in PostgreSQL mode can be backed up and restored.
- KingBase databases started in MySQL mode can be backed up and restored.
- KingBase databases started by port number can be backed up and restored.
· [PostgreSQL] New features:
- PostgreSQL databases started in postmaster mode can be backed up and restored.
- PostgreSQL databases started by the command line (for example, using the commands --config -c) can be backed up and restored.
- PostgreSQL databases in scenarios where the database archiving mode is always can be backed up and recovery.
- The continuity of archive logs can be detected in the data backup scenario. If the archive log is continuous, the incremental backup will not be converted into a full backup, which can save storage space for users.
· [Informix] New features:
- Log backup can be started directly in continuous backup. It can reduce the impact on production business, lower the backup window, and improve RPO in case of job exception.
· [Oracle RAC] New features:
- Whether to receive alarms in the scenario that one node succeeds and another node fails can be configured.
- In the backup and recovery scenario, whether to ignore Oracle ORA errors can be configured, and warnings can be set for the ignored errors. Users can flexibly configure whether to accept or ignore errors to improve ease of use.
· [EOSS] New features:
- O&M cleanup capability is added. Residual bucket data can be cleaned up manually to save data storage space.
- Anomaly sensing capability is provided for the storage management cluster. When an exception occurs in the storage management cluster, the task fails to start by reporting an error, so that the situation that the backup job runs successfully but the data cannot be restored normally can be avoided.
· [D2T/D2D2T] New features:
- Index tapes can be copied and exported, and the copied index tapes and data tapes can be imported into a new environment. The tape data can be reconstructed and restored remotely when a disaster occurs.
· [Remote Replication] New features:
- Only the full backup point in time on a certain day of each month/week can be synchronized.
- Only "full backup + incremental backup" points in time can be synchronized, which can filter differential points in time and log archive points in time.
· [Data Archive] New features:
- The history list can be exported.
· [D2D2T] New features:
- Data archived to tape can be stored and encrypted, and supported encryption algorithm include AES256 and SM4.
Copy Data Management
· [VMware] New features:
- Backup auto retry is supported if the virtual machine backup fails.
- Disks can be backed up and restored concurrently, so that the backup performance of virtual machines can be improved.
· [SLA] New features:
- The timeout for backup jobs can be set, so as to avoid backup running for a long time beyond the backup window period and affect the normal operation of the production system.
· Add Copy Data Management feature in [Dameng]:
- Full backup, incremental forever backup, and transactional log backup are supported.
- DMDSC cluster and Dameng standalone are supported.
- Archive logs in the Dameng database can be deleted periodically.
- Multi-channel backup is supported, so that backup performance is improved.
- SLA policies can be configured. You can set auto-start schedule for jobs to perform regular data protection automatically.
- Instant recovery to the original machine or a dissimilar machine is supported, which can quickly launch the user's production business and realize minute-level mount recovery.
- Recovery at a specified point in time is supported. Data at a specified point in time can be restored.
- Recovery at any point in time is supported. Data at any point in time within the specified interval can be restored.
- Remote replication is supported.
- Log alarm is supported.
· [Oracle RAC] New features:
- Whether to receive alarms in the case that one node succeeds and another node fails can be configured.
- In the backup and recovery scenario, whether to ignore Oracle ORA errors can be configured, and warnings can be set for the ignored errors. Users can flexibly configure whether to accept or ignore errors to improve ease of use.
· [MySQL] New features:
- Lock Tables timeout can be configured. If the lock time exceeds the configured time, the backup will fail to give priority to the user's production business.
- Query timeout can be configured. When a long-running query exists and the query time exceeds the configured time, the backup will fail to give priority to the user's production business.
Public
· [Client] New features:
- Whether the host machine is a KVM virtual machine can be automatically recognized.
- The client machine code can be reset automatically to avoid the issues of connection conflicts of the original client and backup interruption of the original production environment caused by virtual machine cloning, and virtual machine recovery and reconstruction.
· [Security Policy] New features:
- User account can be disabled. Users who have not logged in for more than X days will be automatically disabled.
· [Client Installation] New features:
- For the scenario that the client is directly bound to tenants/operators, the expiration time of the password for accessing the client can be changed via modifying the configuration file, which solves the disadvantage of frequently using new passwords to install clients.
· [Client Log] New features:
- Modifying the output path of the client logs during the client is being deployed or after the deployment.
- Client logs can be dumped and compressed. You can configure dump cycle and file size limit.
- Client log space can be detected automatically. When the client log space is less than 100M, the backup or recovery job will fail immediately and a system alarm will be automatically pushed.
This capability can prevent excessive client logs from affecting system operation.
· [Public] New features:
- For databases without logging enabled, logs can be printed automatically when you perform backup and recovery.
【New Compatibility】
Backup and Recovery
· [Transwarp Data Hub]:
- TDH 7.0 (Hadoop 2.7.2, HBase 1.3.1) + Kylin V10 aarch64
- TDH 9.0 (Hadoop 3.1.4, HBase 2.2.6) + Kylin V10 x86_64
· [MongoDB]:
- MongoDB 3.6.13 replica set/shard set/standalone + openEuler 22.03 LTS x86_64
- MongoDB 3.6.21 replica set/shard set/standalone + Red Hat Enterprise Linux 7.2 x86_64
- MongoDB 6.0.13 replica set/shard set/standalone + CentOS 7.8 x86_64
· [File]:
- Anolis OS 8.6 x86_64 ext3, ext4, xfs
- OpenEuler 22.03 x86_64 ext3, ext4, xfs
- Kylin Server 10 SP2 x86_64 ext3, ext4, xfs
- Oracle Enterprise Linux 7.4 x86 _ 64 ext3、ext4
- Ubuntu 20.04.1 x86_64 ext4
- Ubuntu 20.04.2 x86_64 ext4
- Ubuntu 20.04.3 x86_64 ext4
- CentOS 8.5 86_64 ext4
- Red Hat Enterprise Linux 6.10 x86_64 ext4
- Windows Server 2022 x86_64 NTFS
· [Volume]:
- Windows Server 2022 x86_64 NTFS
- Windows 11 x86_64 NTFS
- Red Hat Enterprise Linux 6.10 x86_64 ext2, ext3, ext4
- Red Hat Enterprise Linux 8.6 x86_64 ext2, ext3, ext4
- Red Hat Enterprise Linux 8.8 x86_64 ext2, ext3, ext4
- CentOS 7.6 x86_64 ext2, ext3, ext4
- CentOS 8.2 x86_64 ext2, ext3, ext4
- CentOS 8.5 x86_64 ext2, ext3, ext4
- SUSE Linux Enterprise Server 15 SP2, SP3, SP4, SP5 x86_64 ext2, ext3, ext4
- EulerOS 2.9 x86_64 ext2, ext3, ext4
- Ubuntu 18.04.1 (4.15.0-30) x86_64 ext2, ext3, ext4
- Ubuntu 20.04 x86_64 ext2, ext3, ext4
- Ubuntu 20.04.1 x86_64 ext2, ext3, ext4
- Ubuntu 22.04.2 x86_64 ext2, ext3, ext4
- Ubuntu 22.04.3 x86_64 ext2, ext3, ext4
- BC-Linux8.2 x86_64 ext2, ext3, ext4
- BC-Linux8.4 x86_64 ext2, ext3, ext4
- BC-Linux for Euler 21.10 x86_64 ext2, ext3, ext4
- BC-Linux for Euler 22.10 x86_64 ext2, ext3, ext4
- Anolis OS 8.6 x86_64 ext2, ext3, ext4
- Kylin Server 10 SP2 x86_64 ext2, ext3, ext4
- Kylin Server 10 SP2 x86_64 ext2, ext3, ext4
- openEuler 22.03 x86_64 ext2, ext3, ext4
- Oracle Linux 6.10 x86_64 ext2, ext3, ext4
· [Operating System]:
- Windows 11 x86_64
- Windows Server 2003 R2 x86_64
- Windows Server 2022 x86_64
· [AnyShare]:
- AnyShare 7.0.5.0
- AnyShare 7.0.5.1
- AnyShare 7.0.5.2
- AnyShare 7.0.5.3
- AnyShare 7.0.5.4
- AnyShare OpenEuler deployment scenario
- Compatible with disaster recovery object storage: XSKY object storage
· [Kubernetes]:
- CCE (Cloud Container Engine)
- RedHat OpenShift Container Platform
- Kubernetes v1.28
· [Huawei Cloud Stack]:
- Compatible storage: OceanStor Pacific 8.1.5
- Compatible platform: Huawei Cloud Stack 8.3.0
· [Alibaba Apsara Stack]:
- Apsara Stack 3.16
· [QingCloud]:
- QingCloud 6.0.3
· [CNware]:
- CNware 8.2.2 (aarch64)
- CNware 9.3
· [H3C CloudOS7]:
- Compatible platform: H3C CloudOS7 E7109
- Compatible platform: H3C CloudOS7 E7110
- Compatible storage: ONEStor 5219
· [VMware]:
- VMware 8.0b
- VMware 8.0U2
· [Heterogeneous Recovery of VMware to FusionCompute]:
- Compatible target platform: FusionCompute 8.3.0
· [Heterogeneous Recovery of VMware to Huawei Cloud Stack]:
- Compatible operating system which can auto repair virtual machines: Windows Server 2022 x86_64
· [FusionCompute]:
- FusionCompute 8.5.0
- FusionCompute 8.6.0
· [H3C CAS]:
- Compatible Platform: UIS E0881P03
- Compatible platform: UIS E0750P10
- Compatible platform: CAS E0730P11
- Compatible platform: CAS E0781P02
- Compatible platform: CAS E0782P03
- Compatible Client OS: Apollo x86_64
· [SANGFOR HCI]:
- Compatible platform: SANGFOR HCI 6.9.0 (x86_64, aarch64)
- Compatible platform: SANGFOR HCI 6.9.1 (aarch64)
- Compatible platform: SANGFOR HCI 6.10.0 (x86_64, aarch64)
· [OpenStack]:
- Compatible client operating system: Kylin V10
· [SmartX]:
- Compatible platform: CloudTower 3.2.0
- Compatible platform: CloudTower 3.2.1
- Compatible platform: CloudTower 3.4.1
- Compatible platform: CloudTower 4.0.0
- Compatible with SMTX OS: 5.0.6 (x86)
- Compatible with SMTX OS: 5.1.1 (x86)
- Compatible with SMTX OS: 6.0.0 (x86)
· [ZStack]:
- ZStack 4.8
· [InCloud Sphere]:
- InCloud Sphere 6.8.0 (x86_64)
- InCloud Sphere 6.10.1 (x86_64, aarch64)
· [Nutanix AHV]:
- Nutanix AHV 20220304.342
· [MySQL]:
- Ubuntu 16.04.6 LTS x86_64 + MySQL 5.7.44
- CentOS7 x86_64 + MySQL 5.7.44
- CentOS7 x86_64 + MySQL 8.0.34
- CentOS7 x86_64 + MySQL 8.0.35
· [PostgreSQL]:
- Linux 7.9 + PostgreSQL13.2
· [DB2]:
- Redhat 8.8 x86_64 + DB2 11.5.8
Copy Data Management
· [VMware]:
- VMware 8.0b
- VMware 8.0U2
· [SANGFOR HCI]:
- SANGFOR HCI 6.0.0R5
- SANGFOR HCI 6.9.0
· [MySQL]:
- Ubuntu 16.04.6 LTS x86_64 + MySQL 5.7.44
- CentOS7 x86_64 + MySQL 5.7.44
- CentOS7 x86_64 + MySQL 8.0.34
- CentOS7 x86_64 + MySQL 8.0.35
· [Dameng]:
- Kylin Linux Advanced Server release V10 x86_64 + Dameng 8.1
- Kylin Linux Advanced Server release V10 aarch64+ Dameng 8.1
- CentOS 7 x86_64 + Dameng 8.1
- CentOS 7 aarch64 + Dameng 8.1
Continuous Data Protection
· [Volume]:
- SUSE Linux Enterprise Server 11 SP4 X86_64 ext3, ext4
- SUSE Linux Enterprise Server 12 SP5 x86_64 ext3, ext4
- Kylin Linux Advanced Server release v10 x86_64 ext3, ext4
Public
· [Client Deployment]:
- CentOS 8.5 x86_64
- Red Hat Enterprise Linux 8.6 x86_64
- Red Hat Enterprise Linux 8.8 x86_64
- Red Hat Enterprise Linux 9.2 x86_64
- BC-Linux 8.4 x86_64
- BC-Linux 22.10 for Euler x86_64
- Oracle Enterprise Linux 6.10 x86 _ 64
- Oracle Enterprise Linux 7.4 x86_64
- EulerOS 2.0 SP10 aarch64
- Anolis OS 8.6 x86_64
· [Server Deployment]:
- Kylin Linux Advanced Server release V10(Tercel) sw_64 [ShenWei architecture]
- AlmaLinux release 8.8 (Sapphire Caracal) x86_64
- Red Hat Enterprise Linux release 8.8 (Ootpa) x86_64
· [System Kernel]:
- Apollo x86/ARM kernel updated to kernel-5.4.40-2009.48
- Server compatibility: Kylin V10 SP1 OS with kernel version Kernel-4.19.90-23.26.v2101.ky10
· [Immutable Driver] OS:
- Kylin V10 SP1 + 4.19.90-23.26.v2101.ky10 x86 64
- Kylin V10 SP1 + 4.19.90-23.26.v2101.ky10 aarch64
- Kylin V10 SP2 + 4.19.90-24.4.v2101.ky10 x86 64
- Kylin V10 SP2 + 4.19.90-24.4.v2101.ky10 aarch64
- Apollo appliance version + 5.4.40-2009.48.el7a x86 64
- Apollo software version + 5.4.40-2009.48.el7a x86 64
- CentOS7.5 1804 + 5.4.40-2009.48.el7a x86 64
- Apollo appliance version + 5.4.40-2009.48.el7a aarch64
- Apollo software version+5.4.40-2009.48.el7a aarch64
- CentOS7.6 1810
【Enhancements】
Feature Optimization
· [License]:
- AnyBackup Express subscription service relaxes the 50TiB maximum capacity limit and allows to add more than 50 TiB of licensed capacity.
· [Agent]:
- The maximum number of loads for a single proxy service is increased from 1000 to 2000, which improves the concurrency of proxy.
· [Kubernetes]:
- The configured name of the script bound can be viewed in the workload details page.
- The logs of the runner can be pulled to the console. In the case of job exceptions, it can prevent the problem that the logs cannot be kept because the runner is cleared.
- The running node and backup/recovery data size can be viewed in the execution output.
· [Cloud Platform Management]:
- Cloud platforms can be added repeatedly by system administrators or tenant administrators.
- Tenant administrators can add, edit or delete the tenants of the cloud platform added by system administrators.
· [Backup and Recovery]:
- The client can be grouped when you select a client for creating a backup or recovery job, so that the client can be quickly located. (The applications supported: VMware, FusionCompute, OpenStack, Huawei Cloud Stack, and HCS Online)
· [Oracle]:
- Whether to clean the control file backup set generated by backup can be configured as needed, so that the occupation of production storage space can be reduced.
· [Public]:
- The storage path of the pipeline configuration file can be changed from the system directory /tmp to other directories, thereby the risk of deleting pipeline configuration files can be solved and the backup success rate can be improved. (The applications supported: MySQL, Oracle, Informix, Sybase, Dameng, DB2)
· [Backup and Recovery]
- The Deduplication feature is optimized as follows:
Ø The fingerprint loading logic for deduplication jobs in the scenario of concurrent backups is optimized. Concurrent loading of the fingerprint library is supported, so that the problem of long initialization queuing time in the scenario of concurrent deduplication jobs can be solved. In the scenario without disk bottlenecks, the fingerprint loading performance of concurrent multi-job scenarios is improved by about N~xN (N>2, which is the concurrency of the deduplication jobs; x is the number of deduplication nodes).
- The metadata collation mechanism of EOSS is optimized as follows:
Ø The accumulation problem of KV for metadata is optimized, the smoothness and performance of LevelDB sorting are improved, and the problem of long metadata sorting time because of large volume of KV is solved. After optimization, the sorting performance is improved by 8 times.
Ø The EOSS metadata lock mechanism is optimized: the backup throughput of a single metadata database under the scenario of "Cleanup + Sorting + Backup" is improved. The throughput performance of a single metadata database is increased by 2 times.
Interaction Optimization
· [Console Interface]:
- The after-sales contact information is provided. Thus, customers can quickly solve problems by contacting after-sales when encountering urgent problems.
- The QR code of WeChat public account is provided, thus customers can better understand our products and user experience can be improved.
· [Backup]:
- The backup point in time can be viewed in the list of backup jobs, so that the users can view the backed-up data.
- The details of backup jobs can be exported in XLS format.
· [MySQL Backup and Recovery]:
- The eef_proc and MySQLProc logs can be downloaded on the console. You can obtain the logs without logging into the production environment, which is convenient for users to locate problems.
【New Features】
· [Backup and Recovery]
- [AnyShare] The backup feature of document library is offline.
AnyBackup Disaster Recovery Management
【New Features】
· [Automatic recovery]
- CNWare data can be restored, and the built-in verification template can be provided for verifying the availability of restored data, and the cleaning template can be provided for cleaning restored resources.
· [Server Deployment] new feature:
- External KingBase V8 is added as the database of AnyBackup DRM management console, so that the need for replacing modules with domestic ones can be satisfied.
【New Compatibility】
· [Server]:
- Kylin Linux Advanced Server release V10 (Tercel) sw_64 [ShenWei Architecture]
- Red Hat Enterprise Linux release 8.8 (Ootpa) x86_64
【Feature Optimization】
· [Report]
- The export mechanism of workflow reports is optimized. Exporting reports on nodes without the Deployment service is supported.
· [Recovery Orchestration]
- The node orchestration rules of the workflow are optimized. Serial connection of multiple application nodes under the downsteam of a single resource node can be supported, so that the configuration process of the workflow is simplified and the orchestration efficiency is improved.
Tiered Protection for Data CenterData center protection and ensure data availability
Anti-ransomware SolutionMulti-layered approach for comprehensive data protection
Kubernetes Data ProtectionBuilt for Kubernetes, flexible and simple
Enterprise Cloud Disk SolutionSecure content collaboration workspace
Intelligent Operation of Backup & Recovery SystemUnified monitoring and analysis
