NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Backup job copies ALL files instead only changes
I have a ReadyNAS NVX running 4.2.26. It has a share used for our ESXi server backups. I then have a ReadyNAS backup job that runs everyday and copies the backups from the NVX share to a USB drive a...
ESXi attaches the ReadyNAS share as a store via NFS, then vmProtect writes to the ESXi store.
FIXED! (Sorta.) I am happy to report that rsync fixes the problem--rsync copies only the missing files and ignores the granularity difference between EXT to NTFS. And StephenB is correct on username/password--none needed. This works on both NVX v4.2.26 and NV+ v4.1.6.
Big downside is that rsync writes the truncated time (nearest second) to the destination time. Be nice if it used that for comparisons only but copied the FULL time (let the destination truncate to its highest granularity). E.g., I've previously used the non-rsync method to copy files without issue from NTFS system to ReadyNAS then ReadyNAS to NTFS USB. Works fine because the granularity was already truncated by the original NTFS system to 7 decimals. However, if I try the same with rsync, the copies get truncated to the nearest second, and their timestamps no longer match the original. Now if I compare timestamps with something other than rsync (which isn't included in Windows...see illiterate user comment above)--or even rsync but with the default, untruncated granularity--the timestamps don't match and I've got the same problem again. Argh! I guess that's why my clients pay me the big bucks to bang my head against the desktop over problems like this so they don't have to...hmmm...maybe they're not such stupid users after all. :)
FIXED! (Sorta.) I am happy to report that rsync fixes the problem--rsync copies only the missing files and ignores the granularity difference between EXT to NTFS. And StephenB is correct on username/password--none needed. This works on both NVX v4.2.26 and NV+ v4.1.6.
Big downside is that rsync writes the truncated time (nearest second) to the destination time. Be nice if it used that for comparisons only but copied the FULL time (let the destination truncate to its highest granularity). E.g., I've previously used the non-rsync method to copy files without issue from NTFS system to ReadyNAS then ReadyNAS to NTFS USB. Works fine because the granularity was already truncated by the original NTFS system to 7 decimals. However, if I try the same with rsync, the copies get truncated to the nearest second, and their timestamps no longer match the original. Now if I compare timestamps with something other than rsync (which isn't included in Windows...see illiterate user comment above)--or even rsync but with the default, untruncated granularity--the timestamps don't match and I've got the same problem again. Argh! I guess that's why my clients pay me the big bucks to bang my head against the desktop over problems like this so they don't have to...hmmm...maybe they're not such stupid users after all. :)
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
