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
Old 09-16-2019
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:-
  1. Added the new LUNs to the VG
  2. Mirrored the LVs (no sync) and confirmed the layout was correct (not spread to old disks etc.)
  3. Ran a syncvg and left if. Any problems, we would drop the new leaving the old intact.
When it had completed, we:-
  1. Removed the mirror from the old/original disk
  2. 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..
 

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... (1 Reply)
Discussion started by: ncmurf00
1 Replies

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 Replies)
Discussion started by: jgutierrez29
3 Replies

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 (2 Replies)
Discussion started by: sijocg
2 Replies

4. HP-UX

HP Storage Array

hi I need to check status and configure HP Storage Array device. HP Storageworks P2000 Please suggest (0 Replies)
Discussion started by: anand87
0 Replies

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... (4 Replies)
Discussion started by: keelba
4 Replies

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... (0 Replies)
Discussion started by: fausto.ncc1701
0 Replies
vgexport(1M)															      vgexport(1M)

NAME
vgexport - export an LVM volume group and its associated logical volumes SYNOPSIS
mapfile] outfile] vg_name mapfile vg_name DESCRIPTION
Using the format of the first command line of the above, the command can be used to remove a volume group from the system. The volume group will be removed without modifying the logical volume information found on the physical volumes. The volume group identified by vg_name is removed from the or file, and the associated device files including the vg_name directory and file are removed from the system. The volume group information and data is untouched on the physical volume. These disks can be imported to another system with the command (see vgimport(1M)). Scan Option Using the format of the second command line of the above, the command generates a mapfile that can be copied to other systems that are part of a high availability cluster (use the option if you do not want to remove the volume group from the system the command is being run from) and the command (see vgimport(1M)) can be used to recreate the volume group. See also vgchange(1M). The mapfile contains a description of the volume group and its associated logical volume(s) (if any). The logical volume information found on the physical volumes is not modi- fied. Options and Arguments recognizes the following options and arguments: vg_name The path name of the volume group. By default, a file named is created in the current directory. This file contains a description of the volume group and its associated logical volume(s) (if any). Use this option to specify a different name for the file, mapfile. This file can be used as input to (see vgimport(1M)). When used with the option, the volume group specified in the mapfile can be shared with other systems in the high availability cluster. Preview the actions to be taken but do not update the or file or remove the devices file. This option is best used in conjunction with the option. Print verbose messages including the names of the physical volumes associated with this volume group. Scan option. When the option is specified, then the options must also be specified. A mapfile is created that can be used to cre- ate volume group entries on other systems in the high availability cluster (with the command). Write the current set of pv_paths for the volume group to the outfile. The outfile may then be used as the infile for the option. If used together with the option the volume group is not exported but the list of pv_paths is still written to the outfile. This may be useful to derive a list of pv_paths for the volume group or to use on another system which is sharing the volume group and which has an identical configuration. EXTERNAL INFLUENCES
Environment Variables determines the language in which messages are displayed. If is not specified or is null, it defaults to "C" (see lang(5)). If any internationalization variable contains an invalid setting, all internationalization variables default to "C" (see environ(5)). EXAMPLES
Export the volume group into mapfile The volume group will be removed from the exporting system. Export the volume group and write the disk names into the file Create a mapfile to be copied to other systems in a high availability cluster to build the volume group information for the volume group, Note that the volume group is not removed from the exporting system. The importing systems will create the volume group with the command using the and options. SEE ALSO
vgimport(1M), vgscan(1M). vgexport(1M)
All times are GMT -4. The time now is 02:41 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy