3 ms·
I've thought like this for a decade, then the hdd of one of my dedicated server at ovh, on which a side-project with paying users runs, failed. I was confident
by oelmekki 9y ago
I've thought like this for a decade, then the hdd of one of my dedicated server at ovh, on which a side-project with paying users runs, failed. I was confident at the moment: I had backups, I knew the server was provided with raid support, so it was just about replacing the hdd. It took one hour of downtime to replace it, and then I got a message from ovh: "the hdd has been replaced. The server still doesn't boot. Customer has to start the server in rescue mode and fix raid support". Now, I wouldn't mind learning about managing raid, but not while my service is down and I keep answering users mails about it.
I switched to aws, despite the additional cost, because it's less dangerous for a small team (or one person team, like me). I realized the additional cost was actually paying for additional services (managing everything related to hardware).