first question on StackExchange, so apologies if there are etiquette breaches!
I am using Robocopy to mirror a complete disk drive to an external drive for backup/archive purposes. I used the following command line: robocopy c:\ f:\BACKUP\20160607 /mir /zb /v /np /mt /r:2 /w:0 /log:f:\BACKUP\20160607.log
The top of the log file looks like this (note the altered switches):
Source : c:\
Dest = f:\BACKUP\20160607\
Files : *.*
Options : *.* /V /S /E /COPY:DAT /PURGE /MIR /ZB /NP /MT:8 /R:2 /W:0
According to Windows, the source drive has 685,361,848,320 bytes of used space So far the target drive (empty before the operation started) has 1,149,757,237,960 bytes of used space. The operation hasn't finished yet.
Why is so much more data being copied and where is it coming from? I can't find any suspicious entries in the log so far.
I did find this: https://stackoverflow.com/questions/34192978/robocopied-drive-is-inconsistent-from-source-number-of-files-match-not-disk-us
but I'm not sure explains the huge changes I'm seeing (the source drive doesn't have compression switched on). I am copying from NTFS to exFAT and the block size on the destination drive is 512Kb (I think), but I wouldn`t have thought that would give this result.
Has anyone else found this problem or what causes it. At the moment, the copy is still running and growing with no end in sight! I don't really want to waste a 2TB drive on a 600Gb mirror copy.
/xj
to the options.