|
|
Sponsored Content
Operating Systems
HP-UX
SAN Migration question
Post 302946595 by Peasant on Wednesday 10th of June 2015 03:04:29 PM
06-10-2015
Moderator
With HPUX v2, it is a bit tricker to do it online, since for every path you will have one disk device which you have to configure. Agile naming and lun map are on HPUX v3 which makes things considerably easier.
But since you have downtime, export the volume group(s) in which FC disks are into a file (-p -m -s easy to remember
)
Stop the service in question and umount the filesystems.
Deactivate and export the volume group.
Unpresent the existing FC luns from host.
Clean up the old device files, you will need to remove the "NO_HW" devices with rmsf -H # this is optional but desirable.
Zone the storage and host on the new switch, and present the luns to the host.
Import the volume group using file you created in setup one.
Activate the volume group and mount filesystems, since you used -m option, it will import with VGID from file.
IF you are migrating SAN root volume group (vg00) additional steps are required.
For online migration, you will need to
Disconnect one path and connect it to a new switch which is zoned and setuped for the host.
Present the luns over that path to host.
Using vgextend, extend the volume group with new luns.
Using vgreduce, remove the existing lun (old switch path)
Disconnect other path, connect to new switch, present, vgextend new, vgreduce old disk path.
Hope that helps.
Regards
Peasant.
But since you have downtime, export the volume group(s) in which FC disks are into a file (-p -m -s easy to remember
) Stop the service in question and umount the filesystems.
Deactivate and export the volume group.
Unpresent the existing FC luns from host.
Clean up the old device files, you will need to remove the "NO_HW" devices with rmsf -H # this is optional but desirable.
Zone the storage and host on the new switch, and present the luns to the host.
Import the volume group using file you created in setup one.
Activate the volume group and mount filesystems, since you used -m option, it will import with VGID from file.
IF you are migrating SAN root volume group (vg00) additional steps are required.
For online migration, you will need to
Disconnect one path and connect it to a new switch which is zoned and setuped for the host.
Present the luns over that path to host.
Using vgextend, extend the volume group with new luns.
Using vgreduce, remove the existing lun (old switch path)
Disconnect other path, connect to new switch, present, vgextend new, vgreduce old disk path.
Hope that helps.
Regards
Peasant.
These 2 Users Gave Thanks to Peasant For This Post:
|
|
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 PHP
vgreduce
VGREDUCE(8) System Manager's Manual VGREDUCE(8) NAME
vgreduce - reduce a volume group SYNOPSIS
vgreduce [-a|--all] [-A|--autobackup y|n] [-d|--debug] [-h|-?|--help] [--removemissing] [-t|--test] [-v|--verbose] VolumeGroupName [Physi- calVolumePath...] DESCRIPTION
vgreduce allows you to remove one or more unused physical volumes from a volume group. OPTIONS
See lvm for common options. -a, --all Removes all empty physical volumes if none are given on command line. --removemissing Removes all missing physical volumes from the volume group, if there are no logical volumes allocated on those. This resumes normal operation of the volume group (new logical volumes may again be created, changed and so on). If this is not possible (there are logical volumes referencing the missing physical volumes) and you cannot or do not want to remove them manually, you can run this option with --force to have vgreduce remove any partial LVs. Any logical volumes and dependent snapshots that were partly on the missing disks get removed completely. This includes those parts that lie on disks that are still present. If your logical volumes spanned several disks including the ones that are lost, you might want to try to salvage data first by acti- vating your logical volumes with --partial as described in lvm (8). SEE ALSO
lvm(8), vgextend(8) Sistina Software UK LVM TOOLS 2.02.95(2) (2012-03-06) VGREDUCE(8)