Release date:February, 2024

Last document update: April 12, 2024

Table of contents

What's new

VMware Cloud Director protection: recovery to a new virtual machine

In previous product versions, a VM could only be recovered if the original VM was available. With the enhancement that we introduce now, the recovery of a deleted or de-provisioned VM can be initiated directly from the product UI, so you do not need to contact Acronis support. This enhancement allows you to:

  • Recover to a new VMware Cloud Director VM in a Virtual Data Center (vDC).
  • Change the restored machine name, CPU sockets/cores, and RAM.

Supported VMware Cloud Director versions: 10.4 or later.

Implementation notes
  • The backups must be created by using Cyber Protection agent version 24.02 or later, to ensure the recovery to a new VM.
  • You cannot choose the target vApp during recovery. The recovered VMs appear in the Standalone VMs section of the VMware Cloud Director hierarchy.

Licensing

All licenses

​Advanced Disaster Recovery

Licensing update

Starting with the 24.02 release, all servers running in Acronis Cloud will be charged for compute points as per their configured flavor, regardless of their VM state (powered on or powered off).

Standby recovery servers will not be affected and will continue being charged for disaster recovery storage only.

Action required by partners by February 15

Per the communication that was sent out on January 22, 2024, Acronis partners are requested to:

  • Review their inventory of running recovery servers in production/test failover and primary servers.
  • Stop test/production failover for recovery servers with VMs in the power-off state and remove primary servers with VMs in the power-off state.​

End of support for Ubuntu 16.04 LTS in Advanced Disaster Recovery on June 30, 2024

The support for Ubuntu 16.04 LTS in Advanced Disaster Recovery will reach its end on June 30, 2024. After this date, we will no longer provide any software or security updates to support Disaster Recovery scenarios for Ubuntu 16.04 LTS workloads. Learn more.

Device Control

Starting with this release, Device control is disabled by default for new protection plans, and will be automatically disabled in exisintg protection plans once you update the Proteciton agent to version 24.02 or later.

Integrations

Jamf Pro 1.3: Support for API clients

The Jamf Pro integration now supports the API client authentication method.

  • Starting with the 24.02 release, a Jamf API client is required to configure the Jamf integration.
  • Existing integrations are not affected.

Licensing

All licenses

Updated components

Cyber Protection agent

The Acronis Cyber Protection agent has new versions as follows:

  • Acronis Cyber Protection Agent for Windows (v.24.2.37668)
  • Acronis Cyber Protection Agent for Mac (v.24.2.37668)
  • Acronis Cyber Protection Agent for Linux (v.24.2.37668)

See the release notes for the Acronis Cyber Protection agent here.

Changes in Acronis Cyber Cloud API

You can find the history of changes in Acronis Cyber Cloud API in the dedicated API change log document.

Fixed issues

Acronis Cyber Protect Cloud

Installation

  • [ABR-371803] The installation on Oracle Linux Server 8.8. fails with the error "Failed to compile Snapapi, most probably you use non-stanrad kernel."

Backup

  • [ABR-380085] Cloud-to-Cloud backups of Microsoft Teams data may fail with the error "Failed to back up files in channel '[Name]': 'can not get latest changes'" in some cases.
  • [ABR-346588] Occasionally, some backups of Microsoft 365 and Google Workspace workloads are unable to resume automatically after network failures which causes the backups to fail.

Common

  • [PLTFRM-60971] Users cannot log in to the Cyber Protection console.

Cyber Protection agent

  • [ABR-378626] An error might occur when opening a backup in the cloud storage vault.
  • [ABR-378444] Some backups are duplicated in the cloud storage location.
  • [ABR-377770] Occasionally, the registration status of the Cyber Protection agent is reported as Success, but the routine is not properly completed and the agent remains unregistered.
  • [ADP-33595] Full and quick scan tasks might run for too long and fail with the error "Task timeout expired. The agent responsible for processing the task is not accessible or is busy processing other tasks."
  • [ADP-31360] Patching the Zoom Desktop Client fails at 90% with the error "Can't load config info."

Known issues and limitations

Backup

  • [ARC-525] Cloud-to-cloud backups of Microsoft 365 mailboxes and OneDrive instances may rarely fail with the error "Could not save BackupStatus: [Archive Server]: ". For details, see https://kb.acronis.com/content/72506.
  • [ABR-375627] Cloud-to-cloud backups of mailboxes and OneDrive instances fail with the backup agent error "Could not save BackupStatus: [Archive Server]: "
  • [ABR-365442] The backup validation completes successfully, but the validation status is incorrect or missing in backup sets with a large number of backups.
  • [ABR-361097] It is possible to create backups with special characters in their names, but such backups are not accessible when saved on a network storage.
    • Solution: Do not use special characters in backup names, even though the application allows you to.

Recovery

For more information on known issues and workarounds, please visit our Knowledge Base.