Just change them to be LTO4 tapes.
Every time you run a catalog backup it overwrites what was on the tape.

-----Original Message-----
From: veritas-bu-boun...@mailman.eng.auburn.edu 
[mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Nate Sanders
Sent: Thursday, June 03, 2010 2:02 PM
To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU
Subject: Re: [Veritas-bu] LTO3 to LTO4 conversion

When it comes to LTO3 to LTO4 conversion, what about the catalog? I
found where to control what tapes are used for Media 1 and Media 2 (and
reside in the Netbackup pool) but I assume I can leave these on LTO3 for
the time being and just focus on the LTO4 upgrade? When I do want to
move the catalog to LTO4, do I just assign new LTO4 tapes from the
Netbackup pool to be Media 1 and Media 2? Or do I need to copy the
existing catalog from the LTO3 tapes to the LTO4 tapes?


On 05/27/2010 09:33 AM, Nate Sanders wrote:
> Yeah that's what I'm thinking as well. I have a new scratch pool just
> for LTO4 media so that all of the old pools will be disassociated from
> existing policies. As LTO3 tapes expire back to their original pools,
> they won't be used anyways.
>
> On 05/26/2010 06:39 PM, Martin, Jonathan wrote:
>   
>> That's why I was thinking about making a new scratch pool. If you make a new 
>> scratch pool, and "deactivate" the old scratch pool, your LTO3 media should 
>> still return to the old scratch pool when they expire, while barcode rules 
>> move new LTO4 media into the new scratch pool.
>>
>> -Jonathan
>>
>> From: veritas-bu-boun...@mailman.eng.auburn.edu 
>> [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Dean
>> Sent: Wednesday, May 26, 2010 6:07 PM
>> To: Nate Sanders
>> Cc: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU
>> Subject: Re: [Veritas-bu] LTO3 to LTO4 conversion
>>
>> This is an interesting one. I understand the need to keep LTO3 and LTO4 as 
>> the same media type, so you can still restore from LTO3 tapes on LTO4 
>> drives. But how to ensure the expiring LTO3 tapes don't return to scratch 
>> and get reused for new backups?
>>
>> Freezing them is the only way I can think of. It will work. It just means 
>> you'll have to manually unfreeze them at some point in the future so you can 
>> delete them. If you have long-ish retentions on some of these backups (like 
>> 7 years, as we do), it's something that will hang around for a while!
>>
>> It would be nice if there was some way to tell NBU, for a particular tape, 
>> or set of tapes, that they shouldn't be returned to scratch. But I can't 
>> think of any way to do it (other than freezing).
>>
>> Manually flipping the write-protect tab on the tapes is not really an 
>> option, as you'll get lots of backups failing with status 84 (media open 
>> error) when they try to write to the write-protected scratch tapes.
>>
>> I guess freezing is the only option. You can periodically run bpmedialist 
>> over the coming ... years? .... and if a tape is both frozen, and expired, 
>> you'll be able to tell that all the images on it have expired. I guess the 
>> best thing to do then would be to physically eject it from the library, then 
>> unfreeze it (I like the term "thaw"), at which point it will go straight 
>> back to the scratch pool. Then you can delete it completely (vmdelete, or 
>> just right click and delete in the GUI).
>>
>> I had an inkling there was a "previous_pool" type parameter you could set 
>> with vmchange, so when a tape expires, it will go back to something other 
>> than the scratch pool, but I can't see any reference to it.
>>
>> If anyone else has a better solution to this little problem, it's something 
>> I'd be interested in too.
>>
>> Cheers
>> Dean
>>
>> On Thu, May 27, 2010 at 4:35 AM, Nate Sanders 
>> <sande...@dmotorworks.com<mailto:sande...@dmotorworks.com>> wrote:
>> Yeah that is our intent, to keep the media type the same. Changing drive
>> types presents a more challenging rollback and also limits us to the
>> amount of drives we can us during the migration and for restores.
>> Overall using new pools is quicker and easier to migrate with.
>>
>> How do I freeze LTO3 media, outside of having to write protect every
>> tape by hand.
>>
>> On 05/26/2010 01:29 PM, Iverson, Jerald wrote:
>>   
>>     
>>> if you are replacing all drives at once, you may want to keep the media
>>> type the same, so that you can still read the lto3 media in the lto4
>>> drives (such as restoring data). the lto4 drives can also write to the
>>> lto3 media if need be, unless you want to write using encryption.  i've
>>> seen it freeze the lto3 media if it loads it when wanting to write to an
>>> encrypted pool.  if you do keep the drives the same type, then simply
>>> freeze all lto3 media and they shouldn't be able to be written to if
>>> they are "active" or even after all images expire.  they will remain
>>> "frozen" until you unfreeze them, and then you could manually move them
>>> to a media pool that no backup policies use.  you wouldn't need to
>>> change any barcode rules or backup policies.
>>>
>>> jerald
>>>
>>> -----Original Message-----
>>> From: 
>>> veritas-bu-boun...@mailman.eng.auburn.edu<mailto:veritas-bu-boun...@mailman.eng.auburn.edu>
>>> [mailto:veritas-bu-boun...@mailman.eng.auburn.edu<mailto:veritas-bu-boun...@mailman.eng.auburn.edu>]
>>>  On Behalf Of Martin,
>>> Jonathan
>>> Sent: Wednesday, May 26, 2010 1:08 PM
>>> To: Nate Sanders
>>> Cc: 
>>> VERITAS-BU@MAILMAN.ENG.AUBURN.EDU<mailto:VERITAS-BU@MAILMAN.ENG.AUBURN.EDU>
>>> Subject: Re: [Veritas-bu] LTO3 to LTO4 conversion
>>>
>>> Barcode rules are only used when injecting new media.  Your existing
>>> media will return to whatever pool they came from when they expire. If
>>> you don't want your old LTO3 media to be used anymore then change your
>>> media type for LTO4 to something different than what your LTO3 media
>>> use, and reconfigure your drives only to use that media type.
>>>
>>> I.e. - LTO3 media type hcart, LTO4 media type hcart1, drive type hcart1.
>>>
>>> NetBackup won't put an "hcart" media an "hcart1" drive.
>>>
>>> -Jonathan
>>>
>>> -----Original Message-----
>>> From: 
>>> veritas-bu-boun...@mailman.eng.auburn.edu<mailto:veritas-bu-boun...@mailman.eng.auburn.edu>
>>> [mailto:veritas-bu-boun...@mailman.eng.auburn.edu<mailto:veritas-bu-boun...@mailman.eng.auburn.edu>]
>>>  On Behalf Of Nate
>>> Sanders
>>> Sent: Wednesday, May 26, 2010 1:59 PM
>>> To: 
>>> judy_hinchcli...@administaff.com<mailto:judy_hinchcli...@administaff.com>
>>> Cc: 
>>> VERITAS-BU@MAILMAN.ENG.AUBURN.EDU<mailto:VERITAS-BU@MAILMAN.ENG.AUBURN.EDU>
>>> Subject: Re: [Veritas-bu] LTO3 to LTO4 conversion
>>>
>>> That tiny bit of information just answered tons of questions. Thank you!
>>>
>>> So now I know how to properly handle all new incoming LTO4 tapes. And
>>> ensure they wind up in the LTO4 scratch pool. In order to ensure LTO3s
>>> wind up in a "dead pool" for old tapes, do I simply enter "L3" as the
>>> barcode rule? And when are these rules actually processed? I know it's
>>> used when injecting new tapes, but what other situations does it apply
>>> these rules?
>>>
>>>
>>> On 05/26/2010 12:16 PM, 
>>> judy_hinchcli...@administaff.com<mailto:judy_hinchcli...@administaff.com> 
>>> wrote:
>>>
>>>     
>>>       
>>>> Bar code rules can be viewed....
>>>> Go to the gui and act like you are going to inject tapes into your
>>>>
>>>>       
>>>>         
>>> library
>>>
>>>     
>>>       
>>>> Choose the radio button for update volume configuration
>>>> This will then un-gray the advanced options
>>>> Click that button and you will see a screen where you configure the
>>>>
>>>>       
>>>>         
>>> barcode rules ( you should be able to find this in the volume manger
>>> manual)
>>>
>>>     
>>>       
>>>> Now the barcode rules are based on what it finds when it scans the
>>>>
>>>>       
>>>>         
>>> barcodes on the tapes.
>>>
>>>     
>>>       
>>>> If you lto3 tapes have a L3 in the barcode then you can make a rule
>>>>
>>>>       
>>>>         
>>> telling it
>>>
>>>     
>>>       
>>>> L3's go to  <old pool>
>>>>
>>>>
>>>>
>>>> Make your rules and put 1 l3 and 1 l4 in the map and inject the tapes,
>>>>
>>>>       
>>>>         
>>> then see if the tapes end up in the pools you want them to.
>>>
>>>     
>>>       
>>>> -----Original Message-----
>>>> From: 
>>>> veritas-bu-boun...@mailman.eng.auburn.edu<mailto:veritas-bu-boun...@mailman.eng.auburn.edu>
>>>>
>>>>       
>>>>         
>>> [mailto:veritas-bu-boun...@mailman.eng.auburn.edu<mailto:veritas-bu-boun...@mailman.eng.auburn.edu>]
>>>  On Behalf Of Nate
>>> Sanders
>>>
>>>     
>>>       
>>>> Sent: Wednesday, May 26, 2010 11:12 AM
>>>> To: 
>>>> VERITAS-BU@MAILMAN.ENG.AUBURN.EDU<mailto:VERITAS-BU@MAILMAN.ENG.AUBURN.EDU>
>>>> Subject: Re: [Veritas-bu] LTO3 to LTO4 conversion
>>>>
>>>> Getting ready to load in the new LTO4 tapes, but I'm still having a
>>>>
>>>>       
>>>>         
>>> hard
>>>
>>>     
>>>       
>>>> time planning the right way to do it. I assume I can make a new LTO4
>>>> scratch pool that will store all my initial blank media. I disable the
>>>> existing scratch pool and this will ensure that only new LTO4 tapes
>>>>
>>>>       
>>>>         
>>> are
>>>
>>>     
>>>       
>>>> rotated into my other pools. But how do I make sure the existing LTO3
>>>> tapes that expire are not put back into this new LTO4 scratch pool?
>>>> People keep mention barcode rules/labels but I've been unable to find
>>>> what this means or where to view/manage these. If I were to make new
>>>> duplicate LTO4 pools for my other volumes (production4, ndmp4,
>>>>
>>>>       
>>>>         
>>> offsite4,
>>>
>>>     
>>>       
>>>> etc) would this ensure none of the existing LTO3 tapes are reused?
>>>>
>>>> I've been digging through the Media Manager (5.1) Admin manual for a
>>>> better understanding of how NBU uses scratch/pools and expires tapes,
>>>> but nothing really seems to explain how it works, just how to manage
>>>> general tasks. If anyone can help answer my questions and also provide
>>>>
>>>>       
>>>>         
>>> a
>>>
>>>     
>>>       
>>>> better place for me to focus studying on I'd appreciate it.
>>>>
>>>> Thanks.
>>>>
>>>>
>>>> On 05/03/2010 10:23 AM, Nate Sanders wrote:
>>>>
>>>>
>>>>       
>>>>         
>>>>> Forgive me for what may be a straight forward question, but our last
>>>>> backup admin has left and I'm doing my best to step up and keep our
>>>>> systems moving along. I'm looking for a general outline of an LTO3 to
>>>>> LTO4 conversion with Netbackup 5.1 (upgrading is on the list, but we
>>>>> can't wait to complete it). Right now we still have some LTO2 tapes,
>>>>>
>>>>>         
>>>>>           
>>> and
>>>
>>>     
>>>       
>>>>> I believe I must migrate and/or eject and store these in order to
>>>>> complete the conversion. Are there any other gotchas or need to knows
>>>>>
>>>>>         
>>>>>           
>>> I
>>>
>>>     
>>>       
>>>>> must be aware of?
>>>>>
>>>>> Thank you much.
>>>>>
>>>>> P.S. New member to the list, working on getting scheduled for some
>>>>> on-line courses.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>         
>>>>>           
>>>     
>>>       
>> --
>> Nate Sanders            Digital Motorworks
>> System Administrator      (512) 692 - 1038
>>
>>
>>
>> This message and any attachments are intended only for the use of the 
>> addressee and may contain information that is privileged and confidential. 
>> If the reader of the message is not the intended recipient or an authorized 
>> representative of the intended recipient, you are hereby notified that any 
>> dissemination of this communication is strictly prohibited. If you have 
>> received this communication in error, please notify us immediately by e-mail 
>> and delete the message and any attachments from your system.
>> _______________________________________________
>> Veritas-bu maillist  -  
>> Veritas-bu@mailman.eng.auburn.edu<mailto:Veritas-bu@mailman.eng.auburn.edu>
>> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>>
>>
>>   
>>     
>
>   


-- 
Nate Sanders            Digital Motorworks
System Administrator      (512) 692 - 1038




This message and any attachments are intended only for the use of the addressee 
and may contain information that is privileged and confidential. If the reader 
of the message is not the intended recipient or an authorized representative of 
the intended recipient, you are hereby notified that any dissemination of this 
communication is strictly prohibited. If you have received this communication 
in error, please notify us immediately by e-mail and delete the message and any 
attachments from your system.
_______________________________________________
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu


_______________________________________________
Veritas-bu maillist  -  Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu

Reply via email to