December 1, 2010 at 6:32 pm
Very strange issue I am facing on my production server which is running without any issues for a long time...(nothing I know changed could cause this other than windows patches installations)
Its a 2 node active/active cluster (DL785 with 32 core & 256Gb of RAM) with windows 2003 r2 SP2 with SQL server 2005 SP2 (sp3 with CU10 is in planning for next month only)
Suddenly since yesterday log backup jobs start failing intermittently giving below message (works fine in next run)
Idera diagnostic monitor starts complaining not able to connect to SQL server once in a while as well
Failover from Node 1 to Node 2 does not help (Apparently not an OS issue)
changed remote login timeout to 60 still no luck (anyway jobs are failing at locally)
Only default windows patched has been implemented (wondering how this could possible change this behaviour)
DBA's Sys admins/network admins looked into it not much luck, everything looks normal......
2010-12-01 14:30:15.42----- START OF TRANSACTION LOG BACKUP -----
2010-12-01 14:30:30.44*** Error: Could not retrieve backup settings for primary ID '3222a279-f58c-4c6b-a51c-b3a30a300a9a'.(Microsoft.SqlServer.Management.LogShipping) ***
2010-12-01 14:30:30.44*** Error: Failed to connect to server xxxx\xxxx.(Microsoft.SqlServer.ConnectionInfo) ***
2010-12-01 14:30:30.44*** Error: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.(.Net SqlClient Data Provider) ***
2010-12-01 14:30:30.46----- END OF TRANSACTION LOG BACKUP -----
Prakash Heda
Lead DBA Team - www.sqlfeatures.com
Video sessions on Performance Tuning and SQL 2012 HA
December 1, 2010 at 6:42 pm
Prakash Heda (12/1/2010)
2010-12-01 14:30:30.44*** Error: Could not retrieve backup settings for primary ID '3222a279-f58c-4c6b-a51c-b3a30a300a9a'.(Microsoft.SqlServer.Management.LogShipping) ***
Is this the recipient, or the source, for a logshipped database?
2010-12-01 14:30:30.44*** Error: Failed to connect to server xxxx\xxxx.(Microsoft.SqlServer.ConnectionInfo) ***
I assume xxxx\xxxx is the local instance?
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA
December 1, 2010 at 10:50 pm
Its node one of cluster, if you are asking its a named instance then yes it is named instance....
Yes, this is source and log backup job is failing
Prakash Heda
Lead DBA Team - www.sqlfeatures.com
Video sessions on Performance Tuning and SQL 2012 HA
December 2, 2010 at 10:33 am
Okay, the primary issue here is the error that states the instance can't find the target log shipping server, or at the least, doesn't have permissions anymore on the target server.
You mention this is intermittant. I assume, then, this is a timeout problem from searching for it.
So, you have a few specific options. Need to find the pattern.
If this happens every Thursday at 3AM, time to take a look at the server for heavy jobs at 3AM, or network maintenance.
If this is random, it's time to do a hardware check. You've most likely got a short somewhere between the two servers.
Your problem isn't local to the server, it's network and related to communication with either the witness or the target log shipping database(s).
Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.
For better assistance in answering your questions[/url] | Forum Netiquette
For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
Twitter: @AnyWayDBA
June 17, 2016 at 8:18 am
Hi
Wondering that IS this issue resolved? If yes, than what was the solution because experiencing same issue since last couple of days for t-log backup for log shipped databases.
Thanks in advance.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply