Move data on another controller

[maillon133]

Hello,

I want to know if it's possible to move quickly volumes (contains Luns) on another controller (on dataontap v8) ? I would move 5To.

I believe there are datamotion for volume (but only on the same controller) and datamotion for filer (but i'm not sure).

Someone can help me ?

Thank you.

Regards,

[arunchak]

HI,

One way of migrating a volume from one filer to another is:

If you are using MEI product DFM, then you can use the space management wizard from NMC to migrate the volume from aggr of one filer to aggr of another filer.

But you will have to remove the exports or LUN maps before doing this.

Here in this example my source filer is sin and destination filer is seawasp:

Conformance Results

=== SEVERITY ===

Information:    Provision a new flexible volume of 15.0 GB from aggregate 'seawasp:Aggr2'(1226).

=== ACTION ===

Provision flexible volume of size 15.0 GB

=== SEVERITY ===

Information:    Copying data from 'sin:/JPMC_DS02'(10835) to VolToProvision:JPMC_DS02 using Volume SnapMirror.

=== ACTION ===

Copying data from source volume.

=== SEVERITY ===

Information:    Backups will be suspended on all the affected datasets during cutover period.

=== ACTION ===

Backup suspension.

=== SEVERITY ===

Information:    Finished cutting over to destination VolToProvision:JPMC_DS02

=== ACTION ===

Cutting over to destination VolToProvision:JPMC_DS02

Migration Job details:

---------------------------

[root@grafspree ~]# dfpm job details 1005

Job Id:                    1005

Job State:                 completed

Job Description:           Migrate volume 'sin:/JPMC_DS02'(10835) to aggregate 'seawasp:Aggr2'(1226).

Job Type:                  migrate_volume

Job Status:                success

Dataset Name:

Dataset Id:

Object Name:               seawasp:/JPMC_DS02

Object Id:                 10898

Started Timestamp:         26 Aug 2011 04:47:43

Abort Requested Timestamp:

Completed Timestamp:       26 Aug 2011 04:51:08

Submitted By:              root

Job progress messages:

Event Id:      8781

Event Status:  normal

Event Type:    job-start

Job Id:        1005

Timestamp:     26 Aug 2011 04:47:43

Message:

Error Message:

Event Id:      8782

Event Status:  normal

Event Type:    volume-create

Job Id:        1005

Timestamp:     26 Aug 2011 04:47:52

Message:       Provision flexible volume of size 15.0 GB

Error Message:

Volume Id:     10898

Volume Name:   seawasp:/JPMC_DS02

Event Id:                         8783

Event Status:                     normal

Event Type:                       rel-create-start

Job Id:                           1005

Timestamp:                        26 Aug 2011 04:47:59

Message:                          Starting baseline data transfer between sin:/JPMC_DS02 and seawasp:/JPMC_DS02 using SnapMirror

Error Message:

Source Volume or Qtree Id:        10835

Source Volume or Qtree Name:      sin:/JPMC_DS02

Destination Volume or Qtree Id:   10898

Destination Volume or Qtree Name: seawasp:/JPMC_DS02

Bytes Transferred:                0

Event Id:                         8784

Event Status:                     normal

Event Type:                       rel-create-end

Job Id:                           1005

Timestamp:                        26 Aug 2011 04:48:29

Message:                          Successfully completed baseline data transfer between sin:/JPMC_DS02 and seawasp:/JPMC_DS02 using SnapMirror

Error Message:

Source Volume or Qtree Id:        10835

Source Volume or Qtree Name:      sin:/JPMC_DS02

Destination Volume or Qtree Id:   10898

Destination Volume or Qtree Name: seawasp:/JPMC_DS02

Bytes Transferred:                0

Event Id:      8785

Event Status:  normal

Event Type:    job-progress

Job Id:        1005

Timestamp:     26 Aug 2011 04:48:31

Message:       Updating SnapMirror relationship between 'sin:/JPMC_DS02'(10835) and 'seawasp:/JPMC_DS02'(10898)

Error Message:

Event Id:      8786

Event Status:  normal

Event Type:    job-progress

Job Id:        1005

Timestamp:     26 Aug 2011 04:49:34

Message:       Updating SnapMirror relationship between 'sin:/JPMC_DS02'(10835) and 'seawasp:/JPMC_DS02'(10898)

Error Message:

Event Id:      8787

Event Status:  normal

Event Type:    job-progress

Job Id:        1005

Timestamp:     26 Aug 2011 04:51:01

Message:       Updated dataset membership and backup versions.

Error Message:

Event Id:      8788

Event Status:  normal

Event Type:    job-progress

Job Id:        1005

Timestamp:     26 Aug 2011 04:51:01

Message:       Successfully migrated relationships of volume 'sin:/JPMC_DS02'(10835) to 'seawasp:/JPMC_DS02'(10898).

Error Message:

Event Id:      8789

Event Status:  normal

Event Type:    job-end

Job Id:        1005

Timestamp:     26 Aug 2011 04:51:08

Message:

Error Message:

Thanks,

  Arun

[kaashyapi]

Hi

Is this Mangment Wizard is licensced

[arunchak]

One more way is,

IF you have volume on vFiler then you can migrate the vFiler from one filer to another.

Or

Create a mirror of your volume from source filer to destination, break the relationship and use the volume on destination (You will have to remap LUNs or export the volume from destination to use it).

Thanks,

  Arun

[ajeffrey]

I would also chime in here that ONTAP 8 supports a true cluster mode.  The feature your are requesting is actually the number one selling point of C-Mode. Vservers can be migrated throughout the cluster easily with no outage, taking all volumes, luns, exports, IP addresses (LIFS) with them. If this is a key requirement for you you should check out C-mode.

[arunchak]

HI,

Please note, the first option and third option are not non disruptive unlike NDVM.

Only the second option of vFiler migration you have an option of online migration (in DFM) which is non disruptive.

Thanks,

  Arun

[ajeffrey]

HI Arun,

I have to partly disagree here.  C-Mode Vserver migrations are non-disruptive provided that you are currently running  ONTAP 8.x in C-Mode, which is probably not the case here. But as you have said Data Motion is the best way to go here, but it would require some pre-work to get the target data into a vFiler.  Also he should be aware that Data Motion (vFiler migration) is not allowed between members of a cluster so you will need to move the data to a different cluster (or do a cf disable to temporarily allow it).

Cheers

Jeff

[arunchak]

Hi Jeff,

  I was only talking about 7 mode. In 7 mode the only non disruptive way to move a vol that I could think of was via the vFiler. Ofcourse if the customer plans to use cmode then what you are saying is absolutely right. Infact, thanks for pitching in and providing that information.

Thanks,

  Arun

[ajeffrey]

Sorry for the nit-picking!    My statement was more of a teaser than an actual suggestion for this particular problem.