- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: vgexport and vgimport problem
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
тАО10-11-2002 07:45 AM
тАО10-11-2002 07:45 AM
i have two hp servers accessing auto raid 12H E-disk array. there i have two luns in a volume group. i have many logical volumes and raw devices in that volume group. the problem is the vg was active on machine A. i wanted it on machine B. by accident i did a vgexport on A with out creating map file. now vg is not available on both the machines. i tried vgimport on machine B but no use. can any body tell me how to come out of this problem.
thanks in advance
ravi
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-11-2002 07:48 AM
тАО10-11-2002 07:48 AM
Re: vgexport and vgimport problem
You can try just using a vgimport without a map file , it should come up with the lvols provide all the disks are the same . ie
do vgimport /dev/vgnew /dev/dsk/cxtydz /dev/dsk/cx1ty1dz1 and so on , this would bring back the logical volumes w/o any problem.
Manoj Srivastava
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-11-2002 07:49 AM
тАО10-11-2002 07:49 AM
Re: vgexport and vgimport problem
i tried that but lvols names are changed it is giving lvol1, lvol2 and so on, instead of orginal names.
regds
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-11-2002 07:51 AM
тАО10-11-2002 07:51 AM
Re: vgexport and vgimport problem
dcsux100 > cat /tmp/vgDCS6DB.map
1 lvol1
2 lvol2
3 lvol3
4 lvol4
5 lvol5
6 lvol6
7 lvol7
8 lvol8
9 lvol9
10 lvol10
11 lvol11
12 lvol12
13 lvol13
14 lvol14
15 lvol15
16 lvol16
17 lvol17
18 lvol18
use the -f file for a list of physical disk devices (in order). Preferable if there are too many disks devices to specify on 1 command line. Both of these files can be generated by a vgdisplay -v of the previous VG on the previous system which of course you do at a regular interval (try sysinfo script from the porting centre or print_manifest from ignite if you do not!)
Share and Enjoy! Ian
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-11-2002 07:53 AM
тАО10-11-2002 07:53 AM
Re: vgexport and vgimport problem
The mapfiles associated with volume group exports and imports are a convienence only.
If you use the default, standard names for logical volumes with volume groups, then the mapfile is superflous, since the logical volume names will be 'lvol1, lvol2', etc.
Otherwise, you can create a mapfile after the fact for use with the 'vgimport'; for example:
1 mylvol1name
2 mylvol2name
Regards!
...JRF...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-11-2002 07:54 AM
тАО10-11-2002 07:54 AM
SolutionThe naming of the lvols will be lost but you will habve all the data.
Next when you do a vgexport -m -m mapfile you can then edit the mapfile and put back in any custom vgnames for the vgimport on Machine B.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-11-2002 07:56 AM
тАО10-11-2002 07:56 AM
Re: vgexport and vgimport problem
Remember that after the 'vgimport' you will need to activate the volume group:
# vgchange -a y /dev/vgXX
Regards!
...JRF...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-11-2002 07:56 AM
тАО10-11-2002 07:56 AM
Re: vgexport and vgimport problem
1 lvol1
2 lvol2
3 lvol3
and so on. BUT if you use "-s" in your vgexport it'll include the VGID in the first line ..
VGID 77612e103c1a5e96
1 lvol1
2 lvol2
3 lvol3
So I need to know if you'd used "-s" or not in your vgexport. If not and if you know all the names of the lvols you can manually create the mapfile and try the vgimport with that map file. You must have had backup of your LVM config to determine those LVs names.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-11-2002 07:56 AM
тАО10-11-2002 07:56 AM
Re: vgexport and vgimport problem
mount /dev/vgnew/lvol1 /test1
now the issues is which lvol on which mount point , what i suggest you is to look inot /etc/fstab of the old server and check what lvols where mounted on which mount points , and then mount them coresspondingly .
Incase you cannot get the names of the mount poijnts then u need to mount on some test directory check the contents and remount using the correct names .
You would need to a fsck -y /dev/vgnew/rl* to make the lvols mountable .
Essentially the map file ahs the list of lvols the old volume group was supoos to have .
Also please doa vgcfgback after you get the stuff up.
Manoj Srivastava
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-11-2002 07:57 AM
тАО10-11-2002 07:57 AM
Re: vgexport and vgimport problem
iam using mknod on machine A as u suggested to create group. after iam trying vgimport with pv paths, but it is saying can not open control file /dev/vgtst/group , no such device.
what to do?
regds