Can I use MS storage migration service in conjunction with DFS namespace to migrate file servers from 2012 to 2019 MS Server STD?
Hi Everyone and thanks in advance for all insights and suggestions.
Getting ready to migrate existing physical 2012 file servers to a virtual 2019 file server.
Each file server hosts its own DFS namespace, which could be moved to DC as host and several hundred GB worth of folders/files.
The last time I did this I moved the DFS namespace, made both old and new server DFS namespace host, used Robocopy to copy everything over and then removed old server from DFS namespace. Done. Had to use Robocopy since I had issues getting it to replicate overall items to the new server.
This time I was going to use the storage migration service from MS and was wondering if it can also take care of the DFS namespace step and/or if not can I just move the namespace and then use the storage migration service to copy the folders etc. as I know it maintains permissions and shares when doing it.
Thoughts?
Method is to do initial copy, then do incrementals to keep the copy fresh, and when ready to cut over, remove access to the shares, run a final copy, change the DFS path and then allow on the new.
I have used DFS replication to do get the shares in sync, but this can take longer than robocopy...
Robocopy does a raw copy, the DFS-R might use compression....
We use it for all of our non-SMS based data migrations.
Right click and Run As Admin then tick the "Copy NTFS Permissions" along with "Keep original file dates".
It's multi-threaded and caches the file/folder catalog to make things really simple and fast.
ASKER
One can set the view between source and destination to "Differences" to see what was missed.
Not sure how RoboCopy would allow for such a simple way to know where it choked and why.
given the existence of DFS-replication that wil maintain the data in sync, the only reason commonly to use robocopy was to prestage, but unlike DFS-replication that can be configured with a limit on the consumption of bandwidth, robocopy would not me limited and will need to be run multiple times to capture ......
And requires that one use the correct options for robocopy.
IMHO, if you want to prestage, use a backup/restore
Computer data storage, often called storage or memory, is a technology consisting of computer components and recording media used to retain digital data. In addition to local storage devices like CD and DVD readers, hard drives and flash drives, solid state drives can hold enormous amounts of data in a very small device. Cloud services and other new forms of remote storage also add to the capacity of devices and their ability to access more data without building additional data storage into a device.
TRUSTED BY
DFS replication will not (by default) replicate any .tmp .bak files or files marked as temporary. This means files that have a temporary attribute 0x100 you can use a powershell script to run through the file to identify if files are marked temporary and if strip/remove this attribute.
https://community.spiceworks.com/scripts/show/1102-remove-temp-file-attribute
Deals with going through the directory structure of every file to see if it has the 0x100 attribute set, if it is set, it strips it out.
Make sure to exclude the DfsrPrivate ...
DFS name space migration? When you add a DC, the DFS namespeace is within the AD. The switch in targets .......is all that you have to address, but adding the new one, and prioritizing, or better deprioritizing the one you wish to retire from the referral portion.
Then as users/clients start connecting to the new DFS name space server, you can remove the old server as a target (disable)