Stefan Peter <s_peter AT swissonline DOT ch> wrote on
11/18/2012 04:55:49 PM:
> On 18.11.2012 20:44, Till Hofmann wrote:
> > But now, when I'm trying to archive more clients at once, the
> process receives ALRM after exactly 20 hours.
> >
> > 2012-11-09 19:54:29 Starting archive
> > 2012-11-10 15:54:29 cleaning up after signal ALRM
> > 2012-11-11 03:16:38 Archive failed (aborted by signal=ALRM)
> >
> > I figured my system is set up to allow only 20 hours of execution
> time but I couldn't find any settings like that, all my files in /
> etc/security are untouched.
> >
>
> Have a look at the ClientTimeout in the "Backup Settings"
of your
> archive host (or the $Conf{ClientTimeout} variable in
> /etc/backuppc/archive.pl).
This is the solution. I have archives that take
days to create (they're about 3TB big before compression) and I have to
crank the ClientTimeout *way* high.
I've tried figuring out a way to get the archive process
to reset the ClientTimeout timer while the archive is running (like backups
do, I believe), but I have yet to hit on a successful way of doing it...
:(
If anyone's interested, I can share details of what
I've tried, as well as accepting any suggestions to try.
Tim Massey
------------------------------------------------------------------------------
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add services
Discover what IT Professionals Know. Rescue delivers
http://p.sf.net/sfu/logmein_12329d2d _______________________________________________
BackupPC-users mailing list
BackupPC-users AT lists.sourceforge DOT net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
|
