New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
one option that comes to mind is,
If you can boot into a rescueCD/GRML type operating system, you can technically create a disk image copy (via DD) and directly scp it to a remote backup server. That way you have a full disk image available for restore as well.
If you want to backup on a service level basis, you can use chatGPT to backup the configuration changes to git and then similarly bash scripts to backup things like databases etc every X hours or days too.
Also it is common to use Docker/podman - basically all your services stored in a single configuration file (or multiple if you have different application deployed separately). In most cases, services settings are stored in .env files within the same directory as compose yaml definition. You can easily backup both config and data in this approach.
Alternatively, you can use btrfs/zfs that offer snapshots on their own, so you can have full system backups without support from provider itself.
As for backup tools, I recommend you to look into https://torsion.org/borgmatic/