November 16, 2007 at 12:38 pm
I have no idea, but I'd call PSS. Something is wrong here and you don't want to be running without the ability to backup or recover.
It's worth the $250.
November 18, 2007 at 11:04 pm
Thanks for the reply, Steve.
This remains unsolved for the moment.
November 19, 2007 at 8:29 am
Please let us know if you find anything.
Has the server been rebooted?
The server does get recovered every time and it's possible if there were lots of changes that needed to be rolled forward or back, that you'd get messages like this. However typically recovery happens quickly. There shouldn't be too many transactions that aren't complete when you shut down.
November 20, 2007 at 6:21 am
The most common cause I have seen of a backup not completing but not giving errors is lack of disk space for the backup. This should give you a clear error message, but I have been at the wrong end of a full disk and a failed backup with no error message more than once. Another possible cause is your server is so busy the backup just takes a very long time to complete.
Your SQL Error Log messages are likely to be due to transactions still being running when the server is rebooted. It is best practice to close SQL Server manually before booting the server, to allow time for active transactions to either finish or be rolled back.
If you are sure none of the above apply then I agree with Steve - contact PSS as there could be something more serious wrong. Even if they find an easy answer, think of the $250 as money invested in your training.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
Viewing 4 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply