Re: [BackupPC-users] Re: Shedulling ?

[Toby J. <pu...@to...>]

> 2002/12/13 04:30:02 Running BackupPC_nightly (pid=1820)
> 2002/12/13 04:30:02 Next wakeup is 2002/12/14 04:30:00
> 2002/12/13 04:30:04 Pool nightly clean removed 0 files of size 0.00GB
> 2002/12/13 04:30:04 Pool is 0.00GB, 0 files (0 repeated, 0 max chain), 1
> directories
> 2002/12/13 04:31:58 Cpool nightly clean removed 0 files of size 0.00GB
> 2002/12/13 04:31:58 Cpool is 0.63GB, 21660 files (0 repeated, 0 max
chain),
> 4344 directories
> 2002/12/13 04:32:08 Finished  admin  (BackupPC_nightly)
> 2002/12/13 07:08:39 User admin recovered file
> //servers/apache/toons/htdocs/images/cartoons
>
(/apps/backups/data/pc/10.10.6.1/0/f%2f/fservers/fapache/ftoons/fhtdocs/fima
> ges/fcartoons)
> 2002/12/13 07:20:27 Re-read config file because of a SIG_HUP
> 2002/12/13 07:20:27 Next wakeup is 2002/12/13 08:30:00
> 2002/12/13 08:30:00 24hr disk usage: 25% max, 25% recent, 0 skipped hosts
> 2002/12/13 08:30:00 Aging LOG files, LOG -> LOG.0 -> LOG.1 -> ... ->
LOG.13

BackupPC is waking up when it's supposed to, but it has decided each time
that there's nothing to do when it wakes up. If you have recently run a
manual backup, that will count towards the $Conf{IncrPeriod} and/or
$Conf{FullPeriod} trigger values.

Also, an automatic backup will not begin during the blackout period. It
appears that you have left this at the default of 7:00 - 19:30, M-F. So even
if it would have run at 8:30, the blackout period would have prevented it.

Maybe the log files should (optionally) be a little more verbose about why
exactly a backup isn't running. But all of the parameters that govern
automatic scheduling -- blackout period, incr/full maximum time period, and
wakeup schedule -- must agree before an automatic backup takes place.

toby