Creating Snapshot for 37 hours?

[BCT-Tech]

I know it is a lot of data, and the drives are not that fast. But should it be taking this long on the creating snapshot step?

Support Case # 02085111

[Mike Resseler]

Hi,

How much size are we talking about? And what is the OS? 37+ hours seems indeed like a very long time. (although, this is not something that is really related to our solution as we simply are the requester and it is the VSS writer that does the work.)

I would say keep working with support and let us know how it goes.

[BCT-Tech]

How much size are we talking about? And what is the OS? 37+ hours seems indeed like a very long time. (although, this is not something that is really related to our solution as we simply are the requester and it is the VSS writer that does the work.)

Backing up about 10TB of data (entire computer method), on Windows Server 2012 R2 to a shared folder on a NAS.

"Creating VSS snapshot" is at 60+ hours now. Support has only asked for logs to be manually uploaded to FTP. Have not heard back from them.

[Dima P.]

BCT-Tech,

Thanks for details. Asked QA team to take a look at your case.

[BCT-Tech]

Thanks for details. Asked QA team to take a look at your case.

Thank you. Support wanted us to reboot the Server and try the backup again. Rebooted the Server (Domain Controller) successfully last night, and the backup was already running again when I logged back in. The job failed within a few minutes, so I disabled the job and rebooted the Server again. Checked VSS writers – all looked good. Started the backup again and it failed with this error:

Code: Select all

"Creating VSS snapshot Error: Failed to create snapshot: Backup job failed. Cannot create a shadow copy of the volumes containing writer's data. A VSS critical writer has failed. Writer name: [NTDS]. Class ID: [{b2014c9e-8711-4c5c-a5a9-3cf384484757}]. Instance ID: [{b4d692b5-b334-4b46-a101-96f6c5bde719}]. Writer's state: [VSS_WS_FAILED_AT_FREEZE]. Error code: [0x800423f2].
Error: Failed to create snapshot: Backup job failed. Cannot create a shadow copy of the volumes containing writer's data. A VSS critical writer has failed. Writer name: [NTDS]. Class ID: [{b2014c9e-8711-4c5c-a5a9-3cf384484757}]. Instance ID: [{b4d692b5-b334-4b46-a101-96f6c5bde719}]. Writer's state: [VSS_WS_FAILED_AT_FREEZE]. Error code: [0x800423f2]."

I have uploaded new logs to the FTP and am waiting to hear back from support.

Also, this caused several VSS Writers to be in a failed state. I was able to restart services, and get all of them to a Stable, No Error state - except for the NTDS Writer. Even when I restart the "Active Directory Domain Services" service, the NDTS Writer stays in a "Failed, Timed Out" state.

[BCT-Tech]

Here are the current VSS Writers:

Code: Select all

C:\Windows\system32>vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001-2013 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: 'DFS Replication service writer'
   Writer Id: {2707761b-2324-473d-88eb-eb007a359533}
   Writer Instance Id: {1df4ff98-9b00-415d-a262-28ad48779238}
   State: [1] Stable
   Last error: No error

Writer name: 'System Writer'
   Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Instance Id: {c4150636-e85f-420c-ada2-3e8b92c25e58}
   State: [1] Stable
   Last error: No error

Writer name: 'SqlServerWriter'
   Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
   Writer Instance Id: {72d8514f-d8de-4902-81bd-e8c4c3fec39f}
   State: [1] Stable
   Last error: No error

Writer name: 'ASR Writer'
   Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
   Writer Instance Id: {9f27229b-2a8a-4cbe-b71d-a5d1e664ad70}
   State: [1] Stable
   Last error: No error

Writer name: 'FSRM Writer'
   Writer Id: {12ce4370-5bb7-4c58-a76a-e5d5097e3674}
   Writer Instance Id: {334d5e38-8fde-4a60-bd78-13db7e520da0}
   State: [1] Stable
   Last error: No error

Writer name: 'Shadow Copy Optimization Writer'
   Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
   Writer Instance Id: {c4d996ea-6a35-442d-8cf4-f7b64488dde6}
   State: [1] Stable
   Last error: No error

Writer name: 'Dedup Writer'
   Writer Id: {41db4dbf-6046-470e-8ad5-d5081dfb1b70}
   Writer Instance Id: {4af77c8a-b87f-4692-a7e3-68ae9db96c24}
   State: [1] Stable
   Last error: No error

Writer name: 'Dhcp Jet Writer'
   Writer Id: {be9ac81e-3619-421f-920f-4c6fea9e93ad}
   Writer Instance Id: {c511fae2-83eb-4605-8723-9a9b7bf892da}
   State: [1] Stable
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {57942101-3b44-4013-9763-e284ba96e12f}
   State: [1] Stable
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {c0510664-eead-4473-86c8-1e4d1b4dcb9c}
   State: [1] Stable
   Last error: No error

Writer name: 'BITS Writer'
   Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
   Writer Instance Id: {5c196437-6e25-4bf5-a903-7bf84e19c729}
   State: [1] Stable
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {a6a4e23a-a793-41ee-8d74-bbcb168421ea}
   State: [1] Stable
   Last error: No error

Writer name: 'NTDS'
   Writer Id: {b2014c9e-8711-4c5c-a5a9-3cf384484757}
   Writer Instance Id: {b4d692b5-b334-4b46-a101-96f6c5bde719}
   State: [9] Failed
   Last error: Timed out

[BCT-Tech]

Uploaded Windows Event Logs and VSS List Writers output to Support last Friday. Still waiting to hear back.

[Mike Resseler]

Hey,

Don't forget for now our support is based on a non-SLA support, so on best effort basis. But we try to get back to you as soon as possible. (Soon there will be the paid versions so that will improve support capacity )

Thanks for your patience

Mike