- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- vgextend in MC/SG
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-13-2003 05:57 PM
02-13-2003 05:57 PM
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-13-2003 06:05 PM
02-13-2003 06:05 PM
Re: vgextend in MC/SG
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-13-2003 06:05 PM
02-13-2003 06:05 PM
SolutionYes. 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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-13-2003 06:08 PM
02-13-2003 06:08 PM
Re: vgextend in MC/SG
You are just extending the VG so no need to do mknode etc..
Cheers
rajeev
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-13-2003 06:11 PM
02-13-2003 06:11 PM
Re: vgextend in MC/SG
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-13-2003 06:15 PM
02-13-2003 06:15 PM
Re: vgextend in MC/SG
i should have thought of that silly point..
Any way thanks for correcting me
Rajeev
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-13-2003 06:15 PM
02-13-2003 06:15 PM
Re: vgextend in MC/SG
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-13-2003 06:17 PM
02-13-2003 06:17 PM
Re: vgextend in MC/SG
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-14-2003 05:57 PM
02-14-2003 05:57 PM
Re: vgextend in MC/SG
david