Jump to content

Recommended Posts

Posted

Morning,

 

I have to replace a file server running 2008R2 with a 2012R2 server my question is regarding the data on the server and the best way to migrate it to the new server so am i best off,

 

  • setting up DFS on the new server and transferring it that way (If so any advice on how to do this please)

 

or

 

  • Using XCOPY with the appropriate switches i.e. XCOPY D:\Data D:\Data /X/H/E/V/D/Y and then just re-applying the relevant shares as the command will take across all the existing permissions.

 

I have never used DFS before so would like to know the process of migrating the data across and if it's more efficient than DOS.

 

Cheers in advance.

Posted
I guess you want to use replication with DFS (DFS-R). The last time I did this (we have used DFS-R for years) I seeded the shares with Robocopy after creating the DFS replications. I think this was MS's recommended method. You could just let it seed itself, but it can be pretty slow.
Posted
Just looking at the available options as it's the only file server on the site so as far as I can see doesn't really need DFS, I was only considering this as an option as someone had previously installed it on the existing FS. I can't actually see any reason why I would need it on the new server just wondered it it would make the migration easier, I may look into the Server Migration Toolkit unless there is another valid reason for having DFS.
Posted

Whilst i've never used replication etc, one benefit of having DFS setup - if it's setup at the domain level is users paths/shortcuts etc in theory all continue to work after file server is changed.

 

i.e. if user's user area is mapped to \\domain\users\staff\fred - and \\domain\users\staff points to \\fileserver1\staff$ for instance. Any documents/macros or weird stuff like that store a file path continue to work as you would update the mapping to fileserver2.

Posted
With a single server (no replication), DFS makes migration easier because you never need to update file paths, profile paths etc - you only ever need to point them at domain.com\path and when you replace or update a server in future it's seamless. You can use the replication feature to help migration then switch it off when you retire the old server.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...