Hi all, I was wondering with volume recycling enabled what will happen
when bacula exceeds the maximum volumes (in a pool) and you are still
within a valid volume retention period? Normally, bacula would recycle
the volume, but in this case it wouldn't be allowed. I assume that this
point user intervention is required.
Here's an example. I have a backup policy that does a full backup once a
month with daily incremental. I want to have 6 months worth of full
backups, so I set maximum volumes = 6 and volume retention = 6 months.
However, I also have maximum volume jobs = 1, and I have 10 clients I
want to backup. After the 6th client's full backup the maximum volumes
parameter has been exceeded. So, bacula should think it needs to recycle
the volume, but cannot because the volume retention period is still valid.
If this was a problem, I take it the solution would be to increase the
number of maximum volumes, like to 60 (6 months x 10 clients). Or
increase the maximum volume jobs to, say, 10 (1 volume = 1 full backup).
And this would have to be incremented each time I added a client. I'm
just curious if any else has tackled this issue and, if so, how they
worked with it.
I'm using Bacula 1.38 on FC4, backing up to disk.
Cheers,
Rob
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
