Hi,I have two ReadyNas that are successfully doing backups (between two sites) via rsync. There is one directory that we do not wish to copy over because it contains large, temporary media files (in excess of 2GB).Using standard rsync you can do:rsync --exclude-from=<path>Does anyone know how I can achieve this on the ReadyNas ?

I would also like to know if this is possible too. Thank you, Tom

You would have to ssh in and make the change manually.

ewok wrote:You would have to ssh in and make the change manually.I, too, need the ability to pass an arbitrary number of extra flags and parameters to rsync when it performs back-ups.For example, I need to back up a chroot'ed BIND installation that features a /proc directory within the chroot'ed environment. If I don't use '--exclude chroot/proc' when backing this up, madness ensues and the job fails. FrontView is inadequate for this. There really ought to be a text field in which one can add the necessary extra options for insertion in the rsync command line that is ultimately invoked.Lacking this, I finally succumbed to the urge to install the EnableRootSSH patch and go poking around in search of something I could easily hack to get the job done.Well, I found it. /frontview/bin/backup is the Perl script that handles the back-ups. It's invoked by each of the scheduled back-up jobs, which are listed in /etc/cron.d/frontview-backup.Happily, the extra functionality can be added to /frontview/bin/backup in about 15 lines of Perl. Here's how I chose to implement it: The patch below works on RAIDiator 4.1.3 (and possibly others).--- backup.orig 2008-09-25 15:56:13.000000000 +0200+++ backup 2008-09-25 22:19:35.000000000 +0200@@ -244,6 +244,22 @@ $rsync_option .= " --delete"; } +my $rsync_option_file = '/frontview/conf/rsync.conf';+if( $backup_source_share_proto eq 'rsync' && -f $rsync_option_file )+{+ open(RSYNC, $rsync_option_file);+ my @rsync = <RSYNC>;+ close(RSYNC);++ my $row = (grep(/$backup_source_path/, @rsync))[0];+ if( $row )+ {+ my ($extra_options) = (split $FS, $row)[1];+ chomp($extra_options);+ $rsync_option .= " $extra_options";+ }+}+ my $mount_point = "/job_${job}"; my $login_param; my $source_path = "/$backup_source_share_proto/$backup_source_path";I wanted to avoid having to repeatedly hack system files when a back-up job with extra rsync options needs to be modified, so I chose to have the new functionality use its own configuration file, /frontview/conf/rsync.conf.That file should contain one line of additional rsync configuration per back-up job. Each line should contain two fields, separated by the standard FrontView field separator, two exclamation marks (!!).The first field is the back-up source, which uniquely identifies the back-up job by host::module/path.The second field consists of the options that should be inserted in the rsync command line before it is invoked.In my case, /frontview/conf/rsync.conf looks like this:foo.caliban.org::slash/var/named!!--exclude chroot/proc --delete-excludedNow, when an rsync back-up job is run that has foo.caliban.org::slash/var/named as its source, '--exclude chroot/proc --delete-excluded' is added to the rsync command line.The nice thing about this approach is that /frontview/conf/rsync.conf can be maintained and edited on some other machine and ssh'ed into place on the ReadyNAS. There's no need to work directly on the ReadyNAS, which is important to me. It's an appliance and I want to treat it as such. Logging into it and performing this hack was the last resort for me.Some would say that, if you need this level of control, you should be configuring the back-up job on the client and pushing your data to the ReadyNAS. However, I need to back-up multiple machines and I want all of my back-up jobs centralised on the ReadyNAS. This is an entirely reasonable approach to managing back-ups.Obviously, I would like to see this functionality added to FrontView. I don't like the fact that I've potentially endangered my right to tech support by installing EnableRootSSH. I also don't like poking around on an appliance that wasn't really intended to be manipulated at this level. I consider it a dangerous activity.Anyway, this works for me. If you know what you're doing, it will work for you, too.

Here's an improved version of my patch. Previously, the extra rsync options would only be used if the back-up source was an rsync server. The new version will also use the options when the back-up destination is an rsync server.Let's suppose your /frontview/conf/rsync.conf file looks like this:foo.caliban.org::slash/var/named!!--exclude chroot/proc --delete-excluded127.0.0.1::USB_HDD_1/backup!!--size-onlyThe first line is the configuration for the job described in my last posting.The second line shows a new job, that backs up a local ReadyNAS share to a USB-attached hard drive. The job could also be configured as a simple share back-up, but that wouldn't allow files that have since been removed from the source to also be removed from the destination. Only rsync jobs allow this (the --delete flag), so we have to use that, even though both source and destination are actually local.The --size-only flag is often needed when the source and destination file-systems aren't the same time. If copying from Linux ext3 to Windows FAT, for example, there will be discrepancies in the timestamps that cause all files to be copied from the source to the destination, defeating the main purpose of rsync. --size-only tells rsync to use only the size of the file to determine whether or not the file has changed on the source.--- backup.orig 2008-09-25 15:56:13.000000000 +0200+++ backup 2008-10-04 00:43:28.000000000 +0200@@ -244,6 +244,29 @@ $rsync_option .= " --delete"; } +my $rsync_option_file = '/frontview/conf/rsync.conf';+if( -f $rsync_option_file && ( $backup_source_share_proto eq 'rsync' ||+ $backup_dest_share_proto eq 'rsync' ) )+{+ open(RSYNC, $rsync_option_file);+ my @rsync = <RSYNC>;+ close(RSYNC);++ my $row = (grep(/$backup_source_path/, @rsync))[0];++ unless( $row )+ {+ $row = (grep(/$backup_dest_path/, @rsync))[0];+ }++ if( $row )+ {+ my ($extra_options) = (split $FS, $row)[1];+ chomp($extra_options);+ $rsync_option .= " $extra_options";+ }+}+ my $mount_point = "/job_${job}"; my $login_param; my $source_path = "/$backup_source_share_proto/$backup_source_path";

Ian-What's the prospect for adding a service to the current array of default services on these readynas devices using the basic hacking method that you've outlined above...?Specifically, I'm thinking of how we could add the tivodesktop server so that our LANs could utilize the readynas to serve up photos and music to tivo boxes in our home, which is currently being done by a pc. The readynas is already storing / backing up all of our music and photo library, so why not take the next step?Thanks for your thoughts on this....

Backup ReadyNas to ReadyNas with rsync and exclude lists

24 Replies

Replies have been turned off for this discussion

mnot
Aspirant
May 31, 2011
On 4.2.17 (Intel), /frontview/bin/backup has 'use ByteLoader', and is a mostly binary file. This makes editing it, well, quite difficult.

Does NetGear make the textual perl sources available any more?
techdruid
Aspirant
Nov 07, 2011
This thread contains the closest to a solution that I've found. but unfortunately, now that the /frontview/bin/backup file is compiled, I'm unable to take advantage of the advice here. I was wondering if anyone has alternative methods for passing parameters along to the rsync backups?

My specific error is this.
uid 5234567890 (-1) is impossible to set on "/USER/FOLDER/FILE.TXT"

From what I've read, this error comes from the UID being too large for rsync to handle. The large UID I believe comes from having user shares auto-created from Active Directory users. There are recommendations to pass the "--fake-super" parameter on to the rsync command to avoid this error. I need to avoid the error so that my backup status can come back as successful.

I'm running RAIDiator 4.2.19 on a ReadyNAS 2100.

Any suggestions would be most appreciated.

UPDATE: By the way, the remote/source of the backup job is a Windows 2003 box running cygwin.

Thank You
Richard
cmmmc
Aspirant
Jan 05, 2013
Hi,

I have had an NVX for years and have been plagued with such poor backup support from Netgear :? that I ended up ditching my FTP solution (which didn't do incremental backups properly anymore) for an rsync offsite backup solution.

I got it working in the unix prompt but I too want email notifications etc so looked whether I could tweak the backup file, but it's non editable.

Haven't seen an update on this but all I need to change is the port number to: 2022.

Anyone knows how you can do this? I tried adding the port number and options to the frontview UI, but no luck.

Can someone share their executable if they got Ian's solution to work? (I have x86). Or maybe share the full script so that a perl version can be built from it. :idea:

Thanks in advance.

MC
AGM1
Aspirant
Jun 11, 2014
Folder exclusion list works on my ReadyNAS Pro in rsync with comma separated folders, WITHOUT spaces after comma. E.g. "Exclude 1,do not use 2,not this"

Forum Discussion

Backup ReadyNas to ReadyNas with rsync and exclude lists

24 Replies

Related Content

ReadyNas 212 HELP needed

ReadyNas 104

ReadyNAS 628x version 6.10.9 applications

admin password discrepancy. ReadyNas 4312

Enabling SSH access on Readynas Ultra 2

NETGEAR Academy

ProSupport for Business