I agree with the idea of using different pools (you can specify the pool
to use in the schedule). The incremental pool could have a volume
retention of 9 days, so you would only have incrementals just past the
last full. While we are talking about changing the retention times, I
would also suggest using 20 days instead of 15 for the full. That way,
you have two full backups almost all the time, in case one of them has a
problem. The oldest full backup will be pruned right before the next
full backup.
The "Maximum Volume Jobs" is not going to do what you want, though.
Imagine that you start the system on a Tuesday. Then your volume is
going to have the Full from Sunday and the next incremental, but also
the incrementals from Tue-Sat *before* the Full.
All that said, my suggestion is to simply keep these old incrementals in
the first place.
a) Incrementals tend to be small, so they don't take up too much space.
b) They aren't actually useless. You can still restore files off these
incrementals. In fact, most of the time the incrementals tend to be the
only files that ever change in the first place. So if you have to go
back a week and a half, you can often come very close by restoring the
week-old Full backup, and then restoring the incrementals on top of it,
even if they are older.
Fahrer, Julian wrote:
> You could use different pools for full and incremental Backups. So an
> incremental backup won't overwrite a full one.
> Or you could set "Maximum Volume Jobs = 7" instead of "Use Volume Once". So
> you will always have your full backup and the incrementals in one volume. You
> also have to adjust Maximum Volumes and Volume Retention.
> But your incrementals will still be worthless when overwriting a full backup.
> I guess that's just the way it works.
>
> -----Ursprüngliche Nachricht-----
> Von: Konrad Matyas [mailto:konrad.matyas AT mobiteam DOT pl]
> Gesendet: Samstag, 31. Januar 2009 08:35
> An: bacula-users AT lists.sourceforge DOT net
> Betreff: [Bacula-users] Bacula strategy question
>
> Hello everybody,
>
> I have a question about bacula strategy.
> Currently I'm making backups on local partition (sata hard drives in
> raid5 configuration). I store 2 FULL backups every week and on all other
> days I make Incremental backups.
> I keep max 15 volumes.
> Below are "parts" from my configuration:
>
> Schedule {
> Name = "DailyCycle"
> Run = Incremental mon at 0:00
> Run = Incremental tue at 0:00
> Run = Incremental wed at 0:00
> Run = Incremental thu at 0:00
> Run = Incremental fri at 0:00
> Run = Incremental sat at 0:00
> Run = Full sun at 1:00
> }
>
> Client {
> Name = name-fd
> Address = xxx.xxx.xxx.xxx
> FDPort = 9102
> Catalog = MyCatalog
> Password = ""
> File Retention = 15 days
> Job Retention = 15 days
> AutoPrune = yes
> Maximum Concurrent Jobs = 30
> }
>
> Pool {
> Name = PNAME
> Use Volume Once = yes
> Pool Type = Backup
> AutoPrune = yes
> Volume Retention = 15d
> Volume Use Duration = 14d
> Maximum Volumes = 15
> Recycle = yes
> Purge Oldest Volume = yes
> Recycle Oldest Volume = yes
> LabelFormat = "VNAME"
> }
>
>
> The problem is when there are 15 volumes and new backup needs to be done
> (situation when one of full backups is the oldest volume). Then bacula
> takes the oldest one and "on that place" creats new backup. But the
> oldest is a full backup so all incremental backups done after the "FULL"
> are then useless.
>
> Maybe my backup strategy is wrong. Has anyone any suggestion what to do
> with that problem?
>
> I'll be thankful.
>
> Best regards,
> Konrad
>
>
>
>
>
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by:
> SourcForge Community
> SourceForge wants to tell your story.
> http://p.sf.net/sfu/sf-spreadtheword
> _______________________________________________
> Bacula-users mailing list
> Bacula-users AT lists.sourceforge DOT net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by:
> SourcForge Community
> SourceForge wants to tell your story.
> http://p.sf.net/sfu/sf-spreadtheword
> _______________________________________________
> Bacula-users mailing list
> Bacula-users AT lists.sourceforge DOT net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
>
--
Kevin Keane
Owner
The NetTech
Find the Uncommon: Expert Solutions for a Network You Never Have to Think About
Office: 866-642-7116
http://www.4nettech.com
This e-mail and attachments, if any, may contain confidential and/or
proprietary information. Please be advised that the unauthorized use or
disclosure of the information is strictly prohibited. The information herein is
intended only for use by the intended recipient(s) named above. If you have
received this transmission in error, please notify the sender immediately and
permanently delete the e-mail and any copies, printouts or attachments thereof.
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
|
