It kinda sounds elaborate? Like, how practical is that, especially in regards to being a standard?
this post was submitted on 28 Oct 2024
32 points (94.4% liked)
Technology
1326 readers
135 users here now
Which posts fit here?
Anything that is at least tangentially connected to the technology, social media platforms, informational technologies and tech policy.
Rules
1. English only
Title and associated content has to be in English.
2. Use original link
Post URL should be the original link to the article (even if paywalled) and archived copies left in the body. It allows avoiding duplicate posts when cross-posting.
3. Respectful communication
All communication has to be respectful of differing opinions, viewpoints, and experiences.
4. Inclusivity
Everyone is welcome here regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, education, socio-economic status, nationality, personal appearance, race, caste, color, religion, or sexual identity and orientation.
5. Ad hominem attacks
Any kind of personal attacks are expressly forbidden. If you can't argue your position without attacking a person's character, you already lost the argument.
6. Off-topic tangents
Stay on topic. Keep it relevant.
7. Instance rules may apply
If something is not covered by community rules, but are against lemmy.zip instance rules, they will be enforced.
Companion communities
!globalnews@lemmy.zip
!interestingshare@lemmy.zip
Icon attribution | Banner attribution
founded 11 months ago
MODERATORS
Data density vs IOPS.
Mechanical media are slow.
Well, for backups this still sounds kinda nice
Tape backups are rather slow as well - at least as far as I know. The professional stuff was always out of my league monetary wise.
If someone has a good alternative, I'm absolutely up for it.
Currently I'm using a local server with just a RAID1 to mirror important files on my workstation and those (incremental) backups are getting encrypted and uploaded to a cloud drive.
But for really large data amounts, this isn't really practical. So I only use this route for business documents, invoices, etc.
But for large data like code, I'm currently only doing a local mirroring (although on multiple devices), so if my office burns down, I'll lose quite much - at the moment I'm lucky, because I can push my code changes to a customer git mirror, so I should be fine on that front for now.
But still, I loathe the day, I really need to restore from my cloud backup.
Maybe I should do some dry runs periodically, to verify my restore path works. But just like server stuff, I really don't like to touch it that much o:-)
I'm currently using BORG (with Vorta) to backup everything locally and distribute it to my server and the cloud.
If anyone has a better idea, I'd be really grateful...
Doing periodically hard disk backups and giving them to a partner company (while I keep theirs in my safe) seems to not really work out in the long term, as I'm often on business trips and our exchanges got more seldom over time...