65 hours for VSS snap creation

[St71]

Hi all,
I have an issue with Veeam agent 2.1.0.423 running on a Windows 10 : the backup stuck while it is creating VSS snapshot.
I tried to disable shadow copies on all disks, reset the Veeam Endpoint database and reconfigure the job but the problem persists.

Do you have any ideas?

Thank you

[Dima P.]

Hello Stefano.

Please launch an administrative command prompt, run vssadmin list writers and share the output. What is the size of the disk in the question? Thanks.

[St71]

Hi Dmitry, thanks for reply.

I ran the command and waited over 30 minutes but the system stayed in "waiting for answers, there may be a delay for the preparation of the shadow copy".

The size of disks are:
C: Size 237.9 GB Free 101.9 GB (SSD)
E: Size 931.5 GB Free 681.6 GB

[Dima P.]

Thanks!

I ran the command and waited over 30 minutes but the system stayed in "waiting for answers, there may be a delay for the preparation of the shadow copy".

Looks like something is wrong with VSS. Please try to reboot your computer and try again.

[St71]

Thanks, but I have already restarted 2 times without success...

[Dima P.]

Try to restart Volume Shadow Copy service (make sure it's enabled), rerun the vssadmin list writers command in cmd and share the output please.

[St71]

Hi,
yesterday I restarted the service but it doesn't works, so I tried with a fix to solve SSL issue (http://kb.macrium.com/knowledgebasearticle50010.aspx) and after a reboot finally the output of "vssadmin list writers" was normal.
However tonight the backup still got stuck in the usual way, and today I have again the problem that "vssadmin list writers" does not return any output.

[St71]

Hi, the problem persists.
I also tried to disable the quick start and the hibernation and run "sfc / scannow".

I do not know what to do anymore, any ideas?

[Dima P.]

Hi Stefano.

If you are still have this problem I suggest you to reach our support team. You can open support case via Control Panel > Support > Technical support (it's free). Do not forget to include you case details in this thread please. Thank you.

[St71]

Hi Dmitry,
I didn't think I could contact support for a free agent.

Thanks so much

[Dima P.]

Stefano,

We do provide a best effort support for all Veeam products running in Free edition. For Veeam Agent for Windows you can open a case directly from Control Panel. Thanks.

[dietoself86]

I'd like to know if you ever got this issue resolved. I've had a case open since the beginning of this year for the exact same issue. As a paying Veeam Agent customer it is beyond frustrating.

[Dima P.]

Hello Clint.

Please share the case number for a review. Thanks!

[dietoself86]

#02613758
Stuck creating VSS Snapshot
2
Veeam Agent for Microsoft Windows
Feb. 14, 2018 16:45

[dietoself86]

Dima,

Any updates here? We leverage Veeam Agent quite a bit for new users & workstation upgrades. We're kinda dead in the water over here & have been for a while.

[Dima P.]

Please keep working with our engineers. I've asked support team to review your case details and get QA team involved if that's required. Thanks.

[dietoself86]

FYI for anyone else who's been dealing with this issue. I can confirm that Windows Feature Update 1803 fixes the VSS snapshot error for Veeam Agent.

[jcapone]

I know this is an old post but we are having exactly the same issue. Did anyone find a resolution to this?

[Dima P.]

Hello John,

Can you please provide more details (Agent version, OS version)? Any chance you have a case ID? Thank you!

[jcapone]

The VSS snapshot did eventually get created thankfully. It was alarming that the job stuck at waiting for the snapshot for so long with no changes in the job status, but it did finally create the snapshot a couple of hours later and then the job completed less than an hour after that. Not sure why it did take so long but it did work without any other intervention.

[Dima P.]

Hello John,

Thank you for the update and glad to hear that it now works correctly! Since Veeam Agent for Windows relies on Microsoft VSS technology it's hard to say what when wrong with VSS snapshot creation without looking into the application debug log. If you face the same behavior again, please raise a support ticket and share the case ID with us. Cheers!