Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

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.



I see DO's weekly backup as a convenience feature for if you need to restore your server, not as your primary backup method. Use the DO snapshot to restore most of the way, then run an up-to-date differential restore from your other (real) backup solution (that is hosted somewhere else).


But wouldn't it be much more convenient (largely because of the complexity) to have the complete backup solution at the same place (i.e. DO)?

Obviously, you want some offsite backups rather than completely relying on DO but that should be for disaster recovery (massive failures in DO's DCs, etc) rather than a more routine one.


Agreed. When you actually need to restore something from backup, often you need a fairly recent state. Hours or days ago (and not 7 days ago).

Having something 7 days old might be useful in some cases (especially e.g. DB dump) but it is far from 'good enough'.

I am not sure what's the reason why they do not provide more recent backups (for additional fee, obviously).

Would it be so complicated that the engineering effort required wouldn't make it worth it? Or such a service wouldn't be popular enough among DO users?


If you're going to switch to linode you might just as well use any public torrent tracker to store your backups.


What did Linode do this time?


You mean besides having a very long history of covering up hacks and straight up deceiving their customers?


Yes exactly besides that. What makes you feel your data is public that its better to host on a public tracker?

Because all those earlier breaches(which you are referring to) revealed customer info not their data. If this was your point of user info, I wouldn't have asked.


Every single one of the previous hacks was used to access customer VMs, except for the passwordless MySQL server they had.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: