Hey guys,
I'm currently looking into implementing a backup-cycle that takes daily
incrementals, weekly differentials and monthly fulls (actually VirtualFulls
in my case). The goal is to be able to restore a file in its daily state
for a 'sliding window' of roughly one month.
My other goal is to recycle volumes as quickly as possible after they
expire (to save diskspace and to have a somewhat constant count of volumes).
My main question is if the retention periods I set are sane for the goals I
have in mind or if there are other catches I'm not aware of.
My schedule looks like:
Schedule {
Name = "WeeklyCycle"
Run = VirtualFull 1st sun at 20:00
Run = Differential 2nd-5th sun at 20:00
Run = Incremental daily at 23:05
}
Pool {
Name = {{ hostname }}-Full
Pool Type = Backup
Recycle = yes
AutoPrune = yes
*Volume Retention = 34 days*
Maximum Volume Bytes = 50G
LabelFormat = "{{ hostname }}-Full-"
Maximum Volume Jobs = 1
Action On Purge = Truncate
Storage = {{ storage_node }}
Next Pool = "{{ hostname }}-Virt"
}
Pool {
Name = {{ hostname }}-Incr
Pool Type = Backup
Recycle = yes
AutoPrune = yes
*Volume Retention = 8 days*
Maximum Volume Bytes = 50G
LabelFormat = "{{ hostname }}-Incr-"
Maximum Volume Jobs = 1
Action On Purge = Truncate
}
Pool {
Name = {{ hostname }}-Diff
Pool Type = Backup
Recycle = yes
AutoPrune = yes
*Volume Retention = 9 days*
Maximum Volume Bytes = 50G
LabelFormat = "{{ hostname }}-Diff-"
Maximum Volume Jobs = 1
Action On Purge = Truncate
}
Thanks for your help!
------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/NeoTech
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
