Hi all,
(running bacula 7.0.5)
We currently, backup to disk and use 'Autoprune = True' in our Pool and
Client resources to remove expired records from the catalog. This works
great, but as our clients are growing I'm wanting to move away from having
the pruning done during the backup period.
My plan is to use 'prune expired' console command as a RunScript in the
catalog backup job. Something like this [1]:
Job {
Name = CatalogBackup
...
RunScript {
Console = "prune expired volume yes"
RunsWhen = Before
}
}
My question though, is, since we rotate through our disk volumes, like so:
Pool {
Name = aim01
Storage = aim01
Pool Type = Backup
Recycle = True
Recycle Oldest Volume = True
AutoPrune = True
Volume Retention = 29 days
Maximum Volumes = 30
Volume Use Duration = 23h
Label Format = "${Client}-${JobId}-vol"
}
will we ever have any volumes that are expired, and need to be pruned? In
my case should I change those Console commands to:
'prune expired files yes'
'prune expired jobs yes'
?
Thank you for any clarification.
[1]: Taken from the Bacula community disk backup whitepaper:
http://blog.bacula.org/whitepapers/CommunityDiskBackup.pdf
------------------------------------------------------------------------------
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
from Actuate! Instantly Supercharge Your Business Reports and Dashboards
with Interactivity, Sharing, Native Excel Exports, App Integration & more
Get technology previously reserved for billion-dollar corporations, FREE
http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
