ReadyNAS 6.1.3 - Eject after backup feature

Do you see it when configuring a backup job to a USB HDD perhaps?

That's the first place I looked. Though, I've only so far checked the settings of an existing backup jobs and not created a new backup job.

Here's a screenshot showing all 6 tabs of the backup dialog.
https://dl.dropboxusercontent.com/u/222 ... creens.jpg

You're specifying the USB disk as a remote Rsync destination not a local USB disk so this option isn't available.

Ah, okay. Thanks for the explanation.
So can I change my backup settings from an Rsync destination to a local USB without destroying anything or would I have to re-create my backups from scratch?

You should be able to change the backup job settings but you would of course lose the benefits of using Rsync.

I think I'll stick with using rsync.
I wonder if it would be possible for the devs to implement an 'eject after backup' option when using rsync?

I do this...

I have the source set as rsync with host 127.0.0.1
I have the destination set as a local USB drive and then you get the "Eject on completion" option appearing on the destination tab.

I think that's what you meant?

Thanks for your input alanwsg.

If you set your source as rsync with localhost, how do you then select a different share for that particular backup or are you just backing up the complete NAS in one hit? If that's the case then it may not suit my needs as I currently have 10 shares, each set to backup on alternate nights throughout the week which means I have 20 separate backup jobs.

Having said that, since my post this morning I have done some simple research in to the benefits of rsync vs direct copying and also experimented by creating a test backup job with the destination set as USB and sure enough, after manually running the job the USB drive is ejected.

From my quick research I understand there are benefits of both rsync and direct copying. The NAS here is used as a shared drive for a reprographics studio so I guess I would benefit from both options as for example, here one share contains directories of live jobs which may have a life of a day to couple of weeks or months as they're worked on. So initially many files may be copied to a directory (which would suit a direct copy backup) but then these files may well be edited during the course of the job (so suit rsync backup). Once completed, they're compressed and moved to a different share for archiving (which would suit a direct copy backup).

Anyway, I've had an idea. I'm going to create a dummy backup, which uses the local USB destination option with 'eject on completion enabled', and set it to run after all the others have completed. This way I can leave my current rsync backup jobs as they are for now and still benefit from the eject feature.

EDIT: Had a email this morning at 06:05 to tell me the external USB drive was successfully ejected. :)

Yes, I backup individual shares with rsync,
E.g. for my share called "public"I have...

Host: 127.0.0.1
path: public

You can then hit the "Test connection" button to check you got it right,
If you spelt the share name wrong or you've got slashes in the wrong places, it fails.

Note that the first time you run an rsync job it performs a full backup which can be quite slow. There seems to be no way out of this even if you've already backed-up the share using direct copy method.

alanwsg wrote:
...Note that the first time you run an rsync job it performs a full backup which can be quite slow. There seems to be no way out of this even if you've already backed-up the share using direct copy method.

There is a way. Start with NFS, and run it the first time. Then edit, and change it to rsync.