NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
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...
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.
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.
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,
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.
In summary as the thread is a little jumbled now:
Issues I have had with ReadyDR:
1. Setup with keys with a pull job requires key generation on destination NAS to be imported to source, opposite of what KB says.
2. Smart snaphot retention setting in ReadyDR share does not seem to function correctly and inappropriate pruning of some snapshots (daily and weekly) occurs, behaviour is different to that on source NAS. Can work around this by setting a custom retention policy on the destination.
3. ReadyDR does not seem to handle non-scheduled snapshots, the presence of a manually generated snapshot on the source causes the job to hang and the readydr share to become undeletable because of a snapshot deletion error.
4. Occassionally a job will run for the first time and will not backup all snapshots. Once this happens only new snapshots will be added to the readydr share on subsequent runs of the job; the source snapshots missing from the destination are not backed up. Regenerating the job and the readydr share usually solves this,
5. There is a large difference between the snapshot space on the source and destination NAS. In my case (Volume tab) the snapshots on the source are 31GB, on the destination 65GB. This is after the first set of readydr backups.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
