Re: Linux Client Won't Back Up
If I back up files individually, it works OK. But when I try to do an incremental back up of a file system, I get the following errors: ANS1005E TCP/IP read error on socket = 8, errno = 104, reason : 'Connection reset by peer'. The peer is the TSM server. What does its Activity Log say about the reason that it terminated the session? Maybe the server was installed with default configuration values and its timeout specs need boosting? Richard Sims, BU
Re: Linux Client Won't Back Up
Thanks for your response Richard, The activity log says: ANR0481W Session 3174 for node GPGECOS (Linux86) terminated - client did not respond within 60 seconds. The TSM server has: IDLETIMEOUT 30 COMMTIMEOUT 60 Other nodes compress and transfer files over a gig in size. With this Linux node, I can't even get /var, with several little files, to back up. I wonder if there's some problems with the TCP/IP settings in Linux itself not necessarily TSM. - Forwarded by Bradley Wallace/TheGuardian on 07/09/2003 08:15 AM - Richard Sims [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent by: ADSM: Dist Stor cc: Manager Subject: Re: Linux Client Won't Back Up [EMAIL PROTECTED] 07/09/2003 07:24 AM Please respond to ADSM: Dist Stor Manager If I back up files individually, it works OK. But when I try to do an incremental back up of a file system, I get the following errors: ANS1005E TCP/IP read error on socket = 8, errno = 104, reason : 'Connection reset by peer'. The peer is the TSM server. What does its Activity Log say about the reason that it terminated the session? Maybe the server was installed with default configuration values and its timeout specs need boosting? Richard Sims, BU
Re: Linux Client Won't Back Up
The activity log says: ANR0481W Session 3174 for node GPGECOS (Linux86) terminated - client did not respond within 60 seconds. The TSM server has: IDLETIMEOUT 30 COMMTIMEOUT 60 Other nodes compress and transfer files over a gig in size. With this Linux node, I can't even get /var, with several little files, to back up. I wonder if there's some problems with the TCP/IP settings in Linux itself not necessarily TSM. The server COMMTimeout is way, way too low for reality. A value of 3600 is much more realistic. Boost it via the SETOPT command (then manually fix the dsmserv.opt file for the next restart.) It's not the size of the file: it's the amount of time in between files. You need to give the client time to rummage around in its file system to accumulate the next buffer's worth of files and send that, which can take considerable time in an Incremental with a file system that has few updates. Richard Sims, BU
