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

It'll be a time sink. Why not do it as dirty as possible now and go back and tune it as time goes on?


See the original submission, that's why not :-)

I want to not only have a backup scheme but also make sure it's restore-tested. Maybe I wasn't totally clear, not planning on a beautiful failover in each place in the beginning (planning failover for the DB at least). Just a tested (even if manual) restore procedure in each situation.




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

Search: