Skip to main content

Intermittent full backup failures on SQL server Win2008R2 64

Thread needs solution

We are seeing intermittent failures on daily full backups of one of our MSSQL 2008 machines running Acronis 11.5.

We are not running backups of the data drive, we use the MSSQL backup for that task.

It seems that 2-3 days per week the Acronis backup fails with errors similar to the following:

1 Information 3/27/2014 3:05:03 AM Command 'Running backup plan 'Daily-Backup-Plan'' is running.
2 Information 3/27/2014 3:05:15 AM Command 'Backing up' is running.
3 Information 3/27/2014 3:05:27 AM Analyzing partition '1-0'...
4 Information 3/27/2014 3:05:27 AM Create Full Backup
From: Disk '1'
To file: "file:X:\Backup\Backup_2014_03_27_03_05_26_725D.TIB"
Compression: Normal
Exclude: Files matching mask
Match criterion: *\System Volume Information\*{3808876B-C176-4e48-B7AE-04046E6CC752}; ...

5 Information 3/27/2014 3:05:27 AM Pending operation 157 started: 'Creating partition image (System Reserved ())'.
6 Information 3/27/2014 3:05:49 AM Locking partition 0-0...
7 Error 3/27/2014 3:07:01 AM Operation with partition '0-0' was terminated.
Details:
Failed to create volume snapshot.

Error code: 0x70021
$module = "disk_bundle_vs_38350"
Tag: 0xA5695862AAF8E69E
Failed to start creating the volume snapshot.

Error code: 0x10C442
$module = "disk_bundle_vs_38350"
Tag: 0x14181C22EF45B0F6
VSS writer 'System Writer' with class ID 'E8132975-6F93-4464-A53E-1050253AE220' has failed to process the snapshot.

Error code: 0x10C469
$module = "disk_bundle_vs_38350"
Tag: 0x14181C22EF45A9E9
Unknown Win32 error

Error code: 0xFFF0
code = 2,147,754,994 (0x800423F2),
$module = "disk_bundle_vs_38350"
Tag: 0xBD28FDBD64EDB8EA
Additional info:
--------------------
Error code: 502
Module: 1
LineInfo: a164035b3ff39289
Fields: $module : disk_bundle_vs_38350
Message: Operation with partition '0-0' was terminated.
Details:
Failed to create volume snapshot.

Error code: 0x70021
$module = "disk_bundle_vs_38350"
Tag: 0xA5695862AAF8E69E
Failed to start creating the volume snapshot.

Error code: 0x10C442
$module = "disk_bundle_vs_38350"
Tag: 0x14181C22EF45B0F6
VSS writer 'System Writer' with class ID 'E8132975-6F93-4464-A53E-1050253AE220' has failed to process the snapshot.

Error code: 0x10C469
$module = "disk_bundle_vs_38350"
Tag: 0x14181C22EF45A9E9
Unknown Win32 error

Error code: 0xFFF0
code = 2,147,754,994 (0x800423F2),
$module = "disk_bundle_vs_38350"
Tag: 0xBD28FDBD64EDB8EA
--------------------
Error code: 33
Module: 7
LineInfo: a5695862aaf8e69e
Fields: $module : disk_bundle_vs_38350
Message: Failed to create volume snapshot.
--------------------
Error code: 50242
Module: 16
LineInfo: 14181c22ef45b0f6
Fields: $module : disk_bundle_vs_38350
Message: Failed to start creating the volume snapshot.
--------------------
Error code: 50281
Module: 16
LineInfo: 14181c22ef45a9e9
Fields: $module : disk_bundle_vs_38350
Message: VSS writer 'System Writer' with class ID 'E8132975-6F93-4464-A53E-1050253AE220' has failed to process the snapshot.
--------------------
Error code: 65520
Module: 0
LineInfo: bd28fdbd64edb8ea
Fields: code : 2147754994, $module : disk_bundle_vs_38350
Message: Unknown Win32 error
--------------------
8 Error 3/27/2014 3:07:01 AM Command 'Backing up' has failed.
Additional info:
--------------------
Error code: 61
Module: 309
LineInfo: 4a8728dc8a1c950f
Fields: $module : service_process_vs_38350
Message: Command 'Backing up' has failed.
--------------------
Error code: 3
Module: 329
LineInfo: 1cd98aae889424f9
Fields: $module : disk_bundle_vs_38350
Message: Backup has failed.
--------------------
Error code: 1060
Module: 1
LineInfo: b43e776571144dec
Fields: $module : disk_bundle_vs_38350
Message: Failed to commit operations.
--------------------
Error code: 33
Module: 7
LineInfo: a5695862aaf8e69e
Fields: $module : disk_bundle_vs_38350
Message: Failed to create volume snapshot.
--------------------
Error code: 50242
Module: 16
LineInfo: 14181c22ef45b0f6
Fields: $module : disk_bundle_vs_38350
Message: Failed to start creating the volume snapshot.
--------------------
Error code: 50281
Module: 16
LineInfo: 14181c22ef45a9e9
Fields: $module : disk_bundle_vs_38350
Message: VSS writer 'System Writer' with class ID 'E8132975-6F93-4464-A53E-1050253AE220' has failed to process the snapshot.
--------------------
Error code: 65520
Module: 0
LineInfo: bd28fdbd64edb8ea
Fields: code : 2147754994, $module : disk_bundle_vs_38350
Message: Unknown Win32 error
--------------------
Task 'Simple backup (Full)' has failed on machine 'Machine'.

Seems to be a lot of Win32 errors, not sure what to make of it all.

Thanks for any help!

0 Users found this helpful

The root cause is this one
- Message: VSS writer 'System Writer' with class ID 'E8132975-6F93-4464-A53E-1050253AE220' has failed to process the snapshot.
all above (up to 8 Error 3/27/2014 3:07:01 AM Command 'Backing up' has failed.
Additional info: ) is the consequence.
The code number in this error is 0x800423f2 . Googling reveals that it's 'Timeout'.
You can search for "system writer" and 0x800423f2 and see if any of suggestions ( like http://social.technet.microsoft.com/Forums/en-US/b16012a6-1245-45df-b88… ) resolve this problem.

Thanks for pointing out the root cause, Fedor! I will try out a few things & report back.

Thanks!
Jim

Try to use VSS "with software auto select"

David

David - I have tried all the VSS settings with the same results. One question though - do I need to restart the service for these changes to take effect?

I also tried extending the VSS idle timeout period from the default of 180 seconds to 360, which seemed to reduce the daily failures from 2-4 a week to 1-2 per week:

Adding DWORD key "IdleTimeout" here:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VSS\Settings

and setting to 360, although this page recommends maximum of 180:

http://msdn.microsoft.com/en-us/library/windows/desktop/bb891959%28v=vs…

Thanks!
Jim

Hello Jim
I do not think you need to restart it. It should update from the AMS.

BTW: thanks for your registry tweek sharing :-), its cool :-)

Thanks David!

No problem. FYI in the last 14 days the backup has only failed once, whereas before it was failing 2-3 times per week. Not sure if the registry tweak is totally responsible for the improvement, but if anyone else has a similar issue, it's worth a shot.

Jim