Hi,

I´ve been facing a problem when trying to backup one of our clients.
The backup starts normally, but after some time, the following message shows up
in the taper log:


dumper: stream_client: our side is 0.0.0.0.45740
driver: result time 553.824 from dumper0: FAILED 01-00002 [mesg read: 
Connection reset by peer]
dumper: kill index command
taper: reader-side: got label DMX224 filenum 1


On the client side, I can read something like this on the sendbackup log:

sendbackup-gnutar: time 0.248: /usr/local/libexec/runtar: pid 15147
sendbackup: time 0.309: started index creator: "/usr/bin/tar -tf - 2>/dev/null 
| sed -e 's/^\.//'"
sendbackup: time 301.700: index tee cannot write [Broken pipe]
sendbackup: time 301.700: pid 15145 finish time Tue Mar 21 15:39:18 2006
sendbackup: time 301.712: 124: strange(?): sendbackup: index tee cannot write 
[Broken pipe]


I've already tried to turn off index and the holding disk, but no success.

One important thing I´ve noticed is that the error allways occurs after 300 
seconds.
Is there some tunable timeout I´m forgetting?

Additional info: strangely, the backup appears successful, even when this 
message shows up.
The same client is able to backup other file systems, and the one that fails 
the most
is the / filesystem.

Any ideas?

TIA