- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- vgexport / 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
тАО02-07-2008 09:02 AM
тАО02-07-2008 09:02 AM
vgexport / vgimport
We are using SGeRAC for Oracle. The storage is configured with SLVM and shared by two nodes.
I need to create a new raw partition (LV).
I realized that I can't create a new LV by using SAM. Instead, I will run following command from node1;
# lvcreate -n SYSFILE2 -L 500 /dev/vg_rac
If this works, I think, the next thing I have to do is that export the volume group configuration of the volume group vg_rac by using vgexport and import it on node2 by vgimport.
My question is that, should I have to export&import the whole volume group information to add just one new LV info?
I worry that if it would affect to the current configuration on node2. Do I not need to worry about it?
Thanks in advance,
Seungjun
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-07-2008 11:43 AM
тАО02-07-2008 11:43 AM
Re: vgexport / vgimport
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-07-2008 03:25 PM
тАО02-07-2008 03:25 PM
Re: vgexport / vgimport
RE: "...If this works, I think, the next thing I have to do is that export the volume group configuration of the volume group vg_rac by using vgexport and import it on node2 by vgimport.
My question is that, should I have to export&import the whole volume group information to add just one new LV info?..."
Absolutely correct. Vgexport the VG into a map file, ftp the map file over to node2, vgimport the new map file.
vgexport -m vg_rac.map /dev/vg_rac
ftp vg_rac.map over to node2
vgimport -s -p -m mapfile /dev/vg_rac (* -p to preview *)
vgimport -s -m mapfile /dev/vg_rac (* when ready *)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-08-2008 12:10 AM
тАО02-08-2008 12:10 AM
Re: vgexport / vgimport
Also, if vg_rac already exists on the other machine, you'll have to export it there first (without the preview option) before you can import it again through the map file.
node1# vgexport -pvs -m /tmp/vgrac.map /dev/vg_rac
node2# ls -l /dev/vg_rac/group
node2# vgexport -v /dev/vg_rac
node2# mkdir /dev/vg_rac
node2# mknod /dev/vg_rac/group c 64
node2# vgimport -vs -m
Cheers,
Wout
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-08-2008 12:33 AM
тАО02-08-2008 12:33 AM