ONTAP Discussions

Moving root volume

JOHNYTHENMARRY

  Hi,

  I need to move the root volume form one aggregate to another onthe same filer. Can we use vol copy command and destroy the existing aggregate.
If someone knows the steps please share

Thanks

Johny

1 ACCEPTED SOLUTION

jhenschell

Hi Johny, here is the method I just recently used to move vol0;

1.       Disable the cluster: cf disable

2.       Check the size of current vol0: vol size vol0

3.       Create a new root volume on the SATA aggr:   vol create vol0_new aggr0_sas <SIZE>

4.       Copy the data to the new volume: ndmpcopy /vol/vol0 /vol/vol0_new

5.       Rename the old root volume: vol rename vol0 vol0_old

6.       Rename the new root volume: vol rename vol0_new vol0

7.       Flag the new root volume as the root volume: vol options vol0 root

8.       Reboot the controller: reboot

9.       Confirm the SAS aggr now hosts the root vol0: aggr status                                                                                                                         on the left under Options it should say root on aggr0_sas

10.   Offline and destroy the old volume vol0: vol offline vol0_old    and    vol destroy vol0_old

View solution in original post

23 REPLIES 23

sanjivv

IGORSTOJNOV

This is interesting, I used to use ndmpcopy as well but now... How about vol move?


Wouldn't something like  vol move start vol0 <new_aggr>  accomplish the same, with a lot less legwork?

ERKANAKSOY

You can't just move root volume to another aggr. Wish it was possible.

IGORSTOJNOV

Erkan, it is possible. Did you even read this thread?

ERKANAKSOY

tried vol move on simulator 8.2.1 7m

ontap3> vol move start vol0 aggr2

vol move: Specified source volume is the root volume

ontap3>

IGORSTOJNOV

Oh, you weren't speaking in general but the actual vol move procedure. Sorry!

Hm, I guess it's not possible. That's too bad. The phases vol move goes through seem to be designed not to allow any data loss and I've used it many times on production volumes. I suppose root volume is a different sort. Thanks for the test!

scottgelb

Note that in 7-mode vol move is onl y for San volumes and only intra node. With cDot both NAS and San intra or internode. CDot root move is a bit different in that it is rebuilt instead of copied. 8.2 makes it pretty easy but not as easy as 7-mode. 8.1 cDot was much more involved to move root.

kkaushal2

Below is what I have used in past

USING NDMP:

1. Enable NDMPD

2. ndmpcopy /vol/vol0 /vol/<new vol0>

3. cifs terminate

4. vol rename vol0 vol0_old (rename existing root volume)

5. vol rename <new_vol0> vol0 (rename new root volume to vol0)

6. vol options vol0 root

7. Reboot Storage System

8. Test FilerView access (prior to Ontap 8.1). Normally this does not work anymore, so run "secureadmin setup ssl" to recreate the ssl certificate, and filerview should work again

9. vol offline vol0_old

10. Check access to C$ share

jhenschell

Hi Johny, here is the method I just recently used to move vol0;

1.       Disable the cluster: cf disable

2.       Check the size of current vol0: vol size vol0

3.       Create a new root volume on the SATA aggr:   vol create vol0_new aggr0_sas <SIZE>

4.       Copy the data to the new volume: ndmpcopy /vol/vol0 /vol/vol0_new

5.       Rename the old root volume: vol rename vol0 vol0_old

6.       Rename the new root volume: vol rename vol0_new vol0

7.       Flag the new root volume as the root volume: vol options vol0 root

8.       Reboot the controller: reboot

9.       Confirm the SAS aggr now hosts the root vol0: aggr status                                                                                                                         on the left under Options it should say root on aggr0_sas

10.   Offline and destroy the old volume vol0: vol offline vol0_old    and    vol destroy vol0_old

View solution in original post

JOHNYTHENMARRY

Hi,

Thanks for you input and i could change the root Vol to diffrent Aggr

Thanks

Johny

scottgelb

Looks good... I would add a step at the end "priv set advanced ; rm /vol/vol0/restore_symboltable" to clean up the ndmpcopy

jhenschell

Thanks Scott. That’s a step I’ve not heard of before.

FLNASHSMS

I haven't done it on a production system, but I have in pre-deployment and on a simulator using the procedure at https://communities.netapp.com/thread/14353

scottgelb

sure...check your vol0 and you will see the restore_symboltable file left behind..

davidrnexon

Hi Johny, I usually use snapmirror to copy the root vol from one aggregate to another, once the snapmirror is finished, I quiesce it, break it, remove the baseline snapshots, mark the vol as root which then marks the new aggregate as root.

The either reboot the controller or issue a cf takeover and cf giveback

mjschneider

Just remember that "reboot" is required after setting 'vol options <volname> root'.  Doing a failover won't suffice.

aborzenkov

Just remember that "reboot" is required after setting 'vol options <volname> root'.  Doing a failover won't suffice.

It will. cf takeover/cf giveback is enough. It provides for moving root volume almost non-disruptively (almost because existing NFS mounts will still become stale and need remount)

scottgelb

Good discussion here... most use snapmirror, vol copy or ndmpcopy.  Lately I use vol copy -S since less to clean up after. and copies all root with all snaps.. for snapmirror the baseline snaps  are an extra clean up step (although good to keep incremental updates prior to cutover if that is goal).  For ndmpcopy, many leave (but I prefer to delete) the restore_symboltable file on the target... not needed after the copy and cutover so good to delete and clean up root by removing that file which can be fairly large.  But I always like having a snapmirror copy of root on a different aggregate as backup (discussion of that on some other posts here).

scottgelb

Another thought... if 32 bit root and you want to go to 64-bit root ndmpcopy is usually the best method or only method... unless on 8.1 where you can snapmirror 32 to 64 but can't vol copy 32 to 64bit.

mjschneider

aborzenkov wrote:

Just remember that "reboot" is required after setting 'vol options <volname> root'.  Doing a failover won't suffice.

It will. cf takeover/cf giveback is enough. It provides for moving root volume almost non-disruptively (almost because existing NFS mounts will still become stale and need remount)

I'm echoing what a netapp installer told me just last week.  But to be honest i'd take your word over the installer's

Announcements
Register for Insight 2021 Digital

INSIGHT 2021 Digital: Meet the Specialists 2

On October 20-22, gear up for a fully digital, totally immersive virtual experience with a downright legendary lineup of world-renowned specialists. Tune in for visionary conversations, solution deep dives, technical sessions and more.

NetApp on Discord Image

We're on Discord, are you?

Live Chat, Watch Parties, and More!

Explore Banner

Meet Explore, NetApp’s digital sales platform

Engage digitally throughout the sales process, from product discovery to configuration, and handle all your post-purchase needs.

NetApp Insights to Action
I2A Banner
Public