NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Questions about Sync w/Google Drive - Shortcuts/Links/Files-Folders Added to Multiple Locations?
Google Drive has a nice feature to allow you to link / short-cut / add-to a file or folder in multiple folders at the same time (Shift z when a file/folder is selected brings up the "Add to" dialog,...
ReadyNASNVUser wrote:
Is there an option on Backup to "copy symlinks, don't follow symlinks" or is this something I can tell rsync to if I use this to do a local backup? (To an option I think you both provided in the other thread?)
It would be nice to have an option for this on the advanced settings for rsync backup jobs - but that isn't there.
The NAS behavior here isn't something I've tested, and it might depend on the backup protocol you pick. Rsync certainly does have options on how to deal with symlinks, but I don't know how the NAS has set those options. Samba is configured to follow symlinks, so if you are using SMB with a remote source, then you certainly end up with the redundant copies.
Anyway, it would be easy to see what the NAS does here by creating a small test share, and trying an rsync backup job.
Hi StephenB
You're right... nothing for regular Backup or rSync to tell them not to follow symlinks, but I understand rsync and regular Backup never follows symlinks anyhow, since the direct inode entry for symlinks marks the file/directory inode as 'simulated'
Plus, I mistakenly said in my earlier post I used rdfind to create symlinks, I didn't I used it to create hardlinks. Which I think is lucky, because I would guess, not tested, if I use rdfind to create symlinks "Sync with Google Drive" would 'notice' the file had been changed and then either copy it back to GoogleDrive if two way sync is on (eek!) or redownload all the duplicated files, if one way sync is on (which is my scenario - I am making a backup of my gDrive). As I've just learned, hard links are actually pointers to the original file's inode, i.e. other than consulting the inode using "stat -c %h -c %A <File>" you can't tell a hardlink from the original file
However, the advanced rSync option does include "Preserve Hard Links" which is *exactly* what I need. So since I created hardlinks with rdfind, moving to rSync to backup locally, using as StephenB said here, localhost 127.0.0.1 and then telling rSync to Preserve Hard Links is a good work around. Preserve Hard Links in rSync
I have updated the idea for Sync with Google Drive to create links not make multiple copies, i.e. preserve hardlinks from GoogleDrive when it syncs to ReadyNAS to include this as a second part of the workaround (part 1: use rdfind to make the hardlinks after the Google Sync is complete.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
