Most of my file server installs these days seem to involve far too much downtime. The actual server install isn't too bad but migrating the data takes forever now that we have 1TB+ arrays we need to worry about. My typical method is to strip share permissions and use robocopy to copy all of the data over. Rather than wait for all of the data to copy over, I'd prefer to copy the data over the night before, then sync over changes after I strip permissions to the old server. Is there a nice way of doing this on Windows? I've looked into using DFS-R to accomplish this, but I'd prefer something a little...eh...smaller.
- Why not just use run robocopy for the main copy ahead of time,then run it again to copy the changes when you have disabled access? If you use the right command line robocopy will just copy things that have changed.Zoredache– Zoredache2010-09-13 20:23:57 +00:00Commented Sep 13, 2010 at 20:23
3 Answers
Couldn't you continue to use Robocopy and use some of the advanced file selection options? So over night you would basically robocopy X:\*.* Y: /M. Then when you want to sync up, do the same thing. This should have the effect of copying all the files with the archive bit, and resetting the bit, then the next time it would copy anything that has it's archive bit set (and reset it again).
- +1, that's how i've done several multi-TB migrations on Linux: run rsync with low priority (perhaps over several days); once it finishes, run it again, and maybe a third time. then stop service, rsync once more and start up replacement. at worst, 10-15 mins of downtimeJavier– Javier2010-09-13 19:20:37 +00:00Commented Sep 13, 2010 at 19:20
- This is how I've done it with Solaris too.user9517– user95172010-09-14 09:16:33 +00:00Commented Sep 14, 2010 at 9:16
DFS-R. Works like a charm, without taking the server down. I never expose a server directly to users - all access is always done using DFS shares. actually my setups normally have 1-multiple DFS trees, most only one.