Re: File Copying

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

I am familiar with Robocopy, so will maybe use that in conjunction with
psexec. I just thought that Windows would be smarter than this when
initiating a copy from a 3rd PC. Do you know if this is documented anywhere
in a KB or technet?

Thanks.

"Philip Herlihy" wrote:

SteveW wrote:
OK, this would make a little more sense, but I don't understand why the
workstation would would copy the files to it's own RAM when the files should
be copied between the servers. This had been the case with Novell and ncopy
had to be used to do a file copy that bypassed the 3rd PC. Do you know if MS
has any documentation supporting your suggestion?

I am running this by using 3rd party automated software via command line.
So, I could try using psexec to run the batch on one of the servers, but
didn't think was required. Having the file copied to local RAM is so old
school!

Thanks Phillip.

"Phillip Windell" wrote:

"SteveW" <SteveW@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:31738180-FF18-4691-8CD5-CC3478E07939@xxxxxxxxxxxxxxxx
Sure, I understand the difference between 1gb and 100 mb. If I moved one
of
the servers to 100mb, I can understand the difference. But why would
moving
the workstation that initiates the copy cause the file copy to slow down?
What data is being exchanged between this workstation and the servers
doing
the copy? It shouldn't make this difference, but it appears it does.
It is because the Workstation copies the file into its own RAM and then
copies it from RAM to the target server because it is the Workstation's own
I/O system that is involved. It does not go directly between the two
servers. Thw workstation's perpspective of the copy is that it is copying
from one UNC Location to another UNC Location just like if it was from one
local drive to another local drive. So you effectively copy the file twice
(to the workstation,..from the workstation).

If you want it to go directly between the two servers either:

1. Go to the server itself and do it (doesn't matter which server, just pick
one)

OR

2. Use Remote Desktop from the workstation to connect to one of the servers
(either one) and do the copy from the remote session.

OR

3. Write a batch file that resides on one of the two servers that has the
command to do the copy. Have it execute using the Task Scheduler. (No you
can't execute the batch file from the workstation because it will run in the
workstation's RAM again).

There are probably a few other ways, but those are the three most obvious
ways that I can think of.

--
Phillip Windell
www.wandtv.com


Much as I prefer top-posting (don't start!) it's definitely best to
stick to one or the other!

I agree with PW: any copy operation consists of a read operation from
disk via a buffer into local RAM and from there, via a buffer (and
possibly a network) onto another disk. If you run the copy on a
"third-party", then all the data has to pass through it. Your
suggestion of using psexec (and Phil W's suggestion of Remote Desktop or
something similar) is a good one. By the way, if there's a lot of data,
and reliability is an issue, it's worth getting to grips with Robocopy,
which has more ingenious options than you can shake a stick at. Part of
the free "Windows Server 2003 Resource Kit Tools" download.

Phil H, London

.

Relevant Pages

  • Re: File Copying
    ... workstation would would copy the files to it's own RAM when the files should ... be copied between the servers. ... Having the file copied to local RAM is so old ... Microsoft Internet Security & Acceleration Server: Partners ...
    (microsoft.public.windows.server.networking)
  • Re: File Copying
    ... workstation would would copy the files to it's own RAM when the files should be copied between the servers. ... So, I could try using psexec to run the batch on one of the servers, but didn't think was required. ... Having the file copied to local RAM is so old school! ... any copy operation consists of a read operation from disk via a buffer into local RAM and from there, via a buffer onto another disk. ...
    (microsoft.public.windows.server.networking)
  • Re: File Copying
    ... workstation would would copy the files to it's own RAM when the files should be copied between the servers. ... So, I could try using psexec to run the batch on one of the servers, but didn't think was required. ... Having the file copied to local RAM is so old school! ... any copy operation consists of a read operation from disk via a buffer into local RAM and from there, via a buffer onto another disk. ...
    (microsoft.public.windows.server.networking)
  • Re: cant login to exchange
    ... Is your workstation configured to use one of your companys DNS servers? ... see Help and Support Center at ... > message DLL files to display messages from a remote computer. ...
    (microsoft.public.exchange2000.general)
  • Re: Event ids 529 and 681
    ... you see a large number of these from the same workstation in a short period ... type of failed audits and the workstation and/or domain names are ... > Servers members of SERVERS domain. ... Not members of SERVERS domain. ...
    (microsoft.public.win2000.security)