This may be a stupid question, but I'm erring on the side of caution here.

If I'm using Windows command line/batch files to Move a file from one server to another and we have a network failure, what will happen to the original file?

I would assume it remains untouched until fully moved, and then deleted, but I need to be sure. My fear is that it deletes bytes as they are moved, which would be bad.

If that isn't the case, is there a better way than Copying the file and Deleting after the copy completes?

Thanks for your help.

EDIT: I suppose super user would have been better. This is part of a job kicked off by code, so my first thought was to come here.

  • Yes, this isn't the same as the Leopard bug. – surfasb Feb 15 '11 at 12:50

Moving on the same logical disk: Windows simply moves the file-system references atomically. Very fast.

Moving on different logical disks: Windows performs a copy from one disk to the other, then deletes the file from the first disk, once successful.


Yes, it only deletes the file once it's finished copying.


You are correct -- Windows Move deletes only after a successful copy.


You are correct, Windows does copy, then delete. It wouldn't make sense from a filesystem point of view to remove chunks as they are copied when all the final delete needs to do is remove the file header.

If you want to test you could always try to send a large file across the network and yank the cable partway through.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.