Release date:August, 2026
‎​

Last document update: September 9, 2026

Table of contents

What's new

Backup: Partner protection plans support agentless virtual machines

Partner-level and folder-level protection plans previously covered only agent-based workloads, such as physical machines and virtual machines that run an agent. Partners can now include agentless virtual machines in these plans.

Key benefits

  • Operational efficiency: Configure the backup of agentless virtual machines once, at the partner or folder level, instead of creating a separate plan for each customer.
  • Wider workload coverage: Apply a single partner-level or folder-level plan to both agent-based and agentless workloads.
  • Centralized management: Apply consistent backup settings to the workloads of all your customers, and update the settings in one place.

Supported scenarios

  • Create or edit a protection plan at the partner or folder level that includes agentless virtual machines at the customer level.

Licensing

  • Solution-based: Backup and DR, Ultimate Protection.
  • Service-based (per-workload, per-gigabyte): Standard Protection.

Backup: Support for Proxmox VE 9.1 and 9.2

Partners can now protect virtual machines that run on Proxmox VE 9.1 and 9.2. The Cyber Protection agent for Linux and the Proxmox add-on support the kernel versions that these Proxmox releases include.

Key benefits

  • Support for the latest Proxmox releases: Install the agent on Proxmox VE 9.1 and 9.2 hosts without kernel compatibility errors.

Supported scenarios

  • Back up and recover Proxmox VE virtual machines agentlessly, including virtual machine configurations that store TPM data in .qcow2 disks.
  • Convert a backup to a virtual machine.
  • Run a virtual machine directly from a backup.

Licensing

  • Solution-based: Backup and DR, Ultimate Protection.
  • Service-based (per-workload, per-gigabyte): Standard Protection.

Disaster Recovery: VPN gateways switch to standby automatically when not in use

VPN gateways in cloud-only and site-to-site connectivity modes now switch to standby automatically when they are not in use. A gateway becomes active again when a test failover, production failover, or another Disaster Recovery operation starts, and returns to standby afterward. Partners can also activate a gateway temporarily at any time. Cyber Protect Cloud preserves the existing VPN configuration and applies it again when the gateway becomes active. No action is required from partners, because the new behavior applies automatically.

Implementation notes

  • While a gateway is in standby, site-to-site and point-to-site VPN connections, as well as Internet access, are unavailable.
  • Multi-site IPsec VPN gateways are not affected, and remain active at all times.

Licensing

  • Solution-based: Backup and DR, Ultimate Protection.

Disaster Recovery: Support for VMware ESXi 8.0 and 9.0 virtual machines

Partners can now use Disaster Recovery for virtual machines that run on VMware ESXi 8.0 and 9.0.

Key benefits

  • Broader platform coverage: Protect virtual machines on the latest VMware ESXi versions with Disaster Recovery.

Supported scenarios

  • Perform test and production failover of agentlessly backed-up virtual machines that run on VMware ESXi 8.0 and 9.0.
  • Perform automated failback of virtual machines to VMware ESXi 8.0 and 9.0.
  • Run the VPN appliance on VMware ESXi 8.0 and 9.0.

Licensing

  • Solution-based: Backup and DR, Ultimate Protection.

Disaster Recovery: Support for Linux workloads with mirrored LVM volumes

Partners can now use Disaster Recovery for physical Linux servers that use mirrored LVM volumes for storage redundancy.

Key benefits

  • Coverage for redundant storage configurations: Protect physical Linux servers that rely on LVM mirroring, a common enterprise deployment.

Supported scenarios

  • Fail over physical Linux servers that have mirrored LVM volumes to the Acronis cloud.
  • Perform automated incremental failback to the original production server after recovery.

Licensing

  • Solution-based: Backup and DR, Ultimate Protection.

RMM: Vulnerability and Patch Management insights – additional widgets

New Vulnerability and Patch Management widgets show which workloads have pending updates. Partners can see how many devices are up to date, pending a reboot, unpatched, or unprotected. The widgets list every device that misses approved patches, and the applications that carry the most vulnerabilities across the managed fleet. Partners can open a device from a widget, and then start remediation.

Key benefits

  • Device patch status at a glance: One chart shows how many devices are up to date, pending a reboot, unpatched, or unprotected.
  • Faster remediation: Identify the devices that miss patches, open a device from a widget, and start remediation.
  • Evidence for customers: Track which vulnerabilities were remediated, when, and on how many devices.
  • Prioritized patching: Identify the applications that carry the most vulnerabilities, and patch those first.

Supported scenarios

  • Filter and group the widgets by customer, severity, or time range.
  • Review the vulnerable applications widget to find an outdated application, and then create a patch management policy that targets it.

Licensing

  • Solution-based: Security and RMM, Ultimate Protection.
  • Service-based (per-workload, per-gigabyte): RMM offering item under the Cyber Protection service.

Platform: Monitoring the online status of devices (coming soon)

Partners can now build a workflow that checks whether devices are online, and reacts when a device goes offline. Three new actions are available in the workflow builder: Get devices, Get device online status, and Post custom alert. A workflow can retrieve the devices of a tenant, check the status of each device, and then post an alert or start a remediation action.

Key benefits

  • Proactive outage detection: Identify offline servers and endpoints before customers report an issue.
  • Shorter downtime: Accelerate incident response, and reduce SLA exposure.
  • Automated alerting: Post a custom alert, or send an email notification, when a device goes offline.
  • Operations at scale: Replace manual device-by-device status checks with automated periodic monitoring.

Supported scenarios

  • Retrieve a list of devices, filtered by tenant ID and workload type, by using the Get devices action.
  • Retrieve the online status of a device by using the Get device online status action.
  • Post an alert of a predefined type by using the Post custom alert action.

Implementation notes

  • A predefined workflow template for this scenario is available.

Licensing

  • Available to all Acronis Cyber Protect Cloud partners at no additional cost.

Platform: Agent deployment through an installation link

Partners and clients can now generate an installation link that installs and registers the protection agent without sign-in and manual setup. The link carries the enrollment settings that the tenant administrator selects, such as the target tenant and the protection plan. The download page detects the operating system of the device, and offers the matching installer. Tenant administrators control the lifecycle of each link, and can require approval before a device registers.

Key benefits

  • Simplified onboarding: Share a link instead of guiding a user through agent installation and registration.
  • No sign-in on the device: The person who installs the agent does not sign in to the console.
  • Administrator control: Review and revoke links, and approve device registrations.

Supported scenarios

  • Enable and configure installation links at the partner and customer tenant levels.
  • Provision installation links automatically for new users.
  • Generate a personalized agent configuration, and then share the installation link.
  • Download, install, register, and protect a device in three clicks, without sign-in.
  • Review, update, and revoke installation links in Devices > Add > Manage links.
  • Approve device registration requests before the devices appear in the tenant.
  • Automate the configuration by using the API.

Licensing

  • Available to all Acronis Cyber Protect Cloud partners at no additional cost.

Platform: Billing report API

Distributors and eligible partners can now retrieve billing report data through the API, instead of waiting for a monthly report file. The API returns data for the past 12 months. Data for a billing period becomes available after the billing cycle closes and the billing report is finalized.

Key benefits

  • Automated billing integrations: Retrieve billing data programmatically for marketplace and billing integrations.
  • Access to historical data: Retrieve billing data for any billing period during the past 12 months.

Supported scenarios

  • A distributor retrieves the billing report data of their partners, including distributor-specific terms.
  • An eligible partner retrieves their own billing report data, without distributor-specific terms.
  • Applications in the Acronis platform use billing report data for business-oriented features.

Licensing

  • Available to cloud distributors, and to partners and cloud aggregators that signed directly with Acronis or through a cloud distributor.

Integrations: NinjaOne support for branded URLs and custom fields

The NinjaOne integration now supports NinjaOne instances that are hosted on a branded URL, and supports all NinjaOne datacenter URLs. Deployment scripts can read the registration token and the datacenter URL from NinjaOne custom fields, so partners no longer need to enter these values manually. The integration also notifies partners when a NinjaOne client ID expires.

Key benefits

  • Branded URL support: Configure the integration for a NinjaOne instance that uses a branded domain.
  • Simpler agent deployment: Deployment scripts obtain the registration token and the datacenter URL from custom fields.
  • Fewer integration failures: The integration notifies partners about expired NinjaOne client IDs.

Supported scenarios

  • Configure the integration for a NinjaOne instance that uses a branded URL.
  • Configure the required custom fields in NinjaOne, and then let the deployment scripts use them to obtain the registration token and the datacenter URL during agent deployment and registration.

Licensing

  • Available to all Acronis Cyber Protect Cloud partners at no additional cost.

Updated Components

Acronis Cyber Protection agent

The Acronis Cyber Protection agent has the following new versions.

  • Acronis Cyber Protection agent for Windows (v.26.8.43101)
  • Acronis Cyber Protection agent for Mac (v.26.8.43101)
  • Acronis Cyber Protection agent for Linux (v.26.8.43101)

For more information about the release history of the Acronis Cyber Protection agent, see the agent release notes.

Fixed issues

Security

For information about security issues fixed in this release, see https://security-advisory.acronis.com/updates/UPD-2608-e38e-7865.

Acronis Cyber Protect Cloud

Backup

  • [PLTFRM-93001] The Cyber Protect console showed the "Backup failed" status for a protection plan, although the most recent backup completed successfully. Reapplying the plan cleared the incorrect status. This issue is now resolved.
  • [PLTFRM-91965] Protection plans showed the status "Succeeded with warnings", although no errors or alerts existed for them. This issue is now resolved.
  • [ABR-414476] Browsing and indexing of Microsoft 365 mailbox backups failed with an internal error when the backup contained email items without a parent folder. This issue is now resolved.
  • [ABR-429059] Backups to an SMB share failed with a credentials error when several protection plans used the same share. This issue is now resolved.
  • [ABR-329053] Recovery of files to a machine with a GPT disk failed with a read error when the protective MBR of the disk was incorrect. This issue is now resolved.
  • [ABR-314208] A file-level backup that used policy rules failed when the parent directory of the selected items contained more than 5000 items. This issue is now resolved.

Cyber Protection agent

  • [ABR-434800] On Linux machines that use multiqueue block devices, the operating system could crash with a kernel NULL pointer dereference during a backup. This issue is now resolved.
  • [ABR-435922] Agent installation on Windows machines with an ARM64 processor failed intermittently with error 1603. This issue is now resolved.

Data Loss Prevention

  • [DEVLOCK-7164] When the Data Loss Prevention module was enabled, access to SMB network shares could stall or fail, and Windows Explorer could freeze or crash. This issue is now resolved.

Management Portal

  • [PLTFRM-69757] A new folder that was created under a partner tenant did not inherit the applications that were enabled for the parent tenant, such as Partner Portal. As a result, moving tenants into the folder failed with an "application is not available" error. This issue is now resolved.

Reporting

  • [ADP-55564] Customized report names were replaced with the default report names in the Reports panel. This issue is now resolved.

Remote management

  • [ADP-32882] A web-based remote desktop connection to a workload was interrupted repeatedly after a failed authentication attempt, even after the correct credentials were entered. This issue is now resolved.

Known issues and limitations

Acronis Cyber Protect Cloud

Backup

  • [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.
  • [ABR-305920] The backups of System state performed via the Windows Server Backup feature fail with the error message "The process cannot access the file because it is being used by another process."

Bootable media

  • [ABR-358235] WinPE-based media: Unable to browse backup files if the cloud storage location contains corrupted backup archives.

Cyber Protection agent

Note: Starting with the 26.09 release, the Cyber Protection agent for Mac will no longer support macOS 12 and earlier versions. The minimum supported macOS version will become macOS 13.

Disaster recovery

  • If the tenant (customer or partner) is disabled or deleted while an Automated Failover is in progress, the operation fails with the error "Please try again later or contact Support" while it should indicate that the tenant is no longer accessible.

Virtualization protection

  • [ABR-383978] No alert about almost reached storage quota is displayed for agentless Microsoft Azure virtual machine backups.
  • [ABR-383972] No alert about exceeded storage quota is displayed for agentless Microsoft Azure virtual machine backups.

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