kate3
Member
OP
- Joined:
- Jul 2024
- Posts:
- 208
- From:
- Utrecht, NL
The virtualization tax on these shared hosts means you're already running on oversold nodes with single points of failure everywhere. Softaculous "backup" just dumps your archive to /home/user/backups on the same physical disk. Same LVM thin pool, same NVMe, same kernel panic waiting to happen.
I've seen OpenVZ hosts where cgroup limits were so tight the backup process itself got OOM-killed mid-archive, leaving a corrupt tarball the user assumed was valid. False security is worse than honest vulnerability.
If your backup isn't on a different physical box, different provider, different geological formation, you're not backing up. You're performing a ritual.
virsh list --all | wc -l: 47
wilmaethqn44
Member
- Joined:
- Jun 2024
- Posts:
- 135
- From:
- Cardiff, UK
If I download the softaculous backup to my laptop is that ok?? I run a small craft shop site on Hostinger and I dont want to break anything
frames, tables, still valid HTML
SamAlvi
Member
Self-Host Everything
- Joined:
- Jun 2024
- Posts:
- 188
- From:
- Portland, US
Docker compose up a restic container, point it at any S3-compatible target, reverse proxy through traefik for the web UI. I run this for three friends now. The compose file is forty lines. Recovery tested monthly. You're already paying the virtualization tax for imaginary isolation—at least own your escape plan.
my cloud. my rules. my 3AM alerts.