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
Restic seems like a solid choice for small VPS setups. I'm curious how many people actually test their restores regularly. A backup is only useful if you can recover from it.
First backup using rsync to a kimsufi server with 8tb capacity then weekly push to one drive
I have a shadow of data loss, especially after experiencing the Cloudcone incident, so now I synchronize all databases and static data to CF R2 so that I can restore it at any time and change service providers at any time.
New kid on the block: https://docs.dbackup.app/user-guide/getting-started
I just use Proxmox cluster and backup VPS to a different Hypervisor.
Not the best, but easy.
a custom ZFS based solution
Restic with rclone as the backend here. Restic takes care of snapshots, dedup and encryption, and going through rclone means the repo can live on pretty much any storage - I push to a cheap storage box plus one cloud bucket, so the same restic config covers two destinations.
Two habits that have saved me more than the tools themselves:
restic restore --target /tmp/restore-test lateston a random snapshot every month or so and spot-check a few files. A backup you have never restored from is a hope, not a backup.On the Acronis question: for a handful of small VPSes it feels like overkill to me - the centralized management is nice, but restic + a cron job + off-site keys covers the same ground for free.
Still figuring out my backup setup. For a small single VPS, is something like restic/borg overkill compared to a simple rclone sync to remote storage? Also curious how people actually test restores — "untested backups don't count" really stuck with me.
ansible pull from private github every 2 hours are my backups since the system configs are my actual important files. Docker compose files are synced there too.
borg is, but restic nope.
I use borg backup. My understanding is that restic has higher memory usage.
A good exercise is to take a spare vps, boot into recovery mode, and restore everything you need for a working system.
I keep it simple: restic to a cheap S3-compatible bucket for the data I actually care about, plus a provider snapshot before any big change. Restic's dedup and encryption are solid, and I keep the repo password outside the backup set. One habit that saved me once: actually restoring to a scratch VM now and then — an untested backup is just wishful thinking.