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@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
