SQL writer and cluster VSS error issue

Question

I have the case, my customer used veeam backup and having the problem, other veeam backup is ok but one backup task is felid. I created veeam case and feedback possible SQL writer and cluster VSS error issue. How can fixe the issue.

Server 01

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: {edfe4ac7-3b6d-4670-be67-8747bbf0b730}
   State: [7] Failed
   Last error: Timed out

Writer name: 'SqlServerWriter'
   Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Instance Id: {3b4a7327-6e7e-4f0f-a432-c2480210c6d0}
   State: [7] Failed
   Last error: Timed out

Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {3f031ca7-1cea-43f2-941b-ab6b5971c094}
   State: [1] Stable
   Last error: No error

Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {44c0f7d0-2041-44be-9e46-6f8370e822d4}
   State: [1] Stable
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {0c91c62c-6c25-482d-9c31-9ddf1fdba236}
   State: [1] Stable
   Last error: No error

Writer name: 'BITS Writer'
   Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
   Writer Instance Id: {76bb91a9-25a8-4524-a73f-e287603051f0}
   State: [1] Stable
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {b43b7ec8-e80c-440f-ab78-8c98b382d3e9}
   State: [7] Failed
   Last error: Timed out

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {7626d114-3c7b-4937-8e6a-aa82e265206c}
   State: [1] Stable
   Last error: No error

Writer name: 'Sentinel Agent Log VSS Writer'
   Writer Id: {90e12c7e-b9c2-4649-81a2-947d06dd5eba}
   Writer Instance Id: {f66d0933-0cbe-405f-8ff6-33859152ddd1}
   State: [7] Failed
   Last error: Timed out

Writer name: 'Sentinel Agent Database VSS Writer'
   Writer Id: {abd005ca-6bfc-44c9-a439-8eb665a676b3}
   Writer Instance Id: {bdf46192-0ec7-4c4a-a060-c9dcfbb43975}
   State: [7] Failed
   Last error: Timed out

Writer name: 'Sentinel Agent Research Data VSS Writer'
   Writer Id: {9112a876-c17f-4051-b2c3-43f646cde241}
   Writer Instance Id: {ff56e25f-bd3c-4d39-985e-2cdeb23de113}
   State: [7] Failed
   Last error: Timed out

Writer name: 'Cluster Shared Volume VSS Writer'
   Writer Id: {1072ae1c-e5a7-4ea1-9e4a-6f7964656570}
   Writer Instance Id: {1d81a6a5-c418-4408-bfd0-c2a459654d29}
   State: [7] Failed
   Last error: Timed out

Writer name: 'Cluster Database'
   Writer Id: {41e12264-35d8-479b-8e5c-9b23d1dad37e}
   Writer Instance Id: {df7d61a8-a8f7-4b7f-aad0-9b5a998c77b0}
   State: [7] Failed
   Last error: Timed out

Writer name: 'Sentinel Agent DFI Research Data VSS Writer'
   Writer Id: {dcf8278a-dc0f-4b35-afd0-37a07e92fe90}
   Writer Instance Id: {7f17bb8e-2ee0-4101-91ec-9be4d4d10cf7}
   State: [7] Failed
   Last error: Timed out

Server 02

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: {06b7a287-924d-44d8-bd83-35bc782cc236}
   State: [1] Stable
   Last error: No error

Writer name: 'SqlServerWriter'
   Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Instance Id: {3b88dfdd-ab43-429a-baa5-c1131ddb2f41}
   State: [1] Stable
   Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {b19fa561-e9bf-49ac-a318-8c0564296782}
   State: [1] Stable
   Last error: No error

Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {cd0aea89-261c-43ea-b7b5-486dcdc1eca1}
   State: [1] Stable
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {401de89a-2b97-44a0-aa00-9f8fecef8bff}
   State: [1] Stable
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {b0c62c4b-3fe8-4330-9733-6f3d6032e74d}
   State: [1] Stable
   Last error: No error

Writer name: 'BITS Writer'
   Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
   Writer Instance Id: {82abf810-d2c4-487f-af04-43aaddb53ce4}
   State: [1] Stable
   Last error: No error

Writer name: 'Sentinel Agent Database VSS Writer'
   Writer Id: {abd005ca-6bfc-44c9-a439-8eb665a676b3}
   Writer Instance Id: {60527421-7900-4045-b9d5-9257a49fa73d}
   State: [1] Stable
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {fa0064b0-7304-46e9-937e-2f045a9a3b1b}
   State: [1] Stable
   Last error: No error

Writer name: 'Sentinel Agent Log VSS Writer'
   Writer Id: {90e12c7e-b9c2-4649-81a2-947d06dd5eba}
   Writer Instance Id: {09789184-87ac-43bb-aa8d-00e4cf18a5a4}
   State: [1] Stable
   Last error: No error

Writer name: 'Sentinel Agent Research Data VSS Writer'
   Writer Id: {9112a876-c17f-4051-b2c3-43f646cde241}
   Writer Instance Id: {7db0f673-1d45-4142-a5de-f6a9f259885a}
   State: [1] Stable
   Last error: No error

Writer name: 'Sentinel Agent DFI Research Data VSS Writer'
   Writer Id: {dcf8278a-dc0f-4b35-afd0-37a07e92fe90}
   Writer Instance Id: {1a4823d1-2019-4f8a-8393-e40e9a0812d6}
   State: [1] Stable
   Last error: No error

Writer name: 'Cluster Database'
   Writer Id: {41e12264-35d8-479b-8e5c-9b23d1dad37e}
   Writer Instance Id: {4135dda3-e9aa-456b-a07f-35132c3bf34a}
   State: [1] Stable
   Last error: No error

Writer name: 'Cluster Shared Volume VSS Writer'
   Writer Id: {1072ae1c-e5a7-4ea1-9e4a-6f7964656570}
   Writer Instance Id: {82abf998-b0c7-42b9-9829-dc97a29c7a02}
   State: [8] Failed
   Last error: Timed out

Answer 1

Hello Chris,

Welcome to the Q&A Forum; this is a great place to get support, answers, and tips.

Thank you for posting your question; I'll be more than glad to help you out.

As a SQL DBA (without deep knowledge of Veeam)... what kind of problem do you (or your customer) have?

You didn't post any SQL Server-related error message... what does the SQL error log state during those times when SQL Server should be backed up?

How is the SQL Server configured (regarding storage), there are some known issues with using snapshots and some storage systems/configurations.

How is Veeam configured to back up those servers/nodes/instances?

Snapshots are not the best idea to backup a SQL Server (my personal opinion/experience)

Does that error come from the Veeam backup during the backup of the servers or the Veeam SQL Server backup?

From my "many" questions, you can see there are a lot of options and variables...

Please tell us a little bit more about your problem.

I hope my answer is helpful to you,

Your

Bjoern Peters

If the reply was helpful, please upvote and/or accept it as an answer, as this helps others in the community with similar questions. Thanks!