@Zerocool -
Yes 2010R3 and Sharepoint version is WSS 3
The sharepoint server is littered with errors 1 minute before the backup failed.
I will investigate them but they are
ID 24583 - SQLWRITER,
ID 1 - SQLVDI,
ID 18210 - MSSQL$MICROSOFT##SSEE
ID 3041 - MSSQL$MICROSOFT##SSEE
ID 3021 - MSSQL$SQLEXPRESS
ID 5789 - BACKUP EXEC - An error occurred while executing the following query: "BACKUP DATABASE [msdb] TO VIRTUAL_DEVICE='BE_SQLAgent-msdb__76362aab_d890_44a5_8cf6_d6c192834ce7_' WITH name='Backup Exec SQL Server Agent', SNAPSHOT".
On server: "SHAREPOINT.MYDOMAIN.co.uk\SQLEXPRESS".
SQL error number: "0C81".
SQL error message: "Cannot open backup device 'BE_SQLAgent-msdb__76362aab_d890_44a5_8cf6_d6c192834ce7_'. Operating system error 0x80070002(error not found).
The SQL Server has no errors
The physical HyperV server has no erros
@CraigV -
The physical HyperV server has the following error
Writer name: 'Microsoft Hyper-V VSS Writer'
Writer Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
Writer Instance Id: {87dda222-4c95-44aa-a2f1-6ba060916ce6}
State: [8] Failed
Last error: Retryable error
The BE Media Server has all writers in stable state with no errors
The SQL 2008 server has all writers in stable state with no erros
The Sharepoint server has a wealth of writers in problem state
Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
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: 'ASR Writer'
Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
Writer Instance Id: {706670db-fbc0-4900-a8f8-b7c506491881}
State: [1] Stable
Last error: No error
Writer name: 'IIS Config Writer'
Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
Writer Instance Id: {8c2f1780-e47d-4ce1-a9d1-db024121ba72}
State: [5] Waiting for completion
Last error: No error
Writer name: 'SqlServerWriter'
Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
Writer Instance Id: {1ad30528-6a98-467d-aa81-da8473a058f3}
State: [8] Failed
Last error: Non-retryable error
Writer name: 'SPSearch VSS Writer'
Writer Id: {57af97e4-4a76-4ace-a756-d11e8f0294c7}
Writer Instance Id: {b43e8973-1a7e-4b1a-baa3-ca057ecc2497}
State: [5] Waiting for completion
Last error: No error
Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {be591f8b-a2a6-4d3b-ac50-79a1578169b1}
State: [5] Waiting for completion
Last error: No error
Writer name: 'BITS Writer'
Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
Writer Instance Id: {5def5c80-802e-43ab-be3b-d80bd7115c15}
State: [1] Stable
Last error: No error
Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {58b6fcb7-47b6-46f5-a2eb-eb2b5f9ffe0c}
State: [1] Stable
Last error: No error
Writer name: 'System Writer'
Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Instance Id: {304fe965-28e6-4afc-b905-b36565ff044a}
State: [5] Waiting for completion
Last error: No error
Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {0f4bfa33-f252-40fd-87d2-78f79aefdd85}
State: [1] Stable
Last error: No error
Writer name: 'IIS Metabase Writer'
Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
Writer Instance Id: {4f192c6b-eda5-43cd-9165-258e62e7aa4c}
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: {8be3e2ca-b9d3-4584-82d1-190dfafcba23}
State: [1] Stable
Last error: No error
Will reboot server and run HyperV job again tonight - will update Monday
Is Server 2008 just bugged with VSS errors because i constantly have the Exchange Writer fail at another site and Symantec blame MS and MS blame Symantec
