Veritas-bu

[Veritas-bu] Newbie volume pool question.

2007-02-13 12:59:43
Subject: [Veritas-bu] Newbie volume pool question.
From: jpiszcz at lucidpixels.com (Justin Piszcz)
Date: Tue, 13 Feb 2007 12:59:43 -0500 (EST)
Yes, sounds like a plan to me.

By assigning per-barcode rules for each volume, that will solve that 
problem of tape-assignment and disabling the global scratch pool as well 
should fix all my issues.

I will most likely be testing this tomorrow, thanks!

Justin.

On Tue, 13 Feb 2007, Martin, Jonathan (Contractor) wrote:

> I haven't really done this but I'm going to take a swing...
>
> You can't have a scratch pool if you don't want volume pools to have an 
> "overfill" tank.  SO I'd say *NO* scratch pool.
>
> Barcode Rules:
> ABC1 - DB Volume Pool
> ABC2 - DB Volume Pool
> ABC3 - FS Volume Pool
> ABC4 - FS Volume Pool
> ABC5 - INF Volume Pool
> ABC6 - INF Volume Pool
>
> I'm not sure *why* you are doing it this way but I think that would work...
>
> -Jonathan
>
> -----Original Message-----
> From: veritas-bu-bounces at mailman.eng.auburn.edu [mailto:veritas-bu-bounces 
> at mailman.eng.auburn.edu] On Behalf Of Justin Piszcz
> Sent: Tuesday, February 13, 2007 12:37 PM
> To: Paul Keating
> Cc: veritas-bu at mailman.eng.auburn.edu
> Subject: Re: [Veritas-bu] Newbie volume pool question.
>
> Example,
>
> I want DB to use tapes 100-200.
> I want FS to use tapes 300-400.
> I want INF to use tapes 500-600.
>
> And I don't want them to be mixed.
>
> Justin.
>
> On Tue, 13 Feb 2007, Paul Keating wrote:
>
>> Depends what you're trying to accomplish.
>>
>> What's your goal? To prevent the INF jobs from using up too many tapes?
>>
>> Paul
>>
>> --
>>
>>
>>> -----Original Message-----
>>> From: Justin Piszcz [mailto:jpiszcz at lucidpixels.com]
>>> Sent: February 13, 2007 12:31 PM
>>> To: Paul Keating
>>> Cc: veritas-bu at mailman.eng.auburn.edu
>>> Subject: RE: [Veritas-bu] Newbie volume pool question.
>>>
>>>
>>> Paul,
>>>
>>> Would the best solution then to be NOT define a global scratch pool
>>> and allocate scratch tapes into their respective (FILESYSTEM) and
>>> (INFINITE)
>>> volume pools?
>>>
>>> Justin.
>>>
>>> On Tue, 13 Feb 2007, Paul Keating wrote:
>>>
>>>> Yeah, you can't really "not" pick tapes from scratch, if you have a
>>> scratch pool defined.
>>>
>>> Sure you can override the Policies default pool in the schedule, but
>>> if there are no tapes in that pool, it will pull from the global
>>> scratch.
>>>
>>> Paul
>>>
>>> --
>>>
>>>
>>>> -----Original Message-----
>>>> From: veritas-bu-bounces at mailman.eng.auburn.edu
>>>> [mailto:veritas-bu-bounces at mailman.eng.auburn.edu] On Behalf Of
>>>> Justin Piszcz
>>>> Sent: February 13, 2007 10:39 AM
>>>> To: veritas-bu at mailman.eng.auburn.edu
>>>> Subject: [Veritas-bu] Newbie volume pool question.
>>>>
>>>>
>>>> I had done this in the past but it has been awhile, I am
>>> checking the
>>>> documentation now.
>>>>
>>>> But I was wondering if someone could point to the page or give me a
>>>> little reminder of how to do this.
>>>>
>>>> I have the following:
>>>>
>>>> FS-1
>>>> FS-2
>>>>
>>>> INF-1
>>>> INF-2
>>>>
>>>> I want the FS (filesytem backups) to use tapes from the global
>>>> scratch pool, no issues here.
>>>>
>>>> I want the INF (infinite-retention backups) to use a separate pool,
>>>> and when that pool runs out of tapes, it will NOT use any tapes
>>> from the
>>>> global scratch pool.
>>>>
>>>> I just define overrides in the schedule to pick from a new pool I
>>>> make and put scratch tapes in correct?
>>>>
>>>> INF-SCRATCH
>>>>
>>>> And then in the schedule policy information I override the volume
>>>> pool and make it INF-SCRATCH, correct?
>>>>
>>>> Am I forgetting anything?
>>>>
>>>> Thanks,
>>>>
>>>> Justin.
>>>> _______________________________________________
>>>> Veritas-bu maillist  -  Veritas-bu at mailman.eng.auburn.edu
>>>> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>>>>
>>> ==============================================================
>>> ======================
>>>
>>> La version fran?aise suit le texte anglais.
>>>
>>> --------------------------------------------------------------
>>> ----------------------
>>>
>>> This email may contain privileged and/or confidential information,
>>> and the Bank of Canada does not waive any related rights. Any
>>> distribution, use, or copying of this email or the information it
>>> contains by other than the intended recipient is unauthorized. If you
>>> received this email in error please delete it immediately from your
>>> system and notify the sender promptly by email that you have done so.
>>>
>>> --------------------------------------------------------------
>>> ----------------------
>>>
>>> Le pr?sent courriel peut contenir de l'information privil?gi?e ou
>>> confidentielle.
>>> La Banque du Canada ne renonce pas aux droits qui s'y rapportent.
>>> Toute diffusion, utilisation ou copie de ce courriel ou des
>>> renseignements qu'il contient par une personne autre que le ou les
>>> destinataires d?sign?s est interdite. Si vous recevez ce courriel par
>>> erreur, veuillez le supprimer imm?diatement et envoyer sans d?lai ?
>>> l'exp?diteur un message ?lectronique pour l'aviser que vous avez
>>> ?limin? de votre ordinateur toute copie du courriel re?u.
>>>
>> ======================================================================
>> ==============
>>
>> La version fran?aise suit le texte anglais.
>>
>> ----------------------------------------------------------------------
>> --------------
>>
>> This email may contain privileged and/or confidential information, and
>> the Bank of Canada does not waive any related rights. Any
>> distribution, use, or copying of this email or the information it
>> contains by other than the intended recipient is unauthorized. If you
>> received this email in error please delete it immediately from your system 
>> and notify the sender promptly by email that you have done so.
>>
>> ----------------------------------------------------------------------
>> --------------
>>
>> Le pr?sent courriel peut contenir de l'information privil?gi?e ou 
>> confidentielle.
>> La Banque du Canada ne renonce pas aux droits qui s'y rapportent.
>> Toute diffusion, utilisation ou copie de ce courriel ou des
>> renseignements qu'il contient par une personne autre que le ou les
>> destinataires d?sign?s est interdite. Si vous recevez ce courriel par
>> erreur, veuillez le supprimer imm?diatement et envoyer sans d?lai ?
>> l'exp?diteur un message ?lectronique pour l'aviser que vous avez ?limin? de 
>> votre ordinateur toute copie du courriel re?u.
>>
>