Chris Sarginson wrote:
Hi Dave,
We have a similar idea - the way we utilise bacula however is just to
create a single pool for a client, and then set their quota as the
Maximum Volume Bytes * Maximum Volumes.
This works for us simply because the client then has a definitive quota
set which we can modify by increasing the Maximum Volumes settings, and
having a File Retention of whatever time is required (1 week/month)
whatever. You just need to make sure you have enough space :)
Close I think. I believe that setting XX volumes of 1GB each in a single
pool for each client. Then setting the following in the client's Pool
resource.
Maximum Volume Jobs = 0
Maximum Volume Bytes = 1,073,741,824
Volume Retention = 7 days
AutoPrune = yes
Recycle = yes
Recycle Oldest Volume = yes
Purge Oldest Volume = yes
As I understand the manual, when backup time arrives Bacula will use the
oldest volumes first and purge whatever data is necessary to recycle the
oldest volume it finds. This would hold true regardless of retention
periods.
So if the client had 60GB of storage allocated, they could retain up to
60GB of data for up to seven days. But if they needed to backup 60GB in
one night, Bacula would recycle every volume to do do.
Am I correct?
DAve
Kind regards
Chris Sarginson
Technical Support
UKFast.Net Ltd
(t) 0870 111 8866
(f) 0870 458 4545
The UK's Best Hosting Provider ISPA Awards 2007, 2006 and 2005
Dedicated Servers - Managed Hosting - Domain Names- http://www.ukfast.net
UKFast.Net Ltd, City Tower, Piccadilly Plaza, Manchester, M1 4BT
Registered in England. Number 384 5616
DAve wrote:
Good afternoon,
We have been using Bacula for a while now and having good success within
our NOCs. We have a problem still, though not with Bacula itself.
Currently we configure three pools per client. A full pool which is used
on the 1st Sun, a Diff pool which is used on the 2nd, 3rd, 4th, and 5th
Sun, and a Inc pool which is used on Mon-Sat. We followed the example at
http://bacula.org/rel-manual/Automated_Disk_Backup.html
Unfortunately this allows some clients to greatly exceed their alloted
space. I think it is our fault for not configuring Bacula properly. I
would like to know if we can create 1GB volumes up to the client's
alloted space and then configure Bacula to use them to best advantage.
IE keep as much data as possible, but complete the scheduled backup even
if pruning all previous data is required to fit the current backup
within the volumes.
I am still reading through the manual again but I am not seeing a
possible solution, though I believe it is there.
Can anyone point me at a solution, a chapter/section to read, or an example?
Thank you.
DAve
--
I've been asking Google for a Veteran's Day logo since 2000,
maybe 1999. I was told they finally did a Veteran's Day logo,
but none of the links I was given return anything but a
normal Google logo.
Sad, very sad. Maybe the Chinese Government didn't like it?
-
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now http://get.splunk.com/
___
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
