• 2 Posts
  • 78 Comments
Joined 1 year ago
cake
Cake day: June 11th, 2023

help-circle



  • Do you use garage for backups by any chance? I was wanting to deploy it in kubernetes, but one of my uses would be to back up volumes, and… that doesn’t really help me if the kubernetes cluster itself is broken somehow and I have to rebuild it.

    I kind of want to avoid a separate cluster for storage or even separate vms. I’m still thinking of deploying garage in k8s, and then just using rclone or something to copy the contents from garage s3 to my nas


  • I really like mine too, I also have a tube and a pro. Both of them have a weird issue with the TV I use most often though. Both shields won’t display anything unless I boot them in safe mode.

    They both work on a different tv that is 4k. This one is an older 1080p plasma. But it’s weird that it used to work just fine. It might be related to the TV, but no other devices have issues so it’s cheaper to replace one of the shields than buy a new tv lol.





  • It’s mostly working fine for me.

    An alternative I tried before was just whitelisting which IPs are allowed to access specific ingresses, but having the ingress listen on both public/private networks. I like having a separate ingress controller better because I know the ingress isn’t accessible at all from a public ip. It keeps the logs separated as well.

    Another alternative would be an external load balancer or reverse proxy that can access your cluster. It’d act as the “public” ingress, but would need to be configured to allow specific hostnames/services through.


  • I did actually consider a 3rd cluster for infra stuff like dns/monitoring/etc, but at the moment I have those things in separate vms so that they don’t depend on me not breaking kubernetes.

    Do you have your actual public services running in the public cluster, or only the load balancer/ingress for those public resources?

    Also how are you liking garage so far? I was looking at it (instead of minio) to set up backups for a few things.







  • I have not had any issues with Kopia so far, but I have also only used it for maybe a year? My main reason for trying it was that I wanted to be able to give something to family members to use as a backup client with a reasonable ui. I can also control the default exclude list and default policies for compression/etc pretty easily.

    I don’t know how many years of restic backups I have, but I still rely on it for my most important data. Anything really important on my desktop/laptop gets backed up via kopia, but also gets copied (usually via nextcloud) to a server that has hourly zfs snapshots and daily restic snapshots. Both the restic and kopia snapshots get stored on a local nas and then synced to rsync.net.


  • I was talking about dumping the database as an alternative to backing up the raw database files without stopping the database first. Taking a filesystem-level snapshot of the raw database without stopping the database first also isn’t guaranteed to be consistent. Most databases are fairly resilient now though and can recover themselves even if the raw files aren’t completely consistent. Stopping the database first and then backing up the raw files should be fine.

    The important thing is to test restoring :)