From: Ray Morris <support@bettercgi.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Migrating LVM
Date: Wed, 21 Apr 2010 09:18:08 -0500 [thread overview]
Message-ID: <1271859488.23509.3@raydesk1.bettercgi.com> (raw)
In-Reply-To: <4BCE79B5.9070600@cajuninc.com> (from cajun@cajuninc.com on Tue Apr 20 23:06:13 2010)
pvmove is good for when you have to keep the machine
live during the copy. dd is about 10 times as fast if you
can be down during the copy. This specific dd invocation
is the fastest I've found for the purpose, running 2-3 times
faster than a simple dd without arguments:
dd if=/dev/old_vg/$1 bs=64M iflag=direct | dd of=/dev/new_vg/$1 bs=64M
oflag=direct
--
Ray Morris
support@bettercgi.com
Strongbox - The next generation in site security:
http://www.bettercgi.com/strongbox/
Throttlebox - Intelligent Bandwidth Control
http://www.bettercgi.com/throttlebox/
Strongbox / Throttlebox affiliate program:
http://www.bettercgi.com/affiliates/user/register.php
On 04/20/2010 11:06:13 PM, M.Lewis wrote:
>
> I'm building a new machine with RAID1+LVM2. I plan to migrate the
> data from the old machine HD to the new machine.
>
> Is it better to make the new VG the same name as the existing VG on
> the old box? Or should I make it different.
>
> Is there an easy way to do this that I've not yet found? I was
> thinking to make the new VG the same name as the old, add the old
> drives to the machine then pvmove the data.
>
> Thanks for any pointers!
> Mike
>
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
>
next prev parent reply other threads:[~2010-04-21 14:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-21 4:06 [linux-lvm] Migrating LVM M.Lewis
2010-04-21 5:42 ` Luca Berra
2010-04-21 14:18 ` Ray Morris [this message]
2010-04-21 15:36 ` malahal
2010-04-21 16:27 ` Phillip Susi
2010-04-21 17:00 ` Ray Morris
2010-04-21 23:10 ` M.Lewis
2010-04-21 16:24 ` Phillip Susi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1271859488.23509.3@raydesk1.bettercgi.com \
--to=support@bettercgi.com \
--cc=linux-lvm@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.