deleted by creator

My setup is running in k8s.

I have autorestic running in a container in a pod. The container mounts the volumes from the pod, I want to have backed up. It then runs every 6 hours(easily changed via a cron expression).

The config in autorestic describes the backends(servers), that it should backup to. Currently I have 3 servers, that it is backing everything up to.

I have also added extra functionallity to autorestic, to make it create a dump of a database before the backup runs.

Might not fit into your plans but if you run Proxmox you can easily backup to an offsite computer (or VM) running Proxmox Backup Server (PBS).

I don’t back up anything I can rebuild. I have multiple half-assed methods in use together for the rest of it:

• Backups daily of homedirs on desktops and laptops using Borg and Vorta to external usb drives. These devices get rotated out annually. I used to run 2-disk RAID1 and when I rotated the disks out, split them and sent them to family but now I’m taking my chances on having them local and putting them in a fireproof box.
• Code repos are synced to github or srht.
• Monthly backups of homedirs are sent via borg to rsync.net.
• Desktop and laptop homedirs get periodic (roughly monthly) burns to Dual-Layer BDRs which I put in the fireproof box and sometimes hand off to family.

I am a fan of using Restic. More specifically using Autorestic, which is a wrapper that allows you to easily configure restic using yaml files. Since all of my services are in docker containers, I just have a hook to shutdown all my containers, do the backup, and then run all my containers again. Downtime is not an issue since it just runs when I would be sleeping. Just have it backup to Backblaze B2, which I think you get 10GB free, which is plenty for me right now.

For Kubernetes you can use Velero. I tried it, but I didn’t like it (overly complex for my use case), so I wrote my own tool.

Essentially the strategy for me is fairly straightforward, but it depends on the data you have.

I have mostly 2 types:

• manifests and configuration. This I have all in git (as I am using flux).
• persistent volumes. I use openEBS, but for a low resources cluster I use host volumes only. For these I have written my tool that simply runs as a daemonset with the whole root of the host mounted in RO and the DAC_read_search capability, queries the API for volumes and backs up using restic the whole PV to Backblaze. Incidentally, this is also the same way I do all my other backups, outside K8s (I.e.borg or restic to b2).

I chose b2 mostly for the price, but any s3 will do. Since all I am uploading there is encrypted anyway, I don’t need to worry about the privacy implication of having a third party potentially having access to my data.

I use the AWS cli to sync the data to S3 on an hourly scheduled task, then I lifecycle it down to Glacier instant access after a day. This winds up being relatively cheap and simply updates changed data, which keeps bandwidth utilization low.

I originally did this as a really cheap Dropbox alternative, but it works pretty good for backup files too.

Multiple ~2tb seedboxes. They can just get shut randomly but I haven’t had that happen to me.

Cheap storage

Not my solution, but I liked an idea and thinking to use it too - copy backups on external HDD and put it into your car trunk. Maybe have two drives in rotation.

It eliminates a need to drive somewhere for rotation, and any cost of renting a safebox.

Doesn’t protect from a serious disaster like forest fire or earthquake or nuclear war, but I keep the most important data in cloud, and if my house and car burns I would be having other problems than worrying about some homelab snapshots.

I use the Proxmox Backup server to backup my VM’s.

For Kubernetes Pvc’s I save a snapshot of the underlying block device(CephRBD) to a borg repo on my shared filesystem(CephFS) which is backed up to Backblaze.

Any backup software that supports incremental backup should work similarly bandwitdth-wise. I like Restic. You can even do incremental backups with plain rsync, if you want. If your data does not change much, than you should be okay. For the initial backup run it would be helpful if you have physical access to the remote location so you can bring a full backup there without having to upload it through your slow uplink.

EDIT: Sorry, I misunderstood this question ~~ I have a raspberry pi connected to a 1 TB SSD. This has the following cron job:

00 8 * * * /usr/bin/bash /home/user/backup/backup.sh

And the command in backup.sh is:

rsync --bwlimit=3200 -avHe ssh user@instance-ip:/var/www/mander/volumes /home/user/backup/$(date | awk '{print $3"-" $2 "-"$6}')

In my case, my home network has a download speed of 1 Gbps, and the server has an upload speed of 50 Mbps, so I use -bwlimit=3200 to limit the download to 25.6 Mbps, and prevent over-loading my server’s bandwidth.

So every morning at 8 am the command is run and a full backup copy is created.

It seems that you have a different problem than me. In your case, rather than doing a full copy like me, you can do incremental backups. The incremental backup is done by using rsync to synchronize the same folder - so, instead of the variable folder name $(date | awk ‘{print $3"-" $2 “-”$6}’), you can simply call that instance_backup. You can copy the folder locally after syncronizing if you would like to keep a record of backups over a period of a few days.

On a second thought, I would also benefit from doing incremental backups and making the copies locally after synchronizing… ~~

Primarily rely on zfs for file system replication.

I have primary/redundant nas on site, then a single node offsite connected via vpn.

On my list of things to tinker with is zettarepl.

I do it 3 ways.

1. Critical stuff (photos, documents etc) is synced in realtime to backblaze. Low RPO. Low RTO.

2. Critical stuff is also backed up to a secondary NAS 2x per day for versioned backups. And that data is synced nightly to Backblaze. Higher RPO but also Higher RTO.

3. All data from secondary NAS/Backup NAS is backed up nightly to 1 of 3 large external hard drives that are rotated monthly. Each disk holds ~30 days of backup archives from #2.

• Most recently pulled disk is stored off site. Oldest disk is brought back on site but stored in a UL rated fire safe

@[email protected] Remote backups might be rough with that upload speed. For example, you will be looking at over 2 hours per GiB uploaded.

I personally have a 3 node setup using kubernetes and I run longhorn for volume management. I do hourly snapshots, and then daily backups of all volumes to an additional drive on one of my 3 nodes with a simple NFS server which is also running in kubernetes. In longhorn I keep 2 replicas of every volume as well so losing one doesn’t hurt anything.

I would imagine it would be pretty easy in this case to replace my local NFS with AWS storage and then I would have remote backups, but since I back up roughly 100 GiB per day that would be a little time consuming. At my 50 Mbps that’s about 4.5 hours, though remote backups could be done less often as a last resort backup.