On 10/22 08:22 , List Receiver wrote:
> > On 10/19 03:53 , List Receiver wrote:
> > > Putting that hosts timeout at 300ms? Where is that defined? I see
> > only
> > > one timeout in BackupPC, and it appears to be globally applied to all
> > > transport methods. Am I missing something obvious?
> >
> > Put
> > $Conf{PingMaxMsec} = 300;
> > (or whatever value you think appropriate)
> > into one of the per-host configuration files. (i.e.
> > /etc/backuppc/<yourhost>.pl)
>
> That doesn't help me here, as some of my WAN hosts are unpingable. I've
> replaced the ping utility with echo. As well, even if I was pinging the
> hosts prior to starting the backup, this would only adjust whether or not
> the backup started, not whether or not it would complete. The backup is
> always starting, and as far as I know, always getting a transfer ID. It
> just never completes an incremental.
Sorry, I don't have a lot of ideas. I was just answering the question you
had that looked unanswered by anyone else. :)
Les had a good idea that may be an explanation. Perhaps you could set up a
continuous ping, or otherwise generate network traffic between the client
and server, to see if that keeps the link from dropping?
--
Carl Soderstrom
Systems Administrator
Real-Time Enterprises
www.real-time.com
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
BackupPC-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/
