VM

Symptoms

Application-aware backup fails with one of these errors:

Error 1

Error code: 34865165
Fields: {"$module":"aavb_backup_command_addon_vsa64_23140"}
Message: Failed to get the metadata from the 'VMware Snapshot Provider' extension library.
------------------------
Error code: 65520
Fields: {"$module":"aavb_backup_command_addon_vsa64_23140","code":2147942402}
Message: The system cannot find the file specified

When contacting Acronis Support with a technical issue, it is recommended to have Acronis System Information at hand

You create an agentless backup of VMware or Hyper-V virtual machine. 

When you try to recover files from a virtual machine backup to original location, only custom location is available in the recovery wizard.

  1. You have a Windows VM with dynamic disks.
  2. You create an agentless backup of this VM using Virtual Appliance.
  3. When you check the backup archive contents, you notice that drive letters are displayed incorrectly.

Symptoms

  1. You created a backup of a VMware VM using Acronis Cyber Protect 12.5 Virtual appliance.
  2. You recover the backed up VM to the same host with Acronis Cyber Protect 15.
  3. When you boot the VM, it is not possible to change the boot order. The message is:
    All items on this menu cannot be modified in user mode. If any items require change, please consult your systems Supervisor.

Symptoms

  1. You want to update several Hyper-V agents at once under Settings - Agents,
  2. When you select required agent machines, the following error is displayed:

More than one Agent for Hyper-V is selected. Simultaneous update of multiple Agents for Hyper-V is not possible. Please update these agents one by one.

Symptoms

You have installed Acronis Cyber Protect 15 software and attempt to deploy Agent for Scale Computing HC3 (Virtual Appliance);

Deployment of the Agent for Scale Computing HC3 (Virtual Appliance) instantly fails with the following error:

Failed to download the virtual appliance. Check the Internet connection on host <hostname> or download the file...

Introduction

The P2V migration or V2P migration of the machines with LVM can be performed only if the backup was created using the agent installed inside the virtual machine (or on physical machine) and the restore operation should be performed using Acronis Bootable Media.

If a machine has LVM volumes, keep in mind the following limitations for restoring to a different platform:

Symptoms

You have a virtual host with VMs, and licenses for Virtual Host workload (such license can be used to back up 1 Hypervisor Host Server and up to an unlimited number of virtual machines that are residing on the Hypervisor Host Server).

When you check the details of host and VMs with applied plans, license assignment is correct.

However, if you look under Settings -> License usage, one or more of Virtual Host licenses are assigned to VMs without Agent, or the licenses are shown as "not assigned".

Symptoms

  1. You have set up some Agents for VMware (Windows or Virtual Appliance) connected to a vCenter/ESX(i) host.
  2. Some virtual machines do not appear in Cyber Protection console after recovery or physical to virtual conversion

Cause

Current Acronis Cyber Protect products use VMware "InstanceUUID" property in order to identify each virtual machine. If one or more machines use the same InstanceUUID then only one machine will appear in the console.

Symptoms

  1. You install Agent for Windows into a Gen 2 Azure VM and perform recovery as described in Windows Azure and Amazon EC2 virtual machines