Hi again,
On Tue, Nov 17, 2009 at 02:09:03AM +0100, Arno Lehmann wrote:
>
> 17.11.2009 00:49, Jerome Alet wrote:
> >
> > On Mon, Nov 16, 2009 at 02:35:12PM +1100, Jerome Alet wrote:
> >> We have an old bacula setup with a single tape drive as part of an
> >> autochanger, which holds three different pools for incremental,
> >> differential and full backups. On restore, the correct tape is correctly
> >> extracted from the database then mounted from the correct pool on our
> >> single tape drive.
> >>
> >> I'd like to replicate such functionnality on hard disks and a newer
> >> release of bacula (2.4.4-1 under Debian Lenny, AMD64 architecture,
> >> PostgreSQL backend).
> >>
> >> During backups, all my pools and volumes are used as needed.
> >>
> >> But during restore, what happens is that only volumes configured as
> >> being part of the pool defined for the "RestoreFiles" job are
> >> automatically mounted, and bacula waits for us to manually mount the
> >> other volumes, which don't seem to be possible since they are file
> >> volumes (i.e. always 'mounted')
> >
> > OK, I've fixed this particular problem by creating multiple Media Types.
>
> Great... I was about to suggest that :-)
>
> > This was written in the documentation, but not about this particular
> > subject, about multiple concurrent accesses instead.
>
> At least you found it - but where did you initially look? (Just so we
> can, perhaps, improve the manual)
I think I've searched this a lot in resources definitions, especially
pools, but the answer is (somewhat hidden) there :
http://www.bacula.org/en/rel-manual/Basic_Volume_Management.html#ConcurrentDiskJobs
Maybe this could be clarified but I don't really know where nor how,
since I'm a bacula newbie (our existing setup was put in place before I
landed here)
> >> As you can see above, I want to have very small volumes, but LOTS of
> >> them. When labelling them automatically, bacula only uses 4 digits, what
> >> will happen when it will reach 9999 ?
> >
> > Could someone tell me what happens then ?
> >
> > Does it automatically label the next volume as, for example,
> > "full-10000",
>
> That's what should happen, if I read the code correctly. Things will
> break if you end up with more than 19 digits.
>
> > or does it start over at "full-0001" and overwrite an
> > existing volume, or does it fail miserably because "full-0001" should
> > not be overwritten (if it's still full, as it will probably be) ?
>
> But - why do you want so many volumes that you expect to have 10,000
> in a few months? Sounds a bit hard to manage...
I knew the question would come !
:-)
I'm currently doing some testing and I like to play with things to see
if the solution is robust. When in production my volumes will certainely
be bigger than 32 MB as they are now.
Thanks a lot for your answers which clarify my thoughts.
bye
--
Jérôme Alet - <jerome.alet AT univ-nc DOT nc> - Centre de Ressources
Informatiques
Université de la Nouvelle-Calédonie - BPR4 - 98851 NOUMEA CEDEX
Tél : +687 266754 Fax : +687 254829
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
|
