Robocopy alternatives

Till 290 characters not more and I will provide you with it soon, if it's over you can switch to robocopy alternatives which easily solve this issue and also can copy updated files or folders or copy the changes, you have peersync and gs richcopy360 , just try to google it . Back to top"> Back to top #4 HenryEthan HenryEthan Topic Starter Members 18 posts OFFLINE Local time:09:48 AM Posted 23 February 2020 - 06:20 AM FreeBooterthanks, I will try this script and what about long path names?NatalieBlakeI have a message from the system that informed me that I don't have the necessary rights to use auditing functions because of the /COPYALL switch. So I had to eliminate it.** during each run, all files get copied. I found the same reason code for each file in the log: OLDER. when inspecting the modified date in source and target files, it appeared identical. also, can you provide me with a long path name solution? if your solution will not help or consume my time, I will switch to robocopy alternatives like the examples you mentioned ( peersync and gs richcopy360). Back to top"> Back to top #5 NoahBrandon NoahBrandon Members 5 posts OFFLINE Local time:09:48 AM Posted 23 February 2020 - 06:32 AM Robocopy by default compares files using remote and local time. when using /MIR, it means both local times is too different from a remote machine you're copying to. so my solution is to use the more tolerant at time comparison /FFT switch. On the other hand long path names is a problem when using robocopy especially the paths that are over 256 so the recommended programs are good solution for that case. Back to top"> Back to top #6 HenryEthan HenryEthan Topic Starter Members 18 posts OFFLINE

To top #11 HenryEthan HenryEthan Topic Starter Members 18 posts OFFLINE Local time:09:48 AM Posted 12 November 2020 - 07:39 AM Juan_Milleris it for long path name only ? more details plz ? Back to top"> Back to top #12 SwaamiBaami SwaamiBaami Members 39 posts OFFLINE Local time:08:48 AM Posted 02 January 2021 - 12:49 PM Juan_Milleris it for long path name only ? more details plz ?It's a know issue, which basically is a bug in Windows, because Windows allows files to be written to the file system, which do NOT comply with other, more strict rules.These stricter rules are followed by Robocopy, and it fails to process these files. Even Xcopy may have the same issue ... so, just to state the fact this is caused by Windows, which is out of synch with the rules according to file creation.For the threadstarter: if the files are not Windows or 3rd party vendor ... you can make the paths shorter ...but if they are not under your control, you can use the "exclude" function of Robocopy. Assuming that doesn't fail for the same reason. /XF file [file]... :: eXclude Files matching given names/paths/wildcards. /XD dirs [dirs]... :: eXclude Directories matching given names/paths. Edited by SwaamiBaami, 02 January 2021 - 12:49 PM. Back to top"> Back to top #13 SwaamiBaami SwaamiBaami Members 39 posts OFFLINE Local time:08:48 AM Posted 02 January 2021 - 12:52 PM Thanks, NoahBrandon , the /FFT switch trick for my situation I saw some solutions for long path names as scripts or fixing system capabilities but it doesn't help , so if I will use any of the other alternatives to robocopy , what do you recommend ? or if you have a good solution ?Microsoft pushes for usage of Robocopy (it used to be external

#1 Hello all, hoping someone can point me in the right direction. I'm running freeNAS version 9.3-Stable and it has been great the last year. Currently I am having a problem trying to get robocopy (or xcopy) to work from windows 7 machines. robocopy is being run with admin rights, and the CIFS share has been mapped in windows, but I always get access denied. I can create and delete files on the share in windows explorer no problem. Does anyone have any ideas?Thanks! #2 Hello all, hoping someone can point me in the right direction. I'm running freeNAS version 9.3-Stable and it has been great the last year. Currently I am having a problem trying to get robocopy (or xcopy) to work from windows 7 machines. robocopy is being run with admin rights, and the CIFS share has been mapped in windows, but I always get access denied. I can create and delete files on the share in windows explorer no problem. Does anyone have any ideas?Thanks! Perhaps try running robocopy without admin rights? #3 Perhaps try running robocopy without admin rights? Yeah, i tried that too, same thing.... #4 Yeah, i tried that too, same thing.... I think your best bet is to do the following:1) verify that robocopy is using the correct user account. There are several ways of doing this - "smbstatus", increasing logging on samba, increasing logging in robocopy.2) verify that you're not asking robocopy to do something that it doesn't have permissions to do. Use "getfacl" to view permissions on your share, and each branch of the file tree leading to the destination folder. Post robocopy command while you're at it. Mirfster Doesn't know what he's talking about #5 1) verify that robocopy is using the correct user account. There are several ways of doing this - "smbstatus", increasing logging on samba, increasing logging in robocopy. +1 to this... You have mapped the drive using different credentials and that is in your current User Profile. So when you are running RoboCopy with "Admin Rights" that is not leveraging your current user mappings.Also, as asked what are the exact switches are you using with RoboCopy (/MIR) ?