DigitalOcean lost our data and gave us $500
dfernandez.me
DigitalOcean lost our data and gave us $500
1–10 of 69 posts
Re: DigitalOcean lost our data and gave us $500
#2Re: DigitalOcean lost our data and gave us $500
#3Hardware failures happen; an application needs to be tolerant of it.
Re: DigitalOcean lost our data and gave us $500
#4EDIT: s/years/months/g. Thanks.
Re: DigitalOcean lost our data and gave us $500
#5With that being said, these days it's a good idea to use a deployment tool or configuration management system like puppet/salt/ansible/chef/etc, especially in a virtualized environment. This will help with scalability as well as situations such as these.
Re: DigitalOcean lost our data and gave us $500
#6Re: DigitalOcean lost our data and gave us $500
#7So if you were backing up your data to Tarsnap, then you'd be up and running as quickly as you could launch a new instance and redownload everything. And $500 credit is enough to power a micro droplet for 100 months, or a small droplet for 50 months. DO handled this well. http://www.tarsnap.com EDIT: s/years/months/g. Thanks.
Re: DigitalOcean lost our data and gave us $500
#8Do you mean you had backups on digital ocean (using their backup service) or something else?
Re: DigitalOcean lost our data and gave us $500
#9I have a master Postgres database that is receiving a TON of transactions per second (I'm talking about thousand concurrent transactions). We tried running pg_dump on this database, but the DB is just too huge, and it took more than 4 days to completely dump out everything. Not only that but it impacted performance to the point where backing it up was just not feasible.
No problem.. just create a slave-DB and run pg_dump on that, right? We did just that, but the problem is that you can't run long running queries on a hot standby (queries that take more than a minute).
What would you do in my scenario? With the hot standby, I technically am backing up my data, but I would have 100% piece of mind if I could daily backups in case someone accidentally ran a "DROP DATABASE X", which would also delete the hot standby/slave db as well.