- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: LVM command just for clarification of BCV impo...
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
тАО09-09-2004 08:42 AM
тАО09-09-2004 08:42 AM
Re: LVM command just for clarification of BCV import
1. If hostB can "see" both the STD and BCV devices you will need to run vgchgid on each BCV device, then specify each of those devices on the vgimport line (without -s). Otherwise hostB might import the BCV devices, the STD devices, or a combination.
Note: As you are probably aware you must specify all devices on the same vgchgid line for it to work correctly. Example: vgchgid /dev/rdsk/c3t1d1 /dev/rdsk/c3t1d4. Not vgchgid /dev/rdsk/c3t1d1; vgchgid /dev/rdsk/c3t1d4
2. If hostB can only "see" the BCV devices you should be able to use 'vgexport -s -v -m vgoradata1.map -p /dev/vgoradata1' on hostA; copy vgoradata1.map to hostB; run 'vgimport -s -v -m vgoradata1.map /dev/vgoradata1' on hostB. If vgchgid has been run on any of the BCV devices you are out of luck using the shared (-s) option.
The error messages you are getting of concern;
Logical Volume is not defined on any physical volumes
It almost sounds like its the wrong map file for the devices. I think you might get this message if a volume group was imported and had 2 LVs defined, but you used a mapfile with 4 LVs specified. Just a thought.
David
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-09-2004 08:43 AM
тАО09-09-2004 08:43 AM
Re: LVM command just for clarification of BCV import
VGID is just how kernels running in the individual nodes refer the volume group.
You would need to execute vgchgid if the source and BCV copies are to be mounted in the SAME node. In this case, since the VGID will be same in both the source and BCV snapshots, you need to change the VGID on the BCV snapshots before you can mount them. This is primarily becoz kernel will not allow two volume groups with the same VGID be activated.
But if your BCV snapshots are going to be mounted on a different node, then you dont need to execute vgchgid.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-09-2004 08:55 AM
тАО09-09-2004 08:55 AM
Re: LVM command just for clarification of BCV import
HostB has the BCVs which is where Im tryin to mount them. HostB cannot see the STD devices on HostA.
I know all of the BCV disks via my Syminq output from EMC... so I do know the BCVS if I need to specify them.
However, one thing I didnt mention is that I may need to resync the BCVs on HostB with the STD devices on HostA...
I think that may be my basic problem.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-09-2004 09:03 AM
тАО09-09-2004 09:03 AM
Re: LVM command just for clarification of BCV import
I think the error messages seem to make sense to me :-). Sync up BCV with STD, you should be good to go.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-09-2004 09:05 AM
тАО09-09-2004 09:05 AM
Re: LVM command just for clarification of BCV import
I talked with my DBA and he is goin to do that establish and let me know.
I probably blew away the disk header when I mounted them as FS.
So check back tomorrow same Bat channel!!! for the exciting conclusion!!!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-09-2004 09:47 AM
тАО09-09-2004 09:47 AM
Re: LVM command just for clarification of BCV import
We do this scenario just about twice a week.
When finished with the BCV's and want to resync
On host that has the BCV's mounted
Unmount all valids filesystems
deactivate the volume groups
# vgchange -a n /dev/myvg
Remove the volumes
# vgexport /myvg
# rm -rf /dev/myvg
Go to the system that does your symcli commands and start your resync, hopefully you are using device groups, otherwise it is very difficult.
e.g
# symmir -g mygrp -noprompt establish
Once the volumes are sync'ed you can then split them off again ready for the host to use them.
# symmir -g mygrp query (to check synching progress)
# symmir -g mygrp -instant -noprompt split
Go to intended host
# mkdir /dev/mygrp
# mknod /dev/mygrp/group c 64 0x090000
# vgchgid `cat mygrp_rdsk` (list of LUN devices on a single line e.g. /dev/rdsk/c10t2d0 /dev/rdsk/c10t2d1 ...) This changes the VGID to the current system
# vgimport -v -m mygrp.mapfile -p /dev/mygrp `cat mygrp_dsk` (list of devices on a single line like before e.g. /dev/dsk/c10t2d0 /dev/dsk/c10t2d1 ...)
This was the preview, if all okay drop the preview option.
# vgimport -v -m mygrp.mapfile /dev/mygrp `cat mygrp_dsk`
After a successful import you can then mount your filesystems. You may still need to run an fcsk on each logical volume prior to mounting.
HTH
Michael
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-10-2004 03:13 AM
тАО09-10-2004 03:13 AM
Re: LVM command just for clarification of BCV import
I think since I had mistakenly used the BCVS as real FS... I blew away the disk header.
My DBA re-established the BCVs with the STD devices.
Here is my output from my import command.
# vgimport -s -v -m vgoradata.mapfile.todd /dev/vgoradata
Beginning the import process on Volume Group "/dev/vgoradata".
Logical volume "/dev/vgoradata/fs01" has been successfully created
with lv number 1.
Logical volume "/dev/vgoradata/fs02" has been successfully created
with lv number 2.
Volume group "/dev/vgoradata" has been successfully created.
chdcfas1-root:/root/LVMcommands/BCVmounts
# vgchange -a y /dev/vgoradata
Activated volume group
Volume group "/dev/vgoradata" has been successfully changed.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-10-2004 03:25 AM
тАО09-10-2004 03:25 AM
Re: LVM command just for clarification of BCV import
As usual I made it harder than it should have.
- « Previous
-
- 1
- 2
- Next »