#! edit: this one got long, sorry!
backuppc doesnt currently do multiple incremental schedules, just one
schedule that can do multiple levels. so monthly level 1 and daily level 2
etc would only be able to be done with the incremental levels and having
them put in some specific order. example:
if you set incremental period to .04(which is less than 1 hour) and the
wakeup period to 1 hour, you would need to set the incremental levels in the
order which you wanted them to happen. for instance, if i put the following
in place for incremental levels
1,2,3,4,5,6,7,8,9,1,2,3,4,5,6,1,2,3
then i would get a level 1 incremetal, then 2 and so on but the 10th
incremetal would be a level 1 and the 16th would be a level 1 and the 19th
would be that cycle repeated. you can make a huge complicated script of
this but then it would get altered whenever you restart backuppc and is not
very elegant.
if you really wanted to do multi-level incrementals based on a schedule you
will need to use cron and issue the proper Backuppc_servermsg backup level
command
cron can understand days of the month so you can do this:(commands are wrong
cause i dont remember the syntax, so ill put it in english)
01 00 1 0 0 sudo -l backuppc backuppc_servermsg hostname_to_backup
level=full
(so that is 1 minute into the first day of the month, all months, and do a
full backup of the host given
and then
01 00 2 0 0 sudo -l backuppc backuppc_servermsg hostname_to_backup level=1
01 00 3 0 0 sudo -l backuppc backuppc_servermsg hostname_to_backup level=2
01 00 4 0 0 sudo -l backuppc backuppc_servermsg hostname_to_backup level=3
01 00 5 0 0 sudo -l backuppc backuppc_servermsg hostname_to_backup level=4
01 00 6 0 0 sudo -l backuppc backuppc_servermsg hostname_to_backup level=5
01 00 7 0 0 sudo -l backuppc backuppc_servermsg hostname_to_backup level=6
01 00 8 0 0 sudo -l backuppc backuppc_servermsg hostname_to_backup level=7
01 00 9 0 0 sudo -l backuppc backuppc_servermsg hostname_to_backup level=8
01 00 10 0 0 sudo -l backuppc backuppc_servermsg hostname_to_backup level=1
01 00 11 0 0 sudo -l backuppc backuppc_servermsg hostname_to_backup level=2
etc etc, or just write a shell script to pull the day of the week out of
date +%d and run an if statement to determine the backup level based on that
or even do a date +%w and do if date=0(sunday) do full, if date=1(mon) do a
level one and so on, and then a seperate line doing a full backup on the 1st
at 12:01. to avoid duplicate backups just do an if inside the first if
saying if it is day 1 of the month then dont do the regular schedule,
instead do a full.
just run you script everyday and let it determine what to do then your cron
will be just 1 line and would wont have to worry about some funky schedule
in backuppc that will get borked when you restart the machine.
if you do this you can turn off automatic backups in backuppc as the cron
script will be initializing them.
the other benefit of using the backuppc_servermsg is that you can have a
remote machine determin when to backup with an ssh script to remotely
execute the command(think laptops). if you have some nightly process like a
system batch job at the end of the night, you can have the ssh client stay
attached and put the backup command at the beginning of the batch job, then
backups get run automatically by the process.
many options :) if you install webmin you can manage cron from a web
browser with an easy to use gui.
On Dec 30, 2007 10:40 PM, Pablo Fernandez <[EMAIL PROTECTED]> wrote:
> Hi
>
> Got that, but if I use rsync would there be a reason to have a full
> backup every hour or so? Does it make sense to have a full once a month,
> level 1 incrementals every week, level 2 incrementals every day and
> level 3 incrementals every hour?
>
> Best regards,
> Pablo
>
>
> On Sun, 2007-12-30 at 21:32 -0800, Craig Barratt wrote:
> > Pablo writes:
> >
> > > Thanks for that information, this brings another question:
> > >
> > > What's the point of having multiple full backups? Wouldn't that be
> > > redundant with the information of a full backup and the incrementals?
> >
> > Full backups provide two things:
> >
> > - a reference point for the following incrementals,
> >
> > - an accurate backup, in contrast to tar and smb incrementals that
> > don't detect deleted, renamed or newly-created files with old
> > modification times (eg: extracting a tar file).
> >
> > If you keep an incremental, you need to keep the prior full (and also
> > prior lower-level incrementals). Therefore, full backups are the ones
> > you typically keep if you want longer-term history.
> >
> > Craig
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> BackupPC-users mailing list
> [email protected]
> List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
> Wiki: http://backuppc.wiki.sourceforge.net
> Project: http://backuppc.sourceforge.net/
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
BackupPC-users mailing list
[email protected]
List: https://lists.sourceforge.net/lists/listinfo/backuppc-users
Wiki: http://backuppc.wiki.sourceforge.net
Project: http://backuppc.sourceforge.net/
