<p><pre><code> From: DigitalOcean <support@support.digitalocean.com>
Subject: [DigitalOcean Ticket ID:xxxxx] cant power on droplet
Date: August 13, 2014 at 1:26:58 AM GMT-4
To: <xxxxxx@xxxxxxx>
Reply-To: <xxxxxxxx@support.digitalocean.com>
</code></pre>
There has been a response to your ticket:<p>Hello,<p>You will be unable to power on this droplet as it has suffered unrepairable damage.<p>We are writing to let you know that the hypervisor that hosts (redacted) has suffered a catastrophic failure. Despite repeated attempts to replace failed components and even to perform two full swaps of the system chassis, we were unable to recover it.<p>Unfortunately, the failure also resulted in loss of all data on the hypervisor. Droplets and data hosted on this hypervisor node are not recoverable, despite all of our efforts.<p>Please let us know if you need help recovering from a recent snapshot or backup. While we know that an account credit is only a small comfort when confronted with data loss, we have gone ahead and credited your account for one month of service.<p>If there is anything else we can do, please let us know. We will be standing by to assist you in recovering from this as best we can, and we have marked the IP that was associated with this Droplet as reserved to your account, so your next Droplet in the SFO datacenter should reclaim it.<p>Regards,<p>(redacted)<p>(edit: line breaks)
It's the cloud. You have backups and you can spin up a replacement server in a minute. If you don't have backups, you should probably rethink the way you use these services. Hardware fails, inevitably.
Did you have DO's backup service enabled when this happened? If so, I feel like they should have provided a more streamlined customer experience restoring the damaged/lost droplet from the latest Amazon Glacier instance.
When backups can be enabled at 20% of instance cost I'll deal with it. Nothing beyond development work runs on only one instance due to the problems I've seen even on Amazon.