November 2, 2011 at 11:06 am
Hi
Would a long running transaction log backup that eventually completed be the reason why my differential backup failed?
The actual error was Failed to login to SQL Server [SQLSTATE HY000] (Error 49999).
We are using Litespeed however re-running the job worked fine so I don't believe there was anything wrong with the account, and the logs are all clear. So could it be that the sql agent threw a wobbly?
Thanks
November 2, 2011 at 11:22 am
According to my memory, but more important this url:-) - http://msdn.microsoft.com/en-us/library/ms189315(v=SQL.100).aspx, you can run both types of backup at the same time.
Adi
--------------------------------------------------------------
To know how to ask questions and increase the chances of getting asnwers:
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
November 2, 2011 at 4:33 pm
ah cool nice graph 🙂
still left with what seems to be an uninvestigatory error though 🙁
November 2, 2011 at 5:09 pm
The failed to login sounds like the domain account being used to login wasn't able to talk to AD (assuming AD is involved). That seems to be a highly likely cause of this error - especially since it worked later.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
Viewing 4 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply