What tool and recommended parameters would meet the requirements of moving a FileBound document storage directory to prep for moving the FileBound Document Storage Location to a new server or directory?
I would suggest that you start copying the FileBound storage location to a new server using Microsoft’s RoboCopy command as soon as is feasible. This command will help to maintain identical copies of a directory structure to the destination. So, initially you could kick it off and once the first run completes you can run it again daily to keep the directories synchronized until you are ready to move the FileBound Document Storage Location to the new directory/server. Subsequent runs only copies directories and files the destination doesn’t have so it should be much faster after the initial run. You could also time the subsequent runs to estimate the amount of time it will take just before moving to the new FileBound server.
Listed below is the command with certain options turned on that has been used many times to do this sort of thing; however I would suggest that you test it first to become familiar with it and read up on the options that have been enabled. The /MIR option copies subdirectories including empty directories and deletes destination files and directories that no longer exist in the source. I have included a few websites with information about this command below. You will need to run this as an administrator (run as administrator).
RoboCopy with Useful Options
robocopy "F:\source" "F:\destination" /E /MIR /COPYALL /MT /LOG:"F:\folder.txt" /B /R:1 /W:1
***Use the /MIR switch carefully since it will be deleting files that do not match in the destination directory.***
RoboCopy Information
https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/robocopy#remarks