Hello Experts, having issues backing up a Windows 2008 R2 server.
The backup operation that started at '2014-07-20T01:43:21.726000000Z' has failed because the Volume Shadow Copy Service operation to create a shadow copy of the volumes being backed up failed with following error code '2155348249'.
I am able to manually create a ShadowCopy on the SystemReserved and C partitions, but I think the issue is in the vss writers.
Here is a paste of vssadmin list writers:
U:\>vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.
Writer name: 'Task Scheduler Writer'
Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
State: [1] Stable
Last error: No error
Writer name: 'VSS Metadata Store Writer'
Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
State: [1] Stable
Last error: No error
Writer name: 'Performance Counters Writer'
Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
State: [1] Stable
Last error: No error
Writer name: 'System Writer'
Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Instance Id: {2bb166c9-9dd0-4a0f-bd5e-a49a6a8bbef0}
State: [7] Failed
Last error: Timed out
Writer name: 'SqlServerWriter'
Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
Writer Instance Id: {f84f3672-fd92-4bca-bf17-7617c8a9dfd9}
State: [7] Failed
Last error: Timed out
Writer name: 'ASR Writer'
Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
Writer Instance Id: {656fc4cd-200c-443c-9516-0fc92109231c}
State: [1] Stable
Last error: No error
Writer name: 'Shadow Copy Optimization Writer'
Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
Writer Instance Id: {2e3c7e75-fe1e-4898-9eee-626e51acf2d6}
State: [1] Stable
Last error: No error
Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {4ff3a1a0-2b6e-4204-b0e5-db6f4c979b0f}
State: [1] Stable
Last error: No error
Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {f0eafc7c-61f8-46de-a123-42c17d157829}
State: [1] Stable
Last error: No error
Writer name: 'IIS Metabase Writer'
Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
Writer Instance Id: {2f4032b3-6c2b-4ee6-9c16-dc980bc2132b}
State: [7] Failed
Last error: Timed out
Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {09d00386-69af-4b6f-a45e-a5385e7c6bf3}
State: [7] Failed
Last error: Timed out
Writer name: 'IIS Config Writer'
Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
Writer Instance Id: {2ccdcb5b-db13-4ad0-8d93-f3bad71f4e1e}
State: [7] Failed
Last error: Timed out
U:\>
Anyone have a clue how to clean up the failed writers?
There is only one listed when running providers:
U:\>vssadmin list providers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft Corp.
Provider name: 'Microsoft Software Shadow Copy provider 1.0'
Provider type: System
Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
Version: 1.0.0.7
U:\>
So after doing a bit of MS updates:
U:\>vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy
Service administrative command-line tool
(C) Copyright 2001-2005 Microsoft
Corp.
Waiting for responses.
These may be delayed if a shadow copy
is being prepared.
Writer name: 'Task Scheduler Writer'
Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
Writer Instance
Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
State: [1] Stable
Last error: No error
Writer name: 'VSS Metadata Store Writer'
Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
Writer Instance
Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
State: [1] Stable
Last error: No error
Writer name: 'Performance Counters
Writer'
Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
Writer Instance
Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
State: [1] Stable
Last error: No error
Writer name: 'System Writer'
Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Instance
Id: {584ae49c-62b9-4d50-9353-117a60f9197b}
State: [1] Stable
Last error: No error
Writer name: 'SqlServerWriter'
Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
Writer Instance
Id: {390ecccb-fdab-4ab1-875e-f87d76db2518}
State: [1] Stable
Last error: No error
Writer name: 'ASR Writer'
Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
Writer Instance
Id: {321fe8f8-f94c-491a-9325-29d432544ee0}
State: [1] Stable
Last error: No error
Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance
Id: {d87d58c0-bcb6-469a-b4ec-fb0cf913251e}
State: [1] Stable
Last error: No error
Writer name: 'IIS Config Writer'
Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
Writer Instance
Id: {24f7cff5-7f57-4c0c-8646-1b70f7212297}
State: [1] Stable
Last error: No error
Writer name: 'Shadow Copy Optimization Writer'
Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
Writer Instance
Id: {3e0613f1-3c60-4cb5-8702-477885d8403a}
State: [1] Stable
Last error: No error
Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance
Id: {afb4b1ee-0aea-4d94-af67-291bd97db7c6}
State: [1] Stable
Last error: No error
Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance
Id: {c34fab38-bd69-4c2d-88cf-981974db6674}
State: [1] Stable
Last error: No error
Writer name: 'BITS Writer'
Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
Writer Instance
Id: {faaa79e0-9724-4283-af02-04058dde7cd5}
State: [1] Stable
Last error: No error
Writer name: 'IIS Metabase Writer'
Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
Writer Instance
Id: {42ddb900-d442-4f9e-a2d4-d7462274afa2}
State: [1] Stable
Last error: No error
U:\>
However, when running the Windows Backup it still fails with the same error and then list writers is full of error's again.
Mark