06-09-2015
SAN Migration question
Hi,
I am very new to HP-UX, and we're going to be doing a SAN migration.
We're going to take down the machine, and zone it to the new SAN.
My question is, will the device names change and will that interfere with the LVM?
If the new disks come in with different device names, how would I remediate that issue so the LVM would know what disks to point to?
Thanks!
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
vgrestore
vgrestore(1M) vgrestore(1M)
NAME
vgrestore - restore a VxVM disk group back to an LVM volume group
SYNOPSIS
/etc/vx/bin/vgrestore vg_name
DESCRIPTION
The vgrestore command restores a Logical Volume Manager (LVM) volume group that was previously converted to a VxVM disk group by the vxvm-
convert utility.
ARGUMENTS
vg_name
Specifies the name of a volume group that was converted to a VxVM disk group by the vxvmconvert utility.
EXIT CODES
vgrestore exits with one of the following values:
0 Successful completion.
>0 Failure; an error occurred.
WARNINGS
vgrestore functions only on VxVM disk groups that were converted from LVM volume groups by the vxvmconvert command.
It is a good idea to back up user data before running vgrestore, and restore it after the vgrestore completes, as vgrestore can only
restore a logical volume back to the state it was in before conversion to VxVM. If data changed on the volume while it was a VxVM volume,
the changes won't be reflected on the volume after being restored to LVM.
As part of the original conversion process, applications that once referenced the now-converted LVM volume's path names may have changed to
reference VxVM volume special device file names. Alternatively, special device file path names originally representing the now-converted
LVM volumes may have changed to symbolic links pointing to the VxVM volume path names. Be sure to undo these actions when restoring back
to LVM.
Do not use vgrestore unless you are certain that you want to restore LVM volume groups. After vgrestore this is run, the VxVM disks will
no longer exist.
EXAMPLES
To restore the LVM volume group vg03 that was converted by vxvmconvert to the VxVM disk group dg03, enter:
vgcfgrestore vg03
SEE ALSO
vxvmconvert(1M)
Veritas Volume Manager Migration Guide
VxVM 5.0.31.1 24 Mar 2008 vgrestore(1M)