On Fri, 13 Jan 2006 - 9:35am, Thomas Simmons wrote:
Hello,
I just realized that bacula is recycling previously written tapes before taking
any from the scratch pool. My pool directives are below. With this setup, I
would think that bacula *could* overwrite any tape after four weeks, but
shouldn't if any are available in the scratch pool. Unfortunately, I still have
nine tapes available in my scratch pool and tapes in the full pool are being
overwritten.
AFAIK the Scratch-Pool is only used if _no other tape_ is available.
If there is one, that one will be used.
This may be true, however IMHO recycling should be the very last resort. Here's
a snippet from the bacula manual.
"It is important to know that when the Volume Retention period expires, Bacula does not automatically recycle
a Volume. It attempts to keep the Volume data intact as long as possible before over writing the Volume."
For the last part to be true, the scratch pool should be checked before a recycle occurs. The only time I can
see this not happening, is when "Max Volumes" is set and has been reached. Again, just my opinion.
What you are looking for is the "Use Oldest Volume" directive, or something
close to it. Please read the manual for it.
I had problems with "Use Oldest Volume" in the past. I have a tape library, and if the "Oldest Volume" was
offsite, bacula would just sit there and wait instead of trying the next oldest volume. A full backup here is
just over 1TB, and takes about 24 hours, so the weekend is the only window I have to fit that in. If that
backup never runs because bacula is waiting or whatever, I lose backups for a week.
This brings to light one other question. A few months back the 1.37 and early
1.38 versions of bacula had a problem with jobs failing when the tape device
was writing to a tape in one pool and a job started that required a tape in
another pool. Has this been fixed yet? My temporary solution has been to use a
single pool, as can be seen below, but I would really like to setup a
full-diff-inc schedule.
At 9pm I have ~10 jobs started, though they all use the same pool.
I would say that its working anyway, if you have a tape-library that
automagically changes the tape and gets one from the correct pool.
One tape can only belong to one pool.
This problem only existed if you were using multiple pools. If I remember correctly only a handful of users
had this problem.
Besides that its not a problem to have full/div/inc tapes in one pool.
For example, if you define a Job as 'differential' and a Job Retention of 6
days, the backup on the 7th day will always be a full backup, cause Bacula
ensures that there's always a valid full backup for a FileSet/Job.
Have a nice day,
Michael
Thanks,
Thomas
-------------------------------------------------------
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
