Basically title. I’m in the process of setting up a proper backup for my configured containers on Unraid and I’m wondering how often I should run my backup script. Right now, I have a cron job set to run on Monday and Friday nights, is this too frequent? Whats your schedule and do you strictly backup your appdata (container configs), or is there other data you include in your backups?

    • IsoKiero@sopuli.xyz
      link
      fedilink
      English
      arrow-up
      0
      ·
      2 years ago

      Yep. Even if the data I’m backing up doesn’t really change that often. Perhapas I should start to back up files from my laptop and workstation too. Nothing too important is stored only on those devices, but reinstalling and reconfiguring everything back is a bit of a chore.

  • JASN_DE@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    2 years ago

    Nextcloud data daily, same for the docker configs. Less important/rarely changing data once per week. Automatic sync to NAS and online storage. Irregular and manual sync to an external disk.

    7 daily backups, 4 weekly backups, “infinite” monthly backups retained (until I clean them up by hand).

      • tal@lemmy.today
        link
        fedilink
        English
        arrow-up
        0
        ·
        2 years ago

        You’re correct and probably the person you’re responding to is treating one as an alternative as another.

        However, theoretically filesystem snapshotting can be used to enable backups, because they permit for an instantaneous, consistent view of a filesystem. I don’t know if there are backup systems that do this with btrfs today, but this would involve taking a snapshot and then having the backup system backing up the snapshot rather than the live view of the filesystem.

        Otherwise, stuff like drive images and database files that are being written to while being backed up can just have a corrupted, inconsistent file in the backup.

        • QuizzaciousOtter@lemm.ee
          link
          fedilink
          English
          arrow-up
          0
          ·
          2 years ago

          Absolutely, my backup solution is actually based on BTRFS snapshots. I use btrbk (already mentioned in another reply) to take the snapshots and copy them to another drive. Then a nightly restic job backs up the latest snapshot to B2.

        • vividspecter@lemm.ee
          link
          fedilink
          English
          arrow-up
          0
          ·
          2 years ago

          btrbk works that way essentially. Takes read-only snapshots on a schedule, and uses btrfs send/receive to create backups.

          There’s also snapraid-btrfs which uses snapshots to help minimise write hole issues with snapraid, by creating parity data from snapshots, rather than the raw filesystem.

          • tal@lemmy.today
            link
            fedilink
            English
            arrow-up
            0
            ·
            2 years ago

            and uses btrfs send/receive to create backups.

            I’m not familiar with that, but if it permits for faster identification of modified data since a given time than scanning a filesystem for modified files, which a filesystem could potentially do, that could also be a useful backup enabler, since now your scan-for-changes time doesn’t need to be linear in the number of files in the filesystem. If you don’t do that, your next best bet on Linux – and this way would be filesystem-agnostic – is gonna require something like having a daemon that runs and uses inotify to build some kind of on-disk index of modifications since the last backup, and a backup system that can understand that.

            looks at btrfs-send(1) man page

            Ah, yeah, it does do that. Well, the man page doesn’t say what time it runs in, but I assume that it’s better than linear in file count on the filesystem.

  • Andres@social.ridetrans.it
    link
    fedilink
    arrow-up
    0
    ·
    2 years ago

    @Sunny Backups are done weekly, using Restic (and with ‘–read-data-subset=9%’ to verify that the backup data is still valid).

    But that’s also in addition to doing nightly Snapraid syncs for larger media, and Syncthing for photos & documents (which means I have copies on 2+ machines).

  • Lucy :3@feddit.org
    link
    fedilink
    English
    arrow-up
    0
    ·
    2 years ago

    Every hour, automatically

    Never on my Laptop, because I’m too lazy to create a mechanism that detects when it’s possible.

    • thejml@lemm.ee
      link
      fedilink
      English
      arrow-up
      0
      ·
      2 years ago

      I just tell it to back up my laptops every hour anyway. If it’s not on, it just doesn’t happen, but it’s generally on enough to capture what I need.

  • hendrik@palaver.p3x.de
    link
    fedilink
    English
    arrow-up
    0
    ·
    edit-2
    2 years ago

    Most backup software allow you to configure backup retention. I think I went with some pretty standard once per day for a week. After that they get deleted, and it keeps just one per week of the older ones, for one or two months. And after that it’s down to monthly snapshots. I think that aligns well with what I need. Sometimes I find out something broke the day before yesterday. But I don’t think I ever needed a backup from exactly the 12th of December or something like that. So I’m fine if they get more sparse after some time. And I don’t need full backups more than necessary. An incremental backup will do unless there’s some technical reason to do full ones.

    But it entirely depends on the use-case. Maybe for a server or stuff you work on, you don’t want to lose more than a day. While it can be perfectly alright to back up a laptop once a week. Especially if you save your documents in the cloud anyway. Or you’re busy during the week and just mess with your server configuration on weekends. In that case you might be alright with taking a snapshot on fridays. Idk.

    (And there are incremental backups, full backups, filesystem snapshots. On a desktop you could just use something like time machine… You can do different filesystems at different intervals…)

  • Lem453@lemmy.ca
    link
    fedilink
    English
    arrow-up
    0
    ·
    2 years ago

    Local zfs snap every 5 mins.

    Borg backups everything hour to 3 different locations.

    I’ve blown away docker folders of config files a few times by accident. So far I’ve only had to dip into the zfs snaps to bring them back.

    • Avid Amoeba@lemmy.ca
      link
      fedilink
      English
      arrow-up
      0
      ·
      2 years ago

      Try ZFS send if you have ZFS on the other side. It’s insane. No file IO, just snap and time for the network transfer of the delta.

      • Lem453@lemmy.ca
        link
        fedilink
        English
        arrow-up
        0
        ·
        2 years ago

        I would but the other side isn’t zfs so I went with borg instead

  • itsame@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    2 years ago

    Using Kopia, backups are made multiple times per day to Google drive. Only changes are transferred.

    Configurations are backed up once per week and manually, stored 4 weeks. Websites and NextCloud data is backed up every hour and stored for a year (although I’m doing this only 7 months now).

    Kopia is magic, recommended!

  • AnExerciseInFalling@programming.dev
    link
    fedilink
    English
    arrow-up
    0
    ·
    2 years ago

    I use Duplicati for my backups, and have backup retention set up like this:

    Save one backup each day for the past week, then save one each week for the past month, then save one each month for the past year.

    That way I have granual backups for anything recent, and the further back in the past you go the less frequent the backups are to save space