Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Brite
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (Cyborg)
  • No Skin
Collapse
Brand Logo

CIRCLE WITH A DOT

  1. Home
  2. Uncategorized
  3. I wrote up my entire backup strategy for my across FreeBSD and Linux:

I wrote up my entire backup strategy for my across FreeBSD and Linux:

Scheduled Pinned Locked Moved Uncategorized
backupzfsfreebsdlinuxproxmox
8 Posts 3 Posters 2 Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • larvitz@burningboard.netL This user is from outside of this forum
    larvitz@burningboard.netL This user is from outside of this forum
    larvitz@burningboard.net
    wrote last edited by larvitz@burningboard.net
    #1

    I wrote up my entire backup strategy for my servers across FreeBSD and Linux:

    - ZFS snapshots with sanoid
    - Off-site replication via syncoid to rsync.net (encrypted at rest)
    - Proxmox Backup Server fronting Backblaze B2 for VMs
    - A Podman trick for backing up RHEL hosts without native packages
    - Dead man's switch monitoring
    - Quarterly restore tests recorded with asciinema

    Real configs included.

    Link Preview Image
    My Multi-Stage Backup Strategy: ZFS, Proxmox, and Paranoia

    Backups are the thing everyone knows they should do and nobody does well enough. Here’s my multi-stage strategy for keeping about a dozen servers safe: ZFS s...

    favicon

    Larvitz Blog (blog.hofstede.it)

    #backup #zfs #freebsd #linux #proxmox #sysadmin #selfhosted

    mrsp@mastodon.cloudM jan@fedi.kcore.orgJ 2 Replies Last reply
    1
    0
    • R relay@relay.infosec.exchange shared this topic
    • larvitz@burningboard.netL larvitz@burningboard.net

      I wrote up my entire backup strategy for my servers across FreeBSD and Linux:

      - ZFS snapshots with sanoid
      - Off-site replication via syncoid to rsync.net (encrypted at rest)
      - Proxmox Backup Server fronting Backblaze B2 for VMs
      - A Podman trick for backing up RHEL hosts without native packages
      - Dead man's switch monitoring
      - Quarterly restore tests recorded with asciinema

      Real configs included.

      Link Preview Image
      My Multi-Stage Backup Strategy: ZFS, Proxmox, and Paranoia

      Backups are the thing everyone knows they should do and nobody does well enough. Here’s my multi-stage strategy for keeping about a dozen servers safe: ZFS s...

      favicon

      Larvitz Blog (blog.hofstede.it)

      #backup #zfs #freebsd #linux #proxmox #sysadmin #selfhosted

      mrsp@mastodon.cloudM This user is from outside of this forum
      mrsp@mastodon.cloudM This user is from outside of this forum
      mrsp@mastodon.cloud
      wrote last edited by
      #2

      @Larvitz this is great, thank you.

      1 Reply Last reply
      0
      • larvitz@burningboard.netL larvitz@burningboard.net

        I wrote up my entire backup strategy for my servers across FreeBSD and Linux:

        - ZFS snapshots with sanoid
        - Off-site replication via syncoid to rsync.net (encrypted at rest)
        - Proxmox Backup Server fronting Backblaze B2 for VMs
        - A Podman trick for backing up RHEL hosts without native packages
        - Dead man's switch monitoring
        - Quarterly restore tests recorded with asciinema

        Real configs included.

        Link Preview Image
        My Multi-Stage Backup Strategy: ZFS, Proxmox, and Paranoia

        Backups are the thing everyone knows they should do and nobody does well enough. Here’s my multi-stage strategy for keeping about a dozen servers safe: ZFS s...

        favicon

        Larvitz Blog (blog.hofstede.it)

        #backup #zfs #freebsd #linux #proxmox #sysadmin #selfhosted

        jan@fedi.kcore.orgJ This user is from outside of this forum
        jan@fedi.kcore.orgJ This user is from outside of this forum
        jan@fedi.kcore.org
        wrote last edited by
        #3

        @Larvitz Could you share some insights in how you configured PBS to use B2 over Cloudflare?

        larvitz@burningboard.netL 1 Reply Last reply
        0
        • jan@fedi.kcore.orgJ jan@fedi.kcore.org

          @Larvitz Could you share some insights in how you configured PBS to use B2 over Cloudflare?

          larvitz@burningboard.netL This user is from outside of this forum
          larvitz@burningboard.netL This user is from outside of this forum
          larvitz@burningboard.net
          wrote last edited by larvitz@burningboard.net
          #4

          @jan

          https://www.cloudflare.com/de-de/partners/technology-partners/scaleway/

          Traffic between Scaleway and Cloudflare isn't metered (also Backblaze isn't counting traffic towards CF!).

          If you want to avoid B2 egress fees on your Scaleway server, you'll need to route the traffic through Cloudflare (e.g., using Cloudflare Workers or fetching via a Cloudflare-proxied domain) rather than hitting the B2 S3 API directly.

          I use a cloudflare protected (sub)domain in front of my public bucket URL to ensure, that the traffic is goung through CF, and therefore is not metered at Backblaze ...

          Scaleway → Cloudflare (free, Bandwidth Alliance) → Backblaze B2 (free, Bandwidth Alliance)

          Just mind, that Cloudflare ToS doesn't actually allow that ... ( Section 2.8 of their self-serve terms)...

          jan@fedi.kcore.orgJ 1 Reply Last reply
          0
          • larvitz@burningboard.netL larvitz@burningboard.net

            @jan

            https://www.cloudflare.com/de-de/partners/technology-partners/scaleway/

            Traffic between Scaleway and Cloudflare isn't metered (also Backblaze isn't counting traffic towards CF!).

            If you want to avoid B2 egress fees on your Scaleway server, you'll need to route the traffic through Cloudflare (e.g., using Cloudflare Workers or fetching via a Cloudflare-proxied domain) rather than hitting the B2 S3 API directly.

            I use a cloudflare protected (sub)domain in front of my public bucket URL to ensure, that the traffic is goung through CF, and therefore is not metered at Backblaze ...

            Scaleway → Cloudflare (free, Bandwidth Alliance) → Backblaze B2 (free, Bandwidth Alliance)

            Just mind, that Cloudflare ToS doesn't actually allow that ... ( Section 2.8 of their self-serve terms)...

            jan@fedi.kcore.orgJ This user is from outside of this forum
            jan@fedi.kcore.orgJ This user is from outside of this forum
            jan@fedi.kcore.org
            wrote last edited by
            #5

            @Larvitz That seems to have moved a bit, but I think it still is a violation of the ToS

            https://blog.cloudflare.com/updated-tos/

            larvitz@burningboard.netL 1 Reply Last reply
            0
            • jan@fedi.kcore.orgJ jan@fedi.kcore.org

              @Larvitz That seems to have moved a bit, but I think it still is a violation of the ToS

              https://blog.cloudflare.com/updated-tos/

              larvitz@burningboard.netL This user is from outside of this forum
              larvitz@burningboard.netL This user is from outside of this forum
              larvitz@burningboard.net
              wrote last edited by
              #6

              @jan Yeah.. For my relatively small PBS server, I just "risk it" atm ...

              jan@fedi.kcore.orgJ 1 Reply Last reply
              0
              • larvitz@burningboard.netL larvitz@burningboard.net

                @jan Yeah.. For my relatively small PBS server, I just "risk it" atm ...

                jan@fedi.kcore.orgJ This user is from outside of this forum
                jan@fedi.kcore.orgJ This user is from outside of this forum
                jan@fedi.kcore.org
                wrote last edited by
                #7

                @Larvitz Thanks for the article. Food for thought.

                I'm currently doing backups offsite towards jottacloud (I send a nightly snapshot) but I'd be interested in a more integrated solution than my combination of scripts 🙂

                larvitz@burningboard.netL 1 Reply Last reply
                0
                • jan@fedi.kcore.orgJ jan@fedi.kcore.org

                  @Larvitz Thanks for the article. Food for thought.

                  I'm currently doing backups offsite towards jottacloud (I send a nightly snapshot) but I'd be interested in a more integrated solution than my combination of scripts 🙂

                  larvitz@burningboard.netL This user is from outside of this forum
                  larvitz@burningboard.netL This user is from outside of this forum
                  larvitz@burningboard.net
                  wrote last edited by larvitz@burningboard.net
                  #8

                  @jan My primary production backps are FreeBSD systems with sanoid/syncoid, just doing zfs send/recv via SSH. The Proxmox-PBS to B2 route is only for a small handful of Proxmox systems, I still run.. Just the stuff, that I can't run on FreeBSD (like Kubernetes, OCI containers, FreeIPA, Ansible Automation Platform, Red Hat Satellite, etc.)

                  1 Reply Last reply
                  0
                  Reply
                  • Reply as topic
                  Log in to reply
                  • Oldest to Newest
                  • Newest to Oldest
                  • Most Votes


                  • Login

                  • Login or register to search.
                  • First post
                    Last post
                  0
                  • Categories
                  • Recent
                  • Tags
                  • Popular
                  • World
                  • Users
                  • Groups