Zaaphod
Contributor
- Joined
- Dec 15, 2015
- Messages
- 109
I have a windows CIFS share on FreeNAS 9.3 where I have all my work related files, Occasionally I will need to go out of town, so I need to bring a backup copy of this share with my on my Windows 10 laptop, then when I return, I need to restore my changes back to FreeNAS. Being a windows computer, I am using robocopy for these backup and restore functions, then problem I am having is that whenever I either backup or restore to a CIFS windows share on FreeNAS, it reports every single file as 'modified' even if it has not been modified. This completely nullifies the reason I was using robocopy in the first place, which is to only transfer the changes, thus saving me a LOT of time and writes on my laptop's SSD.
I cannot figure out why this is happening, I am copying the timestamps, as well as file attributes, and ignoring security. I have removed the attribute bit from all files as I have read that cause problems. Here is the exact robocopy command I am using:
If I run this command and let it finish, then simply run it again, ALL files should be exactly the same, and it should do nothing, but it instead reports every single file as modified and actually copies every single file over again. This ONLY happens when J:\ is a FeeeNas network share. If it is a removable drive for example, then it correctly skips files that have not changed. I have looked at the files on FreeNas and on my laptop drive and I simply cannot see what is triggering it to think that it is modified. I recently added the /fft argument in case there was some microscopic difference in the timestamps, but it did not help. using /XO is NOT an option as it will most certainly corrupt the entire process. I have a LOT of GIT repositories on this drive, and if I am on one branch when I backup, but happen to be on an older branch when I restore, then the entire repo will be corrupted... I need to the destination to match the source in all ways when I am done, but I do not want to re-copy identical files
Does anyone know what might be happening and how to get it to work? Is this just something that can't be done with robocopy and FreeNas, and if so, how can I accomplish this with a Windows 10 Laptop?
Any help would be greatly appreciated!
I cannot figure out why this is happening, I am copying the timestamps, as well as file attributes, and ignoring security. I have removed the attribute bit from all files as I have read that cause problems. Here is the exact robocopy command I am using:
Code:
robocopy J:\ D:\ /XD .recycle .Trash-1000 $RECYCLE.BIN /fft /MIR /V /NP /NDL /copy:DAT /dcopy:T /R:10 /W:5 /log:~Backup2Laptop.txt /tee
If I run this command and let it finish, then simply run it again, ALL files should be exactly the same, and it should do nothing, but it instead reports every single file as modified and actually copies every single file over again. This ONLY happens when J:\ is a FeeeNas network share. If it is a removable drive for example, then it correctly skips files that have not changed. I have looked at the files on FreeNas and on my laptop drive and I simply cannot see what is triggering it to think that it is modified. I recently added the /fft argument in case there was some microscopic difference in the timestamps, but it did not help. using /XO is NOT an option as it will most certainly corrupt the entire process. I have a LOT of GIT repositories on this drive, and if I am on one branch when I backup, but happen to be on an older branch when I restore, then the entire repo will be corrupted... I need to the destination to match the source in all ways when I am done, but I do not want to re-copy identical files
Does anyone know what might be happening and how to get it to work? Is this just something that can't be done with robocopy and FreeNas, and if so, how can I accomplish this with a Windows 10 Laptop?
Any help would be greatly appreciated!