On 6/8/05, Arno Lehmann <[EMAIL PROTECTED]> wrote: > Hello, > > Jonte Norman wrote: > > > Hi Arno, > > > > Tank you very much for your answer. > > > > Now let me see if I got this right :-) > > As I understand the big no no with the way I implemented my config > > files is that I have three pools (full, diff and incr) and defined > > multiple jobs (one full-job and one incr-job) for each client which > > maps against multiple storage devices and this is not allowed in > > Bacula? Beside this I also very much would like my client jobs to run > > concurrently against the director so that the backups will finish > > faster ;-) > > 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. 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. > > The way you describe that can be used instead is to have two pools > > (full + incr), two storage devices, one job resource and two schedules > > (one schedule with another storage device specified). Have I > > understood your suggestions right? Do you use this config with > > concurrent backups? > > Ok, I don't know how much of the manual you already read ;-) Of course, > you can also use three pools (and storage devices), but I want to keep > the axplanation simple. And you only define one job. > 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 ;-) 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. > 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. > that's all. > And yes, you can run jobs concurrently, although using spooling seems to > be avery good idea then. I do that and it works ok. I thought spooling was effective only when you are doing backups to tape and not when you are backing up to disk? > > > I don´t know if I understand your other suggestion about joining the > > partitions, when the thing I would like to do is to have full backups > > to go to one partition and the incremental backups to another > > partition... But maybe it´s just me misunderstanding your suggestions > > :-) > > Or I misunderstood what you need. I thought that space considerations > were the reason to distribute backups to different partitions, and those > you can overcome. If your reasons for using two partitions are > different, then, of course, volume management is not automatically the > way to the easiest solution... No, the only reason for me wanting the full backups on a different partition is because I´m going to move them off site and I thought it would be easier to move them by just having them on one mounted disk instead of mixed full and incr backups all over the place :-) Best regards, Jonte > > Arno > > > Again... A big thank you for your advice! > > > > Best regards, > > > > Jonte Norman > > > > > > > > On 6/7/05, Arno Lehmann <[EMAIL PROTECTED]> wrote: > > > >>Hello, > >> > >>this is one of the guys on this list :-) > >> > >>Kern Sibbald wrote: > >> > >> > >>>Unfortunately, Bacula does not support what you are trying to do. The guys > >>>on > >>>this list will help you do what you want using Pools -- one Job and one > >>>Storage device. > >> > >>You could override the jobs storage device setting in the schedule. > >>For example, define the job with the storage for full backup, use full > >>pool and incremental pool settings, and in the schedule for the > >>incremental you add storage=xxx > >> > >>Something like this works here with tapes and different tape drives. > >> > >>BUT there are some more-or-less serious disadvantages: > >>- automatic job upgrading doesn't work as it should, and > >>- restore can be a pain. > >> > >>You can find more details in the list archive. Or, best solution, try it > >>for yourself :-) as that's the only way to definitely find out if the > >>additional trouble is ok for you. > >> > >>In your place, I'd use your system's volume management to simply join > >>the available partitions. Of course, that increases the risk of errors, > >>but that's what you get for doing backups to tape ;-) > >> > >>Arno > >> > >> > >>>On Tuesday 07 June 2005 14:51, Jonte Norman wrote: > >>> > >>> > >>>>Hi Kern, > >>>> > >>>>Thanks for your quick answer. > >>>> > >>>>Maybe I was somewhat unclear in my problem description :-) > >>>> > >>>>I´ve defined two jobs and two storage devices for each client, one > >>>>job/storage device for full and diff backups and one job/storage > >>>>device for incremental backups... > >>>> > >>>>The reason why I did this is because I want the volumes containing the > >>>>full and diff backups to be stored on a different partition on my disk > >>>>storage. > >>>> > >>>>I´ve specified "Maximum Concurrent Jobs = 4" in bacula-dir.conf and > >>>>bacula-sd.conf and when all the client starts at the same time Bacula > >>>>seems to get confused about which volume to create on each storage > >>>>device. > >>>> > >>>>Best regards, > >>>> > >>>>Jonte Norman > >>>> > >>>>On 6/7/05, Kern Sibbald <[EMAIL PROTECTED]> wrote: > >>>> > >>>> > >>>>>Bacula does not support multiple different MediaTypes or Storage devices > >>>>>within the same Job. > >>>>> > >>>>>On Tuesday 07 June 2005 14:03, Jonte Norman wrote: > >>>>> > >>>>> > >>>>>>Hi, > >>>>>> > >>>>>>I´m using Bacula to backup all my clients to a large disk storage... > >>>>>> > >>>>>>In my bacula-dir.conf I´ve specified so that a separate volume should > >>>>>>be created for each of my clients full, diff and incr backups. These > >>>>>>volumes should also be stored on different disks/partitions based on > >>>>>>if they are full or incr backups. > >>>>>> > >>>>>>This works somewhat fine :-) But the problem is that even thou I´ve > >>>>>>specified different storage devices for each client in their job > >>>>>>resources the director tries to create a wrongly named volume (a > >>>>>>volume for another client) on the specified storage device. > >>>>>> > >>>>>>Here is a bit of a mail report from Bacula that I´ve cut and pasted: > >>>>>> > >>>>>>---snip--- > >>>>>> > >>>>>>05-Jun 14:50 nitrogen-dir: Start Backup JobId 26, > >>>>>>Job=platinum-full.2005-06-05_14.50.01 > >>>>>>05-Jun 14:50 nitrogen-sd: platinum-full.2005-06-05_14.50.01 Warning: > >>>>>>Volume "nitrogen-full.2005-06-05_14.50.00" not on device > >>>>>>/vol/1/platinum-full. > >>>>>>05-Jun 14:50 nitrogen-sd: Marking Volume > >>>>>>"nitrogen-full.2005-06-05_14.50.00" in Error in Catalog. > >>>>>>05-Jun 14:50 nitrogen-sd: Labeled new Volume > >>>>>>"thorium-full.2005-06-05_14.50.02" on device /vol/1/platinum-full. > >>>>>>05-Jun 14:50 nitrogen-sd: Wrote label to prelabeled Volume > >>>>>>"thorium-full.2005-06-05_14.50.02" on device "/vol/1/platinum-full" > >>>>>> > >>>>>>---snip--- > >>>>>> > >>>>>>Does anyone have a clue on why this is happening? > >>>>>>Maybe I´ve done something wrong when configuring the bacula-dir and sd > >>>>>>config files ? :-) > >>>>>>I can mail the content of the config files if this will help... > >>>>>> > >>>>>>Best regards, > >>>>>> > >>>>>>Jonte Norman > >>>>>> > >>>>>> > >>>>>>------------------------------------------------------- > >>>>>>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 > >>>>> > >>>>>-- > >>>>>Best regards, > >>>>> > >>>>>Kern > >>>>> > >>>>> ("> > >>>>> /\ > >>>>> V_V > >>> > >>> > >>-- > >>IT-Service Lehmann [EMAIL PROTECTED] > >>Arno Lehmann http://www.its-lehmann.de > > > >> > > -- > IT-Service Lehmann [EMAIL PROTECTED] > Arno Lehmann http://www.its-lehmann.de >
bacula-dir.conf
Description: Binary data
bacula-sd.conf
Description: Binary data
