Before I quit using DigitalOcean, I enabled backups and found they were very spotty - occurring roughly weekly, but not on a predictable schedule (8 days, 6 days, 4 days, seemingly random). Not something to rely on in place of a real database backup policy (more like an emergency backup of last resort).<p>Plus, they recommend against[1] enabling backups for I&#x2F;O heavy VMs (so, databases) because of the copy-on-write implementation and its effect on I&#x2F;O performance.<p>I ended up going to AWS because I was tired of having to string together a web of iptables rules (e.g. when you provision a new webserver VM you have to iterate over your Postgres, Redis, HAProxy, Elasticsearch, etc. VMs to poke holes in their firewalls), setup WAL-E and monitoring it &#x2F; testing backups, setup 3rd party monitoring VM resources for issues (CPU&#x2F;memory&#x2F;disk space), having to manage package updates and security fixes, aggregating logs to a 3rd party with rsyslog, all that stuff.<p>Unless your app is a complete throwaway that you don&#x27;t care about getting hacked or losing all your data, you quickly have to start worrying about this stuff and it becomes a huge burden to roll it yourself on VPS providers.<p>[1]: <a href="https:&#x2F;&#x2F;www.digitalocean.com&#x2F;community&#x2F;tutorials&#x2F;understanding-digitalocean-droplet-backups" rel="nofollow">https:&#x2F;&#x2F;www.digitalocean.com&#x2F;community&#x2F;tutorials&#x2F;understandi...</a>