- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- vgimport -f
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
тАО08-29-2008 03:01 PM
тАО08-29-2008 03:01 PM
vgexport -m -v /tmp/vgname.map -f /tmp/vgname.outfile /dev/vgname
then on a different node use vgimport -v -m /tmp/vgname.map -f /tmp/vgname.outfile /ev/vgname
rather than using vgexport -s -v -m and vgimport -s -v -m
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-29-2008 03:05 PM
тАО08-29-2008 03:05 PM
SolutionYou could, with the likely assumption that you would edit your "vgname.outfile" device names to match those on the node where you do the 'vgimport'.
Why, bother, though, when the '-s' switch was designed for this kind situation?
Regards!
...JRF...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-29-2008 03:09 PM
тАО08-29-2008 03:09 PM
Re: vgimport -f
thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-29-2008 05:14 PM
тАО08-29-2008 05:14 PM
Re: vgimport -f
vgexport -m -v /tmp/vgname.map -f /tmp/vgname.outfile /dev/vgname>>
yes, you can use it.
-f outfile Write the current set of pv_paths for the volume
group to the outfile. The outfile may then be
used as the infile for the vgimport -f option. If
used together with the -p option the volume group
is not exported but the list of pv_paths is still
written to the outfile. This may be useful to
derive a list of pv_paths for the volume group or
to use on another system which is sharing the
volume group and which has an identical
configuration.
We are also using for vgs with large disks set.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-29-2008 08:37 PM
тАО08-29-2008 08:37 PM