So I’ve been self-hosting for a few years now…got a decent setup…

But I only really got into docker-compose in the last few months… I mean, I’ve used it through the “Apps” in TureNAS, but never directly…

I ran a mastodon host on a VM (giant pain in the ass) and a few other things that weren’t available as apps, but never mainstream…

Once I got into it, I managed to get everything moved over to truenas as docker containers…

Last week it saved my ass…the AC in the house failed…and I was able to shut down everything save the Truenas (with a fan pointed at the front of the server) and keep everything up and running throughout…

So it’s been helpful to know, and an awesome learning experience. (I’m happiest when I’m learning new things)

My question is this…

How do you back them up? I mean, I have snapshot backups of my docker-volume ZFS dataset, and replicate that to a remote host…but I’m not even sure I’d know how to recover it if I had to…is it just a file copy and restart?

  • ShredderFeeder@shredderfood.netOPEnglish
    2·
    1 day ago

    I have another container running the proxmox backup client that does a filesystem dump daily… Not bad, but I think postgres may not recover from that…

    Right now 2 weeks of daily replicated snapshots are probably as good as I’m going to get…

    • Jason2357@lemmy.caEnglish
      2·
      1 day ago

      Works fine… Most of the time. As long as the file gets saved at an instant in time (e.g. zfs snapshot), postgres sees it like a power failure and restores. You want to have several recent backups if you do this because it will occasionally fail.

      • ShredderFeeder@shredderfood.netOPEnglish
        2·
        1 day ago

        Saw an article that says proxmox backup client can be set up to be ZFS aware…will have to do more reading… (for backups)

        Replication is always a point in time, and I keep two weeks worth of dailies.

      • ShredderFeeder@shredderfood.netOPEnglish
        1·
        1 day ago

        Well that worked… Amaze! I copied the lemmy directory to my user directory, made the necessary changes in docker-compose, and boom, it came up. If I were to script the changes using sed, I could even have a full DR failover.

      • ShredderFeeder@shredderfood.netOPEnglish
        1·
        1 day ago

        Not a bad idea…I’ll have to make some network changes in the docker compose and build a new macvlan for it…but it should be easily addressable by IP address. I did to a test startup of my mastodon DB and that did seem to work…

        And I should probably block outbound traffic just to be sure it’s not trying to update the fediverse…

        Cool, now I know what I’m playing with tonight. :)