Comprehensive data protection for all workloads
Post Reply
dspjones
Enthusiast
Posts: 45
Liked: 17 times
Joined: May 04, 2012 2:51 pm
Contact:

SQL and Veeam Services will not start

Post by dspjones »

Case: 01815440 (sev 1)


Need some assistance. All of a sudden neither the sql service nor any of the veeam services will start or they will start and then stop with error 1053. Not sure why this began occurring nothing new or different on the server. We did have a drive failure on the NAS that holds the veeam backup repository and the program files but nothing was lost or went down. The drive has been replaced and has rebuilt. Hard to say if that is the cause here. Nevertheless, backups have not run for over a day and we need to get this running asap especially for the exchange backup and log truncation to run.
Dima P.
Product Manager
Posts: 14716
Liked: 1703 times
Joined: Feb 04, 2013 2:07 pm
Full Name: Dmitry Popov
Location: Prague
Contact:

Re: SQL and Veeam Services will not start

Post by Dima P. »

Hi dspjones,

Did you perform any updates or new software installations on this backup server that could somehow affect SQL instance? Any chance you have a VBR configuration backup?
dspjones
Enthusiast
Posts: 45
Liked: 17 times
Joined: May 04, 2012 2:51 pm
Contact:

Re: SQL and Veeam Services will not start

Post by dspjones » 1 person likes this post

Issue has been resolved. Underlying cause was determined to be file/folder corruption of sql and veeam application files from a drive failure we had in our NAS that stores among other things our veeam application. We had to completely remove veeam and reinstall. Fortunately VBR config files were unaffected and after reinstall we restored the configuration. However, all the storage metadata from the current backups was corrupt so I had to follow the KB articles
https://www.veeam.com/kb1886 and https://www.veeam.com/kb1885 to get backups going again. All is well now though. Veeam is working again and the drive failure that caused all of this was addressed. It is wierd that the drive failure caused this. We've had drive failures in that array before and no corruption of files occurred but this time we weren't so lucky. At any rate support was very helpful in getting me going - Thanks to Torrey Bley from Veeam Support. We worked through the issue (even a bit past the end of his shift). Great Support folks!!!
Post Reply

Who is online

Users browsing this forum: No registered users and 81 guests