Hello,

On 22.10.2005 17:07, Gabriele Bulfon wrote:


Thanx Arno, I'll consider commenting out the MaxVolJobs and using the VolUseDuration. If I use a VolUseDuration = 24h , I should have each volume being marked as Used 24 hours after the daily backup, so I should be enough sure to have it recycled next week-day. Is it correct?

I'd think so. But probably you better make the time less than than 24 hours, just to make sure that, in case a job starts late, the tape isn't valid the next day.

Then comes up a possible problem about my config.
What should I do on vacation? This customer does not have a library LTO.
As a general idea, I should let them have a "vacation" volume (one tape only) to be left inside the LTO when they need for automatic backup every day with no human intervention. As I have one pool per day (I know you don't usually do like this, but let's just discuss),

:-)

I wouldn't want to talk you out of anything, it's just that I try to avoid problems...

is there some
way to label a volume and have it available on all pools?

No way. Each volume is always part of exactly one pool.

This way, I could reuse my pool configuration, by adding the "vacation" volume as a valid volume
for all the daily pools, and so be reused everyday by Bacula when inserted.
If this is possible, I think I should lower the VolUseDuration of this volume to maybe 12h, so that
it will be reused every day.
If this is not possible, what is another possibility?

Well, let the customer pay :-)
Either they hire an operator, they educate their own people, or they pay you enough to hire someone etc.

Or, better, you set up a temporary schedule with only one tape which is only used during your vacation. Or whatever. Perhaps I should offer my services to your customer :-)

Arno

<http://www.sonicle.com>
Gabriele Bulfon - Sonicle S.r.l.
Tel +39 028246016 Int. 30 - Fax +39 028243880
Via Felice Cavallotti 16 - 20089, Rozzano - Milano - ITALY
http://www.sonicle.com




----------------------------------------------------------------------------------

Da: Arno Lehmann <[EMAIL PROTECTED]>
A: bacula-users@lists.sourceforge.net
Data: 22 ottobre 2005 14.03.52 CEST
Oggetto: Re: [Bacula-users] Ensuring tape is not appended

    Hello,

    On 22.10.2005 13:34, Gabriele Bulfon wrote:

     >
     > Hello,
     > I have 5 jobs running daily (4 clients backed up + Catalog),
    making a
     > Full backup of the 5 jobs on a one tape daily. To ensure this, I
    used
     > the Maximum Volume Jobs = 5 and a very short recycle period of
    each volume.
     > There are times when one of the clients is not available during
    backup,
     > so the volume is in a state of 4 used jobs (instead of 5).
     > The next time the volume will be needed (next week), I find the
     > surprise: the first job is appended (to reach 5 jobs), the next 4
    jobs
     > hang in queue requesting for a new volume, leaving me without
    backup. So
     > I have to cancel all jobs, purge the volume manually , and run the 5
     > jobs using bconsole.
     > Shouldn't the short retention period be considered first and force
     > Bacula to purge the volume before starting the first job? The
    behaviour
     > suggests me that Bacula is first considering that the MaxVolJobs
     > parameter, thus appending without looking at the recycle timings.
     > So, my actual question is: is there any way to let the first job
    force
     > Bacula to purge the current volume (if correct for the pool) before
     > starting it? This would ensure that the first job is actually the
    first
     > on the volume, and next jobs will be appended, even when the
    MaxVolJobs
     > is not reached.

    Hmm, I have the impression I answered these questions already...
    anyway,
    once again :-)

    Bacula only considers recycling and purging and whatever when it looks
    for a new volume. In your setting, it _has_ an existing and appendable
    volume, so there's no need to prune it.

    You can use Admin Jobs to call external scripts that could mark a
    volume
    as Used, and that could trigger pruning.

    The, in my opinion, better solution is to set the Volume Use Duration
    and not the Maximum Volume Jobs. You described why.

    Arno

     > <http://www.sonicle.com>
     > Gabriele Bulfon - Sonicle S.r.l.
     > Tel +39 028246016 Int. 30 - Fax +39 028243880
     > Via Felice Cavallotti 16 - 20089, Rozzano - Milano - ITALY
     > http://www.sonicle.com
     >

-- IT-Service Lehmann [EMAIL PROTECTED]
    Arno Lehmann http://www.its-lehmann.de


    -------------------------------------------------------
    This SF.Net email is sponsored by:
    Power Architecture Resource Center: Free content, downloads,
    discussions,
    and more. http://solutions.newsforge.com/ibmarch.tmpl
    _______________________________________________
    Bacula-users mailing list
    Bacula-users@lists.sourceforge.net
    https://lists.sourceforge.net/lists/listinfo/bacula-users




--
IT-Service Lehmann                    [EMAIL PROTECTED]
Arno Lehmann                  http://www.its-lehmann.de


-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to