Hello,
This is the workflow that has worked for us and we have been using this sequence to successfully transition 7-mode CIFS volumes to clustered ONTAP.
Maintenance Steps (CIFS with AD Authentication)
- Shut down all applications running on the CIFS share.
- Make a list of all CIFS shares and current CIFS sessions on 7-mode:
<7-mode>: vfiler run <vfiler_name> cifs shares
<7-mode>: vfiler run <vfiler_name> cifs sessions
- Gracefully terminate CIFS service on the vFiler:
<7-mode>: vfiler run cifs terminate –t 5
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.
- 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:
<7-mode>: vfiler run <vfiler_name> 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.
- Configure CIFS on the SVM with the original 7-mode identity.
Now that the original 7-mode CIFS identity is “free”, it can be applied to the SVM:
<c-dot::> vserver cifs modify -vserver <SVM> -cifs-server <7-mode_CIFS_server> -domain <domain_name> -ou <OU> -status-admin up
Create an AD computer account for the original CIFS identity as it was removed in Step 5 and “cifs modify” command will not automatically add the AD object.
Verify CIFS server is now running with the 7-mode identity:
<c-dot::> vserver cifs show –vserver <SVM>
- Trigger snapmirror update from 7MTT.
- Apply configuration and move project to Precutover phase.
Note: Ensure that CIFS server is running on the target SVM!
- Initiate one last incremental update.
This is needed in order to minimize the amount of data that to be transferred during cutover phase.
- Perform cutover.
- Offline interfaces on 7-mode:
7-mode> ifconfig <interface> down
7-mode> ifconfig <interface> 0.0.0.0
- Enable lifs on c-DOT:
cluster::> net int show –vserver <SVM>
cluster::> net int modify –lif <lif_name> -admin-status <up>
- Update DNS and AD computer account.
Update DNS to point the CIFS IP to the original CIFS identity name. Remove the temporary AD computer account which was automatically created during vFiler CIFS setup in Step 5.
- Verify CIFS configuration on SVM:
- verify CIFS lif is up
- 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
- modify the convert-ucode option on all transitioned volumes:
vol modify -convert-ucode true
- update the ls-mirrors for the SVM root volume:
snapmirror update ls-volume-set
- Verify 7-mode configuration on vFiler:
- verify snapmirror relationship is deleted
- verify source volumes are taken offline
- 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.
- Start applications.
Verify everything works as expected and no issues are detected.
- Clean-up tasks:
- delete vserver peer relationship
- update RC file on 7-mode
- decrease volume size to the original value if volumes have been increased before baseline
- delete snapmirror base snapshots on the SVM
- delete 7-mode snapshots after they expire
- Ensure that project is completed on 7MTT.
Good luck with your upcoming CIFS transitions!