From: raid@bymeinc.com
To: linux-raid@vger.kernel.org
Subject: RE: Imaging Mirrored OS Drives
Date: Wed, 16 Aug 2006 13:28:57 -0400 (EDT) [thread overview]
Message-ID: <20060816172857.9FF69AE3DC@bymeinc.com> (raw)
The first method that comes to mind is to make a raw copy of each mirrored disk to another disk attached to the same server. dd if=/dev/sda of=/dev/sdb will do a raw dump from one drive to another. Assuming you copy to a drive of equal or greater capacity, your partition structure, RAID superblock (including UUID), and data should remain intact. mdadm should be able to run a disk pair made by raw copies of the disks. I don't see a problem with identical UUID drives living in the same machine, so long as the array isn't started. Obviously copying a mounted block device is a bad idea, so I'd do it from a bootable CD environment, etc.
next reply other threads:[~2006-08-16 17:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-16 17:28 raid [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-08-16 22:20 Imaging Mirrored OS Drives andy liebman
2006-08-16 17:32 raid
2006-08-16 17:05 andy liebman
2006-08-16 20:47 ` Luca Berra
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=20060816172857.9FF69AE3DC@bymeinc.com \
--to=raid@bymeinc.com \
--cc=linux-raid@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).