NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
bspachman
Nov 15, 2010Aspirant
Step-by-Step: Rsync to Local USB
UPDATE: 11/16/2010 LAST UPDATE: 11/17/2010 -------------------------------------- It would be great to create a step-by-step guide to backing up a ReadyNAS to a local USB drive for those of us ne...
ewok
Nov 18, 2010NETGEAR Expert
bspachman wrote:
Understood, however, is one more advantageous than the other? Consider one likely case: where a user wants to do a partial backup of a share. Does the SOURCE have to be the rsync entry so that the exclusion feature can be used? What happens if you 'exclude' on an rsync destination?
It normally doesn't matter either way. I prefer writing to local share (so rsync source) to minimize permissions issues. Exclude works the same way regardless of which side is rsync (excluded files are not transferred to the destination).
bspachman wrote:
Is it sufficient to look at the man page for rsync on my OSX machine? How is it passed? via the "--exclude" option? My documentation says that it only takes one rule/pattern…. If I want to exclude all transport stream and MPEG files from the backup, can I use "*.ts,*.mpg"?
The OSX rsync man page should have the info you need. The exclude field is split by comma and each element is passed to an --exclude option.
bspachman wrote:
It seems that you are right when you actually run the backup job, however, when I click "Test Connection" with any of the above entries in the host field, a pop-up appears telling me that the connection failed.
It works on my Pro regardless of which of the three formats used.
bspachman wrote:
So does the option apply at all if you are using rsync as a source? If it applies, what happens? For the destination, it would seem to be clearer language to say "remove files already deleted from source" or if it applies in either case, just "Remove deleted files from backup"
If this option is enabled on the source, files that exist on the destination but not on the source are deleted. Basically, it keeps the source and destination in sync.
bspachman wrote:
So what's the purpose of having an end time for any of the jobs? Something else I had read here on the boards tried to explain the utility of the end times, but I guess I didn't grasp it.
It's not an end time for a job, it's the end time for the schedule. For example, if you set a start time of 1:00, and end time of 3:00, and a backup every hour, backups will run at 1, 2, 3, and then not run again until 1 of the next scheduled day.
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!