SQL won't freeze after v6 upgrade

[aweiss]

I confirm it was playing well in v5 !

[robertson]

I also have a replication job for a server running SQL Server 2008 hosting vcenter and remote veeam database that prior to upgrading the job to V6 the replication would complete ignoring the warning of " Unable to release guest. Details: VSSControl: Failed to freeze guest, wait timeout"
With the V6 job I recieve the same message but the job fails. I have the same situation as wberryment above anyone got any reccomendation on how I should proceed?

[foggy]

Just as Anton stated above, this issue was already investigated by our R&D team and will be addressed in a timely manner. Anyway, please open a support case for it. Thanks.

[aweiss]

Hi Guys,
My customer is still running the old veeam server just to run the Veeam DB. Any idea for the release date of the fix. My case # is 5159575
Thks
Alex

[Gostev]

Hi Alexandre, this would take at least a few weeks minimum. Thanks.

[ssinyol]

Hi,

We have the same problem.

Veeam in a VM, SQL in another VM. Backups were working with v5, we upgraded to v6, and VSS starts to fail in SQL server every time.

It must be something different in v6, because we didn't have any other change.

Thank you,

[rct]

Hi,

Veeam and SQL Server Express in a VM.
Working with v5 and with v6 it fails with the same message.

Waiting for this fix

[Vitaliy S.]

Make sure you open a support case to be notified about hotfix availability.

[ssinyol]

I've opened the case 5165361, but I can't get the patch 2.

Can you pass me the link?

Thank you

Sergi

[Vitaliy S.]

B&R 6.0 Patch 2 is available through our technical support, but this hotfix doesn't address the issue discussed in this thread.

[stepfes]

Same here! Since v6 no backup of SQL hosting Veeam DB.

Case: 5165681

[notermanjeroen]

Hi,

When I selected "Failover to network mode ..." on the local proxy it was able to backup, replicate and copy the local VM where I installed Veeam v6 and it's SQL Express DB on. When "Failover to network mode ..." was unchecked the jobs failed. Can someone confirm that this workaround works?

Kind regards.

[foggy]

Jeroen, according to VBR6 release notes you cannot use virtual backup proxy to backup Veeam server in hot add mode. That's why when you disable failover to Network mode, the job fails. However, this is not connected with the issue discussed in this thread (application-aware processing of SQL server with Veeam database).

[stevenrodenburg1]

Just wanted to add that I'm experiencing the same error. Veeam DB backup *always* worked correctly in V5 but *sometimes* will not freeze in V6. It happens maybe two or three times a week on a SQL VM that is replicated every hour and backed-up once a day. It's not a busy SQL server.

[ccitrano]

Guys,

I'm experiencing the same issue wit the "Unable to release guest". I have several other 'identical' servers except for 1 thing. The server that is giving me the error is hosting the Virtual Center Database. I'm wondering if that might be a side effect. I'm going to try and move the Virtual Center Database to a physical server and see if that helps.

Chuck.

[ccitrano]

All,

Having the Virtual Center Database on a Virtual SQL Server was the issue for me. I moved the VC database to a physical server and the backup ran cleanly. This kind of makes sense when you think it through.

Chuck.

[scoobymagic]

Hi,

Is their a patch or update for this, just wondering how its progressing?
cheers
A

[Vitaliy S.]

As far as I correctly see it from the internal patch release notes, this issue should be fixed by patch 3.

[foggy]

And patch 3 is already available (see the sticky topic in the main forum).

[Hotgun]

Applied Patch 3, even rebooted but still same error.

[foggy]

Have you got support team involved?

[averylarry]

Sorry Hotgun. The patch did work for me. (Happy dance!)

[kurt]

This issue started for me as well after upgrading to v6. I did install patch 3 and it's now showing version 6.0.0.181 64bit but it didn't help. I have veeam set up to retry after 30 minutes and the retry almost always works fine and is successful.

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

[Gostev]

This only means that your issue has nothing to deal with what is discussed in this topic, and has to be investigated separately.

From your description, it sounds like this problem has nothing to deal with Veeam though. Looks like SQL is legitimately unable to freeze itself within 60 seconds, because of being too busy. VSS framework gives all apps a maximum of 60 sec to freeze, and then there is hard stop - to make sure other applications do not stay unavailable for extended period of time because of misbehaving ones. While retry helps probably because most of housekeeping items were already done by SQL during the 1st attempt.

[kurt]

This only means that your issue has nothing to deal with what is discussed in this topic, and has to be investigated separately.

From your description, it sounds like this problem has nothing to deal with Veeam though. Looks like SQL is legitimately unable to freeze itself within 60 seconds, because of being too busy. VSS framework gives all apps a maximum of 60 sec to freeze, and then there is hard stop - to make sure other applications do not stay unavailable for extended period of time because of misbehaving ones. While retry helps probably because most of housekeeping items were already done by SQL during the 1st attempt.

Thanks for the info. Sorry if I thought it was the same issue. I've been backing up my SQL server with veeam 5x for over a year without any issue. This just started after upgrading to v6 so that's why I thought the new version was causing the problem. Is there anything I can check or should I just open a support case?

[Gostev]

Well, may be workload on that SQL has changed (increased). Or some performance issues with infrastructure/storage appeared, making the freeze go slower. One thing we can be sure about: our in-guest VSS component logic has not been changing for a few versions now.

[dasherrill]

We are backing up 500+ VMs with veeam. 95% of our SQL server and Exchange servers fail regularly since our upgrade to Veeam 6...all of the issues are VSS related. We have installed each patch and are now on patch 3 with no greater success. We still have Veeam 5 backup servers in our environment. If we take the backup jobs back to Veeam 5 we have good success as we did before the upgrade. If we move the job back to Veeam 6 then we experience a high rate of failures. Veeam support states that we have a resource problem some where in our environment. I really don't see how that is possible when the backups work well under the old version but poorly under the new version. We really could use some help here.

[Gostev]

The only caveat of this theory is that our in-guest VSS coordination process (the one that orchestrates the application freeze) has not been changing for a few versions now...

[hms7777]

I'm also running into this issue.

We are a smaller shop, and the SQL server in question hosts the Veeam v6 DB, but not the vCenter db.

Anyone have any ideas?

[Gostev]

Did you apply patch 3?