> Simon Köstlin wrote: > >>> It does not look like a tar problem but rather like one of the >>> underlying >>> network. What does the network topology look like? Is there a firewall >>> between BackupPC server and client host? A DSL link (that gets >>> disconnected >>> once every 24 hours by your provider, maybe, perhaps)? A flakey switch? >>> Someone shutting down the client (which happens to be a SuSE system and >>> therefore shuts down networking before killing processes ...)? >>> >>> True, the address does not *look* very remote ... >>> >> The network topology consists of some switches. I don't think that the >> network is the problem. All other host are in the same network and they >> are backuped up correctly. > > If the switches are managed, check for full/half duplex mismatches > between them and on the host connection (ethtool or mii-tool on the > linux side). If they don't match you'll get errors that are fixed by > tcp resends that can drastically reduce the throughput. A large ftp > tranfer is a good end-to-end speed check if you don't have access to > the switches. > The network should be ok. FTP transfer has also good speed. I ran the following command on the backuppc Server in a Shell: /usr/bin/ssh -q -x -n -p 14377 -l backuppc -i /home/backuppc/.ssh/id_dsa 192.168.10.201 nice -n 19 env LC_ALL=C sudo /bin/tar -c -v -f - -C /home --totals . >test.tgz But I got still the same Error after hours: Read from remote host 192.168.10.201: Connection timed out
It stopped at the same file I have posted. But it did stop on other files, too. ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ BackupPC-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/backuppc-users http://backuppc.sourceforge.net/
