Windows 10: RoboCopy is reporting a failed copy in the summary but not in the details even with /V and...

In Windows 10 robocopy is reporting a failed copy but the detail log looks fine so I can't fixed the problem.

Total Copied Skipped Mismatch FAILED Extras
Dirs : 1101 0 1101 0 0 0
Files : 5369 111 5257 0 1 110

When it fails it returns error code 11 FAIL XTRA COPY

This started happening With the last update of windows 10 20H2. It seems to be happening approx every other day. What can I do to find out what's failing?

Here is the command line I use to run it;

robocopy /V /JOB:$JobFile $DriveToBackup $BackupDestDir

Here is the job file. As you can see the /V and /Log+ option is on the common solutions you can find on line.


::
:: Robocopy Job C:\DATA\NETWORK.LAN\ROBOCOPY.FLUX.N.TO.U.VIA.NETWORK.RCJ
::
:: Created by thx on Tuesday, February 9, 2021 at 11:18:39 AM
::

::
:: Source Directory :
::
/NOSD :: NO Source Directory is specified.
:: :: To Be Specified on the Command Line

::
:: Destination Directory :
::
/NODD :: NO Destination Directory is specified.
:: :: To Be Specified on the Command Line

::
:: Include These Files :
::
/IF :: Include Files matching these names
:: *.* :: Include all names currently - Command Line may override
/XJD :: eXclude symbolic links for Directories and Junction points.

::
:: Exclude These Directories :
::
/XD :: eXclude Directories matching these names
$RECYCLE.BIN
System Volume Information
Temporary Internet Files

::
:: Exclude These Files :
::
/XF :: eXclude Files matching these names
:: :: eXclude no names currently - Command Line may override
::
:: Copy options :
::
/S :: copy Subdirectories, but not empty ones.
/E :: copy subdirectories, including Empty ones.
/DCOPYA :: what to COPY for directories default is /DCOPYA.
/COPYAT :: what to COPY for files default is /COPYAT.
/PURGE :: delete dest files/dirs that no longer exist in source.
/MIR :: MIRror a directory tree equivalent to /E plus /PURGE.
/A+:AN :: add the given Attributes to copied files.
/A-:SH :: remove the given Attributes from copied files.
::
:: Retry Options :
::
/R:2 :: number of Retries on failed copies: default 1 million.
/W:1 :: Wait time between retries: default is 30 seconds.
::
:: Logging Options :
::
/V :: produce Verbose output, showing skipped files.
/ETA :: show Estimated Time of Arrival of copied files.
/LOG+:C:\Data\Network.lan\RoboCopy.FLUX.N.Log :: output status to LOG file append to existing log.
/TEE :: output to console window, as well as the log file.

------------------------------------------------------------------------------

:)

 

Cannot force ROBOCOPY to copy files with /IS

I'm encountering the following situation:

- in directory ./bf2 I have a corrupted copy of a file with the same name found in directory ./bf

- I run

ROBOCOPY /v /is bf bf2

in a attempt to overwrite the faulty copy in 'bf2' with the correct file found in 'bf'

- the output from ROBOCOPY is:

PS C:\Users\steph> robocopy /is /v /ts C:\users\steph\Desktop\bf C:\users\steph\Desktop\bf2 *.7z

-------------------------------------------------------------------------------

ROBOCOPY :: Robust File Copy for Windows

-------------------------------------------------------------------------------

Started : Tuesday, July 26, 2016 10:12:48

Source : C:\users\steph\Desktop\bf\

Dest : C:\users\steph\Desktop\bf2\

Files : *.7z



Options : /V /TS /DCOPYA /COPYAT /IS /R:1000000 /W:30

------------------------------------------------------------------------------

1 C:\users\steph\Desktop\bf\

modified 335.2 m 2016/07/25 15:26:45 off_homedir.bkp.7z

------------------------------------------------------------------------------

Total Copied Skipped Mismatch FAILED Extras

Dirs : 1 0 1 0 0 0

Files : 1 0 1 0 0 0

Bytes : 335.24 m 0 335.24 m 0 0 0

Times : 0:00:00 0:00:00 0:00:00 0:00:00

Ended : Tuesday, July 26, 2016 10:12:48

As you can see, the file is NOT copied, so the bad copy remains in 'bf2' instead of getting overwritten with the correct data.

How can I get ROBOCOPY to work properly?

FWIW I'm running Windows 10, and the problem can be repro'ed both with 10.0.10586.494 and with 10.0.14393.3

 

why is robocopy failing to copy files with long path names

I thought one of robocopy's great features was the ability to copy long path names?

I am trying to copy files on a windows 2008 R2 server and everything accept items with long paths are copying.

I am copying from one volume to another H:\ -> K:\

does it not work on server 2008? are there certain scenarios where it wont copy long file names?

robocopy "\\server\k$\Shares\Projects\2020-move" "\\server\h$\2020-move" /S /E /COPYALL /ZB /MT:12 /R:1 /W:1 /TEE /LOG:H:\robocopy\2020-unc.log

 

Copy NTFS permissions to a NAS with Robocopy

Hello,

I'm actually using Robocopy to copy a "home" folder with NTFS permissions to a NAS Synology. All theses equipment are on the domain, that will be named XXXXX in this post.

The permissions on the "home" folder are explicit, and not inherited from the parent folder. Also note that the SYNOLOGY NAS have the Windows Permissions activated.

The goal is to create a backup of this "home" folder to the NAS with the permissions.

Here is the Robocopy script that i'm using :

------------

set rep_log=C:\Script\log

set rep_sync_DATA=\\SRV1\e$\home\

set rep_sync_NAS=\\NAS-SYNOLOGY01\test01\backup\home\

robocopy %rep_sync_DATA% %rep_sync_NAS% /MIR /SEC /ZB /NP /XF thumbs.db /R:2 /W:5 /log:%rep_log%\Synchronisation_backup_nas.txt

-----------

The Robocopy script works well, and the files are well copied. EXCEPT one. On my "home" source folder, we can find on the permission list the XXXXXX\Administrators group. (explicit permission)

But, unfortunately, once the folder is copied to the NAS, it change the XXXXX\Administrators group to NAS-SYSNOLOG01\Administrators. This folder take the local domain of the NAS instead of my AD domain.

Please note that this "domain change" is only applied to this group, and the others lambda groups are not impacted by this strange change. (example XXXXXX\Sales group on source folder will be copied as XXXXXX\Sales to the destination)

The same script works perfectly if the destination is a USB HDD for example. It only happens if I want to copy to the NAS.

Any idea to fix this issue ? I faced this issue twice, with SYNOLOGY and with NETAPP technology. Whatever soft I tried to copy (robocopy or others), the result is the same...

Thanks for your potential help

Sébastien