Network Storage Protocols Discussions

CIFS vFiler Migration to Cluster Mode

TMADOCTHOMAS

I have seen some contradictory information on migrating a CIFS vFiler in 7-Mode to a CIFS Server in an SVM in Cluster Mode and would like to see if anyone can provide some clarity.

 

First, the basics: I have six vFilers to migrate, each going into their own SVM.  For all of them, we are preserving the identity of the vFiler - i.e. we want the name to stay the same once it is functional in Cluster Mode.  For five of the six, we want to migrate the IP address as well.  For one of them we want a new IP.

 

I was under the impression that in order to preserve the vFiler's identity, I had to create a temporary CIFS server on the Cluster Mode system during the 7MTT migration.  At cutover, I would terminate CIFS on the 7-mode system, tear down the CIFS server on the Cluster Mode system, and recreate it with the identity of the vFiler from the 7-Mode system.  We would then complete the migration.

 

However, having read tr-4336, page 61, and the 7MTT 2.0 Data and Configuration Transition Guide, page 58, it appears that I have it backwards.  These documents appear to say that, before pre-cutover, I need to terminate CIFS on the 7-mode system, tear down the vFiler on the 7-Mode system, and recreate it with a temporary name before pre-cutover.  I would then need to create the new CIFS Server on the cluster mode system using the identity of the original vFiler.

 

I would be interested in hearing from anyone who has performed migration of CIFS vFilers.  The main things I'm trying to determine are:

  1. Do I need a temporary CIFS Server on the Cluster Mode system, or a temporary vFiler on the 7-Mode system?  Or do we need all three running at the same time - the original vFiler and a temporary vFiler AND CIFS Server?
  2. If the latter, if the goal is to preserve the 7-Mode configuration information so it can be transitioned, how is that possible if I am creating a new vFiler, presumably using the same root volume as before, which wipes out the original configuration?

Any thoughts or advice will be appreciated!

25 REPLIES 25

DLista
Hello guys, I'm new on migration and still learning. I don't understand how do you migrate the data previous to configure the cifs vserver on the cdot. How do you configure the vserver destination? That's not clear for me.

naga_queen

Hello,

 

This is the workflow that has worked for us and we have been using this sequence to successfully transition 7-mode vFilers with CIFS volumes to clustered ONTAP.

 

MAINTENANCE STEPS

 

1. Close open files and sessions on the CIFS share.
2. Write down the CIFS share configuration and current sessions on 7-mode.
3. Gracefully terminate CIFS service on the vFiler.
Note: it is not a requirement to disconnect CIFS shares from client end. The best practice is to discontinue connectivity from storage side. However, if there will be any IP or share name/path changes, shares must be disconnected from client end as well and re-connected after cutover.
4. Assign a temporary CIFS server name on the vFiler and update DNS.
Re-run CIFS setup on the vFiler in order to reconfigure the CIFS server to use a temporary name.
Update DNS to point the IP to this temporary name. Remove the AD computer account for the original CIFS server identity. A new AD computer account with the temporary identity will be automatically created during CIFS setup.
Note: CIFS service should be running with the new temporary identity because it is required to read CIFS configurations from the vFiler during pre-cutover phase. 
5. Configure CIFS on the SVM with the original 7-mode identity ("vserver cifs modify" command for ONTAP 9.0 or later).
Create an AD computer account for the original CIFS identity and verify CIFS server is now running with this identity.
6. Apply configuration and move project to Precutover phase.
Note: Ensure that CIFS server is running on the source vFiler and the target SVM!
7. Perform cutover.
8. Update DNS and AD computer account.
Update DNS to point the CIFS IP to the original CIFS identity. Remove the temporary AD computer account which was automatically created during vFiler CIFS setup along with the temp CIFS server which was initially configured on the SVM.
9. Perform cleanup tasks.
- verify CIFS lif is up on the SVM
- remove the CIFS lif which has been initially configured on the SVM so that it could be temporarily joined to the AD domain
- verify volume is online and writable, and shares are visible
- verify CIFS export policy and rule are applied on the SVM
- verify volume is junctioned into the SVM namespace
Note: if volume was transitioned with its 7-mode path, unmount the volume from /vol directory and mount it into the SVM namespace (/).
- delete vserver peer transition relationship
- update the ls-mirrors for the SVM root volume
10. Ensure CIFS shares are accessible from client end.
Connect shares with the new path along with all prefixes (if /vol direstory has been removed). Ensure write operations are successful.

 

Good luck with your upcoming CIFS transitions!

TMADOCTHOMAS

DLista, see my post at the top of this page, I think it may answer some of your questions. if not, post again.

TMADOCTHOMAS

Thanks John.  So, to summarize, here are the steps we would perform prior to cutover:

 

  • Stop all connections to the vFiler.
  • Rename the vFiler to a temporary name, update DNS to point the IP to the temporary name, and remove the AD computer account/add a new AD computer account with the temporary name
  • Once migration is complete, THEN turn off the original vFiler, update DNS to point the IP to the permanent name again, remove the temporary AD computer account, and join the new CIFS Server to the domain

On the second bullet, would it be better to have a temporary IP to go with the temporary name?  That way no DNS/AD changes are needed (I would assume).  We just change the vFiler name and CREATE a temporary DNS entry and AD computer account to go with the temporary name.  Then after cutover completes, we just turn off the temporary DNS/AD/vFiler, and create the CIFS Server with the original identity on the cdot system.

--John--

Yes, that would be best.

TMADOCTHOMAS

So I began our test this morning, and it didn't work.  The 7MTT did in fact require that a temporary CIFS Server be configured on the destination SVM, which I had removed.  Instead, I had renamed the 7-Mode vFiler to a temporary name before attempting cutover.  Any ideas here?  Do we actually need TWO temporary names/IPs, one to set up a temporary vFiler name, and one to set up a temporary CIFS Server?

TMADOCTHOMAS

FYI I think I've figured it out.  Apparently, after renaming the CIFS Server on the 7-mode system, the CIFS Server in Cluster Mode should be configured with the original vFiler identity BEFORE cutover.  I had been under the impression that this final step should only be done after transition is complete.  Will retest later today.

TMADOCTHOMAS

For the record if anyone searches this topic, that worked great!  Share definitions are even copied over, which I've not seen documented anywhere - apparently this capability was added in a recent revision of the 7MTT.

LITTLEREDCAR

Just curious to know if you have any updates to share on this topic, i'm in the same process of migrating CIFS share from 7 mode to clustermode and would like to pick your brain on this process.

TMADOCTHOMAS

What do you want to know?  I am about to do our first migration hopefully later this week.

atb29

Hi THOMAS i will migrate some vfiler units with 7mtt 2.0 to cdot 8.3 and i want to preserve the same cifs server name. Finally what has been the steps you made to solve it?

 

Thanks

TMADOCTHOMAS

Here is what worked for us:

Assign a temporary IP to the SVM.

Run the 7MTT to replicate the data.  (NOTE: We didn't include the option to transition the IP address because the 7MTT includes default settings for LIFs we didn't like).

When you are ready to cutover, re-run cifs setup on the SOURCE system and rename the CIFS Server to a temporary name (be sure you already had a DNS entry created for the temporary name).

Run the cutover commands on the 7MTT.

After cutover, create the permanent LIF manually for the SVM (if you had the 7MTT do this then you don't need to do it manually).

If everything is working, decommission the vFiler with the temporary name on the source system, and remove the LIF with the temporary IP on the SVM.

Anand0786

Did you create original CIFS server name on SVM before cutover(along with original DNS entry)

 

 

Run the 7MTT to replicate the data.  (NOTE: We didn't include the option to transition the IP address because the 7MTT includes default settings for LIFs we didn't like).

When you are ready to cutover, re-run cifs setup on the SOURCE system and rename the CIFS Server to a temporary name (be sure you already had a DNS entry created for the temporary name).

**Create original CIFS server identity on SVM before cutover--Is that right ?

Run the cutover commands on the 7MTT.

After cutover, create the permanent LIF manually for the SVM (if you had the 7MTT do this then you don't need to do it manually).

If everything is working, decommission the vFiler with the temporary name on the source system, and remove the LIF with the temporary IP on the SVM.

TMADOCTHOMAS

No - at cutover we changed the existing CIFS Server on 7-mode to a temporary name, then ran CIFS Setup on the SVM and used the original CIFS Server name then ran cutover. Strange sequence but it worked mutiple times. I wondered if it was right myself! Documentation was very incomplete. Thankfully I had a test system and some resources to ask and was able to figure it out.

Anand0786

Thanks! and i believe no DNS changes was required ? And are the changes at 'pre-cutover' or 'Storage cutover' phase of 7mtt?

TMADOCTHOMAS

Actually we pre-created a DNS entry for the temporary CIFS Server name.Right before we clicked Apply Configuration and Complete Transition in 7MTT, we did this:

 

  1. On the 7-mode source system, terminate CIFS, re-run CIFS Setup and rename the CIFS Server with the temporary name.
  2. On the cdot destination system, create the CIFS Server with the original name. It is using a temporary LIF we added to the SVM.

After finishing the 7MTT process, we then stopped the 7-mode CIFS Server completely which allowed us to re-use the original IP. We added the original IP to the SVM on cdot and removed the temporary one. I hope that helps!

SeanHatfield

On recent versions of ONTAP you also have the option of completing the cutover on the temp cifs ID, then modifying the vserver's cifs-server name.

 

If this post resolved your issue, help others by selecting ACCEPT AS SOLUTION or adding a KUDO.

TMADOCTHOMAS

Thanks for the tip! That's good to know as we will have several more 7MTT jobs next year as we try to upgrade our 2220's to cdot.

john_higgins

Did you clear the credential cache, I saw that as a required step opn the source vFiler when you give it the temporary/new name, maybe its not always needed ot just generates erors in logs.  Just interersted to know if you did that step.

TMADOCTHOMAS

John,

 

I'm afraid I'm not familiar with clearing the credentials cache. We migrated three CIFS servers and didn't have to do that. Doesn't mean we might have needed to in certain circumstances.

Announcements
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