51–56 of 56 posts
Earlier quoted context omitted.
> borg (vorta) So that's like an assimilated Weyoun or what?
Offtopic, but this has reminded me that allegedly some of the more obscure star trek novels actually did do some kind of borg-meets-dominion crossover. (and on the seventh day, the devops nerd didst look upon his backups, said "this is good", and enjoyed a trashy scifi book)
A gentle reminder to actually TEST your restore workflow. WBD: since 2011! https://hn.algolia.com/?q=worldbackupday
People always say that but what do they actually mean? Restore one file, check if the backup is bootable in case it should?
Earlier quoted context omitted.
Well the current system is a shell script with rsync that I wrote but I'd like something slightly more sophisticated without having to build logic myself for incremental backups, potentially encryption, etc, etc
They might have meant rclone: https://rclone.org/
Earlier quoted context omitted.
It may look messy but this is really the minimal amount of info. You need the location of backup, operation, time for restoration, pattern to restore and the destination. If you already set up the backup part of restic, then this command shouldn't be hard to understand / reproduce at all. You could maybe default to latest and default to restoring to ".", but that carries some risks. This is only as complex as necessa…
> this command shouldn't be hard to understand I understand the command, I'm just questioning the example if they want to do some positive marketing for the tool. Something simple like the following gives the same information but is much more understandable than unnecessarily convoluted directory names. restic -r /backups/restic restore latest --target /home/dewey --include /home/dewey/myfile.txt
I commend his real example "* From my recent .bash_history".
If someone is intimidated by paths in the CLI, the tool isn't for them. Appropriate solutions and their value is relative. Better to be realistic and honest than push people to adopt something they may struggle with.
Besides, this is HN.
Coincidentally this landed on my weekly backup day. Using Time Machine weekly to an external SSD. Also a separate flat monthly archive to another SSD. And just in case that is not enough, rclone my documents and pictures library (everything) to S3 monthly too. This is restored once a quarter into my spare Mac mini.
In the same breath, lost a lot of spinning rusts over the years, and been at the mercy of data recovery services. Multiple copies, both cold and hot ones backed by parity are important.
I've lost drives I'm restoring backups from multiple times too, as restoration operations tend to be intensive and extended. I also don't recommend the average external spinning rust in a caddy as they're usually not very well ventilated, so they can get very hot and suffer from diminished longevity. Not to mention that a lot of off-the-shelf external drives already in an enclosure are frequently B-grade, or refurbished drives. Yes, even from big manufacturers. Storage is fairly woeful.
Just wait until this becomes so big that like backblaze starts crashing on March 31st because of the flood of uploads.