this post was submitted on 02 Oct 2023
56 points (95.2% liked)
PC Master Race
14955 readers
1 users here now
A community for PC Master Race.
Rules:
- No bigotry: Including racism, sexism, homophobia, transphobia, or xenophobia. Code of Conduct.
- Be respectful. Everyone should feel welcome here.
- No NSFW content.
- No Ads / Spamming.
- Be thoughtful and helpful: even with ‘stupid’ questions. The world won’t be made better or worse by snarky comments schooling naive newcomers on Lemmy.
Notes:
- PCMR Community Name - Our Response and the Survey
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
https://www.seagate.com/au/en/blog/what-is-a-3-2-1-backup-strategy/
Thank you!
One thing it doesn't mention is that a sync is not a backup. If deleting a file in one copy of the data triggers a delete in another copy, then it doesn't count as a copy.
The right sync is actually an excellent backup, and compliments other methods (like local storage) quite nicely.
Any worthwhile sync will delete to a recycle bin and support versioning of files. A bad actor would have to have account level access to dump the recycle bin, which proper use of MFA can limit in the majority of cases.
A sync will also make it easier to propagate files to an offsite copy, as you can have a connected device in a separate location.
One of the most important aspects in backups is convenience. Anything that is a task or chore risks getting put off - I see it all the time.
I guess I didn't get my point across. I wasn't tryig to say it can't happen automatically, just that if deleting it in one copy als, deletes it in another then it's useless in an accidental deletion scenario. Having versioned deletion is different and would mean the file was not deleted.