11-04-2013
Redhat 4 host based migration
Hi,
I need to migrate using Redhat 4 as host based migration,EMC Clariion to VNX.
Please what are the best ways to perform online migration,with users working on the box?The file system is ext3 and the source logical voulumes are raid 1.
- adding the 3rd LUN(from VNX) to the current raid1 logical volume
- using rsync between 2 boxes with redhat 4,one box has raid 1 logical volume and the other one has new LUN(VNX).NFS exports the file system on the LUN in VNX and mount this on the other box.Then tar,cpio.
- pvmove,only if I do not need the data in old raid 1 logical volume.
- split raid1 into 2 submirrors and mirror one of those submirrors with LUN in VNX.
tnx a lot,
marius
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I'm looking for some sort of provider that I can connect to through a browser and subsequently open an ssh connection to another host. client based applet type solutions are blocked by firewall (2 Replies)
Discussion started by: dirtybrown
2 Replies
2. HP-UX
Hi,
We are planning to do migration from HP-UX to Redhat linux. We have 1300 makefiels. Is there any difference between HP-UX make and GNU make? Is there any tutorial on that?
Regards
hari_anj (0 Replies)
Discussion started by: hari_anj
0 Replies
3. Red Hat
Hi All
when I give the command,
$ ping <hostname>
I get the following error
ping: unknown host <hostname>
I have checked in the following files,
/etc/sysconfig/network
/etc/hosts
/etc/resolv.conf
/etc/nsswitch.conf
Every where in these files host name and IP address are given... (2 Replies)
Discussion started by: nagapradeep
2 Replies
4. UNIX for Advanced & Expert Users
I do a ssh to remote host(A1) from local host(L1). I then ssh to another remote(A2) from A1.
When I do a who -m from A2, I see the "connected from" as "A1".
=> who -m
userid pts/2 2010-03-27 08:47 (A1)
I want to identify who is the local host who initiated the connection to... (3 Replies)
Discussion started by: gomes1333
3 Replies
5. UNIX for Dummies Questions & Answers
Hi,
We are currently using solaris 9 on sunfire v240 and strongly considering to migrate to redhat enterprise. But we are not sure if we can install redhat enterprise on sunfire WS . Although, we will purchase a X64 machine we also want to use sunfire machine.
can we install redhat on sunfire... (2 Replies)
Discussion started by: titanic
2 Replies
6. Red Hat
Hi, I am fairly new to Linux. I have a Win XP host machine where I am running a Redhat virtual machine using VMplayer. I have a tool in the VM that I need to run using some input data located on the host machine. How can I share files between the host and the VM? I need to be able to read/write... (3 Replies)
Discussion started by: ilyaz
3 Replies
7. Cybersecurity
Hello guys,
I'm currently working on replacing old server and it's migration from SuSe
SUSE Linux Enterprise Server 10 (x86_64)
VERSION = 10
PATCHLEVEL = 4
to the RedHat
Red Hat Enterprise Linux Server release 6.4 (Santiago)
Problem seems be in migration of users passwords,... (2 Replies)
Discussion started by: brusell
2 Replies
8. Solaris
Hi All
Kindly let me know how can I move Solaris 10 OS running update 10 on physical machine to another machine solaris zone running Solaris 10 update 11 (2 Replies)
Discussion started by: amity
2 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. Red Hat
Hello,
we got a high security network which is completely offline.
We want to use a Sync Host like described here in the Redhat documentation for Sattelite 6.
I have the following Questions:
- We need the complete Repository not only the main one how much space we need for this ?
- Can... (2 Replies)
Discussion started by: izual
2 Replies
PVMOVE(8) System Manager's Manual PVMOVE(8)
NAME
pvmove - move physical extents
SYNOPSIS
pvmove [--abort] [--alloc AllocationPolicy] [-b|--background] [-d|--debug] [-h|--help] [-i|--interval Seconds] [--noudevsync] [-v|--ver-
bose] [-n|--name LogicalVolume] [SourcePhysicalVolume[:PE[-PE]...] [DestinationPhysicalVolume[:PE[-PE]...]...]]
DESCRIPTION
pvmove allows you to move the allocated physical extents (PEs) on SourcePhysicalVolume to one or more other physical volumes (PVs). You
can optionally specify a source LogicalVolume in which case only extents used by that LV will be moved to free (or specified) extents on
DestinationPhysicalVolume(s). If no DestinationPhysicalVolume is specifed, the normal allocation rules for the volume group are used.
If pvmove gets interrupted for any reason (e.g. the machine crashes) then run pvmove again without any PhysicalVolume arguments to restart
any moves that were in progress from the last checkpoint. Alternatively use pvmove --abort at any time to abort them at the last check-
point.
You can run more than one pvmove at once provided they are moving data off different SourcePhysicalVolumes, but additional pvmoves will
ignore any logical volumes already in the process of being changed, so some data might not get moved.
pvmove works as follows:
1. A temporary 'pvmove' logical volume is created to store details of all the data movements required.
2. Every logical volume in the volume group is searched for contiguous data that need moving according to the command line arguments. For
each piece of data found, a new segment is added to the end of the pvmove LV. This segment takes the form of a temporary mirror to copy
the data from the original location to a newly-allocated location. The original LV is updated to use the new temporary mirror segment in
the pvmove LV instead of accessing the data directly.
3. The volume group metadata is updated on disk.
4. The first segment of the pvmove logical volume is activated and starts to mirror the first part of the data. Only one segment is mir-
rored at once as this is usually more efficient.
5. A daemon repeatedly checks progress at the specified time interval. When it detects that the first temporary mirror is in-sync, it
breaks that mirror so that only the new location for that data gets used and writes a checkpoint into the volume group metadata on disk.
Then it activates the mirror for the next segment of the pvmove LV.
6. When there are no more segments left to be mirrored, the temporary logical volume is removed and the volume group metadata is updated so
that the logical volumes reflect the new data locations.
Note that this new process cannot support the original LVM1 type of on-disk metadata. Metadata can be converted using vgconvert(8).
OPTIONS
--abort
Abort any moves in progress.
--noudevsync
Disable udev synchronisation. The process will not wait for notification from udev. It will continue irrespective of any possible
udev processing in the background. You should only use this if udev is not running or has rules that ignore the devices LVM2 cre-
ates.
-b, --background
Run the daemon in the background.
-i, --interval Seconds
Report progress as a percentage at regular intervals.
-n, --name LogicalVolume
Move only the extents belonging to LogicalVolume from SourcePhysicalVolume instead of all allocated extents to the destination phys-
ical volume(s).
EXAMPLES
To move all logical extents of any logical volumes on /dev/hda4 to free physical extents elsewhere in the volume group, giving verbose run-
time information, use:
pvmove -v /dev/hda4
SEE ALSO
lvm(8), vgconvert(8)
Sistina Software UK LVM TOOLS 2.02.67(2) (2010-06-04) PVMOVE(8)