Media type on tapes and volume group mismatch

[capasun]

Hello everyone,

I changed media type on all tapes of a certain type, but the volume group kept the old media type and I don't have a new volume group with the new one.

Plaese, how can i fix that?

Thanks in advance,

Dng

[Mark_Solutions]

Not quite sure what you mean here .. a volume group usually refers to tapes in or out of the library or a Vault group .. but that relates to teh tapes residence rather than media type and is generated automatically as tapes go into and out of the library.

But if you change tape type .. from hcart2 to hcart3 for example you may need to change your tape drives and storage units to match

You may also need to move all tapes to standalone and then re-inventory the library to get everything straight

Maybe some screenshots to help us understand better where your problem lies

[mph999]

There will be a different volume group for each typ[e of media

So if you have hcart and hcart2, there should be two volume groups, but the volume group does not show 'which' density.

If you have 1 media density type in the robot (eg hcart) you will have one volume group

If you change the media to hcart3 (for example) you will still only have one volume group ...

No matter, if you think it is still wrong, move all the media to standalone.  THe media will move to vol group --- and the other volue group should disappear, then re-inventory the robot.

[capasun]

Sorry. I'll try to explain better:

We have two media density type and a robot.

Before I made the change, in Netbackup we had two media type: HCART and 8MM.
Than we had two volume group: 000_00002_TLD and 002_00002_TLD.

I changed media type from 8MM to HCART2, but volume groups obviously are not changed.
Now there's no volume group associated to HCART2 media type.

Maybe adding a new media as HCART2 will generate a new volume group, but i can move media from a volume group to another?

Many thanks

Dng

[Mark_Solutions]

Why do you want to move media between volume groups?

They are system generated things and of little relevance other than use with the Vault option.

They just come into play when tapes go into and out of the library

There should be nothing you need to do manually with volume groups

[mph999]

Here is one of my media

media ID:              E03020
media type:            1/2" cartridge tape (6)
barcode:               E03020L4
media description:     Added by Media Manager
volume pool:           Scratch (4)
robot type:            TLD - Tape Library DLT (8)
robot number:          0
robot slot:            20
robot control host:    nbmaster1
volume group:          000_00000_TLD
 

I now moved all the media in this vol group to a different density

media ID:              E03020
media type:            1/2" cartridge tape 3 (24)
barcode:               E03020L4
media description:     Added by Media Manager
volume pool:           Scratch (4)
robot type:            TLD - Tape Library DLT (8)
robot number:          0
robot slot:            20
robot control host:    nbmaster1
volume group:          000_00000_TLD
 

As you see, the vol group stays the same.

I then moved one media only to hcart (previously unused)

This time it stayed in vol group 000_00000_TLD

media ID:              E03003
media type:            1/2" cartridge tape (6)
barcode:               E03003L4
media description:     Added by Media Manager
volume pool:           Scratch (4)
robot type:            TLD - Tape Library DLT (8)
robot number:          0
robot slot:            3
robot control host:    nbmaster1
volume group:          000_00000_TLD
 

I made this tape non-robotic, and then ran an inventory

It went back into volume group 000_00000_TLD ...  - so yes, that seems incorrect.

Only way I could 'fix' it was to move ALL the media to standalone, and then re-inventory.

I then ended up with 3 volume groups, one for each density of media (I had hcart hcart2 and hcart3)

[root@nbmaster1 bin]# vmquery -a |grep group |sort -u
volume group:          000_00000_TLD
volume group:          000_00001_TLD
volume group:          001_00000_TLD
 

So yes, I agree, it doesn't quite behave itself, but is easily resolve by moving all media (I had to move from both robots) to standalone and then re-inventory.