What is the best way to migrate data ?

[IT Staff]

Currently we are using a 3rd party software to synchronise data between 3
countries offices. Only 1 master source, the other 2 sites are "receiver".

Therefore technically 3 servers have similar files/folders.

We are planning to use DFRS, windows 2003 r2.

The master source office is going to close down and move to a new location.

In the new location, can i setup a server with DFRS and then use the other 2
sites to push its files to the new location using MESH/custom topology ?
After complete synch, then i make the new location a hub-spoke again ?

[HAL07]

Post by IT Staff
Currently we are using a 3rd party software to synchronise data between 3
countries offices. Only 1 master source, the other 2 sites are "receiver".
Therefore technically 3 servers have similar files/folders.
We are planning to use DFRS, windows 2003 r2.
The master source office is going to close down and move to a new location.
In the new location, can i setup a server with DFRS and then use the other 2
sites to push its files to the new location using MESH/custom topology ?
After complete synch, then i make the new location a hub-spoke again ?

Don't think so difficult. Just shut down the server at first location. Then set up the new server at the new location.
Then robocopy all data from one of the "receivers" to the new location.
Then make the new folder a member of the DFS and you are back on track. Remove the old server in the end.

[IT Staff]

The estimated size of folders is about 73gb.

Is it recommeded to robocopy via the WAN ?

Post by HAL07
Don't think so difficult. Just shut down the server at first location.
Then set up the new server at the new location.
Then robocopy all data from one of the "receivers" to the new location.
Then make the new folder a member of the DFS and you are back on track.
Remove the old server in the end.
--
-- HAL07, Engineering Services, Norway

[DaveMills]

If you are going to use Robocopy over the WAN why not just let DFSR do the
replication. The data transfer will be a similar size. Pre-staging is only worth
it is you are transferring the data by some other out of bandwidth method (tape
etc.)

Consider setting up the new server and synchronizing the data on the same site
then shipping the server to the new location with the data already on it.

Post by IT Staff
The estimated size of folders is about 73gb.
Is it recommeded to robocopy via the WAN ?

Post by HAL07
Don't think so difficult. Just shut down the server at first location.
Then set up the new server at the new location.
Then robocopy all data from one of the "receivers" to the new location.
Then make the new folder a member of the DFS and you are back on track.
Remove the old server in the end.
--
-- HAL07, Engineering Services, Norway

[HAL07]

Post by DaveMills
If you are going to use Robocopy over the WAN why not just let DFSR do the
replication. The data transfer will be a similar size. Pre-staging is only worth
it is you are transferring the data by some other out of bandwidth method (tape
etc.)
Consider setting up the new server and synchronizing the data on the same site
then shipping the server to the new location with the data already on it.

Post by IT Staff
The estimated size of folders is about 73gb.
Is it recommeded to robocopy via the WAN ?

Post by HAL07
Don't think so difficult. Just shut down the server at first location.
Then set up the new server at the new location.
Then robocopy all data from one of the "receivers" to the new location.
Then make the new folder a member of the DFS and you are back on track.
Remove the old server in the end.

Don't use DFS for initial syncs of large data. You will need large staging folders and you it will take a long time before all
servers are in Sync. It will also affect ALL servers in the replication groups whilst the empty servers data is filled. I highly
recommend robocopy first before adding the server as member. It's not important that the robocopy contain very fresh data, as DFS
will detect the files and start syncing the changed files immediately after becoming a member (note that DFS members read the
membership info from domain so you might speed that schedule up by using DFSRDIAG POLLAD command)

[DaveMills]

Post by HAL07

Post by DaveMills
If you are going to use Robocopy over the WAN why not just let DFSR do the
replication. The data transfer will be a similar size. Pre-staging is only worth
it is you are transferring the data by some other out of bandwidth method (tape
etc.)
Consider setting up the new server and synchronizing the data on the same site
then shipping the server to the new location with the data already on it.

Post by IT Staff
The estimated size of folders is about 73gb.
Is it recommeded to robocopy via the WAN ?

Post by HAL07
Don't think so difficult. Just shut down the server at first location.
Then set up the new server at the new location.
Then robocopy all data from one of the "receivers" to the new location.
Then make the new folder a member of the DFS and you are back on track.
Remove the old server in the end.

Don't use DFS for initial syncs of large data. You will need large staging folders and you it will take a long time before all
servers are in Sync. It will also affect ALL servers in the replication groups whilst the empty servers data is filled. I highly
recommend robocopy first before adding the server as member. It's not important that the robocopy contain very fresh data, as DFS
will detect the files and start syncing the changed files immediately after becoming a member (note that DFS members read the
membership info from domain so you might speed that schedule up by using DFSRDIAG POLLAD command)

I see. I have used DFSR for initial replication but only with two servers in the
group. Then it does not make so much difference but I can see why when there are
more than 2 replicas