Les Mikesell wrote:
On Mon, 2005-11-14 at 11:51, Paul Fox wrote:
even if the full were to take three days to complete? fulls happen
after a given number of incrementals, not after a given number of
days, right? at work we switched to cron for scheduling, for this
reason.
You should get a full run on the first opportunity (backuppc's wakeup
when you haven't already hit a limit on activity) every Conf{FullPeriod}
days regardless of what the incrementals are doing - as long as
$Conf{IncrPeriod} has elapsed since a successful one. The default 6.97
makes this effectively the same time every week.
Ah, thanks for clearing that up - I had the same sort of
misunderstanding as Paul, mine being that the full would start
$Conf{FullPeriod} days after the last one ended (vs. started), leading
it to slew through the week eventually. I suppose it's not an issue
until fulls are taking greater than $Conf{FullPeriod} to complete.
Eep. And since I sent the initial message off, I looked at the system
to see why it's so much data - turns out there's another form of backup
occuring that we might be able to nix and save some time and "effort".
(Well, probably a DVD-R every month in the archive set, anyway..)
I'll keep the cron method in mind in case it does slew (server down for
the weekend, etc) just to nail it into place.
Thanks!
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
BackupPC-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/backuppc-users
http://backuppc.sourceforge.net/
