Backup started at '5:11:09 AM' failed as Volume Shadow copy operation failed for backup volumes with following error code '2155348129'. Please rerun backup once issue is resolved.
Run Command vssadmin "list writers" without quotes.
This is the output of vssadmin:
C:\Users\Administrator>vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.
Writer name: 'System Writer'
Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Instance Id: {6847904d-a095-4880-86cb-7682104da43b}
State: [5] Waiting for completion
Last error: No error
Writer name: 'SqlServerWriter'
Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
Writer Instance Id: {c6c3d255-1987-4f7f-93e0-6082b0398caf}
State: [8] Failed
Last error: Non-retryable error
Writer name: 'ASR Writer'
Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
Writer Instance Id: {bb38516f-cb8b-47ec-badb-11f5ec87e923}
State: [1] Stable
Last error: No error
Writer name: 'IIS Config Writer'
Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
Writer Instance Id: {d67b4f5f-2abb-47ef-8589-f2cc1584b1e0}
State: [5] Waiting for completion
Last error: No error
Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {df172a32-a7b7-4aa8-bbf6-e58f6b83a13f}
State: [1] Stable
Last error: No error
Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {1cd3c854-487d-468d-8f96-bab5676a2883}
State: [5] Waiting for completion
Last error: No error
Writer name: 'Shadow Copy Optimization Writer'
Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
Writer Instance Id: {48eebe9a-bf75-459d-8f0a-ed418da6f7f2}
State: [1] Stable
Last error: No error
Writer name: 'BITS Writer'
Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
Writer Instance Id: {f64c6d19-1cd5-433d-bc9b-2e557f9fb9e1}
State: [1] Stable
Last error: No error
Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {388deaf4-fde5-4ba2-acfb-04d70d4ed3a7}
State: [1] Stable
Last error: No error
Writer name: 'IIS Metabase Writer'
Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
Writer Instance Id: {6c1d3da2-0502-4656-8bae-b47be2cf3556}
State: [5] Waiting for completion
Last error: No error
Event Error:
Sqllib error: OLEDB Error encountered calling ICommandText::Execute. hr = 0x80040e14. SQLSTATE: 42000, Native Error: 3013
Error state: 1, Severity: 16
Source: Microsoft SQL Server Native Client 10.0
Error message: BACKUP DATABASE is terminating abnormally.
SQLSTATE: 42000, Native Error: 3271
Error state: 1, Severity: 16
Source: Microsoft SQL Server Native Client 10.0
Error message: A nonrecoverable I/O error occurred on file "{E7BFA343-622B-4059-AF1B-C668891C0241}32:" 995(The I/O operation has been aborted because of either a thread exit or an application request.).
Trouble Shoot:
Go to services and turn off SOL Server VSS Writer service then attempt to do a backup as your normal schedule. If it functions you are likely dealing with a worker thread pooling issue.
Purpose of max worker threads Option:
Thread pooling helps optimize performance when large numbers of clients are connected to the server. Usually, a separate operating system thread is created for each query request. However, with hundreds of connections to the server, using one thread per query request can consume large amounts of system resources. The max worker threads option enables SQL Server to create a pool of worker threads to service a larger number of query request, which improves performance.
Calculating max worker threads:
The default value for max worker threads, 0, allows SQL Server to automatically configure the number of worker threads at startup. This setting is best for most systems; however, depending on your system configuration, setting max worker threads to a specific value sometimes improves performance.
Caution:
We recommend 1024 as the maximum for 32 bit SQL Server.
Solution:
Open SSMS right click properties of the server select Processors You will see Threads then maximum worker threads: The default is set to '0' change that to 255 and restart your SQL server. This should resolve your problem.