Hello,
On 1/8/2006 2:22 AM, Barry L. Bond wrote:
Greetings!
The highlight/most important problem is: I started using bacula in
mid-October. I went through about a week, learning things and getting it
to where it worked okay. It has worked very well since. Then, this past
week, with *no change* to my three bacula daemon configuration files, my
backups no longer work.
Hmm. After reading you post, I suspect that there waere not only changes
to the .conf files, but to the underlying OS...
As I didn't rebuild a sezup similar to yours ;-) I can keep my answer
shorter.
One important thing that comes to my mind is that you should only have
one restore template in the DIR configuration. Then, using identical
media types for different devices is not a good idea. I suspect it works
with drives that share one autochanger, but as your OS can't transfer
files from one mount point to the other when they are needed I guess
this doesn't work with your setup.
What I would suggest:
First, really simplify your setup.
Start with setting up the OS the way you want it - in this case,
separate mount points for the different disk drives. Make sure this part
works as expected.
Set up Bacula as follows:
- one device per disk mount point, obviously.
- different media types per storage device. This one is important for
restores, I guess.
- comment out or remove all test or default devices. This keeps your
status output more streamlined.
- think about how you want your jobs to work before you set up
schedules. Once you have lots of different jobs running with different
schedules it gets harder and harder to verify that you get what you want.
In your case, I'd probably use a backup scheme that sends the data to
the different storage devices, but uses the same pool names. For
example, use one pool Full and one pool Part, set maximum volume bytes
and volume use duration as you want them, and set up a schedule
Run = Level=Full Pool=Full Storage=Disk1 1st sun at 23:00
Run = Level=Full Pool=Full Storage=Disk2 3rd sun at 23:00
Run = Level=Differential Pool=Part Storage=Disk1 1st, 2nd mon-sat at
23:00
Run = Level=Differential Pool=Part Storage=Disk2 3rd, 4th, 5th
mon-sat at 23:00
Well, admittedly I didn't try the "3rd, 4th, 5th mon-sat" syntax, but I
guess you get my point... this idea cold becoma es fine-grained as you
like, for example you could send Mondays, Wednesdays and Fridays
differential backups to one disk, Tuesdays, Thursdays and Saturdays to
the other, and similarly handle the Full backups. And, also obvious
enough, if you want longer intervals between backups, yo can easily
adapt the above example. (I admit I copied it from another example...).
My idea is usually that it's best to keep the whole setup as simple as
possible. So, usually, I try not to use too many pools or too many
different schedules. Very important, too, is to only use one job for any
given fileset / client combination, otherwise you will never easily know
which backups rely on which ones. And, but that's more a personal thing,
I guess, I'm completely satisfied with volume names like Full-0001 or
even File-0001. The catalog and the available queries are the best tols
to see which volumes contain which files, I never relied on "telling names".
Arno
--
IT-Service Lehmann [EMAIL PROTECTED]
Arno Lehmann http://www.its-lehmann.de
-------------------------------------------------------
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
