40845: Acronis Backup 11.7/11.5: Backup on Windows XP Fails with Error 'Failed to Create Volume Snapshot' If MS SQL Server is Installed
IMPORTANT NOTICE:Extended Support for Acronis Backup 11.x ended May 31, 2019. If you are using version 11.x, upgrade to the latest version of Acronis Cyber Protect (v15) to ensure your data and infrastructure are protected. To see if you are eligible to upgrade to the latest version, click here or contact us at firstname.lastname@example.org
Backup on Windows XP fails with error "Failed to create volume snapshot" if MS SQL Server is installed.
You have installed Acronis software on a Windows XP System;
On this system MS SQL Server is installed and running;
(!) MS SQL Express 2008 is automatically installed along the installation of Acronis Management Server component.
You run a disk or volume backup with the default settings:
Use VSS option = enabled (default backup option value);
Software-System provider or Software-Select automatically selected (default backup option value);
Enable VSS Full Backup is disabled (default backup option value);
This backup fails with:
Failed to create volume snapshot.
By default the product uses COPY method of VSS snapshotting. However, Microsoft 'SqlServerWriter' VSS Writer doesn't support VSS COPY method on Windows XP - and thus VSS snapshot can't be created successfully in this OS. The workaround is to switch to VSS Full backup option (see below) which will switch the VSS snapshot method to FULL - and it is supported properly by SqlServerWriter in Windows XP.
To work around this issue, please enable the VSS Full backup option.
Navigate to the backup plan options or to the default backup options -> Volume Shadow Copy Service and enable the VSS Full backup option. See Enabling VSS Full backup in user guide.
(!) Ifthe issue happens NOT on Windows XP, or the above workaround implemented on Windows XP machine doesn't help - then there must be some other Microsoft VSS corruption (e.g. another component of Microsoft VSS subsystem malfunctions). You'll need to investigate this VSS issue separately, e.g. as described in Acronis Backup: VSS Troubleshooting Guide