- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: vgimport and vgexport
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
Discussions
Discussions
Forums
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
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
тАО05-08-2013 04:20 AM
тАО05-08-2013 04:20 AM
vgimport and vgexport
Hi
I am doing vgexport
vgexport -v /dev/vgs01
Beginning the export process on Volume Group "/dev/vgs01".
/dev/dsk/c5t0d1
/dev/dsk/c7t0d1
vgexport: Volume group "/dev/vgs01" has been successfully removed.
after that ,
option 1:
I am importing with -s option and there is no error.
vgimport -v -s -m /tmp/mapfile2/vgs01.map /dev/vgs01
Beginning the import process on Volume Group "/dev/vgs01".
Logical volume "/dev/vgs01/lvol1" has been successfully created
with lv number 1.
Logical volume "/dev/vgs01/lvol2" has been successfully created
with lv number 2.
Logical volume "/dev/vgs01/lvol3" has been successfully created
with lv number 3.
Logical volume "/dev/vgs01/lvol4" has been successfully created
with lv number 4.
vgimport: Volume group "/dev/vgs01" has been successfully created.
------------------------------------------------------------------------
option 2:
I am importing with two disk path with refrence from vgexport output and i am getting warning error
vgimport -v -m /tmp/mapfile/vgs01.map /dev/vgs01 /dev/dsk/c5t0d1 /dev/dsk/c7t0d1
Beginning the import process on Volume Group "/dev/vgs01".
vgimport: Warning: Volume Group belongs to different CPU ID.
Can not determine if Volume Group is in use on another system. Continuing.
vgimport: Warning: Volume Group contains "1" PVs, "2" specified. Continuing.
option 3:
I am importing with one disk path with refrence from vgexport output and i am getting warning error
vgimport -v -m /tmp/mapfile/vgs01.map /dev/vgs01 /dev/dsk/c5t0d1
Beginning the import process on Volume Group "/dev/vgs01".
vgimport: Warning: Volume Group belongs to different CPU ID.
Can not determine if Volume Group is in use on another system. Continuing.
Logical volume "/dev/vgs01/lvol1" has been successfully created
with lv number 1.
Logical volume "/dev/vgs01/lvol2" has been successfully created
with lv number 2.
Logical volume "/dev/vgs01/lvol3" has been successfully created
with lv number 3.
Logical volume "/dev/vgs01/lvol4" has been successfully created
with lv number 4.
vgimport: Volume group "/dev/vgs01" has been successfully created.
Warning: A backup of this volume group may not exist on this machine.
Please remember to take a backup using the vgcfgbackup command after activating the volume group.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-08-2013 04:39 AM
тАО05-08-2013 04:39 AM
Re: vgimport and vgexport
By the way, if you want to use the map file, you should create it during vgexport.
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-08-2013 05:02 AM
тАО05-08-2013 05:02 AM
Re: vgimport and vgexport
Hi
when i am using -s option, There is no issue.
and when i am importing with disk path, i am getting error.
what is the reason.?
do my command in option 2 or 3 are wrong ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-08-2013 05:18 AM
тАО05-08-2013 05:18 AM
Re: vgimport and vgexport
Volume Group belongs to different CPU ID.
The system knows the VG was created on another system. It cannot say if this other system has still access, so this check is up to you.
In option 1 when using -s you already specify the VGID you want to import, hence no warning.
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-08-2013 06:44 AM
тАО05-08-2013 06:44 AM
Re: vgimport and vgexport
Did you actually run your 'vgexport' with the '-s' option? I didn't see that from your output.
My preferred 'vgexport' command line:
# vgexport -v -s -m /tmp/file.map /dev/vgwhatever
The importing you can just do:
# vgimport -v -s -m /tmp/file.map /dev/vgwhatever
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-08-2013 07:10 AM
тАО05-08-2013 07:10 AM
Re: vgimport and vgexport
hi
i have done the exported the vg with -s option
vgexport -p -s -v -m /tmp/vgxx.map /dev/vgxx
and then imported in secondary node with
vgimport -s -v -m /tmp/vgxx.map /dev/vgxx
and with other option 2 and 3
i have done the vgexport without -s option
vgexport -p -v -m /tmp/vgxx.map /dev/vgxx
and then imported in secondary node with disk path
vgimport -v -m /tmp/vgxx.map /dev/vgxx
but without using -s option ,, i am getting warning message.
disk is shared between two nodes that i am cureently doing vgexport and vgimport.
same disk is presented to two nodes.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-08-2013 07:30 AM
тАО05-08-2013 07:30 AM
Re: vgimport and vgexport
So your question is answered now?
Hope this helps!
Regards
Torsten.
__________________________________________________
There are only 10 types of people in the world -
those who understand binary, and those who don't.
__________________________________________________
No support by private messages. Please ask the forum!
If you feel this was helpful please click the KUDOS! thumb below!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-08-2013 07:36 PM
тАО05-08-2013 07:36 PM
Re: vgimport and vgexport
As said, the VGID is the key.
but still when i am able to do with -s option without any warning in v2.
why can't i import with disk path without any warning in v3.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-12-2013 11:37 PM
тАО05-12-2013 11:37 PM
Re: vgimport and vgexport
Hi all,
In option 3 the warning is that to take vgcfgbackup, this is general warning message. This can be neglected, but vgcfgbackup need to be performed.
In option 2 the error is ddue to one of the device file is not presented in that node, that's why on exclude the unwanted device vgimport has happened successfully in the option 3.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-12-2013 11:39 PM
тАО05-12-2013 11:39 PM
Re: vgimport and vgexport
the error in option 2 "vgimport: Warning: Volume Group contains "1" PVs, "2" specified. Continuing." clearly specifies .