1,882 karma · joined August 22, 2008
Location: Austin, TX / Los Angeles, CA
Drop me a line at janitha@janitha.com if you have something to talk about
#--hackrtrackr:z0zfrO8MC5bQsROWpv2LCko5al0sRR#
[ my public key: https://keybase.io/janitha; my proof: https://keybase.io/janitha/sigs/GsifrQ48ZPfegD3cJMdiOFHkPVYbeQIizibKRShKN08 ]
meet.hn/city/30.2711286,-97.7436995/Austin
Socials:
- github.com/janitha - instagram.com/psynack - linkedin.com/in/janitha - janitha.com
A cheap one time procedure (ie. vasalgel) is far less lucrative than a pill that need to be bought repeatedly.
An anecdotal data point, but I've been running the home-assistant container image on k8s without any issue, and I have a lot of integrations.
I've only verified with a smaller test dataset to validate the workflow on s3 deep archive (retrieval is $0.02/GB). I've done full backup/restore with the zfs send/gpg/recv workflow successfully (to a non aws s3 destination), and used s3 for quite a long time for work and personal without issue, so personally I have high confidence in the entire workflow.
aws s3 cp s3://... - | gpg -d ... | zfs recv ...
When restoring the order of restores matters, you first need to restore the full snapshot, and then the subsequent incremental ones in order. sudo zfs send -i <LAST_BACKUPED_SNAPNAME> <CUR_SNAPNAME> | gpg -e -r <YOURKEY> --compress-algo none -v | pv | aws s3 cp --storage-class DEEP_ARCHIVE - s3://<PATH_TO_DEST>.zfs.gpg
The very first time you do it, you will need to do a full backup (ie. without the `-i <...>` option). Afterwards, subsequent backups can be done with the -i, so only the incremental difference will be backed up.I have a path/naming scheme for the .zfs.gpg files on s3 which include the snapshot from/to names. This allows to determine what the latest backed up snapshot name is (so the next one can be incremental against that). And also use when backing up, since the order or restore matters.
I have a ZFS based NAS. And periodically do a incremental backup (zfs send) of the entire dataset, encrypt it gpg and pipe it straight up to S3 deep archive. Works like a charm.
The catch with S3 deep archive is if you want to get the data back... It's reliable, but you will pay quite a bit more. So as a last resort backup, it's perfect.