Solved:
For reference if anyone else has this problem, it seems that at some
point (presumably to stop backups) someone has changed the FullPeriod
option to -1, which upon reading the comments in greater detail seems to
disable backups from running.
Having changed this to a positive value - I ca
On Jun 09, Les Mikesell wrote:
>
> The usual reason for backups stopping is that your disk space is nearly
> full but the error message makes this look like some other problem.
>
There's well over 600 gigs available on the current storage pool so I
don't think this is the issue. I've just gone t
On Jun 09, Chris Robertson wrote:
>
> How certain? ;o)
>
100% ;-)
> Fair enough, but is it possible that $Conf{BackupsDisable} is set twice
> in this one file?
> When you performed your grep, you stated "nothing turned up". Does that
> mean that nothing UNEXPECTED showed up, or nothing at a
Hiya,
Thanks for your reply.
> I assume this means the main config file. There are also per-host
> config files that will override the main one.
Correct. I have checked that there were no overriding settings in other
configuration files. Did a grep on the entire configuration directory to
be
Hi,
I've run in to a bit of a strange issue. We have a large number of
backups running on backuppc and up until recently they have all been
working fine. Now I see everything as Idle with aging "last backups"
Now, when I attempt to kick backups off manually I get the usual:
"Reply from server
