Sorry for adding to the massive pile of backup-related question, but I could not figure out how to manage backups from existing answers…

I want to backup my VPS setup (think container-defining files, its volumes, and etc configs), but am unsure where to put it. Does keeping these in the VPS itself make sense? If so, how do I create and manage the backup?

Also, I would need a remote copy - what is the good location for this? I wish I could copy to my laptop, but obviously I cannot do that automatically. Should I pay money for a backup? I want to avoid paying lots of money just for backups. Thanks in advance!

  • 𝕽𝖚𝖆𝖎𝖉𝖍𝖗𝖎𝖌𝖍@midwest.socialEnglish
    1·
    7 days ago

    Lots of good ideas.

    I’m a fan of stow-like tools, but there are advantages to using something like Salt (or similar) if you’re dealing with VPSes that share don’t common configs like firewalls. There’s a lot to learn with things like salt/chef/puppet/attune/ansible, whereas something like yas-bdsm, which is what I’m currently using, is literally just:

    1. Keep your configs in a git repos, in a structure that mirrors your target
    2. Run a command and it creates symlinks for the destination files
    3. Commit your changes and push them somewhere. Or just restic-backup the repos.

    The config file formats are irrelevant; there’s no transformation logic to learn. Its greatest feature is its simplicity.