![[H]ard|Forum](/styles/hardforum/xenforo/logo_dark.png){kind=logo}
Hello everyone,
This issue has been rearing its head for me for sometime and I keep running into roadblocks. Basically we have a FA2240 that shares out CIFS for our home directories, file shares, etc and it is all tied together in a single DFS namespace.
As we are not replacing the NetApp with another Netapp I want to migrate the data to a Windows file server and do a mass redirection of the DFS links while maintaining the NTFS permissions on the folders. My goal is to put this into VMDK's or a single VMDK for easy migration to another storage platform, easier native VMware backups, and so fourth.
I have inherited this environment to be 100% frank - I am doing everything in my power to fix the crazy antics that are in place currently.
Currently I have a Server 2012 R2 box with a 10TB volume attached to it all ready to go. Here are my ideas so far and the road blocks:
1) Use the File Server Migration Toolkit v1.2 and complete the DFS Root Consolidation Wizard and the server data migration wizard that is included. The problem I am running into is related to the Root Consolidation Wizard needing to be running Server 2003/2008 Enterprise or DC to which both are running standard.
For this option to work I need to spin up a DFS root running one of those 2 O/S's. Am I missing something?
2) I am thinking that scripting the DFS Target/Link changes and using Robocopy/Rsync may be an easier option. Basically complete a base Robocopy of the raw data from the CIFS share to seed it. Then on the cutover day issue the final copy for Robocopy and upon completion using DFScmd to unmap and remap every link/share to the proper location.
3) Use the Server Migration Toolkit - in going through the documentation it doesn't look to support my scenario as I am not really migrating from a "server"
----
I am thinking Option 2 would be the best and be the lowest risk and provide the highest level of control.
Any thoughts or insight on doing this?
This issue has been rearing its head for me for sometime and I keep running into roadblocks. Basically we have a FA2240 that shares out CIFS for our home directories, file shares, etc and it is all tied together in a single DFS namespace.
As we are not replacing the NetApp with another Netapp I want to migrate the data to a Windows file server and do a mass redirection of the DFS links while maintaining the NTFS permissions on the folders. My goal is to put this into VMDK's or a single VMDK for easy migration to another storage platform, easier native VMware backups, and so fourth.
I have inherited this environment to be 100% frank - I am doing everything in my power to fix the crazy antics that are in place currently.
Currently I have a Server 2012 R2 box with a 10TB volume attached to it all ready to go. Here are my ideas so far and the road blocks:
1) Use the File Server Migration Toolkit v1.2 and complete the DFS Root Consolidation Wizard and the server data migration wizard that is included. The problem I am running into is related to the Root Consolidation Wizard needing to be running Server 2003/2008 Enterprise or DC to which both are running standard.
For this option to work I need to spin up a DFS root running one of those 2 O/S's. Am I missing something?
2) I am thinking that scripting the DFS Target/Link changes and using Robocopy/Rsync may be an easier option. Basically complete a base Robocopy of the raw data from the CIFS share to seed it. Then on the cutover day issue the final copy for Robocopy and upon completion using DFScmd to unmap and remap every link/share to the proper location.
3) Use the Server Migration Toolkit - in going through the documentation it doesn't look to support my scenario as I am not really migrating from a "server"
----
I am thinking Option 2 would be the best and be the lowest risk and provide the highest level of control.
Any thoughts or insight on doing this?