NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
ReadyNAS 104 running 6.6.1 amazon deleting files
I just read a post here which claims this problem was discovered and then solved in 6.6.1. It is not. I have been syncing to amazon for a few months, with a fear that this would happen, and ...
Bi-directional sync is great for having access to your data on all your devices. As StephenB mentioned it isn't a backup.
Feature Requests should be posted in the Idea Exchange.
I do not understand your comment. "Bi-directional sync is great for having access to your data on all your devices".
If the sync was a single (direction UP to amazon) how would that change your comment? "access" is one thing, "control" is another. If the sync was a single direction, I would still be able to SEE all my content on amazon from any device I choose.
The issue here is control. Where amazon now has control over my data and it's logic is nw negatively affecting my data.
Redwolf wrote:
I do not understand your comment. "Bi-directional sync is great for having access to your data on all your devices".
Stepping back, he was agreeing that bi-directional sync is not good for backup, though it was useful for other things.
If the NAS and other devices are two-way synced to the cloud, and anything put on any device automatically propagates to all other devices and the cloud. Of course deletions also propogate, so this is not something you want to do with all your data. But if you have a subset of content (music, ebooks, photos, etc) that you want available on all devices, this is one way to do it. And it is handy to have content created on the mobile device automatically propagated to all other devices.
Redwolf wrote:
If the sync was a single (direction UP to amazon) how would that change your comment? "access" is one thing, "control" is another. If the sync was a single direction, I would still be able to SEE all my content on amazon from any device I choose.
You are (I think) combining sync for upload and with manual download (at least most of my content would need to be downloaded to the device to consume it). You'd end up with some disorganization of data. Management of local device storage therefore becomes a bit harder. Propagation downward isn't done automatically in the background, so your ability to access new content depends on your current data connection speed.
Also, if this applies to the NAS as well, then the only repository that has all your data is the AWS cloud. Not something I'd want to do myself.
Though you might be thinking about some form of selective sync?? Personally I like using "selective sync" in the mobile devices for larger shares. I use resilio sync for that (running on a PC that has the NAS data volume mapped as a network drive). Files that aren't on the device show up as placeholders, that I can then choose to download. I can wait for it, or just let it continue in the background. Propagation is only from the server to the device, so I can delete files as needed from each device to manage storage, with no concern about deleting the server copy. Data is organized the same way on all the devices.
I use two-way sync on some other folders - ok for propagation of adds, but managing propogation of deletions is a bit of a pain. At least with Resilio, some files end up re-appearing. These folders aren't on the NAS, as I don't want to risk losing the server copy. They are on the PC, with content manually transfered back and forth to the NAS. This can be useful for uploaded photos/videos from the mobile device, but also to force propagation to all other devices from the PC.
Although this is workable, despite playing around with sync for about a year now, I haven't run into a package that actually lets me manage my personal data across my devices exactly the way I want to manage it.
I'd prefer a one-way automatic sync in the uplink direction from some mobile device folders to the NAS shares, combined with selective sync in the downlink. There'd need to be a warning if I tried to delete something on the mobile device that hadn't been uploaded yet. I'd also like a "reverse" selective sync, where I can push specific content from the NAS to my devices (and maybe vice-versa).
I'm not sure how I'd want cloud storage to fit in. I do know I'd want client-based encryption so the cloud provider can't decrypt the content. One option is to simply use one-way uplink sync from the NAS shares to the cloud - treating the cloud as a pure backup, that is never accessed directly from the mobile clients. The other option is to use the NAS as the backup for the cloud repository, which requires one-way sync from the cloud to the NAS. The first way optimizes for remote access, the second optimizes for local access. I guess you could provide both (at least with peer-to-peer you can), but then you'd need a different cloud repository for backup (using one-way sync).
StephenB wrote:
Redwolf wrote:I do not understand your comment. "Bi-directional sync is great for having access to your data on all your devices".
Stepping back, he was agreeing that bi-directional sync is not good for backup, though it was useful for other things.
(I'm not claiming to be an expert on the subject, but have done quite a bit of research and testing on the subject.)
Even one-way sync isn't necessarily a good "backup" (on its own). It depends what you want to do (and what other feature you may have available).
"Mirroring" or "one-way sync" is very good for DR as you can quickly recover the exact status of the source from the destination. As it propagates deletions and modifications, it's not a good backup solution for file recovery.
"Contribute" or "Update" (or whatever you want to call it) is more useful for file recovery as it doesn't propagate deletions, but it generally propagates modifications, so it's better for file recovery but still not the "ultimate" solution. It's a poor solution for DR as you can't recover the exact state of the source from the destination (you also have previously deleted files).
There are some hybrids or some softwares that allow further customization, like not propagating modifications, but then you're getting further away from actual "sync".
There also isn't really a standard on how to call the different behaviors, I've seen them called differently in different softwares.
On top of these sync methods, if your destination storage provide versioning capabilities, it may help with file recovery. But some are very limited or cumbersome to use, like recovering files one by one. I don't know the capabilities of Amazon as I don't use it.
Then, if you start considering incremental and differential backups, there's much more to say. I believe that what ReadyNAS Replicate does is very good: hardlink the previous occurrence into the new one, mirror the source onto the new occurrence. This way, you have occurrences with the exact status of the source at the time, so good DR, and keep revisions of everything, so good file recovery. There are multiple modern softwares that use similar approach. These are the best, imho, for backup. Afaik, this kind of stuff isn't available on ReadyNAS (except Replicate), which is why I use my own backup script.
For data accessibility and convenience, bi-directional or one-way sync are great. But I wouldn't use it (on its own) for a backup.
Back to OP's issue, of course, the amazon sync should work properly
EDIT: hardlink, not symlink.
I agree that one-way sync doesn't allow rollback. If the sync destination is a readynas share with snapshots enabled, that is likely ok, since the snapshots will provide some rollback.
Even without rollback, one-way sync to inexpensive cloud storage might be attractive backup method to many people. Though CrashPlan has versioning and is similarly priced to AWS.
Backup aside, I am still waiting for really good sync application with enough flexibility to cover the use cases above:
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
