Sponsored Content
Full Discussion: SAN Migration
Operating Systems AIX SAN Migration Post 302900347 by gull04 on Tuesday 6th of May 2014 09:54:32 AM
Old 05-06-2014
Hi Elizabeth,

It would also be possible to mirror the data over the two arrays - a solution I used when going from DS8300 to VMax.

Regards

Gull04
 

10 More Discussions You Might Find Interesting

1. HP-UX

SAN migration

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

Thoughts/experiences of SAN attaching V880 to EMC SAN

Hi everyone, I wonder if I can canvas any opinions or thoughts (good or bad) on SAN attaching a SUN V880/490 to an EMC Clarion SAN? At the moment the 880 is using 12 internal FC-AL disks as a db server and seems to be doing a pretty good job. It is not I/O, CPU or Memory constrained and the... (2 Replies)
Discussion started by: si_linux
2 Replies

3. AIX

IBM SAN TO SAN Mirroring

Has anyone tried SAN to SAN mirroring on IBM DS SAN Storage. DS5020 mentions Enhanced Remote Mirror to multi-LUN applications I wonder if Oracle High availibility can be setup using Remote Mirror option of SAN ? (1 Reply)
Discussion started by: filosophizer
1 Replies

4. HP-UX

SAN Migration of HP-UX hosts

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

5. Solaris

Need Help On Solaris Cluster Steps For San Migration

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

6. HP-UX

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

7. Red Hat

Volume group not activated at boot after SAN migration

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

8. AIX

AIX - FC Switch migration, SAN Migration question!

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

9. Solaris

How to identify if disk is attached to SAN and assist in migration.?

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

10. Filesystems, Disks and Memory

Faster way: SAN hd to SAN hd copying

hi! i got a rhel 6.3 host that already have an xfs filesystem mounted from a SAN (let's call it SAN-1) whose size is 9TB. i will be receiving another SAN (let's call it SAN-2) storage of 15TB size. this new addition is physically on another SAN storage. SAN-1 is on a Pillar storage while the new... (6 Replies)
Discussion started by: rino19ny
6 Replies
LVCONVERT(8)						      System Manager's Manual						      LVCONVERT(8)

NAME
lvconvert - convert a logical volume from linear to mirror or snapshot SYNOPSIS
lvconvert -m|--mirrors Mirrors [--mirrorlog {disk|core}] [--corelog] [-R|--regionsize MirrorLogRegionSize] [-A|--alloc AllocationPolicy] [-b|--background] [-i|--interval Seconds] [-h|-?|--help] [-v|--verbose] [--version] LogicalVolume[Path] [PhysicalVolume[Path]...] lvconvert -s|--snapshot [-c|--chunksize ChunkSize] [-h|-?|--help] [-v|--verbose] [-Z|--zero y|n] [--version] OriginalLogicalVolume[Path] SnapshotLogicalVolume[Path] DESCRIPTION
lvconvert will change a linear logical volume to a mirror logical volume or to a snapshot of linear volume and vice versa. It is also used to add and remove disk logs from mirror devices. OPTIONS
See lvm for common options. Exactly one of --mirrors or --snapshot arguments required. -m, --mirrors Mirrors Specifies the degree of the mirror you wish to create. For example, "-m 1" would convert the original logical volume to a mirror volume with 2-sides; that is, a linear volume plus one copy. --mirrorlog {disk|core} Specifies the type of log to use. The default is disk, which is persistent and requires a small amount of storage space, usually on a separate device from the data being mirrored. Core may be useful for short-lived mirrors: It means the mirror is regenerated by copying the data from the first device again every time the device is activated - perhaps, for example, after every reboot. --corelog The optional argument "--corelog" is the same as specifying "--mirrorlog core". -R, --regionsize MirrorLogRegionSize A mirror is divided into regions of this size (in MB), and the mirror log uses this granularity to track which regions are in sync. -b, --background Run the daemon in the background. -i, --interval Seconds Report progress as a percentage at regular intervals. -s, --snapshot Create a snapshot from existing logical volume using another existing logical volume as its origin. -c, --chunksize ChunkSize Power of 2 chunk size for the snapshot logical volume between 4k and 512k. -Z, --zero y|n Controls zeroing of the first KB of data in the snapshot. If the volume is read-only the snapshot will not be zeroed. Examples "lvconvert -m1 vg00/lvol1" converts the linear logical volume "vg00/lvol1" to a two-way mirror logical volume. "lvconvert --mirrorlog core vg00/lvol1" converts a mirror with a disk log to a mirror with an in-memory log. "lvconvert --mirrorlog disk vg00/lvol1" converts a mirror with an in-memory log to a mirror with a disk log. "lvconvert -m0 vg00/lvol1" converts a mirror logical volume to a linear logical volume. "lvconvert -s vg00/lvol1 vg00/lvol2" converts logical volume "vg00/lvol2" to snapshot of original volume "vg00/lvol1" SEE ALSO
lvm(8), vgcreate(8), lvremove(8), lvrename(8), lvextend(8), lvreduce(8), lvdisplay(8), lvscan(8) Red Hat, Inc LVM TOOLS 2.02.44-cvs (02-17-09) LVCONVERT(8)
All times are GMT -4. The time now is 07:19 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy