Backup hangs on Server 2012

[tromsonoc]

Hi

Lately we have been experiencing trouble with one of our customers.
The backupjob is set to take backup on 2 servers: Server 2008R2 and 2012.

The 2008R2 is done in a few minutes, but the backup of the 2012 server is currently approaching a week
http://imgur.com/ujuyT3s

I have recreated the backupjob multiple times, and i have set the timeout to 30 mins.
Last time when i waited for the actual error message it took 1,5 months.

Error:
Failed to prepare guest for hot backup. Error: VSSControl: Failed to prepare guest for freeze, wait timeout 18875 sec
Error: VSSControl: Failed to prepare guest for freeze, wait timeout 18875 sec

Timeout is set to 1800000.

Best regards,
TN

[foggy]

What kind of VM it is (does it hold SQL Server, for example)? Could you check the VSS writers state by running the following command within the guest OS:

Code: Select all

vssadmin list writers

Do you have something related in the Windows Events Log? Have you ever contacted Veeam support with this?

[veremin]

Hi, Tromso. Can it also be that this VM is a vCenter machine with locally attached SQL database, or just a machine that apart from DC hosts a vCenter database?

Thanks.

[tromsonoc]

Hi

Thanks the for the replies.

No it doesnt hold any databases, its only a DC.

I tried the "vssadmin list writers", but it didn't work. VSS is not enabled on any of the drives.
Nothing in the event log about the backup either.

[foggy]

I tried the "vssadmin list writers", but it didn't work.

What do you mean by "didn't work"? What was the output of this command?

[tromsonoc]

Didn't get any output, it just hanged.
However, i found out that the VSS service had stopped. Though i experienced another problem when i tried to start it again.

Im gonna reboot when the customer leaves work today. Got error 1053 in services.

[foggy]

Didn't get any output, it just hanged.
However, i found out that the VSS service had stopped. Though i experienced another problem when i tried to start it again.

Generally, there's no need to enable anything manually. I would recommend to open a case with technical support, as it is advised for any technical issue. Logs should definitely tell more information of why the VM cannot be backed up normally.

[tromsonoc]

Case solved

Had to delete the VeeamVssSupport folder and let Veeam recreate it.
(C:\Windows\VeeamVssSupport)

[veremin]

Thanks for coming back and updating the topic with the found resolution; much appreciated.