TDP Domino Backup issue

balaji419

ADSM.ORG Member
Joined
Nov 17, 2017
Messages
12
Reaction score
0
Points
0
Recently our full domino database server backup session is running too long, and in the middle of the backups we are getting below errors.
01/09/2018 11:29:32 ACD5450E A failure occurred on TSM server session number (4), rc = 118
01/09/2018 11:29:33 ANS1017E (RC-50) Session rejected: TCP/IP connection failure.
01/09/2018 11:29:34 ACD5450E A failure occurred on TSM server session number (1), rc = 418
01/09/2018 11:29:34 ACD5701E A Tivoli Storage Manager API error has occurred.
01/09/2018 11:29:34 ACD5450E A failure occurred on TSM server session number (2), rc = 418
01/09/2018 11:29:34 ACD5701E A Tivoli Storage Manager API error has occurred.
01/09/2018 11:29:35 ACD5450E A failure occurred on TSM server session number (3), rc = 418
01/09/2018 11:29:35 ACD5701E A Tivoli Storage Manager API error has occurred.
01/09/2018 11:29:36 ACD5450E A failure occurred on TSM server session number (0), rc = 418
01/09/2018 11:29:36 ACD5701E A Tivoli Storage Manager API error has occurred.
01/09/2018 11:29:36 Backup of mail\glaborat.nsf failed.
01/09/2018 11:29:36 ACD5701E A Tivoli Storage Manager API error has occurred.

What could be the cause of this error? Is this related to network issue? Have any one faced this type of issue before?
 
Have you checked the health of your network, or the network in generally between the TSM Server and Domino servers?
 
Last edited:
Have you check the health of your network, or the network in generally between the TSM Server and Domino servers?
Thanks moon-buddy for your reply. we restarted the windows domino server, and after that TDP Domino Full backups seems to run fine. Will update how is it working in the future.
 
I am facing same issues and updated the TSM domino client to 5.5.3. But observed same issues again.

05/20/2019 11:45:23 ANS0326E (RC41) This node has exceeded its maximum number of mount points.
05/20/2019 11:45:23 ACD5450E A failure occurred on TSM server session number (0), rc = 418

I checked ping and tracert details but not found any errors.
 
Back
Top