SQL Errors and Veeam not backing up since updates

[Theldron]

Hi all,

 

Our VM DC was working fine, but I installed the new Server 2012 r2 updates installed last night, and now I am seeing SQL errors and Veeam is not backing it up.

 

Looking in Event Viewer there is alot of

SQLVDI, WIDVDI

 

BackupVirtualDeviceFile::PrepareToFreeze: failure on backup device '{B290FC54-DC3C-4C35-BC70-16DAEFF7F85A}4'. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).

 

Any ideas?

 

Thanks

[webbobfc]

I suspect this may be something to do with the VSS writers in a failed state on your dc. Has it had a reboot after the updates?

 

https://www.veeam.com/kb2041

 

Maybe worth logging a call with Veeam if you have support.

[Theldron]

Hi all,

 

Our VM DC was working fine, but I installed the new Server 2012 r2 updates installed last night, and now I am seeing SQL errors and Veeam is not backing it up.

 

Looking in Event Viewer there is alot of

SQLVDI, WIDVDI

 

BackupVirtualDeviceFile::PrepareToFreeze: failure on backup device '{B290FC54-DC3C-4C35-BC70-16DAEFF7F85A}4'. Operating system error 995(The I/O operation has been aborted because of either a thread exit or an application request.).

 

Any ideas?

 

Thanks

 

Fixed this, looks like the latest update, messed with the SQL Browser, plus other SQL stuff. Ran repairs, started the browser, plus VSS writer, plus the apps, and retrying the backup. So far, so good.

[Koldov]

Fixed this, looks like the latest update, messed with the SQL Browser, plus other SQL stuff. Ran repairs, started the browser, plus VSS writer, plus the apps, and retrying the backup. So far, so good.

 

When you say 'ran repairs' what does that entail?

 

I wonder if this is a VEEAM issue, a general SQL issue or just your set-up?

 

Would be interesting to know for those of us with 2012R2 servers and big SQL databases like SIMS, who haven't taken the plunge with the November Update yet...

[Theldron]

That is an interesting one, hopefully it was just our setup. But if not maybe the below might help.

 

Programs and Features in Control Panel, and repaired the Microsoft SQL entries. I ran repair on SQL Server 2012 LocalDB and SQL Server 2012 Setup.