W2K19 vss issue
Hello, I'm looking for some troubleshooting suggestions for a 2019 Server that is experiencing vss issues. Yesterday I had a backup fail with a VSS error. Failed: Failed - 0x80042306 - IDispatch error #8454 - Retrying without VSS Writers ERROR: COM call "m_pVssObject->BackupComplete(&pAsync)" failed. - Returned HRESULT = 0x80042301 - Error text: VSS_E_BAD_STATE After some further troubleshooting I realised that the VSS issue extended beyond the backup system C:\windows\System32>vssadmin list writers vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool (C) Copyright 2001-2013 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: {4a4003f5-e11d-4f99-8071-e8a74259dfb3} State: [1] Stable Last error: No error Writer name: 'ASR Writer' Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4} Writer Instance Id: {7254596f-d6ee-4268-b16b-0ac353af5af6} State: [1] Stable Last error: No error Writer name: 'Shadow Copy Optimization Writer' Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f} Writer Instance Id: {6704e612-a914-4db9-81da-fe66b9a63684} State: [1] Stable Last error: No error Writer name: 'Microsoft Hyper-V VSS Writer' Writer Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de} Writer Instance Id: {d4e0e02d-d932-424c-8708-976037c2fc5f} State: [7] Failed Last error: Timed out Writer name: 'Registry Writer' Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485} Writer Instance Id: {faf20311-d7ae-446d-b82b-f73f3c94a91b} State: [1] Stable Last error: No error Writer name: 'COM+ REGDB Writer' Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f} Writer Instance Id: {62ce4679-7634-423c-b549-efd60969679e} State: [1] Stable Last error: No error Writer name: 'BITS Writer' Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0} Writer Instance Id: {bd78bd8d-0bcb-4143-9494-1f94aaa9412e} State: [1] Stable Last error: No error Writer name: 'IIS Config Writer' Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6} Writer Instance Id: {cabe2719-7881-4a17-a306-b91bf55a0ca7} State: [7] Failed Last error: Timed out Writer name: 'WMI Writer' Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0} Writer Instance Id: {327e2198-51e5-418f-857b-807592618509} State: [7] Failed Last error: Timed out Writer name: 'Certificate Authority' Writer Id: {6f5b15b5-da24-4d88-b737-63063e3a1f86} Writer Instance Id: {53ff0a16-053f-4b4a-a670-63dbf07f0cd0} State: [7] Failed Last error: Timed out Writer name: 'DFS Replication service writer' Writer Id: {2707761b-2324-473d-88eb-eb007a359533} Writer Instance Id: {f7b764bc-f504-4542-b423-2b2436c3c373} State: [1] Stable Last error: No error Writer name: 'NTDS' Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757} Writer Instance Id: {2c66a49d-efd6-41a7-a35b-ce3362000b2a} State: [7] Failed Last error: Timed out Writer name: 'Dhcp Jet Writer' Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad} Writer Instance Id: {de15b14a-bcf4-41b9-bdf0-76af8edaee68} State: [7] Failed Last error: Timed out Writer name: 'WINS Jet Writer' Writer Id: {f08c1483-8407-4a26-8c26-6c267a629741} Writer Instance Id: {05ee1245-8ad7-4486-9845-3d83bb443557} State: [7] Failed Last error: Timed out I have done the following: chkdsk /f on all volumes dism /online /cleanup-image /checkhealth dism /online /cleanup-image /scanhealth dism /online /cleanup-image /restorehealth sfc /scannow no errors reported After the above: vssadmin list writers reported no errors and the backup completed normally. So I thought that the issue was resolved. Today the backup failed again and vssadmin list writers is as above again. I can't see anything in the Event Log (System or Application) that looks to be relevant. At this stage the only idea that I have is to restore the server back to prior to the errors commencing, but this is a DC in a multi-DC environment, so that is not a trivial step. I'd prefer to try and resolve the issue directly if I can. Thanks VW
Some info on VSS required
Hi everyone, I wanted to ask / clarify some points on VSS. I have quiet a few VMs on ESXi and am backing them up via a backup software. Do i need to have vss enabled for VMs only with SQL and Exchange installed? or Do i need to have vss enabled for all Windows VM? I ask, because i receive vss snapshot failure alerts for VMs which don't have any databases or exchange installed. vss admin listwriters shows "no error" as well. thanks
Virtualization for Server Workloads: Avanade Case Study, NetApp Whitepaper
First published on TECHNET on Mar 08, 2010 Our customers often deploy Microsoft server workloads, such as SQL Server, SharePoint and Exchange, on Microsoft Hyper-V and System Center, and want to know how other customers have deployed these workloads and if there are deployment guidelines from specific solution partners that can help optimize for scale and business continuity.Working around the pass through limitations of the Hyper-V VSS Writer
First published on TECHNET on Mar 03, 2009 While the Hyper-V VSS writer provides backup admins significant flexibility in their ability to back up VMs in an application-consistent way while running backup applications in the physical machine, it does have a prominent limitation when it comes to VMs with pass-through storage.
