Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

SQL Server backup Failures with TSM \TDP TCP\IP Connection Failure Expand / Collapse
Author
Message
Posted Thursday, September 19, 2013 12:54 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Monday, June 2, 2014 2:18 PM
Points: 20, Visits: 173
Sql Server Versions 2005, 2008R2
Folks I'm at a loss and the TSM Administrators are also now throwing lines into the water to start fishing.
Has anyway had or seen the following errors from the backups
09/19/2013 13:10:13 ACO5436E A failure occurred on stripe number (1), rc = 418
09/19/2013 13:10:13 ANS1017E (RC-50) Session rejected: TCP/IP connection failure
09/19/2013 13:10:13 ACO5436E A failure occurred on stripe number (0), rc = 418
09/19/2013 13:10:13 ANS1017E (RC-50) Session rejected: TCP/IP connection failure
09/19/2013 13:10:13 ACO5436E A failure occurred on stripe number (2), rc = 418
The failure is random, it can be at the start, middle, end of the backup process. I have looked the IBM Blogs to no help, they just point into a loop within them the blogs and never answer the question. the diserrorlog is no help.
So has anyone every encountered this error, and what did you do to get around the error.
I see this in about 12 to 15 servers a night.
Yes manual backups through the TDP gui does complete normally. But that consumes allot resources...
Post #1496560
Posted Monday, September 23, 2013 2:48 PM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Thursday, July 24, 2014 10:24 AM
Points: 373, Visits: 1,235
It looks like a network problem to me.

Ask your IT guy or Network admin to check the switches, traffic and overall network status between your MS-SQL server and your target machine. Even the cables, if he has access to the data center.

Based on those errors, it looks like you are dropping TCP/IP packets which is causing the connection to be reset or dropped altogether. A very slow disk subsystem may also cause this (if you have a fast network) as they both need to be in sync.
Post #1497556
Posted Tuesday, September 24, 2013 2:41 PM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Tuesday, March 25, 2014 2:25 PM
Points: 327, Visits: 537
you can find all system actions and user responses related to TSM

Click Client Messages reference.

http://publib.boulder.ibm.com/infocenter/tsminfo/v6/index.jsp?topic=%2Fcom.ibm.itsm.messages.doc%2Fmsgs5542.html
Post #1498038
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse