On Tue, Nov 06, 2007 at 07:11:24PM +0100, Holger Parplies wrote:
> I've redirected my reply to <backuppc-devel> (and
> changed the subject) because your issue does raise a
> question regarding the design of the web interface.
> And sorry if I've misquoted you :).
No problem.
> John Rouillard wrote on 01.11.2007 at 19:03:23
> [[BackupPC-users] Incremental backup levels not
> working.]:
> > I am working with BackupPC 3.1.0Beta0. I have
> >
> > $Conf{IncrLevels} = [1, 2, 3];
> >
> > set in my config file. However when I schedule a backup from the web
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > interface it always shows up as a level 1, even when the prior backup
> ^^^^^^^^^
> > was a level 1. Is this expected?
Actually it is a bug in the beta software. It should
schedule the next incremental. so if the prior one was a
level 1 and the next should be a level 2 it will
schedule a level 2 (if the bug is fixed).
> Prior to the notion of multi-level incremental backups, there were
> two choices for manual backups: do a full backup or do an
> incremental backup. Is the matter still so simple with multi-level
> incrementals? In the example above, if the last run backup was level
> 2, I could meaningfully request
>
> - a full backup
> - a level 1 incremental
> - another level 2 incremental or
> - a level 3 incremental
>
> to be run, and at least three of these options seem to make sense:
Yup. I can see that. I was wondering why there wasn't an option to
BackupPC_dump to force an particular incremental. When I used the OSU
backup system, I would run a tower of hanoi schedule with level 9
incrementals at noon every day. So I had a backup of the morning's
work in case somebody deleted it. The level 9 incrementals were held
onto for 3 days and cycled out. I can't do quite the same with
BackupPC because the $Conf{IncrKeepCnt} and $Conf{IncrAgeMax} are
scalars and not arrays like $Conf{IncrLevels}.
So I can't say:
$Conf{IncrLevels} = [ 1, 9, 2, 9, 3, 9,];
$Conf{IncrAgeMax} = [30, 3, 30, 3, 30, 3,];
$Conf{IncrKeepCnt} = [12, 3, 12, 3, 12, 3]
> - I need a full backup done now. Period. This can already be done.
> - The previous level 2 incremental was, for some reason, not what I
> wanted. Redo it now.
> - Prepone the normal level 3 incremental to right now.
Or even perform another level 1 incremental (or in general incremental
less than the currently scheduled one) because the level 2 was too
big.
> I'm not quite sure how it works right now, because I don't use
> multi-level incremental backups (yet), but I'd guess the
> "incremental backup" button either always does level 1 or whatever
> would be due next according to the configuration. Of these, the
> latter option seems to be preferrable.
It does a "whatever would be due next" if the bug is fixed.
> Would it make sense to add the option to "Start level X incr backup"
> where X would be specified in a text input field? Strictly, that one
> option would suffice (level 0 is a full backup), but retaining
> "Start full backup" and "Start whatever incr backup is due" for
> convenience would probably be a good choice.
I think so.
> What does "run whatever is due" do if a full backup is due next?
> What effect do manual incremental backups have on the automatic
> schedule?
It looks like incrementals only schedule an incremental. Probably
because BackupPC_dump takes a 0/1 argument to specify the level (full,
incr). So with a request to do an incremental, only an incremental is
done.
--
-- rouilj
John Rouillard
System Administrator
Renesys Corporation
603-643-9300 x 111
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
BackupPC-users mailing list
BackupPC-users@lists.sourceforge.net
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
