This article describes how to back up a virtual machine using Acronis True Image Echo and VMware Consolidated Backup
Snapshot
Acronis True Image errors out with "Unable to create volume snapshot" when backing up volumes of over 4 TB in size in Linux
You are either trying to back up a free VMware ESXi using Acronis Agent for ESX/ESXi or you have not added a license to your paid version of VMware ESX/ESXi
Try disabling write caching for the USB drive to solve the issue
This has been fixed
Instructions on how to enable Microsoft native VSS instead of the default Acronis VSS in Acronis Backup & Recovery 10
Make sure the backup is run under administrator or that you back up without using VSS
Recovery points in Acronis vmProtect 7
Close all running programs, restart the product and try to run the backup plan again
Please contact Acronis Support to get a special build with the timeout increased
How to create backup with these applications
Reinstall SnapAPI drivers to fix the issue
The issue has been fixed in update 6
Update to the latest build or turn on snapshotting for file backup
Description of the Acronis SnapAPI module
Activate Acronis VSS provider or turn off VSS entirely
Pre/post commands are executed before or after the whole backup process. Before/after data capture commands are executed during the backup process, right before and immediately after the snapshot
Instructions on how to enable Microsoft native VSS instead of the default Acronis VSS in Acronis Backup
You are running a single-pass backup of SQL instances that fails with the error. To fix this issue, re-register the VSS service
Acronis VSS provider is used to initiate creation of VSS snapshot, but MS VSS service is actually used
If there is not enough storage space to create the temporary snapshot file, the backup operation will fail with an error message similar to the following one:
Not enough storage is available to process this command
This article describes what this temporary file is and how to modify its size. For detailed description of the snapshot process, see SnapAPI.
This article describes what to do if after a backup failure the backed up virtual disks are left attached to Acronis Virtual Appliance
Agentless backup of Hyper-V VMs with pass-through disks finishes with a warning:
Cannot take checkpoint for 'MachineName' because one or more pass-through disks are attached.
Change the databases to Simple Recovery Mode
As a workaround, use Microsoft VSS instead of Acronis VSS
Backup fails with "Cannot continue backup. There is not enough free space on the drive where the snapshot cache file is located.". You can solve this issue by moving the destination for temporary file of snapshot.
Deactivate scoped snapshots for Hyper-V virtual machines.
You are backing up a virtual machine with Windows Server 2019 on ESXi 6.5 or 6.7 using Agent for VMware (Windows) or Virtual Appliance,
Agentless backup finishes with warning
Creating a crash-consistent snapshot of virtual machine because the creation of its application-consistent snapshot has failed. An error occurred while saving the snapshot: Failed to quiesce the virtual machine
Symptoms
Backup of a Linux system with kernel 4.18 fails with the following error:
Failed to create a snapshot
Increase the storage size or change the storage location of the volume snapshot