Hi all, We need to move about 1T of data from one zpool on EMC dmx-3000 to another storage device (dmx-3). DMX-3 can be visible on the same host where dmx-3000 is being used on or from another host. What is the best way to transfer the data from dmx-3000 to dmx-3? Is it possible to add the new dmx as a sub mirror of the old dmx and after the sync is finished, remove the old dmx from the mirror. Thank you, This message posted from opensolaris.org
Vahid,> We need to move about 1T of data from one zpool on EMC dmx-3000 to > another storage device (dmx-3). DMX-3 can be visible on the same > host where dmx-3000 is being used on or from another host. > What is the best way to transfer the data from dmx-3000 to dmx-3? > Is it possible to add the new dmx as a sub mirror of the old dmx and > after the sync is finished, remove the old dmx from the mirror.See: zpool replace [-f] pool old_device [new_device] - Jim> > Thank you, > > > This message posted from opensolaris.org > _______________________________________________ > zfs-discuss mailing list > zfs-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Thanks for your reply Jim, The current pool is consist of a few EMC LUNs and we are moving the entire pool to the new EMC storage with different devices. What would be my old or new device? Here is some parts of zpool status: NAME STATE READ WRITE CKSUM rd_01 ONLINE 0 0 0 c4t60060480000187870150525244353543d0 ONLINE 0 0 0 c4t60060480000187870150525244353942d0 ONLINE 0 0 0 c4t60060480000187870150525244353943d0 ONLINE 0 0 0 # zpool list rd_01 NAME SIZE USED AVAIL CAP HEALTH ALTROOT rd_01 25.1G 616M 24.5G 2% ONLINE - This is one of many pools. Thanks, This message posted from opensolaris.org
On 3/14/08, Vahid Moghaddasi <vahid at cckeeper.com> wrote:> > Thanks for your reply Jim, > The current pool is consist of a few EMC LUNs and we are moving the entire > pool to the new EMC storage with different devices. > What would be my old or new device? Here is some parts of zpool status: > > NAME STATE READ WRITE CKSUM > rd_01 ONLINE 0 0 0 > c4t60060480000187870150525244353543d0 ONLINE 0 0 0 > c4t60060480000187870150525244353942d0 ONLINE 0 0 0 > c4t60060480000187870150525244353943d0 ONLINE 0 0 0 > > # zpool list rd_01 > NAME SIZE USED AVAIL CAP HEALTH ALTROOT > rd_01 25.1G 616M 24.5G 2% ONLINE - > > This is one of many pools. > Thanks, > > > > This message posted from opensolaris.org > _______________________________________________ > zfs-discuss mailing list > zfs-discuss at opensolaris.org > http://mail.opensolaris.org/mailman/listinfo/zfs-discuss >replace your LUNs one at a time: zpool replace -f rd_01 c4t60060480000187870150525244353543d0 first_lun_off_dmx-3 zpool replace -f rd_01 c4t60060480000187870150525244353942d0 second_lun_off_dmx-3 and so on. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20080314/83148e00/attachment.html>
Simple enough thanks. I assume as I start the zpool replace operation, the original LUNs will not be in rd_01 pool any more. Not that will do that, but theoretically I can perform this on a live machine without interruption, is that right? Thank you, This message posted from opensolaris.org
On 3/14/08, Vahid Moghaddasi <Vahid at cckeeper.com> wrote:> > > On Fri, Mar 14, 2008 at 11:26 PM, Tim <tim at tcsac.net> wrote: > > > > > > > replace your LUNs one at a time: > > > > zpool replace -f rd_01 c4t60060480000187870150525244353543d0 > > first_lun_off_dmx-3 > > zpool replace -f rd_01 c4t60060480000187870150525244353942d0 > > second_lun_off_dmx-3 > > > > > > and so on. > > > > Simple enough thanks. I assume as I start the zpool replace operation, the > original LUNs will not be in rd_01 pool. Not that will do that, but > theoretically I can perform this on a live machine without interruption, is > that right? > Thank you, >Yes, it''s the same as replacing a bad drive. Just make sure you do one, let it completely finish, then move on to the next. Obviously the drives need to *rebuild* as you replace them. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/zfs-discuss/attachments/20080314/0a14dbf2/attachment.html>
On 3/14/08, Vahid Moghaddasi <Vahid at cckeeper dot com> wrote:
On Fri, Mar 14, 2008 at 11:26 PM, Tim <tim at tcsac dot net> wrote:
replace your LUNs one at a time:
zpool replace -f rd_01 c4t60060480000187870150525244353543d0
first_lun_off_dmx-3
zpool replace -f rd_01 c4t60060480000187870150525244353942d0
second_lun_off_dmx-3
and so on.
Simple enough thanks. I assume as I start the zpool replace operation, the
original LUNs will not be in rd_01 pool. Not that will do that, but
theoretically I can perform this on a live machine without interruption, is that
right?
Thank you,
On Fri, Mar 15, 2008 at 12:11 AM, Tim <tim at tcsac dot net> wrote:
Yes, it''s the same as replacing a bad drive. Just make sure you do
one, let it completely finish, then move on to the next. Obviously the drives
need to *rebuild* as you replace them.
Tim and Jim thank you very much for your help. I will give it a shot.
Vahid.
This message posted from opensolaris.org