Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

DigitalOcean lost our server

murze.be

Post reply on HN
Print view View original

31–40 of 219 posts

Re: DigitalOcean lost our server

#35

Post by trustfundbaby »

The weekly backup deal is something I really do not like with Digital Ocean, I think Linode does it better, I've been planning to move for a while now, I've just been super lazy, but this might be the push I need. 7 days of lost data is unacceptable to me, especially when I'm paying for backups.

> Three backup slots are executed and rotated automatically: a daily backup, a 2-7 day old backup, and an 8-14 day old backup. A fourth backup slot is available for on-demand backups.

Re: DigitalOcean lost our server

#37

Post by codazoda »

Although I have backups of my critical files, I don't want to try to rebuild from those files if I can help it.

After learning that Digital Ocean does no backups of their own (even for critical hardware failure on their own side) I've enabled weekly backups for an additional $1 per month.

Glad you posted this so that I know that option is available and really necessary. And who wouldn't pay $1?

Edit: It costs 20% but I only pay $5 for my personal server.

Re: DigitalOcean lost our server

#38

Post by mikeash »

chrismartin wrote: post #26

Probably due to optimization of the conversion funnel, it's VERY easy to build things on DigitalOcean without understanding that - unlike many other *-as-a-service - droplets do not include backups and that is your responsibility. As a sysadmin, this is fine since I don't trust a single provider for both prod and backups anyhow, but I fear for those who are just getting started and don't realize this. I agree that DO…

I would really hope that the presence of a "Backups" checkbox on the droplet creation page is enough to tell the (presumably tech-savvy) user that backups don't happen unless you check that box.

Re: DigitalOcean lost our server

#39

Post by cortesoft »

gdgtfiend wrote: post #4

This seems like a non-issue to me. If you're using an IaaS provider you should be treating the network as volatile from the get-go. This is the reason AWS has things like auto-scaling groups. You should be designing for failure in "the cloud"

It is no different if you are running your own hardware - your server hardware can fail no matter who owns the machine.
Post reply on HN