Hi.
The drive where one end of our DFS Namespaces exist has become corrupt. We are unable to solve with chkdsk as the drive is too big and it never finishes.
I was planning on creating a new drive (everything is virtual) on the server and use robocopy with a /mir parameter to copy the data to the new location, stop DFS services, recreate the shares in the new location and then start DFS.
However, I have read that I shouldn't 'pre-seed' with a /mir - https://docs.microsoft.com/en-us/windows-server/storage/dfs-replication/preseed-dfsr-with-robocopy
Does that apply in my situation?? I'm not really pre-seeding the files, just copying the data to a new drive. Do I need to worry about file hashing?
