I think this is a mistake. Media type (hcart, dlt, hcart2) etc is just a label - part of the media database. It exists per tape regardless of the backups on it. Volume Pool is what's usually assigned through backup creation. You can change the media type (via the vmchange) command regardless of assignment status. hcart, hcart2, etc. are just labels. Netbackup matches the media type of an individual tape to the storage unit type. It doesn't know that hcart2 is a superset of hcart1. It doesn't know hcart2 is anything, really, other than a label. To NB, hcart & hcart2 are as different as hcart & dlt - they're different media types and are therefore different tapes. I know that I can change the media type on an LTO1 tape from hcart to hcart2 and all of a sudden Netbackup will start reading and writing that tape in the LTO2 drives (since they're type is hcart2 in the storage unit definitions). Change it back to hcart1 and it'll only be read & written in LTO1 drives. I have to know that the two media types are backwards compatible and manage that myself. If you built an all new system and started with LTO4 tapes and called them hcart type, you'd be just fine as long as the media type on the storage units and the media types on the tapes themselves match. They should've called it "type1" and "type3" rather than anything that implied a physical type - it'd avoid this kind of confusion. -M
________________________________ From: [email protected] [mailto:[email protected]] On Behalf Of Marianne Van Den Berg Sent: Tuesday, May 05, 2009 2:07 PM To: [email protected] Subject: Re: [Veritas-bu] LTO4 recognized as DLT You should've changed media and drive type before doing backups. You can change drive type and media type of unassigned tapes, not once you've written backups to it. Throughput is determined by physical capabilities, not drive type in NBU config. -----Original Message----- From: sql_noob <[email protected]> Sent: 05 May 2009 21:48 To: [email protected] <[email protected]> Subject: [Veritas-bu] LTO4 recognized as DLT i just had the same thing happen to me on NB 6.5.3. we're still in the testing stage of a new HP MSL 8096 and NB 6.5.3 running on a HP x86 server on Windows 2003. the compatibility list says the robot is type TLD and it recognized it as such. all the tapes were recognized as DLT. we're getting very good perfomance, but long term we might connect an old autoloader to this to import old DLT tapes and i'm concerned this may be a problem. should I delete the robot and set it up again making sure it says HCART3? we're using LTO-4 drives and tapes +---------------------------------------------------------------------- |This was sent by [email protected] via Backup Central. |Forward SPAM to [email protected]. +---------------------------------------------------------------------- _______________________________________________ Veritas-bu maillist - [email protected] http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu This email has been scanned for viruses and malware, and automatically archived by Mimecast SA (Pty) Ltd, an innovator in Software as a Service (SaaS) for business. Mimecast Unified Email Management (tm) (UEM) offers email continuity, security, archiving and compliance with all current legislation. To find out more, contact StorTech <http://www.stortech.co.za/> . stormcid
_______________________________________________ Veritas-bu maillist - [email protected] http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
