Failed to create volume snapshot

Thread needs solution
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Messaggi: 1
Commenti: 1

We are using Acronis Version 11 for the first time on one of our servers in California. It is installed on a Windows 2003 Server SP2.

When the Scheduled Task for a Backup attempts to run, we get an error "Failed to create volume snapshot". There is a lot more info in the log than just this error statement (see attached).

When we start Acronis 11 manually to run the Backup, it requires us to log into the 'localhost'. Once this is complete, the "exact" same backup runs fine.

It just won't run at night by itself.

We have been using Acronis for several years and have never had this problem.

Any ideas what might be wrong or any changes we need to make?

Allegato Dimensione
acronis_log.txt 2.44 KB
Gio, 02/02/2012 - 14:47
0 Users found this helpful
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Messaggi: 1
Commenti: 1

I change the VSS to use Microsft VSS instead of Acronis VSS and it started working.

It still gets a warning of "704" and "65520" (see below), but it works. :

1 Information 2/4/2012 3:00:11 AM Command 'Backing up' is running.
2 Information 2/4/2012 3:00:16 AM Analyzing partition '1-0'...
3 Information 2/4/2012 3:00:16 AM Create Full Backup
From: Disk '1'
To file: "file:G:\DC1\DC1_C_D_2012_02_03_19_00_15_796D.TIB"
Compression: Maximum
Exclude: Files matching mask
Match criterion: *.tmp, *.tib, *.bkf; ...

4 Information 2/4/2012 3:00:16 AM Pending operation 151 started: 'Creating partition image'.
5 Information 2/4/2012 3:00:16 AM Locking partition 1-1...
6 Information 2/4/2012 3:00:16 AM Failed to get VSS metadata for backup.
Additional info:
--------------------
Error code: 704
Module: 64
LineInfo: 26556611c50a732a
Fields: $module : C:\Program Files\Acronis\BackupAndRecovery\DiskBundle.dll
Message: Failed to get VSS metadata for backup.
--------------------
Error code: 65520
Module: 0
LineInfo: bd28fdbd64edb8bc
Fields: code : 2147942450
Message: The request is not supported
--------------------
7 Information 2/4/2012 3:00:17 AM Pending operation 151 started: 'Creating partition image'.
8 Information 2/4/2012 3:00:21 AM Locking partition C:...
9 Information 2/4/2012 3:12:58 AM Pending operation 151 started: 'Creating partition image'.
10 Information 2/4/2012 3:13:00 AM Locking partition D:...
11 Information 2/4/2012 4:04:06 AM Pending operation 148 started: 'Saving partition structure'.
12 Information 2/4/2012 4:04:07 AM Command 'Backing up' has completed successfully.
Task 'Full backup' has succeeded on machine 'DC1.wcs.local'.

Dom, 02/05/2012 - 04:15
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Messaggi: 0
Commenti: 1

Hi, I have got the same errors on one of my win2k3 servers (0x70021 volume snapshot, snapshot bitmap - STRANGE -started occuring after some WinUpdates has been installed and server restarted) and then I changed option to not use multivolume snapshot, just system VSS, it works FINE now. I am thinking if VSS will be enough to preserve SQL database continuity, can you advice me?
Thanks.

Mer, 03/07/2012 - 10:52
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Forum Star
Messaggi: 24
Commenti: 3268

Hello Tomasz,

Welcome to our Forum, we're glad to greet you here. And thank you for sharing your concerns with us.

Sure VSS is more then enough to preserve SQL, multi-volume snapshot is a good tool, but not obligatory. It's more important to have VSS enabled for successful backup of the database.

The original issue might've occurred due to some mess in the low-level drivers. I believe we can fix it, but investigation might take time. Let us know if you would like to proceed with working on the issue, we will be glad to help.

Should you need anything else or have any further questions - feel free to contact us at your earliest convenience, we will be happy to help you!

Thank you.

Mer, 03/07/2012 - 12:51