Migrating LUNs to new storage array Post: 303038873

Sponsored Content

Operating Systems AIX Migrating LUNs to new storage array Post 303038873 by rbatte1 on Monday 16th of September 2019 07:57:15 AM

09-16-2019

Moderator

Just a thought (and trying to avoid downtime) can you not add the new LUNs into the VG and then migrate them with the server still live? I've done this very successfully and prevented needless hours of downtime (three weekends-worth)

The team I was helping to do this were very nervous and wanted the belt & braces approach so we:-

Added the new LUNs to the VG
Mirrored the LVs (no sync) and confirmed the layout was correct (not spread to old disks etc.)
Ran a syncvg and left if. Any problems, we would drop the new leaving the old intact.

When it had completed, we:-

Removed the mirror from the old/original disk
Removed the original disks from the volume group

Like I say, this was done with the server online and processing. The volume manager deals with this very well, and whilst it takes a long time to synchronise, it's probably no worse than waiting for something else to migrate the data. It is also reversible up to the point you commit by removing the mirror copies on the old disks.

Why do you not want to have both SANs connected at the same time? The usual arrangement is to have the SAN connections passed through a switch rather than direct to the AIX host. Is there a reason that you could not just add the new SAN connections to these switches?

I hope this gives you an alternative,
Robin

Last edited by rbatte1; 09-16-2019 at 09:03 AM..

rbatte1

View Public Profile for rbatte1

Visit rbatte1's homepage!

Find all posts by rbatte1

6 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

Storage array question

We just purchased a MOD30 disk array strage system. We have 15 drives and 2 hot spares. We're running a database app with 8 data sets. I'm trying to get the best i/o speed out of my disk configuration. Right now I have 3 raid5 arrays setup. This seems to offer the same performance as having the...

2. Filesystems, Disks and Memory

how can I monitoring the LUNs in HP storage

Hi, How can i monitoring the LUN in HP Storage with korn shells? I would like to have a shell can monitoring the LUN, VGs, lvols and raw devices. Jesus

3. Solaris

storage array simulator

hi i haven't much experience in solaris. I would like to know about storage. how to configure,how it is working etc....can i get any simulator for doing these work? plaese send me the link . please help me advance thanks to all

4. HP-UX

HP Storage Array

hi I need to check status and configure HP Storage Array device. HP Storageworks P2000 Please suggest

5. UNIX for Advanced & Expert Users

VxVM breaking mirror for migrating storage

We are in the process of migrating storage from one array to another. I know the commands I would use in LVM but I am not very familiar with VxVM. The goal is to attach the new LUNs from the new array and add them to the disk group. Then mirror the data online to these new LUNs using VxVM...

6. Red Hat

Migrating an Oracle database storage - REDHAT4

e have a RHEL4 server with an Oracle 10 ( RAC ) are migrating storage bank records. The copy is made by the storage they make a copy of the level of disk all blocks are copied and the file permissions. Problems we had Initially the Cluster service was not rising due to absence of OCR disks...

LEARN ABOUT REDHAT

vgexport

VGEXPORT(8)						      System Manager's Manual						       VGEXPORT(8)

NAME

       vgexport - make volume groups unknown to the system

SYNOPSIS

       vgexport [-a|--all] [-d|--debug] [-h|--help] [-v|--verbose] [--version] [VolumeGroupName...]

DESCRIPTION

       vgexport allows you to make the inactive VolumeGroupName unknown to the system.	You can then move all of the physical volumes in that vol-
       ume group to a different system for later vgimport(8).  An exported volume group is not detected by  vgscan(8),	but  pvscan(8)	will  show
       which physical volumes belong to the exported volume group.

   OPTIONS
       -a, --all
	      Exports all inactive volume groups.

       -d, --debug
	      Enables additional debugging output (if compiled with DEBUG).

       -h, --help
	      Print a usage message on standard output and exit successfully.

       -v, --verbose
	      Display verbose runtime information about vgexport's activities.

       --version
	      Display tool and IOP version and exit successfully.

DIAGNOSTICS

       vgexport returns an exit code of 0 for success and > 0 for error:

       1  no volume groups found at all
       2  no volume group name on command line

       95 driver/module not in kernel
       96 invalid I/O protocol version
       97 error locking logical volume manager
       98 invalid lvmtab (run vgscan(8))
       99 invalid command line

SEE ALSO

       lvm(8), vgimport(8)

AUTHOR

       Heinz Mauelshagen <Linux-LVM@Sistina.com>

Heinz Mauelshagen						     LVM TOOLS							       VGEXPORT(8)