1833847 Members
1928 Online
110063 Solutions
New Discussion

Re: vgextend in MC/SG

 
SOLVED
Go to solution
Ian lee
Advisor

vgextend in MC/SG

I have a two-node MC/SG cluster,use a AutoRAID 12H model disk array with 4 disks 2LUN,only one of LUN in use,now I wanna to extend the vg,how to do that?Should I do vgextend in one node,and then do vgimport in the other node?
8 REPLIES 8
Rajeev  Shukla
Honored Contributor

Re: vgextend in MC/SG

Hi,
Thats right you first do vgextend in the active machine(where the vg is active) and then create a map file by doing
vgimport -s -p -v -m vg.map vgname

copy this map file to another node and the do vgimport using this map file.

vgimport -m vg.map -v -s vgname

Cheers
Rajeev
John Poff
Honored Contributor
Solution

Re: vgextend in MC/SG

Hi,

Yes. You've got it right. Do your 'vgextend' on the first node, and then do a 'vgexport' on that node using the shared option. Write a map file and copy it to the second node.

Then on your second node you'll have to do a 'vgexport', mkdir your /dev/vg_name and do a 'mknod' for the group file, and then vgimport. Be sure to use the shared options for vgimport and use your map file. Then you should be in business.

JP
Rajeev  Shukla
Honored Contributor

Re: vgextend in MC/SG

Hi, you dont need to recreate the /dev/vgname and do mknode because you already have that vg in service gurard and i presume you already have that vg imported in other node at the time of cluster setup.
You are just extending the VG so no need to do mknode etc..

Cheers
rajeev
John Poff
Honored Contributor

Re: vgextend in MC/SG

Hi Rajeev,

He can't do the vgimport on the second node if the volume group already exists, right? If I'm not mistaken I think 'vgimport' will complain about the VG already being on the second node. That's why he'll have to vgexport it first and recreate it with the vgimport.

JP
Rajeev  Shukla
Honored Contributor

Re: vgextend in MC/SG

Sorry John Proff for that...
i should have thought of that silly point..
Any way thanks for correcting me

Rajeev
Ian Kidd_1
Trusted Contributor

Re: vgextend in MC/SG

I think you'll have to recreate the /dev/vgname and do mknode on the second node because you're going to vgexport the volume group before vgimport'ing it.

Refer to doc ID UXSGLVKBAN00000002 for a step-by-step breakdown
http://www1.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000064900203
If at first you don't succeed, go to the ITRC
John Poff
Honored Contributor

Re: vgextend in MC/SG

Rajeev,

Don't worry about it. I had to think about it for a minute too. I only know it will complain because I've seen that message quite a few times. For about the first ten times I did that procedure I always forgot about the vgexport, and I was kindly reminded by vgimport. :)

JP
Ian lee
Advisor

Re: vgextend in MC/SG

Hi all,thanks,now I know how to do,and thanks angain!

david