- Exclusive traffic type reassignment and cluster IP address change. It is now possible to change the configuration of exclusive traffic types or IP addresses in the cluster. It is needed when the node IP address has changed, but network topology remains the same, or if the network subnet has changed. It is also possible now to reassign the service traffic type when a customer wants to relocate a service to another network (for example, move the “Storage” traffic type to a dedicated network).
- Node locations as new failure domains. A failure domain defines a scope (a location) within which services might go down together. Now all the nodes can be assigned to specific locations: rooms, rows, and racks. Locations provide for redundancy among the failure domains. This gives an additional, flexible way for service providers to utilize the available hardware more efficiently, while delivering high availability.
Improved latency and performance. Technical optimization in the kernel and networking.
- Erasure coding is now available for running virtual machines.
- The erasure coding self-healing process now has less impact on the performance.
- The networking subsystem in the storage has been improved for lower l/O latency and CPU consumption.
- RDMA performance and stability have been improved. Now, RDMA moves from evaluation to production-ready.
- Adding a new Acronis Cyber Appliance to an existing cluster. The Acronis Cyber Appliance can now be added to an existing cluster deployed on another appliance or other hardware.
- Acronis Cyber Appliance automated installation using all connected network interfaces. Acronis Cyber Appliance can now have any available network interface and connectivity option selected during the installation. It makes a better fit for the existing datacenter physical network infrastructure.
S3 geo-replication improvements.
- Improved security for geo-replication (ACL for buckets)
- User-level and bucket-level customization of S3 geo-replication
- S3 bucket access log. Now the records of requests to a bucket can be provided and stored in another bucket. In addition, the end users can enable the access log via Amazon S3 API and get detailed information about the objects in their buckets.
Monitoring and alerting
Dashboard for performance and statistics charts for S3. You can now monitor:
- Service board – S3 GW, NS, OS services availability, rate of operational requests, bandwidth, and GET and PUT latency.
- Geo-replication board – Service availability, error rates, replication backlog, queue depth, and bandwidth.
- Dashboard for performance and statistics charts for NFS. You can now monitor the availability of NFS servers and services, usage, shares, exports, latency, IOPS, and bandwidth.
- Chinese language localization for the admin panel and documentation
- Japanese language localization for the admin panel and documentation
- Rescue mode for virtual machines. Rescue mode provides a mechanism to access the virtual machine's boot volume in case the virtual machine experiences boot problems.
- Distributed virtual router. The virtual routing architecture has been changed from centric to distributed (across all compute nodes).
- QoS policies for virtual machine volumes. The storage policy has been extended with additional parameters that define the IOPS and bandwidth limits of virtual machine volumes.
- Paging for compute and common objects in the admin panel. Improved the admin panel performance for a large number of virtual machines.
- VLAN-based network management for virtual machines. Simplified the process of creating VLAN-based networks for virtual machines.
- More supported guest operating systems. Added support for Debian 10, CentOS 8, and Ubuntu 20.04.x.
- Disabled pNFS. pNFS is now disabled by default and cannot be enabled for any forthcoming use cases.