Anr0480w

mvieselman

Newcomer
Joined
Dec 26, 2009
Messages
3
Reaction score
0
Points
0
Location
Hilversum
Hi there, a client of mine has a TSM 6.3.4 environment with 720 nodes and limited bandwidth.
They have once a week a schedule that backs up a directory on all clients.
Every time the backup starts they get:


2013-11-10-00.15ANR0480WSession 37937 for node FIL104 (Linux x86-64) terminated - connection with client severed. (SESSION: 37937)



2013-11-10-00.47ANR0480WSession 37947 for node FIL104 (Linux x86-64) terminated - connection with client severed. (SESSION: 37947)



2013-11-10-01.23ANR2579ESchedule BACKUP_FILIALEN_0000_SUN in domain PD_UNIX for node FIL104 failed (return code 8). (SESSION: 38489)



The commtimeout is on 36000 and the idletimeout is on 600.
but this doesnt seem to help.

We have tried making a script which eliminates return code 8 and put the to return code 0 whch makes them completely blind since they can't see if the backup was failed or correct.
But these errors they also don't want to see because it's a known issue.

Myself i want to eliminate these anr0480w errors, so is there an alternative which kills these errors?
 
Hi, for the first 2 errors, it seems it was caused by client side (like reboot?) / network level. May be you need to adjust the TCPWindowsize, which u may need to check the buffer space setting on the network adapter.

Also, not sure if you are scheduling backup running at the same time, you may need to consider to tune your backup windows a bit to avoid overwhelming traffic at the same time and generating causualilties
 
Back
Top