- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- mounting VG on another system that already has sam...
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
04-11-2005 08:10 AM
04-11-2005 08:10 AM
How can I mount a volume group from one system to another system. The new system already has active volume group on it with same name. SOrt of like MCSG, but manually without software. i.e VG03 on server A needs to be mounted on VG03 on server B. Can I vgimport and change what VOLUME GROUP it will activate too? LIke to VG04?
Hope I explained myself correctly.
Thanks,
Charlie
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-11-2005 08:16 AM
04-11-2005 08:16 AM
Re: mounting VG on another system that already has same VG name
On second,
mkdir /dev/vgxx
mknod /dev/vgxx/group x 64 0x050000
(assuming vg05 monor number)
vgimport -v -m /mapfile /dev/vgxx
Activate and mount.
Anil
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-11-2005 08:27 AM
04-11-2005 08:27 AM
Re: mounting VG on another system that already has same VG name
vgchange -a n /dev/vg00
# use real vgname
to activate
vgchange -a y /dev/vg00
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-11-2005 08:30 AM
04-11-2005 08:30 AM
Re: mounting VG on another system that already has same VG name
Charlie
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-11-2005 08:48 AM
04-11-2005 08:48 AM
Re: mounting VG on another system that already has same VG name
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-11-2005 08:59 AM
04-11-2005 08:59 AM
Re: mounting VG on another system that already has same VG name
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-11-2005 05:03 PM
04-11-2005 05:03 PM
Re: mounting VG on another system that already has same VG name
Yes, you can import vg03 of serverA as vg04 on serverB.
Anil -
>Just make sure that you are using any exsisiting vg's minor number.
Correcttion - Just make sure you are not using any existing VG's minor number.
Deavtivate and Deportvg03 on serverA
After unmount file systems belonging to /dev/vg03 on serverA
#vgexport -v /dev/vg03
Procedure for importing remote VG :-
On Server B (Assuming disks are allready accessible on serverB and devices files for them is allready created)
#mkdir /dev/vg04
#cd /dev/vg04
#mknod group c 64 0x0?0000
?= Unique no. in this host ( Confirm by 'ls -l /dev/vg*/group' and use next available no. (0x000000,0x010000,0x020000...)
#vgimport /dev/vg04 /dev/dsk/cxtydz /dev/dsk/cx1ty1dz1 (Give address of all the disks of that vg as they are accessible on serverB)
#vgchange -a y /dev/vg01
You will find device files of all the logical volumes in /dev/vg03 of serverA, in /dev/vg04 of serverB and you can mount these on any desired mount points.
HTH,
Devender
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-11-2005 05:13 PM
04-11-2005 05:13 PM
Re: mounting VG on another system that already has same VG name
When you "vgexport" the Volume group is deleted and the information about the VG is removed from /etc/lvmtab and from the PV headers.
and the information is recreated in the new machine when you vgimport it.
Regards,
Naveej
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-12-2005 01:41 AM
04-12-2005 01:41 AM
Re: mounting VG on another system that already has same VG name
THanks,
Charlie
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-12-2005 01:53 AM
04-12-2005 01:53 AM
Re: mounting VG on another system that already has same VG name
Yes it is quite possible. Atlast it is same vgexport command you are using, options do not matter.
HTH,
Devender
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-12-2005 02:01 AM
04-12-2005 02:01 AM
Re: mounting VG on another system that already has same VG name
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-12-2005 02:16 AM
04-12-2005 02:16 AM
Re: mounting VG on another system that already has same VG name
Volume group name is not contained into the physical disk.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-12-2005 02:20 AM
04-12-2005 02:20 AM
Re: mounting VG on another system that already has same VG name
Here is example of pvdisplay on one of my disks.(luns)
pvdisplay /dev/dsk/c12t0d4
--- Physical volumes ---
PV Name /dev/dsk/c12t0d4
VG Name /dev/vg01
PV Status available
Allocatable yes
VGDA 2
Cur LV 1
PE Size (Mbytes) 8
Total PE 9598
Free PE 0
Allocated PE 9598
Stale PE 0
IO Timeout (Seconds) default
Autoswitch On
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-12-2005 02:31 AM
04-12-2005 02:31 AM
Re: mounting VG on another system that already has same VG name
Yes, it will display the vg name from the disk which contained it. But a VG can be accessed from two hosts , but only from one at a time. And even if you remove information from first host by not applying -p option then also it can be recreated back on the host when you want to access it from this host again.
But it is always required to remove information pertaining to that vg from your host where you do not want to use this. Otherwise on reboot this host will probe you warnings related to that vg.
HTH,
Devender
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-12-2005 02:32 AM
04-12-2005 02:32 AM
SolutionFor example - you have a backup server.
You have 3 hosts - SAN attached.
All have say /dev/vg10
Create map files on each server:
vgexport -p -s -v -m /tmp/vg10.`hostname`.map /dev/vg10
rcp those to the backup server.
On backup server:
mkdir /dev/vg10svr1
mkdir /dev/vg10svr2
mkdir /dev/vg10svr3
mknod /dev/vg10svr1/group c 64 0x0a0000
mknod /dev/vg10svr2/group c 64 0x0b0000
mknod /dev/vg10svr3/group c 64 0x0c0000
vgimport -s -v -m /tmp/vg10.server1.map /dev/vg10svr1
vgimport -s -v -m /tmp/vg10.server2.map /dev/vg10svr2
vgimport -s -v -m /tmp/vg10.server3.map /dev/vg10svr3
Create your mount points....
Then, umount file systems on each server, then vgchange -a n the vg's on those servers...
On backup server,
vgchange -a y /dev/vg10svr1
vgchange -a y /dev/vg10svr2
vgchange -a y /dev/vg10svr3
Then mount the file systems and back them up...
When done - umount, vgchange -a n them, and vgchange -a y and mount on the actual servers...
Rgds...Geoff