Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Thursday, April 2, 2020 12:02 PM
Hi, this post is consequence of a issue with Veeam Backup.
Short summary: all the jobs fails with error (another shadow copy creation is already in progress), and the last step was test a backup with Windows Server Backup.
So, i tried a job (Full and VSS mode), but in bot cases, these failed with the error: "The backup operation that started at '2020-04-02T01:08:27.852000000Z' 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 '0x80780021'. Please review the event details for a solution, and then rerun the backup operation once the issue is resolved."
This is a Windows Server 2012 R2, Physical, with Hyper-V role installed and several Productions VMs running on. Is part of a Cluster of 12 nodes.
I tried restart the VSS services, but the error persist. The last weekend we reboot all nodes
There is no errors on writers:
C:\vssadmin list providers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2013 Microsoft Corp.
Provider name: 'Microsoft CSV Shadow Copy Helper Provider'
Provider type: Software
Provider Id: {26d02d81-6aac-4275-8504-b9c6edc5261d}
Version: 1.0.0.1
Provider name: 'Microsoft CSV Shadow Copy Provider'
Provider type: Software
Provider Id: {400a2ff4-5eb1-44b0-8a05-1fcac0bcf9ff}
Version: 1.0.0.1
Provider name: 'VSS Null Provider'
Provider type: Software
Provider Id: {8202aeda-45bd-48c4-b38b-ea1b7017aec3}
Version: 5.0.158.0
Provider name: 'Microsoft File Share Shadow Copy provider'
Provider type: Fileshare
Provider Id: {89300202-3cec-4981-9171-19f59559e0f2}
Version: 1.0.0.1
Provider name: 'Microsoft Software Shadow Copy provider 1.0'
Provider type: System
Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
Version: 1.0.0.7
Provider name: 'VSS Null Provider'
Provider type: Fileshare
Provider Id: {f4a69dd4-f712-40e3-a6b3-faeff03cb2b8}
Version: 5.0.158.0
**************
C:\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: {a0f6e4a6-4876-450e-ab27-0dcdb20872d7}
State: [1] Stable
Last error: No error
Writer name: 'Microsoft Hyper-V VSS Writer'
Writer Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
Writer Instance Id: {002ec0b5-07cb-41a1-a7a6-a8d1da9178c8}
State: [1] Stable
Last error: No error
Writer name: 'Cluster Shared Volume VSS Writer'
Writer Id: {1072ae1c-e5a7-4ea1-9e4a-6f7964656570}
Writer Instance Id: {879cdb3d-34d7-44ab-8ef3-786195073fe7}
State: [1] Stable
Last error: No error
Writer name: 'ASR Writer'
Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
Writer Instance Id: {de69ac02-fa58-409a-8c69-00a24a6fa0bc}
State: [1] Stable
Last error: No error
Writer name: 'Shadow Copy Optimization Writer'
Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
Writer Instance Id: {b491f370-506e-4201-aaa7-e9d97ad0acb6}
State: [1] Stable
Last error: No error
Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {637adda5-d3c7-4042-9f85-be644ec582a5}
State: [1] Stable
Last error: No error
Writer name: 'BITS Writer'
Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
Writer Instance Id: {0b7f82ca-2e03-421b-8c20-fd8b672df530}
State: [1] Stable
Last error: No error
Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {b423f282-8f3b-4000-a59d-bbf288eb66bf}
State: [1] Stable
Last error: No error
Writer name: 'Cluster Database'
Writer Id: {41e12264-35d8-479b-8e5c-9b23d1dad37e}
Writer Instance Id: {886e0d10-ca78-456e-a8e3-ea09b1f547a5}
State: [1] Stable
Last error: No error
Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {f67dabce-48ba-4166-83c3-cff9cc45fab7}
State: [1] Stable
Last error: No error
*******************************************************
UPDATE:
When we executed: "list shadows all”, stuck and generate always the same 3 particular events:
DISKSHADOW> list shadows all
Querying all shadow copies on the computer ...
Volume Shadow Copy Service error: Error creating the Shadow Copy Provider COM class with CLSID {7efeb38a-18cc-4cc8-a348-a668bd9d07d4} [0x80070422, The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.
].
Operation:
Obtain a callable interface for this provider
List interfaces for all providers supporting this context
Query Shadow Copies
Context:
Provider ID: {8202aeda-45bd-48c4-b38b-ea1b7017aec3}
Class ID: {7efeb38a-18cc-4cc8-a348-a668bd9d07d4}
Snapshot Context: -1
Snapshot Context: -1
****************
Volume Shadow Copy Service information: The COM Server with CLSID {7efeb38a-18cc-4cc8-a348-a668bd9d07d4} and name SW_PROV cannot be started. [0x80070422, The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.
]
Operation:
Obtain a callable interface for this provider
List interfaces for all providers supporting this context
Query Shadow Copies
Context:
Provider ID: {8202aeda-45bd-48c4-b38b-ea1b7017aec3}
Class ID: {7efeb38a-18cc-4cc8-a348-a668bd9d07d4}
Snapshot Context: -1
Snapshot Context: -1
Execution Context: Coordinator
******************************************
If we try to stop the service, this stuck on "Sttopping" status, and must to end the process.
Some idea?
Regards¡
Marcos Ferreira
Update 07/04
I forget tell that there is a Cluster of 12 nodes.
So, when i try to list writers or shadows, the service stuck on "stopping" state, and must to kill the process
This happen on any node on cluster
Marcos Ferreira
All replies (13)
Thursday, April 9, 2020 3:04 AM ✅Answered
Hi,
>>the VSS Null is because we migrate from DPM to Veeam the last year, but we delete some days ago.
Please try to remove this provider and try agin:
https://support.efolder.net/hc/en-us/articles/115004593767-Remove-Unwanted-VSS-Provider
>>this is a clúster of 12 nodes, and when we evict one one, can list the shadows without problems.
Do you mean when you remove the node from cluster, you can do backup successfully?
>>So, the problem is with VSS on the Clúster..
But I noticed that you metioned that you backup a small folder on C:, this folder is on your host and have no relationships with your cluster.
If you want to backup contain CSV, you should check this first:
/en-us/previous-versions/windows/it-pro/windows-server-2012-r2-and-2012/jj614621(v%3Dws.11)
Best Regards,
Daniel
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact
Thursday, April 2, 2020 12:10 PM
Hi,
Since you're using a third party backup software, I'd start by asking in the Veeam forums.
Best regards,
Leon
Blog: https://thesystemcenterblog.com LinkedIn:
Thursday, April 2, 2020 12:12 PM
Yes, is open a case with the support.
I want to advance with the troubleshooting on Windows Server, to isolate problem.
Regards.
Marcos Ferreira
Thursday, April 2, 2020 12:18 PM
I'd wait to see what the Veeam support has to say, usually these kind of errors are due to incompatibility errors with third party software.
If the VSS are running fine, then the only thing to check is the event logs, more information here:
Diagnosing Failures in Windows Server Backup - Part 1 (VSS/SPP Errors)
https://techcommunity.microsoft.com/t5/storage-at-microsoft/diagnosing-failures-in-windows-server-backup-part-1-vss-spp/ba-p/423990
Blog: https://thesystemcenterblog.com LinkedIn:
Thursday, April 2, 2020 4:11 PM
Hi, the Shadow is configured with no limits:
Marcos Ferreira
Friday, April 3, 2020 2:26 AM
Hi,
Have you try to use Windows Server Backup to test your backup task? What was the result?
If you can use WSB to backup your VM successfully，we will think that the problem is related to veeam backup tool. As Leon said, you should contact veeam technical support for help.
If WSB also failed, please run "vssadmin list writers" and publish your result in here.
>>another shadow copy creation is already in progress
Please make sure there is no other backup task or hyper-v checkpoint during your backup process.
Also try to uninstall AV software and then try again.
Best Regards,
Daniel
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact
Monday, April 6, 2020 4:22 PM
Yes, with Windows Server backup, the error is:
The backup operation that started at '2020-04-06T12:50:03.370000000Z' 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 '0x80780021'. Please review the event details for a solution, and then rerun the backup operation once the issue is resolved.
vssadmin list writers:
C:\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: 'Microsoft Hyper-V VSS Writer'
Writer Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
Writer Instance Id: {b2052b8f-5d3c-4ebf-b32a-e0bde9049ee1}
State: [1] Stable
Last error: No error
Writer name: 'ASR Writer'
Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
Writer Instance Id: {78881d0d-9491-460b-b7c3-f32b16167964}
State: [1] Stable
Last error: No error
Writer name: 'Shadow Copy Optimization Writer'
Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
Writer Instance Id: {7540ea69-515d-4f6d-811c-6b6052a39739}
State: [1] Stable
Last error: No error
Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {e6a75124-408f-4bed-8c3b-98ac37ea065c}
State: [1] Stable
Last error: No error
Writer name: 'BITS Writer'
Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
Writer Instance Id: {39823d3a-4609-4732-b41a-f92e10d1b26b}
State: [1] Stable
Last error: No error
Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {c27c746c-5ca7-4aaf-92c7-f5cf78c30887}
State: [1] Stable
Last error: No error
There is no another task or chekpoint
Also, disabled the AV, bit the error is the same.
Marcos Ferreira
Tuesday, April 7, 2020 7:22 AM
Hi,
Do you run backup task on your host? And what do you want to back up？
If your backup contains CSV, maybe you should look at this:
/en-us/previous-versions/windows/it-pro/windows-server-2012-r2-and-2012/jj614621(v%3Dws.11)
Best Regards,
Daniel
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact
Tuesday, April 7, 2020 12:54 PM
Hi, i tried a backup of a small folder on c:\ disk.
Marcos Ferreira
Wednesday, April 8, 2020 7:33 AM
1.Besides Veeam，do you install any other backup tool on your server? try to uninstall VEEAM and try again.
Provider name: 'VSS Null Provider'
Provider type: Fileshare
Provider Id: {f4a69dd4-f712-40e3-a6b3-faeff03cb2b8}
Version: 5.0.158.0
Provider name: 'VSS Null Provider'
Provider type: Software
Provider Id: {8202aeda-45bd-48c4-b38b-ea1b7017aec3}
Version: 5.0.158.0
Do you install DPM on your server?
2.Can you do a snapshot for your VM?
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact
Wednesday, April 8, 2020 2:39 PM
Hi, the VSS Null is because we migrate from DPM to Veeam the last year, but we delete some days ago.
The snapshot of the VM, result OK, from Hyper-V Manager.
Important data: this is a clúster of 12 nodes, and when we evict one one, can list the shadows without problems.
At the moment of include again on the clúster, when try to list the shadows, the same stucks:
C:\Windows\system32>vssadmin list shadows
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2013 Microsoft Corp.
So, the problem is with VSS on the Clúster..
If we list the Writers on another node, see this writers "extra"
Would be a chance to register or export this writer?
Thanks
Marcos Ferreira
Saturday, April 11, 2020 9:54 PM
Hi, resolved after reboot all nodes.
Regards.
Marcos Ferreira
Friday, April 17, 2020 1:27 AM
Sounds good！
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact