- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: need help to migrate info
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
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
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
01-05-2015 05:50 AM
01-05-2015 05:50 AM
need help to migrate info
I have an HP-UX box running 11.23 and I need to move all of our existing data to a new storage, below is our current LVM info:
--- Volume groups ---
VG Name /dev/vg01
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 6
Open LV 6
Max PV 16
Cur PV 1
Act PV 1
Max PE per PV 35002
VGDA 2
PE Size (Mbytes) 8
Total PE 34998
Alloc PE 22912
Free PE 12086
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0
--- Logical volumes ---
LV Name /dev/vg01/lvol1
LV Status available/syncd
LV Size (Mbytes) 137216
Current LE 17152
Allocated PE 17152
Used PV 1
LV Name /dev/vg01/lvol2
LV Status available/syncd
LV Size (Mbytes) 4096
Current LE 512
Allocated PE 512
Used PV 1
LV Name /dev/vg01/lvol3
LV Status available/syncd
LV Size (Mbytes) 30720
Current LE 3840
Allocated PE 3840
Used PV 1
LV Name /dev/vg01/lvhome
LV Status available/syncd
LV Size (Mbytes) 2048
Current LE 256
Allocated PE 256
Used PV 1
LV Name /dev/vg01/lvol5
LV Status available/syncd
LV Size (Mbytes) 1024
Current LE 128
Allocated PE 128
Used PV 1
LV Name /dev/vg01/lvtempo
LV Status available/syncd
LV Size (Mbytes) 8192
Current LE 1024
Allocated PE 1024
Used PV 1
--- Physical volumes ---
PV Name /dev/dsk/c3t0d1
PV Name /dev/dsk/c4t0d1 Alternate Link
PV Name /dev/dsk/c5t0d0 Alternate Link
PV Status available
Total PE 34998
Free PE 12086
Autoswitch On
Proactive Polling On
VG Name /dev/vg00
VG Write Access read/write
VG Status available
Max LV 255
Cur LV 9
Open LV 9
Max PV 16
Cur PV 1
Act PV 1
Max PE per PV 4216
VGDA 2
PE Size (Mbytes) 8
Total PE 4206
Alloc PE 4206
Free PE 0
Total PVG 0
Total Spare PVs 0
Total Spare PVs in use 0
--- Logical volumes ---
LV Name /dev/vg00/lvol1
LV Status available/syncd
LV Size (Mbytes) 304
Current LE 38
Allocated PE 38
Used PV 1
LV Name /dev/vg00/lvol2
LV Status available/syncd
LV Size (Mbytes) 9216
Current LE 1152
Allocated PE 1152
Used PV 1
LV Name /dev/vg00/lvol3
LV Status available/syncd
LV Size (Mbytes) 536
Current LE 67
Allocated PE 67
Used PV 1
LV Name /dev/vg00/lvol4
LV Status available/syncd
LV Size (Mbytes) 56
Current LE 7
Allocated PE 7
Used PV 1
LV Name /dev/vg00/lvol5
LV Status available/syncd
LV Size (Mbytes) 7000
Current LE 875
Allocated PE 875
Used PV 1
LV Name /dev/vg00/lvol6
LV Status available/syncd
LV Size (Mbytes) 200
Current LE 25
Allocated PE 25
Used PV 1
LV Name /dev/vg00/lvol7
LV Status available/syncd
LV Size (Mbytes) 5832
Current LE 729
Allocated PE 729
Used PV 1
LV Name /dev/vg00/lvol8
LV Status available/syncd
LV Size (Mbytes) 4360
Current LE 545
Allocated PE 545
Used PV 1
LV Name /dev/vg00/lvol9
LV Status available/syncd
LV Size (Mbytes) 6144
Current LE 768
Allocated PE 768
Used PV 1
--- Physical volumes ---
PV Name /dev/dsk/c7t0d0s2
PV Status available
Total PE 4206
Free PE 0
Autoswitch On
Proactive Polling On
Mirro-UX is installed, for vg01 do I have to present a single LUN that is as large as /dev/dsk/c3t0d1 and it will be mirroring automatically? what about vg00? what would be the procedure to migrate the existing data to our new storage and then remove the LUNs from the old storage?
Thanks
- Tags:
- LVM mirror ux
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-05-2015 07:23 AM
01-05-2015 07:23 AM
Re: need help to migrate info
There's a lot of missing information here.
model of the computer?
What is the new storage (interface, SAN details, array models, etc)?
Is Mirror/UX installed?
Currently, none of the disks are mirrored at all.
Is vg00 using an internal disk?
For your new storage, do you know if your interface card and the disk storage will support booting from HP-UX?
For vg01, the steps are fairly simple as long as the storage is compatible.
vg00 requires a large number of commands to allow bootup to succeed.
Bill Hassell, sysadmin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-05-2015 07:28 AM
01-05-2015 07:28 AM
Re: need help to migrate info
The machine is a rx3600.
The new storage is a VNX (FiberChannel interface) and current storage is FC as well.
MirrorUX is installed.
The reason the disks are not mirrored is probably because its a large LUN thats already mirrored @ storage level.
vg00 is using /dev/dsk/c7t0d0s2 which ioscan shows as an IR Volume volume so I assume its internal yes.
Class I H/W Path Driver S/W State H/W Type Description
====================================================================================
disk 0 0/0/2/1.0.16.0.0 sdisk CLAIMED DEVICE TEAC DV-28E-N
/dev/dsk/c0t0d0 /dev/rdsk/c0t0d0
disk 1 0/3/1/0/4/0.1.1.0.0.0.1 sdisk CLAIMED DEVICE HP MSA VOLUME
/dev/dsk/c3t0d1 /dev/rdsk/c3t0d1
disk 4 0/3/1/0/4/0.1.1.255.0.0.1 sdisk CLAIMED DEVICE HP MSA VOLUME
/dev/dsk/c4t0d1 /dev/rdsk/c4t0d1
disk 3 0/4/1/0.0.0.0.0 sdisk CLAIMED DEVICE HP IR Volume
/dev/dsk/c7t0d0 /dev/dsk/c7t0d0s1 /dev/dsk/c7t0d0s2 /dev/dsk/c7t0d0s3 /dev/rdsk/c7t0d0 /dev/rdsk/c7t0d0s1 /dev/rdsk/c7t0d0s2 /dev/rdsk/c7t0d0s3
disk 2 0/7/1/0/4/0.1.0.0.0.0.0 sdisk CLAIMED DEVICE HP MSA VOLUME
/dev/dsk/c5t0d0 /dev/rdsk/c5t0d0
Thanks for your reply Bill and hope you can guide me.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-05-2015 09:55 AM - edited 01-05-2015 10:00 AM
01-05-2015 09:55 AM - edited 01-05-2015 10:00 AM
Re: need help to migrate info
OK. The IR volume means that your rx3600 has a built-in disk array controller called a Smart Array. Since this is already mirrored and perhaps striped for performance, I would leave vg00 as is. This will save a *LOT* of work, and possibly after all that effort, your VNX storage may not even support HP-UX boot. There is no advantage to moving off the internal disks for vg00. The Smart Array makes it very easy to replace a bad disk in the rx3600.
For vg01, it is fairly simple. You currently have a single LUN from the HP MSA storage which is 34998 extents of 8 MB each for a total of 279984 MB (about 280 GB). So have your VNX storage administrator present a 280 GB LUN to your system. Be absolutely sure that the presentation mode is HP-UX and not Windows, etc.
Once presented, scan for the new disk and use insf to create the new disk LUN on HP-UX:
# ioscan -fnCdisk
(you'll see the new disk as it will not have any device files associated with it)
# insf -Cdisk
(you'll see the new device file names for this LUN).
If you don't see any device files reported, stop. You'll need to troubleshoot the SAN presentation.
I'll refer to the new device as cXtYdZ.
Check the size and read a couple of hundred MB of data to test the LUN:
# diskinfo /dev/rdsk/cXtYdZ # dd if=/dev/rdsk/cXtYdZ of=/dev/null bs=1024k count=200
If the size of the LUN is correct (diskinfo queries the LUN itself) and the dd command completes without an error, then initialize the disk for LVM use:
# pvcreate /dev/rdsk/cXtYdZ
Now add the disk to vg01:
# vgextend vg01 /dev/dsk/cXtYdZ
If you run the command: vgdisplay vg01
you'll see that the Cur PV changed from 1 to 2 (PV = Physical Volume).
If you have more than one fibre cable running to the VNX storage, you need to add the Alternate paths to vg01. Just use vgextend vg01 /dev/dsk/__CTD__ for each alternate path.
Now mirror each disk.
You can run lvextend on each lvol one at a time, or use this short script to run all of them in order:
for LVOL in $(vgdisplay -v vg01 | awk '/LV Name/{print $NF}') do lvextend -m 1 $LVOL /dev/dsk/cXtYdZ done
Then check with vgdisplay -v vg01 that all the lvols have Used PV = 2.
To switch over to justy using the VNX storage, just reduce each of the lvols.
for LVOL in $(vgdisplay -v vg01 | awk '/LV Name/{print $NF}') do lvreduce -m 0 $LVOL /dev/dsk/c3t0d1 done
The above shows c3t0d1 which is from your listing for vg01.
Check that all the extents on the old LUN are free: vgdisplay -v vg01
(where Total PE = Free PE on the MSA LUN).
Again, stop if any of the above steps show any errors.
Now remove the old disks from vg01:
# vgreduce vg01 /dev/dsk/c5t0d1 /dev/dsk/c4t0d1 /dev/dsk/c3t0d1
vg01 is now completely migrated to the VNX.
At a later time, you should use rmsf -H to get rid of the old MSA device files. -H requires the hardware paths (from ioscan).
Bill Hassell, sysadmin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-05-2015 11:01 AM
01-05-2015 11:01 AM
Re: need help to migrate info
Bill,
Thanks a bunch! I will be seeing only one path to the VNX because the other PATH will be seeing the MSA, when I'm done migrating I will disconnect the other PATH (the other thats connected directly to the MSA) and connect it to our FC switch so I will be seeing a new path to the VNX (2 PATHs total) what will I have to do to add the alternate path then?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-05-2015 03:17 PM - edited 01-05-2015 03:20 PM
01-05-2015 03:17 PM - edited 01-05-2015 03:20 PM
Re: need help to migrate info
To keep things clean, use rmsf -H <hw_path> for the MSA LUNs.
Then, it will be the same steps (present the LUN on the new path, ioscan, insf) but do NOT run pvcreate -- that has already been done.
Use vgextend to add the path -- it will comment that the path is an alternate.
And that's it. Use vgdisplay -v vg01 to see the alternate path at the end.
Bill Hassell, sysadmin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-06-2015 07:44 AM
01-06-2015 07:44 AM
Re: need help to migrate info
Bill,
vgextend vg01 /dev/dsk/c10t0d1
vgextend: Warning: Max_PE_per_PV for the volume group (35002) too small for this PV (37119).
Using only 35002 PEs from this physical volume.
Couldn't open physical volume "/dev/rdsk/c3t0d1":
Verification of unique LVM disk id on each disk in the volume group
vg01 failed.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-06-2015 09:15 AM
01-06-2015 09:15 AM
Re: need help to migrate info
>>vgextend: Warning: Max_PE_per_PV for the volume group (35002) too small for this PV (37119).
>>Using only 35002 PEs from this physical volume.
The new LUN from your SAN is too large for thei VG. It will only use part of the LUN and not the whole thing.
>>Couldn't open physical volume "/dev/rdsk/c3t0d1":
>>Verification of unique LVM disk id on each disk in the volume group vg01 failed.
This is likely because c3t0d1 is an alternate path for the MSA storage used by the VG. Try reducing the c3t0d1 from the VG by using:
# vgreduce /dev/vg01 /dev/dsk/c3t0d1
Once that is done, use 'vgdisplay -v vg01' to see what disks are in the VG.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-06-2015 09:19 AM
01-06-2015 09:19 AM
Re: need help to migrate info
vgreduce /dev/vg01 /dev/dsk/c3t0d1
Device file path "/dev/dsk/c3t0d1" is an alternate path.
Volume group "/dev/vg01" has been successfully reduced.
Volume Group configuration for /dev/vg01 has been saved in /etc/lvmconf/vg01.conf
--- Physical volumes ---
PV Name /dev/dsk/c5t0d0
PV Name /dev/dsk/c4t0d1 Alternate Link
PV Status available
Total PE 34998
Free PE 12086
Autoswitch On
Proactive Polling On
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-06-2015 09:32 AM
01-06-2015 09:32 AM
Re: need help to migrate info
Now try running your vgextend again.
# vgextend vg01 /dev/dsk/c10t0d1