NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
vandermerwe
Oct 30, 2016Master
ReadyDR setup
I have finally installed OS6 onto my Ultra 6+, in order to make use of ReadyDR. I am pulling the snapshots from a 316, once a day. The smart snapshot schedule on the source is hourly. Firstly in o...
vandermerwe
Oct 30, 2016Master
GTested the volume occupied on another small share and similar outcome. Readydr share indicates 496 MB occupied ( same as source share volume) but volume tab indicates 873 MB of snapshots. If the Readydr share is a backup of the snapshots, surely they should be the same especially as this is the first backup.
Running the Readydr backup again leads to something even stranger. The backup completes but the Readydr share then mysteriously loses some snapshots. There are 78 snapshots in the source share (hourly smart snapshots). The first Readydr backup backed them all up. Running it a second time now there are only 49 snapshots in the Readydr share. Reviewing the snapshots on source and destination it appears that all the retained daily and weekly snapshots have been omitted from the second backup. Only the 48 hours worth of hourly snapshots then monthly snapshots are kept whereas on the source there are daily snapshots and weekly snapshots (which is how smart pruning should work). The smart pruning on the destination is behaving differently .
vandermerwe
Oct 30, 2016Master
Swapping to a push job works as expected, all snapshots are backed up and there is no unexpected pruning after the second run of a job. There is still a very large difference in the Readydr share volume compared to the volume occupied by snapshots in the volume tab. It appears then that if the job is setup on the destination NAS, then pruning in the Readydr share does not work correctly on the second run of a Readydr job. Bug?
I suppose I could set it up this way but my destination NAS is only powered on for backups so I want shutdown to be postponed for queued backup tasks. This would not happen if some of the jobs are push jobs. I don't want backup jobs to fail because the destination has shut down and I don't want to have to leave the destination NAS on for longer than necessary.
- vandermerweOct 30, 2016Master
I spoke too soon. Shortly after my last post it appears that snapshot prune worker on the destination NAS pruned all the daily and weekly snapshots from the DR share, leaving only the hourly and monthly snapshots. This is with a Readydr job set up on my 316 pushing to a Ultra 6 + running 6.6.0. Definitely not working as expected.
Presumably a workaround would be to turn off smart pruning and use some sort of custom pruning. What I'd like to see is that the Readydr job just prunes the same snapshots that the source has pruned.
- FramerVOct 30, 2016NETGEAR Employee Retired
Hi vandermerwe,
Have not been able to make some test with ReadyDR. But if I remember correctly, manually created snapshots are not pruned. So it might be the same with ReadyDR.
Regards,
- vandermerweOct 30, 2016Master
Yes you are correct but that is not the problem. I have deleted the manual snapshot so now all the snapshots are smart snapshots on the source. The snapshot pruner was removing scheduled snapshots on the destination even though these same snapshots were still present (and should have been) on the source.
Related Content
NETGEAR Academy

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