Mixmangle
asked on
Xcopy across a slow network
I am trying to do an xcopy of a large workgroup drive from another computer on the network. NTBackup would always fail with no explanation. and no log file - - -computer actually restarts.
When I do a down and dirty xcopy, I see that the network drive is lost after about 800 M of transfer. I did it again and got much farther.
I see the
/Z Copy files in restartable mode. If the copy is interrupted part
way through, it will restart if possible. (use on slow networks)
But have never used this switch. if my network connection is timing out, are there any other options? With this switch, I assume it won't pick up where left off <g> but simply reissue the command?
I am also wondering if the ntbackup fauliure and machine reboot is related to the xcopy telling me the connection was lost?
When I do a down and dirty xcopy, I see that the network drive is lost after about 800 M of transfer. I did it again and got much farther.
I see the
/Z Copy files in restartable mode. If the copy is interrupted part
way through, it will restart if possible. (use on slow networks)
But have never used this switch. if my network connection is timing out, are there any other options? With this switch, I assume it won't pick up where left off <g> but simply reissue the command?
I am also wondering if the ntbackup fauliure and machine reboot is related to the xcopy telling me the connection was lost?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
OK. Robocopy seems to handle the network quirks better than xcopy. I will also look into the gui.
So, if I want to run robocopy daily on the same directory and subs and then only copy new/changed files on each subsequent run . . . . .
robocopy x:\*.* c:\robocopy /s /z
I guess where I am a bit confused . . .will it only copy new or changed files by default . . . . . . or do I need to ad another switch. I'm using /s (maybr /e) for subs . . . and /z for retires . But is the part about only newer or changed in subsequent runs . . .is that incuded by default or do I need to specify something else. I downloaded the gui as well
but I just need a temp bandaide and I don;t need all the logging or anything more than above.
So, if I want to run robocopy daily on the same directory and subs and then only copy new/changed files on each subsequent run . . . . .
robocopy x:\*.* c:\robocopy /s /z
I guess where I am a bit confused . . .will it only copy new or changed files by default . . . . . . or do I need to ad another switch. I'm using /s (maybr /e) for subs . . . and /z for retires . But is the part about only newer or changed in subsequent runs . . .is that incuded by default or do I need to specify something else. I downloaded the gui as well
but I just need a temp bandaide and I don;t need all the logging or anything more than above.
Robocopy's syntax requires you to specify directory paths, so you'd want to remove the *.* from that command.
robocopy x:\ c:\robocopy /s /z
Its default behavior is only to copy new or changed files. It skips ones which already have identical copies in the destination. You don't need any additional switches.
If you want you can use /PURGE or /MIR to delete files which exist in the destination but not in the source.
robocopy x:\ c:\robocopy /s /z
Its default behavior is only to copy new or changed files. It skips ones which already have identical copies in the destination. You don't need any additional switches.
If you want you can use /PURGE or /MIR to delete files which exist in the destination but not in the source.
ASKER
ROBOCOPY must be more tolerant of network problems "out of the box" so to speak.
Thanks for the suggestion