>
> Hi,
>
> Simon K?stlin wrote on 30.04.2007 at 12:25:18 [[BackupPC-users] Tar Backup
> aborts (Connection Timed out)]:
>
>> I can see the following error log at the end of this mail created by one
>> of my hosts to backup.
>>
>
> yes, I can see it too :-).
>
>
>> My Timeout is set to $Conf{ClientTimeout} = 576000. Which should be about
>> 160h, but the backup aborted already at about 41h.
>>
>
> You're not hit by the timeout (that would be a SIGALRM) but rather by a
> network error. 41 hours is quite a long backup run. If you were using rsync,
> I'd suggest splitting up your backup by first excluding a large part of it
> and gradually reducing the exclude list. That way you'd get shorter backup
> times and things would be more likely to complete (or at least wouldn't
> restart from scratch). "Millions of files" might or might not make that a
> bad idea though.
>
> You won't like the suggestion, but you *could* split the "share" up into
> several "shares" to also reduce backup run time ...
>
What do you mean with gradually reducing the exclude list? To exclude
some files of a share and then define the same share with the backuped
files before?
>
>> Why is tar aborting?
>>
>
> 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.
A firewall isn't there, too.
The server should be always on, nobody is shutting down it. The backup
failed every time a backup was running, but it failed not at the same
position.
>
>> All other hosts backed up without any problem. It is normal that the
>> backup takes so long because there are millions of files to backup.
>>
>
> Does that mean that this host normally works? Or only other similar hosts?
> Did it fail just once or repeatedly? What's the exact difference to the
> other hosts? Distributions? Kernel versions?
>
No, only the other hosts work correctly. It fails repeatedly.
It is a debian server with Kernel 2.6.10. The other servers are debian
or ubuntu servers, too. There shouldn't be much difference.
> Regards,
> Holger
>
>
-------------------------------------------------------------------------
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/
