Right now I'm creating a nightly restic snapshot of my server on borgbase and on some spare drives, and keeping the snapshots forever. There's a ton of daily churn in my data though, between databases and logs and other files that don't constitute 'real data' but might be needed to restore the app.

you are viewing a single comment's thread
view the rest of the comments
[–] 2 points 3 weeks ago (2 children)

A back up on the same drive as the original isn't a backup. It's a waste of space, and a stupid idea.

It's a backup that helps against software errors, but not against drive failures. Depending on what you want to achieve, it's a perfectly valid strategy.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 3 weeks ago

    I generally have Operating System backups that are stored on the same drive. Those backups are immediately copied to 3 different devices, my computer and two other drives

    The backup on the local drive is useful for when I'm tinkering, making adjustments, adding or removing stuff. Restoring from that local backup is far more convenient than using the remote backups

    I don't use anything with a database so all my static media files and wiki's don't go to the local backup. I handle them separately but they are still spread across the 3 other devices in my network

  • source
  • parent
  • [–] 1 point 2 weeks ago

    Still don't consider it a proper back up personally.

    It's just not a good long term solution. A short term backup for redundancy while actively working on something sure. Just keep it local.

    But as a real actual backup? No, local doesn't cut it.

  • source
  • parent