NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
OS6 Backup feature
Hi all,
Me again ! :D
When a incremental backup runs from ReadyNAS (A) to an attached USB drive (B) it, of course, adds new files from A to B.
But if files are removed from A, it seems that thes files are not removed from B after a daily backup runs.
Is this a normal behaviour of the OS6 backup process?
Thanks and good day !
Limerick_fr wrote:
But on my original backup, I managed to setup a single backup process which runs only once to backup the whole ReadyNAS to the USB HDD in one shot.
Here it seems that I have to setup a backup for each share ...
Instead of having a single process, multiple ones will have to run, am I right? 20 shares = 20 setup = 20 runs ?
If you do this trick on the source, then you will need multiple backup jobs. They would run sequentially, and can be on the same schedule. Personally I do back up my own NAS with one backup job per share, as it does give me a bit more flexibility on the destination(s) and scheduling.
However, you can back up the entire NAS with one backup job if you apply this trick in a somewhat different way.
You set up the USB destination folder as a share (it might already be one), and enable rsync on it - making it read/write, since it is a destination. Then instead of making the source "remote", you make the destination "remote" - using the same trick with 127.0.0.1.
7 Replies
Replies have been turned off for this discussion
Limerick_fr wrote:
But if files are removed from A, it seems that thes files are not removed from B after a daily backup runs.
Is this a normal behaviour of the OS6 backup process?
Yes. Many people want that, as it allows them to recover files that were deleted by mistake. Though it does create clutter on the backup over time.
But there is a way to set up a backup job so that the files on the destination are deleted when you delete them from the source.
The trick is to change the backup protocol to rsync, and make the backup source remote (using IP address 127.0.0.1). If you do that, you'll find an advanced option that automatically deletes files that are no longer on the backup source. If you do this, make sure you enable rsync as a protocol on the source share(s).
Note IP address 127.0.0.1 is special (called localhost). It is always assigned to the local machine, which is a convenience.
StephenB wrote:The trick is to change the backup protocol to rsync, and make the backup source remote (using IP address 127.0.0.1).
Hi StephenB,
As usual, thank you for your kind help.
But you probably guessed that I somewhat just a newbie and if things are not clear at first stage, I quickly get lost.
And indeed, what seems to be very simple is not obvious to me and I don't see what to do amongst the various menus and parameters to set in order to setup what you describe.
But I might have a workaround if it is too complicated for me. This is to use SyncBackPro to perform such backup. This is not super efficient because my computer needs to run and data run from the ReadyNAS to my computer, then back to the attached HDD through the ReadyNAS again, but it gives the possibility to make the backup the way you described it.
Limerick_fr wrote:But I might have a workaround if it is too complicated for me. This is to use SyncBackPro to perform such backup. This is not super efficient because my computer needs to run and data run from the ReadyNAS to my computer, then back to the attached HDD through the ReadyNAS again, but it gives the possibility to make the backup the way you described it.
I don't know why I can't edit my posts anymore, evene within few minutes after posting.
So my quoted idea above is a fail because it is impossible to select the whole ReadyNAS as the source and you have to select share by share, which makes the setup much more boring...
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
