Mailing List Archive: Netapp: toasters

SnapMirror for data migration within the same controller

Index | Next | Previous | View Threaded

Andre.Clark at earthlink

Jan 13, 2010, 6:12 AM

Post #1 of 8 (3453 views)
Permalink

SnapMirror for data migration within the same controller

Is there a way to perform a SnapMirror migration within the same controller
without using the internal loopback adapter (~40Mbs). I have a situation
where I need to migrate close to 6TB of data (multiple volumes) off of older
smaller drives to larger 300G drives. Ideally I'd like to use SnapMirror
multiplexing, however, I'm not sure that, even with direct connection
between interfaces, this would even work (I'm thinking that the internal
loopback would still take over). I don't want to do multiple snapmirrors
(orig. controller> temp controller> orig. controller) but this may be my
only path in order to get the speed that I need for the transfer. Any ideas?

mschipp at asi

Jan 13, 2010, 4:35 PM

Post #2 of 8 (3337 views)
Permalink

RE: SnapMirror for data migration within the same controller [In reply to]

If you do not need snapshots then maybe vol copy will do what you need.

From: owner-toasters [at] mathworks [mailto:owner-toasters [at] mathworks] On Behalf Of André M. Clark
Sent: Thursday, 14 January 2010 1:12 AM
To: toasters [at] mathworks
Subject: SnapMirror for data migration within the same controller

Is there a way to perform a SnapMirror migration within the same controller without using the internal loopback adapter (~40Mbs). I have a situation where I need to migrate close to 6TB of data (multiple volumes) off of older smaller drives to larger 300G drives. Ideally I'd like to use SnapMirror multiplexing, however, I'm not sure that, even with direct connection between interfaces, this would even work (I'm thinking that the internal loopback would still take over). I don't want to do multiple snapmirrors (orig. controller> temp controller> orig. controller) but this may be my only path in order to get the speed that I need for the transfer. Any ideas?

************************************************************************************
This footnote confirms that this email message has been scanned by
PineApp Mail-SeCure for the presence of malicious code, vandals & computer viruses.
************************************************************************************

romeotheriault at gmail

Jan 14, 2010, 3:12 AM

Post #3 of 8 (3317 views)
Permalink

Re: SnapMirror for data migration within the same controller [In reply to]

>
> If you do not need snapshots then maybe vol copy will do what you need.

vol copy can copy snapshots as well. From 7.2.6.1 vol man page,

vol copy start [ -S | -s snapshot ] source destination
>
> Copies all data, including snapshots, from one vol-
> ume to another. If the -S flag is used, the com-
> mand copies all snapshots in the source volume to
> the destination volume. To specify a particular
> snapshot to copy, use the -s flag followed by the
> name of the snapshot.
>

Though I'm not sure this would be any faster than a snapmirror.

Andre, I'd be interested to hear what your outcome of this eventually is.

Thanks,

--
Romeo Theriault
System Administrator
Information Technology Services

Adam.Fox at netapp

Jan 14, 2010, 1:54 PM

Post #4 of 8 (3301 views)
Permalink

RE: SnapMirror for data migration within the same controller [In reply to]

The vol copy option is a good one as long as you don't want to do incremental updates. Vol copy is simply an level 0-only version of SnapMirror (and it's free). What you get with SnapMirror are things like block level incrementals, the ability to schedule those updates, qtree-level replication options, the ability to resync after a break without re-initialization, sync and semi-sync options, and probably a few others.

-- Adam Fox

Systems Engineer

adamfox [at] netapp

From: Romeo Theriault [mailto:romeotheriault [at] gmail]
Sent: Thursday, January 14, 2010 6:12 AM
To: Michael Schipp; André M. Clark
Cc: toasters [at] mathworks
Subject: Re: SnapMirror for data migration within the same controller

If you do not need snapshots then maybe vol copy will do what you need.

vol copy can copy snapshots as well. >From 7.2.6.1 vol man page,

vol copy start [ -S | -s snapshot ] source destination

Copies all data, including snapshots, from one vol-
ume to another. If the -S flag is used, the com-
mand copies all snapshots in the source volume to
the destination volume. To specify a particular
snapshot to copy, use the -s flag followed by the
name of the snapshot.

Though I'm not sure this would be any faster than a snapmirror.

Andre, I'd be interested to hear what your outcome of this eventually is.

Thanks,

--
Romeo Theriault
System Administrator
Information Technology Services

Andre.Clark at earthlink

Jan 14, 2010, 4:15 PM

Post #5 of 8 (3295 views)
Permalink

Re: SnapMirror for data migration within the same controller [In reply to]

Romeo,

I need to keep snapshots so vol copy is out. Also, it will still use the
internal loopback adapter. What I am trying to do is see if I can get
faster throughput than the loopback adapter within the same controller. I
will definitely let you know what the final outcome is. Thanks for the
advice.

André

On 1/14/10 6:12 AM, "Romeo Theriault" <romeotheriault [at] gmail> wrote:

>> If you do not need snapshots then maybe vol copy will do what you need.
>
> vol copy can copy snapshots as well. From 7.2.6.1 vol man page,
>
>> vol copy start [ -S | -s snapshot ] source destination
>>
>>               Copies all data, including snapshots, from one vol-
>>               ume to another. If the -S flag is used, the com-
>>               mand copies all snapshots in the source volume to
>>               the destination volume. To specify a particular
>>               snapshot to copy, use the -s flag followed by the
>>               name of the snapshot.
>
>
> Though I'm not sure this would be any faster than a snapmirror.
>
> Andre, I'd be interested to hear what your outcome of this eventually is.
>
> Thanks,

Andre.Clark at earthlink

Jan 14, 2010, 4:17 PM

Post #6 of 8 (3285 views)
Permalink

Re: SnapMirror for data migration within the same controller [In reply to]

I need to use SnapMirror because the cutover is not going to be right after
the initial copy (I have close to 6TB on multiple volumes) so I need to keep
incremental going until that time.

AC

On 1/14/10 4:54 PM, "Fox, Adam" <Adam.Fox [at] netapp> wrote:

> The vol copy option is a good one as long as you don¹t want to do incremental
> updates. Vol copy is simply an level 0-only version of SnapMirror (and it¹s
> free). What you get with SnapMirror are things like block level incrementals,
> the ability to schedule those updates, qtree-level replication options, the
> ability to resync after a break without re-initialization, sync and semi-sync
> options, and probably a few others.
>
> -- Adam Fox
> Systems Engineer
> adamfox [at] netapp
>
>
> From: Romeo Theriault [mailto:romeotheriault [at] gmail]
> Sent: Thursday, January 14, 2010 6:12 AM
> To: Michael Schipp; André M. Clark
> Cc: toasters [at] mathworks
> Subject: Re: SnapMirror for data migration within the same controller
>
>> If you do not need snapshots then maybe vol copy will do what you need.
>
>
> vol copy can copy snapshots as well. >From 7.2.6.1 vol man page,
> vol copy start [ -S | -s snapshot ] source destination
>
> Copies all data, including snapshots, from one vol-
> ume to another. If the -S flag is used, the com-
> mand copies all snapshots in the source volume to
> the destination volume. To specify a particular
> snapshot to copy, use the -s flag followed by the
> name of the snapshot.
>
>
>
> Though I'm not sure this would be any faster than a snapmirror.
>
> Andre, I'd be interested to hear what your outcome of this eventually is.
>
>
> Thanks,

john.stoffel at taec

Jan 15, 2010, 6:42 AM

Post #7 of 8 (3277 views)
Permalink

Re: SnapMirror for data migration within the same controller [In reply to]

André> I need to keep snapshots so vol copy is out. Also, it will
André> still use the internal loopback adapter. What I am trying to
André> do is see if I can get faster throughput than the loopback
André> adapter within the same controller. I will definitely let you
André> know what the final outcome is. Thanks for the advice.

Do you have spare network interfaces? You could spin up another
interface with a new IP and try copying via that path:

snapmirror initialize -S filer:/vol/a filer-eth1:/vol/a_new

That might be faster than the loopback. But I wonder if the real
issue is come other bottleneck. Are the new volumes/RGs on different
fibre channel controllers as well?

Thanks,
John
John Stoffel - Senior Staff Systems Administrator - System LSI Group
Toshiba America Electronic Components, Inc. - http://www.toshiba.com/taec
john.stoffel [at] taec - 508-486-1087

Andre.Clark at earthlink

Jan 15, 2010, 1:44 PM

Post #8 of 8 (3275 views)
Permalink

Re: SnapMirror for data migration within the same controller [In reply to]

So after trying a wide variety of things there was nothing that I could do
to prevent snapmirror from using the loopback adapter for in controller
snapmirrors. I really wish that 7G had the volume move command like GX.

Thanks anyway for the suggestions.

AC

On 1/15/10 1:38 AM, "Nils Vogels" <bacardicoke [at] gmail> wrote:

> What you could try (and I don't know if it works) is specify the
> snapmirror destination as the interface IP of one of your ethernet
> interfaces ?
>
> Greetings,
>
> Nils
>
> On Fri, Jan 15, 2010 at 01:15, André M. Clark <Andre.Clark [at] earthlink>
> wrote:
>> Romeo,
>>
>> I need to keep snapshots so vol copy is out. Also, it will still use the
>> internal loopback adapter. What I am trying to do is see if I can get
>> faster throughput than the loopback adapter within the same controller. I
>> will definitely let you know what the final outcome is. Thanks for the
>> advice.
>>
>> André
>>
>>
>> On 1/14/10 6:12 AM, "Romeo Theriault" <romeotheriault [at] gmail> wrote:
>>
>> If you do not need snapshots then maybe vol copy will do what you need.
>>
>> vol copy can copy snapshots as well. From 7.2.6.1 vol man page,
>>
>> vol copy start [ -S | -s snapshot ] source destination
>>
>>               Copies all data, including snapshots, from one vol-
>>               ume to another. If the -S flag is used, the com-
>>               mand copies all snapshots in the source volume to
>>               the destination volume. To specify a particular
>>               snapshot to copy, use the -s flag followed by the
>>               name of the snapshot.
>>
>>
>> Though I'm not sure this would be any faster than a snapmirror.
>>
>> Andre, I'd be interested to hear what your outcome of this eventually is.
>>
>> Thanks,
>>
>
>

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads