mvieselman
Newcomer
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:
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?
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.15 | ANR0480W | Session 37937 for node FIL104 (Linux x86-64) terminated - connection with client severed. (SESSION: 37937) |
2013-11-10-00.47 | ANR0480W | Session 37947 for node FIL104 (Linux x86-64) terminated - connection with client severed. (SESSION: 37947) |
2013-11-10-01.23 | ANR2579E | Schedule 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?