Any idea about what is happening here? OS is Windows 8 Pro 64-bit.
I'm backing up a folder on drive e:\ to drive c:\. The source folder
is sized 1,801,834,496 bytes containing 1,725 files in 109 folders. If
I use xcopy in CLI to create it, the number of files and folders in properties window of the newly created folder on c:\ are off from that
of the source folder on e:\. If I use the GUI to copy the folder from
e:\ to c:\, there is no discrepancy.
Any idea about what is happening here? OS is Windows 8 Pro 64-bit.
I'm backing up a folder on drive e:\ to drive c:\. The source folder
is sized 1,801,834,496 bytes containing 1,725 files in 109 folders. If
I use xcopy in CLI to create it, the number of files and folders in properties window of the newly created folder on c:\ are off from that
of the source folder on e:\. If I use the GUI to copy the folder from
e:\ to c:\, there is no discrepancy.
On 3/14/21 4:15 PM, this is what Yes wrote:
Any idea about what is happening here? OS is Windows 8 Pro 64-bit.
I'm backing up a folder on drive e:\ to drive c:\. The source
folder is sized 1,801,834,496 bytes containing 1,725 files in 109
folders. If I use xcopy in CLI to create it, the number of files
and folders in properties window of the newly created folder on c:\
are off from that of the source folder on e:\. If I use the GUI to
copy the folder from e:\ to c:\, there is no discrepancy.
Ya think xcopy is missing hidden system files?
Why not use robocopy <src> <dest> /MIR
Teddy-Bears wrote:
On 3/14/21 4:15 PM, this is what Yes wrote:
Any idea about what is happening here? OS is Windows 8 Pro 64-bit.Ya think xcopy is missing hidden system files?
I'm backing up a folder on drive e:\ to drive c:\. The source
folder is sized 1,801,834,496 bytes containing 1,725 files in 109
folders. If I use xcopy in CLI to create it, the number of files
and folders in properties window of the newly created folder on c:\
are off from that of the source folder on e:\. If I use the GUI to
copy the folder from e:\ to c:\, there is no discrepancy.
Why not use robocopy <src> <dest> /MIR
Thanks. I'll have to first read the info about robocopy. I'm not
familiar with it. I'm so used to using copy, xcopy or the GUI to copy
files. I wasn't even aware that there was that type of command.
I'm not so sure if hidden system files are at issue. I have one folder
in which I have some deeply nested sub-folders and some files names in
it are pretty long. I worry that perhaps during the copying process
the file name may exceed the 256 char limit. I have received that type
of warning in the past and immediately renamed the file with something shorter and then manually copying them.
From Paul's reply, I realize that I failed to note that both drives are internal hard drives on the same pc and used by the OS.
Robocopy has a lot of options, including an option to handle Junctions.
To see if a home directory has Junctions, run this command.
There are probably around 62 junctions minimum on C: at a guess.
https://docs.microsoft.com/en-us/sysinternals/downloads/junction
To list junctions beneath a directory, include the ?s switch:
junction -s c:\
Then you'd know if a junction-avoidance option is needed.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 296 |
Nodes: | 16 (2 / 14) |
Uptime: | 70:25:08 |
Calls: | 6,656 |
Calls today: | 2 |
Files: | 12,200 |
Messages: | 5,332,151 |
Posted today: | 1 |