This article applies to:
- Acronis Backup 9 for VMware
This article applies to:
Privileges for VM backup and recovery on vCenter Server or ESX(i) host
I am having issues cloning a clustered VM from Acronis Manager Datacenter. What might be causing this, and how do I fix it?
This issue can happen when the host agents are having difficulties identifying the management server. To address this, please reinstall the Management Service and use FQDN or IP address in the connection setup (instead of host name as shown below).
Applies to Acronis Cyber Infrastructure 3.0 or later
It is possible to copy a Virtuozzo 7 virtual disk to Acronis Cyber Infrastructure Storage and create a new VM with that disk.
Follow the steps below:
On Virtuozzo 7 node:
1. Stop the source VM and find its virtual disk:
# prlctl stop <VM_name>
# prlctl list -i <VM_name> | grep hdd
Example of command execution:
You are backing up several virtual machines with Acronis Agent for Hyper-V (installed on the Hyper-V host) or Acronis Agent for VMware (Windows) installed on a Windows machine connected to the ESX(i) host.
The backup plan is applied to a group of machines.
In a while, you receive an error message or an email notification about the error: "No backup items were resolved. GXT: The item provider has skipped the report of an item with key."
Specifics of product architecture.
This article provides instruction for troubleshooting virtual machine backup failures in Acronis Cyber Backup virtualization solutions.
Follow these steps to troubleshoot virtual machine backup failures:
You are trying to back up a Hyper-V virtual machine which has virtual disk with an ampersand (&) in file name, e.g. Docs&Users.vhdx. Backup fails with the following error:
Failed to get the disk information.
1. You have a Hyper-V host with Virtual Desktop Infrastructure role;
2. You install Acronis Agent for Hyper-V;
3. When you try to create a new automatic collection, creation fails with
Could not retrieve the virtual desktop template details for <VM_Name>
SAN policy is set to Offline All during Agent for Hyper-V installation. This change is necessary to prevent Windows from breaking the bootability of the VMs recovered and/or converted from backups by Agent for Hyper-V.
The following critical alert is displayed when backing up Hyper-V host and virtual machine(s) on it:
The running backup has not shown any progress for some time and may be frozen
Most likely cause for this alert is that VM backup is queued as it is waiting for host backup to be completed.
Error message text will be improved in the future product releases.
Invalid configuration for device '0'
(!) This issue does not reproduce with agentless backup
Specifics of product implementation.