On 6/9/05, Arno Lehmann <[EMAIL PROTECTED]> wrote:
> Hello,
>
> Jonte Norman wrote:
>
> > On 6/8/05, Arno Lehmann <[EMAIL PROTECTED]> wrote:
> >
> >>Hello,
> >>
> >>Jonte Norman wrote:
> ...
> >>
> >>Hmm. Should work. BUT using more than one Media Type (and thus,
> >>implicitly, more than one storage device) makes restoring rather
> >>difficult. But you _have_ to use one job definition per... yes, per job :-)
> >>
> >>Not one job for full and one job for diff, both using the same fileset.
> >>
> >
> >
> > Maybe this is were I´ve made my mistake to begin with... I read
> > through the chapter about "Basic Volume Management" -->
> > "Considerations for multiple clients" for the fifth time :-) and found
> > that the recommendations were that you should also specify different
> > Media Types to be shure that the volumes are saved on the right
> > Storage Device.
>
> Yes, that might help.
>
> > The problems I´m having are not that Bacula does´nt create the backups
> > but that it also creates 0 byte Volumes on the wrong Storage Devices
> > and are reporting errors about this in the mail reports... Maybe the
> > problem disappears if I also specify different Media Types as File1,
> > File2 instead of only one Media Type? I´ll try that tomorrow night and
> > see what happens.
>
> You'll have to try, I never really used automatic labeling or backup to
> files.
>
> ...
> > I´ve read quite a lot of the Bacula documentation but I´m not sure if
> > I have understood it and implemented it all correctly ;-)
>
> Well, I guess most bacula users needed some time to get it working as
> wanted, and the more complex your needs are the more time you've got to
> spend on it. Obviously. Well, bacula is simply very flexible, and that
> has a price.
>
> > I´ve attached my bacula-dir and bacula-sd config files with this mail.
> > If you have the time I would be very happy if you could take a look at
> > them to see if I have misunderstood the hole Bacula concept... But I
> > fully understand if you don´t have time to look at them.
>
>
> Well, I looked :-)
>
Big thanks for taking time looking at the config files... Sometimes
it´s hard to explain in words how something is configured :-)
> First thing I find in bacula-dir.conf is that you still seem to have job
> definitions in it where you separate full and incremental jobs into
> separate job definitions. That's just what won't work.
>
I understand that now :-(
> You need one job definition, like
> Job {
> Name = "nitrogen"
> Client = nitrogen-fd
> JobDefs = "FullJob"
> Storage = "Nitrogen-Full"
> FileSet = "Nitrogen FileSet"
> Write Bootstrap = "/usr/local/bacula/var/bacula/working/nitrogen.bsr"
> }
>
> And in the schedule you can do things like the following:
> Change
> > Schedule {
> > Name = "Full"
> > Run = Full 1st sun at 01:05
> > Run = Differential 2nd-5th sun at 1:05
> > }
> >
> > Schedule {
> > Name = "Incremental"
> > Run = Incremental mon-sat at 1:05
> > }
>
> to something like
> Schedule {
> Name = "Full"
> Run = Level=Full storage=Full 1st sun at 01:05
> Run = Level=Differential storage=Diff 2nd-5th sun at 1:05
> Run = Level=Incremental storage=Incr mon-sat at 1:05
> }
OK! Now here is where I´m getting confused again :-) If I understand
this right, this only allows me to use three different Storage
Devices. Is it possible to have one schedule for each client so that I
can backup each client to a separate volume on a separate Storage
Device?
>
> >
> >>Like this:
> >>Define job with client, fileset, name, schedule, options. You can use
> >>the directives to setup different pools per backup level.
> >>
> >>You create one schedule:
> >>Setup name and multiple run lines, for example
> >>run= storage=S-Full level=Full pool=Full fri at 23:00
> >>run= storage=S-Diff level=Differential pool=Diff mon-thu at 23:00
> >>
> >
> >
> > When I first tried to do my concurrent multi client, multi storage
> > backups I did try this... But with three Pools and two Storage Devices
> > but then I could not get the concurrent jobs working, Bacula was just
> > waiting for the first job to finish before it continued with the next
> > job.
>
> Can't tell you why exactly, but it is important to make sure that no two
> jobs try to access one storage device and different volumes. Even though
> with file storage that could work, bacula doesn't like that because it
> also has to know how to handle tapes.
>
But if I can use one schedule for each client it would still be
possible to have a separate storage device for each client and still
have each volume automatically labeled.
I´ll try to re-work my config files this weekend with one job
definition, two storages and two schedules per client... I´ll let you
know how it all goes :-)
Best regards,
Jonte
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput
a projector? How fast can you ride your desk chair down the office luge track?
If you want to score the big prize, get to know the little guy.
Play to win an NEC 61" plasma display: http://www.necitguy.com/?r
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
