- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: vgexport and vgimport
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
тАО11-01-2010 09:27 AM
тАО11-01-2010 09:27 AM
vgexport and vgimport
can i have with an example
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-01-2010 09:38 AM
тАО11-01-2010 09:38 AM
Re: vgexport and vgimport
You use 'vgexport' and 'vgimport' to (1) move LVM volume groups from one server to another; (2) to rename a volume group; (3) to copy volume group information from one server to another in a cluster (e.g. under Serviceguard); and (4) to remove a volume group from a server ('vgexport' without any subsequent 'vgimport').
The manpages for each command provide examples and more information.
Regards!
...JRF...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-01-2010 10:33 AM
тАО11-01-2010 10:33 AM
Re: vgexport and vgimport
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-01-2010 08:37 PM
тАО11-01-2010 08:37 PM
Re: vgexport and vgimport
"also we use vgexport to take configuration backup of a vg (in the form of a map file), so that in the event of a failure we can recreate the vg from that backup"
I am confused. Could you please explain it ?
Regards,
Sooraj
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-01-2010 08:43 PM
тАО11-01-2010 08:43 PM
Re: vgexport and vgimport
(11.31)
/usr/sbin/vgexport [-m mapfile] [-p] [-v] [-f outfile] vg_name
Using the format of the above command line the vgexport command can be used to remove a volume group from the system.
The volume group will be removed without modifying the logical volume information found on the physical volumes.
The volume group identified by vg_name is removed from the /etc/lvmtab
or /etc/lvmtab_p file, and the associated device files including the
vg_name directory and group file are removed from the system.
The volume group information and data is untouched on the physical volume.These disks can be imported to another system with the
vgimport command
/usr/sbin/vgexport -m mapfile -s [-p] [-v] vg_name
Using the format of the above command line,
vgexport command generates a mapfile that can be copied to other
systems that are part of a high availability cluster (use the -p
option if you do not want to remove the volume group from the system
the command is being run from) and the vgimport command (see
vgimport(1M)) can be used to recreate the volume group. See also
vgchange(1M). The mapfile contains a description of the volume group
and its associated logical volume(s) (if any). The logical volume
information found on the physical volumes is not modified.
Regards,
Sooraj
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-01-2010 09:53 PM
тАО11-01-2010 09:53 PM
Re: vgexport and vgimport
i was talking about the second one you mentioned:
/usr/sbin/vgexport -p -v -s -m mapfile vg_name
using this, we get the mapfile and the vg will not be removed from system.
If later on, while working on this vg, if it is removed using vgexport or like that, then using the existing mapfile we can regenerate the vg by vgimport:
/usr/sbin/vgimport -v -s -m mapfile vg_name
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-01-2010 11:10 PM
тАО11-01-2010 11:10 PM
Re: vgexport and vgimport
Thank you verymuch for the reply.
==>to take configuration backup of a vg (in the form of a map file),
The command used for this is vgcfgbackup.
vgimport will take the configuration from disks only , not for the mapfile.
in case of vgexport, map file is only used to save the "VGID" so that it can search for the disks which is having same VGID. it saves the name of the LV also.
you can import a VG with data without help of any mapfile.. all you need is disks.
Regards,
Sooraj
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-01-2010 11:50 PM
тАО11-01-2010 11:50 PM
Re: vgexport and vgimport
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-01-2010 11:59 PM
тАО11-01-2010 11:59 PM
Re: vgexport and vgimport
http://bizsupport1.austin.hp.com/bc/docs/support/SupportManual/c02023734/c02023734.pdf
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-02-2010 10:12 AM
тАО11-02-2010 10:12 AM