HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- exporting and importing volume groups
Operating System - HP-UX
1833325
Members
3128
Online
110051
Solutions
Forums
Categories
Company
Local Language
back
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
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
06-08-2007 12:27 PM
06-08-2007 12:27 PM
exporting and importing volume groups
Hi Mates,
I have a simple problem with exporting and importing volume groups uning HP lvm. Basically i am not quite familiar with the concept. My situation is, i have a LUN in Hitachi array where i have created a volume group /dev/vg02. Now using some data migration tool i copied the whole LUN into a HP-MSA array. Where, the copy was done at block level and all data using filesystem properties are copied. Once data migration is completed i want my HP-UX host to point to the newly migrated LUN in HP-MSA array and start using it. So how can i do this operation without having to create the physical volume again ? Thanks for the reply.
- NKD
I have a simple problem with exporting and importing volume groups uning HP lvm. Basically i am not quite familiar with the concept. My situation is, i have a LUN in Hitachi array where i have created a volume group /dev/vg02. Now using some data migration tool i copied the whole LUN into a HP-MSA array. Where, the copy was done at block level and all data using filesystem properties are copied. Once data migration is completed i want my HP-UX host to point to the newly migrated LUN in HP-MSA array and start using it. So how can i do this operation without having to create the physical volume again ? Thanks for the reply.
- NKD
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-08-2007 02:39 PM
06-08-2007 02:39 PM
Re: exporting and importing volume groups
It's actually fairly simple.
1) Identify the disk device associated with the copied LUN. If you have not done so already (and I assume that the host can access this new LUN at this point), issue an "ioscan -fn" followed by "insf". This will create the device nodes. I will pretend that the new LUN is /dev/dsk/c1t5d1.
2) If this new LUN and the original LUN are available to the same host then you should change the volume group ID of the copied LUN.
vgchgid /dev/rdsk/c1t5d1
3) Now you need to create a new directory and a group file. I'll pretend the new VG is /dev/vg05.
mkdir /dev/vg05
chmod 750 /dev/vg05
Now you need to find a unique value for the minor device number. Do an "ls -l /dev/vg*/group" and note the minor device numbers. By convention, vg05 should use 0x050000 where the 1st 2 hex digits correspond to the VG number but that is convention. An unused value so long as the first two hex digits are less than the kernel tunable maxvgs will work.
For our example,
mknod /dev/vg05/group c 64 0x050000
chmod 644 /dev/vg05/group
4) We are now ready to do the vgimport:
vgimport /dev/vg05 /dev/dsk/c1t5d1
5) Now we can activate the VG and backup the VG configuration.
vgchange -a y /dev/vg05
vgcfgbackup /dev/vg05
6) At this point, you have default lvol names, /dev/vg05/lvol1, lvol2, ...
7) vgdisplay -v /dev/vg05 to confirm that all is well.
8) You can now create mountpoints for the LVOL's, make /etc/fstab entries, and mount the filesystems.
1) Identify the disk device associated with the copied LUN. If you have not done so already (and I assume that the host can access this new LUN at this point), issue an "ioscan -fn" followed by "insf". This will create the device nodes. I will pretend that the new LUN is /dev/dsk/c1t5d1.
2) If this new LUN and the original LUN are available to the same host then you should change the volume group ID of the copied LUN.
vgchgid /dev/rdsk/c1t5d1
3) Now you need to create a new directory and a group file. I'll pretend the new VG is /dev/vg05.
mkdir /dev/vg05
chmod 750 /dev/vg05
Now you need to find a unique value for the minor device number. Do an "ls -l /dev/vg*/group" and note the minor device numbers. By convention, vg05 should use 0x050000 where the 1st 2 hex digits correspond to the VG number but that is convention. An unused value so long as the first two hex digits are less than the kernel tunable maxvgs will work.
For our example,
mknod /dev/vg05/group c 64 0x050000
chmod 644 /dev/vg05/group
4) We are now ready to do the vgimport:
vgimport /dev/vg05 /dev/dsk/c1t5d1
5) Now we can activate the VG and backup the VG configuration.
vgchange -a y /dev/vg05
vgcfgbackup /dev/vg05
6) At this point, you have default lvol names, /dev/vg05/lvol1, lvol2, ...
7) vgdisplay -v /dev/vg05 to confirm that all is well.
8) You can now create mountpoints for the LVOL's, make /etc/fstab entries, and mount the filesystems.
If it ain't broke, I can fix that.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP