Select Language
Products & Solutions
Data-driven Organization
Industries
Solutions
Products
Services & Support
Data as a Service
Customer Success Services
Community
Developer Community
Documentation
Demo
Blog
Partners
Why Partner with AISHU
Become a Signed Partner
Training & Certification
Find A Partner
About AISHU
About Us
News & Events
Join Us
Products & Solutions
Data-driven Organization
Industries
Solutions
Products
Services & Support
Data as a Service
Customer Success Services
Community
Developer Community
Documentation
Demo
Blog
Partners
Why Partner with AISHU
Become a Signed Partner
Training & Certification
Find A Partner
About AISHU
About Us
News & Events
Join Us

AISHU Blog

All AnyBackup AnyShare AnyRobot

AnyBackup Family 7.0.16.1 Release Notes

2021-10-29 869 0
Introduction
This document provides last-minute information about AnyBackup Family 7.0.16.1. New features, new compatibilities, and enhancements can be found in the following sections of this document.
The release version of AnyBackup Family 7.0.16.1 is available from October 22, 2021. If you are upgrading from previous versions, please review the upgrade guide closely before performing the upgrade.

See next:
- New Features
- New Compatibilities
- Enhancements

New Features
l [Licenses]
- Package mode with full features is supported for AnyBackup Express Package 7.
- Package mode with optional features is supported for AnyBackup Express Package 7.
l [Report] System administrator, inspector and tenant can view capacity statistics and export related reports.
l [Snapshot Storage] Reset interface is provided by snapshot storage.
l [Anti-Ransomware] Immutable storage is supported.
- Immutable storage is now supported for Apollo-x86 appliances. The path to storage resources can be customized to prevent files under the protected directory from being accessed, tampered, or destroyed by ransomware.
- Immutable storage can be applied to data stored on OFS volume, metadata volume, self-backup volume, snapshot pool and snapshot metadata volume.
Backup and Recovery 
l [H3C CAS]
- Data sources can be filtered by host pool, cluster, host or VM.
- Data can be archived to tape libraries.
- Recovery for a VM with no NIC configured is supported.
- The MAC address conflict that occurs when a VM recovery job is being created is solved.
- For Original Configuration, the original MAC address will be used by default.
- For Specified Configuration, a new MAC address will be generated automatically.
- The problem that data cannot be recovered if the volume name is too long during recovery is addressed.
- When the volume name contains over 100 characters, only the first 20 characters will be retained, so that the recovery can be executed normally.
l [OpenStack]
- Data can be archived to tape libraries.
- By Ceph-based storage solutions, “volume name template” and “snapshot name template” can be set up in the configuration file if backup fails due to the non-default Ceph configurations (volume_name_template/snapshot_name_template).
- By Ceph-based storage solutions, the parameter “back-end storage match pattern” can be set up in the configuration file if backup or recovery fails due to non-standard Ceph configurations.
- [HUAWEI Cloud Stack] The parameter “retries for status code 429” can be set in the configuration file to enhance the backup logic when interfaces on HUAWEI Cloud Stack are requested concurrently. The risk of backup failure can be decreased.
l [H3C CloudOS] The following features are supported for H3C CloudOS, including:
- Service Settings
- Data Backup
- Data Recovery
- Data Cleanup
l [ZStack] The following features are supported for ZStack, including:
- Data Backup (full backup only)
- Data Recovery
- Data Cleanup
- Policy Template
- Remote Replication
l [SQL Server]
- SQL Server HA can be backed up and recovered.
- SQL Server Standalone can be recovered with a different instance name.
l [Oracle]
- Databases of multiple versions on one client can be backed up and recovered.
- System ID verification is supported when authorizing an Oracle database. 
l [MySQL-Physical backup]
- MySQL Standalone containers can be backed up and recovered.
- MariaDB container cluster (AnyShare 7.0.2.2) can be backed up and recovered.
l [SAP HANA] When recovering a specified full backup, you can browse and select the full backup identifier.
l [AnyShare]
- Data on the AnyShare object storage can be backed up to Azure.
- Backup for single-node AnyShare is supported.
l [D2C/D2D2C] Data can be backed up to Kingsoft Cloud KS, Ctyun OOS, Baidu Netdisk and S3 compatible object storage.
l [C2D] Data in Kingsoft Cloud KS can be backed up to the local storage.
l [Remote Replication] Retention policy can be applied, either retention cycle based or backup cycle based.
l [Fingerprint Library] When creating a backup job, the fingerprint library can be created automatically.
- Streamlines the process for creating a backup job with deduplication enabled.
- Enhance the accuracy of capacity statistics for deduplication jobs.
Copy Data Management
l [Flow Control] Speed limit is supported for remote replication jobs.
l [Oracle]
- System ID verification is supported when authorizing an Oracle database.
- If ASM is specified as the storage for Oracle RAC backup, the ASM disk group can be renamed during instant recovery.
- Oracle databases can be backed up by using AnyBackup Family and the local backup scripts of backupset type alternately.

New Compatibilities
Backup and Recovery 
l [HUAWEI Cloud Stack]
- OceanStor Pacific 8.1.0 (storage)
l [H3C CAS]
- H3C CAS E0710P09
- H3C CAS E0710P11
l [OpenStack] VMs and disks on FusionSphere OpenStack can be backed up and recovered.
l [SANGFOR HCI]
- SANGFOR HCI 6.3.0 / 6.3.0 R1
l [Hadoop HDFS]
- CentOS 7.6 aarch64 + Apache3.0.3
- EulerOS 2.0 SP8 aarch64 + Apache3.1.1
- Centos7.2 x86 + Transwarp Hadoop 2.7.2
l [FusionCompute]
- FusionCompute 8.1.0 (platform)
- OceanStor Pacific 8.1.0 (storage)
l [Virtualization & Cloud Platform] The console of a higher version is compatible with the lower client. On a console of AnyBackup 7.0.16.1, features in this release can be applied to a client of AnyBackup 7.0.16.0 or higher.
- VMware (fully compatible)
- FusionCompute (partially compatible)
- HUAWEI Cloud Stack (partially compatible)
- H3C CAS (partially compatible)
- H3C CloudOS (partially compatible)
- OpenStack (partially compatible)
- SANGFOR HCI (fully compatible)
- XenServer (fully compatible)
- Hyper-V (fully compatible)
 
Mind the following:
- A client is fully compatible means that on a console of AnyBackup 7.0.16.1, all features in this release can be applied to the client of AnyBackup 7.0.16.0.
- A client is partially compatible means that on a console of AnyBackup 7.0.16.1, part of the features in this release can be applied to the client of AnyBackup 7.0.16.0.
l [MySQL]
- SUSE Linux Enterprise Server 12 SP2 x86_64 + MySQL 5.7.23
- SUSE Linux Enterprise Server 12 SP2 x86_64 + MySQL 5.6.42
- SUSE Linux Enterprise Server 12 SP5 x86_64 + MySQL 5.7.13
- SUSE Linux Enterprise Server 12 SP4 x86_64 + MySQL 5.7.6
- NeoKylin x86_64 + MySQL 5.7.30

- NeoKylin x86_64 + MySQL 5.7.28
- SUSE Linux Enterprise Server 12 x86_64 + MySQL 5.6.30
- CentOS 6.1 x86_64 + MySQL 5.5.6
- CentOS 6.1 x86_64 + MySQL 5.5.39
- CentOS 6.1 x86_64 + MySQL 5.5.55
- CentOS 6.2 x86_64 + MySQL 5.6.33
- CentOS 6.3 x86_64 + MySQL 5.5.12
- CentOS 6.3 x86_64 + MySQL 5.5.21
- CentOS 6.3 x86_64 + MySQL 5.5.45
- CentOS 6.4 x86_64 + MySQL 5.5.24
- CentOS 6.4 x86_64 + MySQL 5.6.39
- CentOS 6.5 x86_64 + MySQL 5.5.27
- CentOS 6.5 x86_64 + MySQL 5.5.51
- CentOS 6.6 x86_64 + MySQL 5.5.33
- CentOS 6.7 x86_64 + MySQL 5.5.57
- CentOS 6.8 x86_64 + MariaDB 5.5.62
- CentOS 7.3 x86_64 + MySQL 5.7.16
- CentOS 7.6 x86_64 + MySQL 5.7.11
- CentOS 7.9 x86_64 + MariaDB 5.5.66
- SUSE Linux Enterprise Server12 SP5 x86_64 + MariaDB 5.5.63
l [SQL Server HA]
- Windows Server 2008 R2 + SQLServer 2008R2
- Windows Server 2016 + SQLServer 2016
Mind the following:
The compatibilities of other versions are the same as that of SQL Server Standalone.
l [GaussDB]
- GaussDB T 1.1.0 + x86 Platform + Euler V2.9 + Standalone
- GaussDB T 1.0.5 + x86 Platform + SUSE Linux Enterprise Server 12 SP2 + HA
- GaussDB T 1.0.5 + x86 Platform + Euler V2.5 + Standalone
l [Dameng]
- Dameng 8.1.1.190 + Kylin Linux Advanced Server release V10 x86_64
- Dameng 8.1.1.190 + UnionTech OS Server 20 Enterprise aarch64
- Dameng 8.1.1.126 + NeoKylin Linux Advanced Server release 6.5 x86_64
l [DB2]
- AIX 6.1 + DB2 9.7.0.4
l [MongoDB]
- MongoDB 3.4.1 + x86 Platform + Ubuntu 12.0.4 + Standalone/Replica Set/Sharding Cluster
l [Kingbase]
- KingbaseES_V008R007CB0160 + UnionTech OS Server 20 Enterprise aarch64
l [Oracle OS]
- Oracle Linux 7.9/7.8
- Oracle Solaris 11.4
l [D2D2B]
- Amethystum Blu-ray Storage ZL2520
l [AnyShare High-Performance Backup and Recovery]
- Anyshare 7.0.2.2 only
l [LAN-Free Backup]
- Windows Server 2016R2 X86_64 Client
- Windows Server 2019R2 X86_64 Client
- Kylin ARM Kylin 4.0.2 Client
- Kylin ARM Kylin Linux Advanced Server V10 Client
- NeoKylin X86 Red Hat Enterprise Linux Server release 6.5 Client
Copy Data Management 
l [VMware] The console of a higher version is fully compatible with the lower client.
l [Oracle]
- Oracle Linux 7.9/7.8 OS
- SUSE Linux Enterprise Server 11/SUSE Linux Enterprise Server 11 SP1 OS
- Oracle Solaris 11.4 OS
Continuous Data Protection
l [File-Level Replication] The console of a higher version is fully compatible with the lower client.
l [Continuous Data Protection (FusionCompute DR platform based])] The console of a higher version is fully compatible with the lower client.
Public
l [Console]
- Kylin V4 4.0.2 (FT- 2000, aarch)
- Kylin V10 SP2 Build09 (Hygon, x86)
- OpenEuler 20.03 SP2 (Kunpeng 920, aarch)
l [Client]
- SUSE Linux Enterprise Server 10 SP1 x86_64
- SUSE Linux Enterprise Server 10 SP2 x86_64
- SUSE Linux Enterprise Server 10 SP3 x86_64
- SUSE Linux Enterprise Server 10 SP4 x86_64
- CentOS 7.5 aarch64
- CentOS 7.6 aarch64
- Oracle Solaris 11.4 SPARC_64
- Proton RDS MariaDB client is supported.
l [Certificate Authentication]
- Kylin V4 4.0.2 (FT-2000, aarch)
- Red Hat Enterprise Linux 8.0 x86_64
- Red Hat Enterprise Linux 8.1 x86_64
- Red Hat Enterprise Linux 8.2 x86_64
- Red Hat Enterprise Linux 8.3 x86_64
- CentOS 8.0 x86_64
- CentOS 8.1 x86_64
- CentOS 8.2 x86_64

Enhancements
Feature
l [Inspector] An inspector can query backup points in time.
l [Alarm Management] If an alarm is selected to be shown, it will be shown in the system alarms and system logs once triggered.
l [Backup in Intranet-Extranet]
- Proxy management service HA is supported for cross-network segment backup in intranet-extranet.
- The external mapping IP of proxy service can be a domain name.
- An external mapping IP in the domain name format and multiple IPs are supported for client connection and the proxy detection tool.
l [Cluster Deployment] 
- Installation parameters are modified. Control node and service node can be configured respectively.
- ClusterMgmService is supported for cluster status monitoring.
- Service registration and renewal are supported for ETCD cluster.
- Useless services can be disabled temporarily through load balancing by Nginx.
- The risk of DBService collapse is reduced in the event of a power failure, network outage or restart error.
- If an exception occurs to a monitored service, this service will be restarted within a minute. The node management service can respond to this in a minute. 
- After recovery from a restart or power failure, services can get back to normal in about 2 minutes. The node management service can respond to the node status in about 5 minutes.

- After recovery from a power failure, services can return to the Running status in 15 seconds and the node management service can respond to the node status in one minute.
l [Data Archive] Backup jobs on which archive jobs and archive recovery jobs are based can be filtered by application type or backup job name.
l [D2C] Backup jobs on which D2C recovery jobs and data cleanup jobs are based can be filtered by application type or backup job name.
l [User Management] Authentication via CAS Server is supported.
l [File System]
- Aggregated small files can be backed up.
- NAS can be instantly recovered.
- APL files in Windows can be backed up.
l [Deduplication] With multiple deduplication nodes, errors will be returned for deduplication jobs if more than 2/3 deduplication nodes are brought offline. In other words, at least 1/3 nodes have to be online to ensure that deduplication is available.
l [Capacity Statistics] The capacity statistics for CDM and remote replication jobs is enhanced. The accuracy of the statistics is improved.
Performance
l [Virtualization & Cloud Platform] Data update policy is optimized. Update per query (namely, data will be updated each time it is queried) is changed to periodic update by system (update every other hour), in order to address the problem that recoverable points in time of the protected VMs cannot be obtained if there are too many backup jobs or points in time. This is applicable to:
- H3C CAS
- VMware
- HUAWEI Cloud Stack
- FusionCompute
l [Logs] The speed of log query and export is enhanced. For the same amount of data, the log query speed is about 2-3 times faster, the export speed in txt/csv is about 3 times faster, and the export speed in xls is about 6 times faster.
l [Remote Replication]
- With deduplication disabled, data can be synchronized in a rate up to 900 MB/s or greater. In the opposite case, the rate can be up to 700 MB/s or greater.
- Resumable data transfer is optimized. Data transferred is reduced thanks to less network requests and ideal deduplication ratio.
l [Storage] Storage of metadata in the object storage is optimized. LevelDB is broken up into a certain number of databases. The number of databases in the single volume group can be set up manually, 10 by default. This reduces the burden of the metadata database and enhances database traversal, thus improving the performance of data cleanup. Besides, it can decrease the corruption ratio in the event of damaged metadata due to uncontrollable factors.
Interaction Optimization
l [Data Backup]
- The File Aggregation option is added to the Data Backup interface. The maximum size of files aggregated and maximum size of scraped files can be set up.
- The description Completed (denoting data volume completed) is changed to Transferred Data Volume.
l [Alarm Rules]
- For file backup, the warning notifying that the directory /dev, /proc, or /sys is not backed up is changed to Info.
Reliability
l [Backup in Intranet-Extranet] The Encryption/Decryption Library that secures proxy authentication information for the database storage in the intranet-extranet uses three-layer instead of two-layer encryption and decryption.
 

Was this helpful?

Related Articles

Stay up to date

Stay up to date

Must be valid email.

Submit

Enter your email upper to be notified about new articles.

You have successfully subscribed, thank you

Subscription failed, please try again

 

    support@aishu.cn(Japan & Korea)