Archived from groups: microsoft.public.win2000.file_system (More info?)

Hello

We are planning to use robocopy to move an exceptional amount of data to a
new server. We are migrating from Windows Server 2000 to Windows 2003 Server.
We have used robocopy successfully in the past, but never with anything
close to this amount of data.

Unfortunately we are talking about 480G of data, all under 1 share point.
The share point is also a little tricky. The share was created at the Volume.
So, for example...E: is shared as ShareName and all users point to this root
share.

Please let me know your thoughts and if you see any issues based on your
experience using RoboCopy.

Thank you,

Mark Clark

Archived from groups: microsoft.public.win2000.file_system (More info?)

My preferred method at this point would be to use a tape to restore and
restore the security info as well (BUExec does this by default). It sounds
like you're doing a swing upgrade from 2000 to 2003 (new hardware/new
software).

Robocopy should work. I've done about a 200+gig transfer with no issues.
If you do this method, you'll still have to setup the shares and rights to
them.

"Mark Clark" wrote:

> Hello
>
> We are planning to use robocopy to move an exceptional amount of data to a
> new server. We are migrating from Windows Server 2000 to Windows 2003 Server.
> We have used robocopy successfully in the past, but never with anything
> close to this amount of data.
>
> Unfortunately we are talking about 480G of data, all under 1 share point.
> The share point is also a little tricky. The share was created at the Volume.
> So, for example...E: is shared as ShareName and all users point to this root
> share.
>
> Please let me know your thoughts and if you see any issues based on your
> experience using RoboCopy.
>
> Thank you,
>
> Mark Clark
>

Archived from groups: microsoft.public.win2000.file_system (More info?)

i use robocopy to move between 1.5TB and 3 Tb on a weekly basis! this is one
of the most reliable tools i have.
robocopy ROCKS! some minor issues when you get using /mon or /mot switches
but otherwise it is the tool to use

Archived from groups: microsoft.public.win2000.file_system (More info?)

Mark Clark wrote:
> Hello
>
> We are planning to use robocopy to move an exceptional amount of data to a
> new server. We are migrating from Windows Server 2000 to Windows 2003 Server.
> We have used robocopy successfully in the past, but never with anything
> close to this amount of data.
>
> Unfortunately we are talking about 480G of data, all under 1 share point.
> The share point is also a little tricky. The share was created at the Volume.
> So, for example...E: is shared as ShareName and all users point to this root
> share.
>
> Please let me know your thoughts and if you see any issues based on your
> experience using RoboCopy.
>
> Thank you,
>
> Mark Clark
>

robocopy is cool. migrated around 200gb of data no probs. It can keep
security too, so you should only have to set up the share.