Windows Vista Tips

Windows Vista Tips > Newsgroups > Windows Server > File Systems > What is the best way to migrate data ?

Reply
Thread Tools Display Modes

What is the best way to migrate data ?

 
 
IT Staff
Guest
Posts: n/a

 
      07-07-2009

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 ?





 
Reply With Quote
 
 
 
 
HAL07
Guest
Posts: n/a

 
      07-07-2009
IT Staff wrote:
> 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.

--
-- HAL07, Engineering Services, Norway
 
Reply With Quote
 
IT Staff
Guest
Posts: n/a

 
      07-08-2009
The estimated size of folders is about 73gb.

Is it recommeded to robocopy via the WAN ?



>
> 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



 
Reply With Quote
 
DaveMills
Guest
Posts: n/a

 
      07-08-2009

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.

On Wed, 8 Jul 2009 09:48:43 +0800, "IT Staff" <> wrote:

>The estimated size of folders is about 73gb.
>
>Is it recommeded to robocopy via the WAN ?
>
>
>
>>
>> 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

>

--
Dave Mills
There are 10 types of people, those that understand binary and those that don't.
 
Reply With Quote
 
HAL07
Guest
Posts: n/a

 
      07-08-2009
DaveMills wrote:
> 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.
>
> On Wed, 8 Jul 2009 09:48:43 +0800, "IT Staff" <> wrote:
>
>> The estimated size of folders is about 73gb.
>>
>> Is it recommeded to robocopy via the WAN ?
>>
>>
>>
>>> 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)

--
-- HAL07, Engineering Services, Norway
 
Reply With Quote
 
DaveMills
Guest
Posts: n/a

 
      07-08-2009

On Wed, 08 Jul 2009 09:33:43 +0200, HAL07 <> wrote:

>DaveMills wrote:
>> 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.
>>
>> On Wed, 8 Jul 2009 09:48:43 +0800, "IT Staff" <> wrote:
>>
>>> The estimated size of folders is about 73gb.
>>>
>>> Is it recommeded to robocopy via the WAN ?
>>>
>>>
>>>
>>>> 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
--
Dave Mills
There are 10 types of people, those that understand binary and those that don't.
 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Migrate data to new SAN storage Steve Server Migration 15 07-25-2008 02:59 AM
Migrate Data from Sharepoint 2.0 to 3.0 WallScott Windows Small Business Server 7 01-10-2008 03:43 PM
Migrate data from samba server Windows Fans Active Directory 1 06-06-2007 05:18 PM
Migrate DNS data from NT4 to W2K3 Caio Wendel Server Migration 1 01-18-2006 07:43 PM
Re: Migrate Data Miha Pihler Windows Server 0 11-19-2004 01:10 PM



1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59