- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: 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-22-2009 04:30 AM
тАО05-22-2009 04:30 AM
# vgexport -v -m /tmp/dboracl.map dboracle_vg
then
need to create dir
#mkdir /dev/dboraclenew
#mknod /dev/dboraclenew c 64
then
#vgimport -v -m /tmp/dboracle.map dboraclenew
then we nee to activate the vg..
here my Question starts:
we are copying the information of vg dboracle_vg to /tmp/dboracle.map while vgexport.
so if we vgimport the same information will be there in the file right( i mean to say, teh information about failed path will be there right) then how it will work.,......
thanks in Advance
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-22-2009 04:37 AM
тАО05-22-2009 04:37 AM
Re: vgexport
You should also add more pathes as alternate paths either on the same vgimport command or later with vgextend.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-22-2009 04:42 AM
тАО05-22-2009 04:42 AM
Re: vgexport
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-22-2009 04:50 AM
тАО05-22-2009 04:50 AM
Re: vgexport
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-22-2009 05:06 AM
тАО05-22-2009 05:06 AM
Solution>>>You mean to say the map file will not contain the information about the failed path.....<<<<
Yep. You are right. There are few options you can specify with vgexport. If you specify only -m, map file will contain only the logical volume names. With this map file, you need to specify the all the physical paths with vgimport command when you import it.
Example:
#vgexport -p -v -m /tmp/vg01.map vg01
Result map will looks like this..
/# more /tmp/vg01.map
1 lvol1
2 lvol2
3 lvol3
4 lvol4
5 lvol7
6 lvol8
7 lvol9
8 lvol10
5 lvol5
6 lvol6
#vgimport -v -m /tmp/vg01.map vg01 pvpath1 pvpath2 ...
There is another option -s . If you specify -s with vgexport VGID will be included in the map file. With this map file, you don't need to specify the disks when you import. System will scan all the disks which contains the VGID and import it.
#vgexport -p -v -s -m /tmp/vg01.map vg01
#more /tmp/vg01.map
VGID 286ef1244162b5ce
1 lvol1
2 lvol2
3 lvol3
4 lvol4
5 lvol7
6 lvol8
7 lvol9
8 lvol10
5 lvol5
6 lvol6
Second option is the preferred way. It will import with all the paths. If not you can add all the paths later on with vgextend.
Ganesh.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-22-2009 05:15 AM
тАО05-22-2009 05:15 AM
Re: vgexport
There is another option with vgexport which is -f. If you specify -f with vgexport, it will write current set of the pv paths in output file. You can use the same file or modify the output with correct path and import it.
Example:
# vgexport -p -v -f /tmp/vg01.out vg01
# more /tmp/vg01.out
/dev/dsk/c33t4d1
/dev/dsk/c31t4d1
#
#vgimport -v -f /tmp/vg01.out vg01
You can use any of the above options depends on your convenient and import it.
Ganesh.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-22-2009 05:31 AM
тАО05-22-2009 05:31 AM
Re: vgexport
Once the new path is part of the VG, you could try vgreducing the bad path out of the VG.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-22-2009 05:47 AM
тАО05-22-2009 05:47 AM
Re: vgexport
Whether it will work, if only one path added , if it goes down dirctly adding the other path?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-22-2009 05:57 AM
тАО05-22-2009 05:57 AM
Re: vgexport
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-22-2009 06:01 AM
тАО05-22-2009 06:01 AM