[EMAIL PROTECTED] wrote:
> Hi World,
>
> First, thanks to developers for this wonderful tool: "Bacula".
>
> But some questions remained a little bit hard for me... let's go with the
> firs :)
>
> It's about my backup strategy, I have the same question than Gilberto Nunes
> Ferreira, and I saw that Phil Stracchino said that there is no solutions for
> a
> two weeks rotation strategy (mean pair/odd)? Did I understand well? You know
> I
> would like to make daily backup beetwen Mon and friday (so 5 tapes for pair
> week) and after WE, make 5 others daily backup from Mon to Fri (then 5 others
> tapes for odd week), then 2 weeks later, restart with the first 5 tapes (pair
> week).
The documentation appears to be in error in this regard. According to
Kern, the following Schedule syntax will work for this:
Schedule {
Name = "Alternate Pools"
Run = Level=Differential Pool=Pool1 1st,3rd,5th mon-fri at 10:00
Run = Level=Differential Pool=Pool2 2nd,4th mon-fri at 10:00
}
However, the BNF for date-time specifications in the manual says this
syntax will not work. This is apparently an error in the manual. Try
this and see if it works for you.
I tried to create volumes, label the first 5 tapes, then delete volume
> an recreate it with the other 5 tapes. It worked. But, what i didn't
> understand
> before, was the "number of files in catalog" parameter... it differs from a
> day
> of a pair week than a day from a odd week of course! and Bacula said to me
> that's wrongn, because for him it should the same tapes! So i don't know what
> to do...
>
> My second problem, is the size of the backup. You know my tapes can contains
> up
> to 80 Gb of compressed data, but Bacula don't want to write more than 37 Gb
> on
> its? what's the matter? in this case, i have to cancel Jobs... really bad you
> know ! Even with Compression=GZIP9 in Filesets parameters
Do you have hardware compression enabled on your tape drive? If
available, turning on hardware compression is almost always better in
all regards than using software compression. Remember, too, that not
all data compresses equally; in particular, already-compressed data
cannot usually be compressed further (unless the original compression
was not done well). Most tape manufacturers' claims of compressed
capacity manek highly optimistic assumptions about the average
compressibility of the data.
> Last question is about the catalog jobs... By default this jobs is separate
> from other Jobs... UI delete this Jobs and includes catalog path in my
> Fileset
> data... Am I wrong? Is this completely stupid? why?
There are several very good reasons for backing up the Catalog database
separately.
First, backing up the binary Catalog files is not guaranteed to give a
clean backup of the database, especially since the database will be open
and being modified as you back it up. It is better to exclude the
actual catalog database, perform a dump or hot copy of the database, and
back up that instead.
Secondly, if you back up the catalog with everything else, you back up
the catalog state in the middle of a job. What you want to do is wait
until all other jobs for the day have completed, and then back up the
catalog in THAT state, containing all the most up-to-date job data.
--
Phil Stracchino [EMAIL PROTECTED]
Renaissance Man, Unix generalist, Perl hacker
Mobile: 603-216-7037 Landline: 603-886-3518
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server.
Download it for free - -and be entered to win a 42" plasma tv or your very
own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users
