Windows 10: I'm wondering why logging in robocopy or any copy tasks matters.

I've been replied that to enhance reliability of robocopy task, better logging recommended.1.But, Robocopy does report results of all the copy task after task finished, under all tasks, even I didn't put additional logging feature like, failed 0 0 0 / skipped 0 0 0 ... etc.Is that report unreliable? I'm wondering even robocopy reports result, why people prefer additional logging.2.If I found nothing wrong on the result report I mentioned before no failure or skipped, etc, Is the task results report reliable? Is additional logging required? Or it's enough?If you wanna say it suppose to be a

:)

 

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

 

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

 

When does robocopy without parity become unreliable?

I've seen this article that says robocopy has no parity so it's unreliable.

Robocopy issues with cloud files

I wanna ask

1. Does windows native paste task including parity?

And

2. How much does parity in copy/paste task matter?

I'm using robocopy on copy/pasting all the sub-directories combined with files

3. When does robocopy without parity become unreliable, and was the reply on the link above just telling about 'file partitions'? Or all the copying things including folders?