06-10-2015
Is the HPUX in question v2 or v3 ?
If the answer is v3, the operation can be online, since on v3, every lun has a WWID.
Just do it port by port, rescan and check paths after each, should not be any issues.
If you want to do it offline, do a vgexport preview (to a file not actual export) of all volume groups on the system using SAN disks (just to be safe do it anyway in each scenario) and deactivate the volume group.
Since the VG info is actually written on disks, even if everything changes (disk names etc.) you will be able to import the volume group using a file you created earlier. There are also other methods (vgscan), but this one is most trivial.
Commands you will require are
scsimgr -> to check lunmap and paths before and after.
ioscan -> to rescan after port change.
This assumes you are using hpux native multipath, not other multipath solutions.
10 More Discussions You Might Find Interesting
1. HP-UX
Hi, I'm going to be involved in a migration of SAN islands to one big SAN. I've not worked with SANs before and I'm not sure how to approach this. I suspect the disk devices on the HP servers are going to change, when the EVA's and servers are plugged into this new Cisco 9509 switch.
Any... (0 Replies)
Discussion started by: Hils
0 Replies
2. Solaris
Using Solaris 10 with Veritas Storage Foundation running. I want to copy all contents from DISKA LUN1 to DISKB LUN2. What would be the command syntax to do this? (0 Replies)
Discussion started by: soupbone38
0 Replies
3. Solaris
I have a general question regarding Zone Migration.
I have an older system that is currently running a zone configured with ProFTPD & SSL.
If I want to migrate or clone that zone to another (much newer) system, will I still have to setup & configure ProFTPD & SSL on the new system? (3 Replies)
Discussion started by: em23
3 Replies
4. Red Hat
Hey everyone.
I am working on designing a logging solution for a deployment we have going out in a few months. Right now we have a single storage head end, connected via fibre to a SAN. Basically the plan is to create a number of smaller LUNs on the SAN, and then use LVM2 to handle concatenating... (5 Replies)
Discussion started by: msarro
5 Replies
5. HP-UX
Hello gurus,
I am a SAN Admin - not very familiar with the HPUX administration - so need help with the steps in regards to the migration I need to do at my client place.
Environment: Migrating from CX4 to VMAX - using OR/Hot Pull.
Here are the steps I have put together - HPUX gurus please... (5 Replies)
Discussion started by: jps460
5 Replies
6. Solaris
I am going to do a SAN Array migration and need the sequence of steps required on the Solaris cluster before moving the old array luns to new array luns.
Here are the steps and I need info on the bold points:( I might even be wrong on the sequence of steps please correct me if I am wrong)
1.... (0 Replies)
Discussion started by: sunshinedeepu
0 Replies
7. AIX
Hi all,
We are migrating our SAN storage from HSV360 to 3PAR. The system runs aix 6.1 version with HACMP.
Please let me know what are requirements from OS side and how are the data copied to the new disks. (10 Replies)
Discussion started by: ElizabethPJ
10 Replies
8. Red Hat
I have an IBM blade running RHEL 5.4 server, connected to two Hitachi SANs using common fibre cards & Brocade switches. It has two volume groups made from old SAN LUNs. The old SAN needs to be retired so we allocated LUNs from the new SAN, discovered the LUNs as multipath disks (4 paths) and grew... (4 Replies)
Discussion started by: rbatte1
4 Replies
9. AIX
I'm New to AIX / VIOS
We're doing a FC switch cutover on an ibm device, connected via SAN.
How do I tell if one path to my remote disk is lost? (aix lvm)
How do I tell when my link is down on my HBA port?
Appreciate your help, very much! (4 Replies)
Discussion started by: BG_JrAdmin
4 Replies
10. Solaris
I am working on VM host and collecting data to identify the type of storage attached to the server which will be migrated to VNX.
it has one ldom created on it
luxadm probe output ---
No Network Array enclosures found in /dev/es
Found Fibre Channel device(s):
Node... (7 Replies)
Discussion started by: kpatel786
7 Replies
LEARN ABOUT HPUX
vxvmconvert
vxvmconvert(1M) vxvmconvert(1M)
NAME
vxvmconvert - convert LVM volume groups to VxVM disk groups
SYNOPSIS
vxvmconvert
DESCRIPTION
vxvmconvert is a menu-driven program to convert an HP Logical Volume Manger (LVM) configuration to a Veritas Volume Manager configuration.
This man page is a brief overview of vxvmconvert. Refer to the Veritas Volume Manager Migration Guide for a detailed description before
using the conversion procedure.
The vxvmconvert script is interactive and prompts you for responses, supplying defaults where appropriate. There is a Help facility at
every prompt. Enter a question mark (?) at a prompt to display a context-sensitive help message.
With vxvmconvert you can identify LVM volume groups, list disks, analyze volume groups for conversion and complete the conversion of LVM
volume groups to VxVM disk groups.
LVM configurations are converted at the volume group level. All disks used in a volume group are converted together. You cannot use vxvm-
convert to convert unused LVM disks (those not part of an LVM volume group) to VxVM disks. To convert unused LVM disks, use pvremove to
take the disk out of LVM control, then initialize the disk for VxVM use by using vxdiskadm (see pvremove(1M) and vxdiskadm(1M) for more
information).
vxvmconvert changes disks within LVM volume groups to VxVM disks by replacing the areas of the disks used for LVM configuration information
and with the equivalent VxVM volume configuration information. Portions of the disks used for user data, such as file systems and data-
bases, are not affected by the conversion.
The conversion process changes the names by which your system refers to the logical storage, so must be done offline. No applications can
access data in the volume groups undergoing conversion. You must unmount file systems using those volumes and shut down any applications,
such as databases, that might use the volumes directly.
OPERATIONS
Analyze LVM Volume Groups for Conversion
Use this operation to analyze one or more LVM volume groups for conversion to use by VxVM. The analysis checks for problems that
can prevent the conversion from completing successfully. It calculates the space required to add volume group disks to a Volume
Manager disk group. More than one volume group may be entered at the prompt. A grep-like pattern may be used to select multiple
volume groups.
See the ``Limitations in Conversion'' section in the Volume Manager Migration Guide for more information.
Convert LVM Volume Groups to VxVM
Converts one or more LVM volume groups to one or more VxVM disk groups. This adds the disks to a VxVM disk group and replaces
existing LVM volumes with VxVM volumes.
vxvmconvert prompts you to name the VxVM disk group that replaces the LVM volume group being converted. A default is suggested
at the prompt. For example, if you are converting a volume group vg08, vxvmconvert renames it as dg08.
See to the sections ``Dealing with New Logical Volume Names'' and ``Tailoring your VxVM Configuration'' in the Volume Manager
Migration Guide for more information.
Rollback from VxVM to LVM
Rollback reverts VxVM disk groups to LVM volume groups. vxvmconvert provides a limited snapshot capability for the LVM metadata
in a converted volume group. A snapshot is a simple protection method to use during conversion.
Caution! Do not use this operation if the VxVM disk group was modified since the conversion.
See to the section ``Restoring LVM Volume Groups and Disaster Recovery'' in the Volume Manager Migration Guide for more informa-
tion.
List Disk Information
Displays information about the disks on a system. You can obtain detailed information about a disk by entering a specific disk
device address.
List LVM Volume Group Information
Listvg displays a list of LVM volume groups. You can obtain detailed information about an LVM volume group at a specific disk
device address.
SEE ALSO
pvremove(1M), vgcfgbackup(1M), vgrestore(1M), vxdisk(1M), vxdiskadd(1M), vxdiskadm(1M), vxintro(1M)
Veritas Volume Manager Migration Guide
VxVM 5.0.31.1 24 Mar 2008 vxvmconvert(1M)