I just checked my BackupPC server and noticed that it hadn't run any
backups for a couple of days, so I checked the logs and saw:
2005-11-30 23:00:00 Disk too full (77%); skipping 6 hosts
2005-11-30 23:00:00 Next wakeup is 2005-12-01 00:00:00
(and so forth)
Rather than risk not having backups for a few days, I bumped the
$Conf{DfMaxUsagePct} up a bit and fired off some manual jobs. I can't
tell from the documentation, however, whether this is a self healing
situation where BackupPC will start to expire older archives to make
space for some new backups. I'm sort of assuming yes, but only when
$Conf{FullAgeMax} is hit, which gives good reason to set FullAgeMax to
only slightly over the longest full kept period instead of (as I had set
it) double.
On the other hand, though, will it remove aged fulls that have
dependent incrementals? In other words, is this generally a human
intervention situation, or will BackupPC eventually deal with it through
the usual scheduling methods within a reasonable amount of time?
Now, to figure out why I didn't get any email!
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
BackupPC-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/
