Question
Just a quick warning - London droplets aren't backing up.
- Posted July 25, 2014
I opened a ticket and DO are apparently aware of a bug on the LONDON datacentre meaning droplets aren’t backing up. At all. A bit worrying that they haven’t thought to note this on the status, or in a blog post.
So in case you were kicking back and relaxing, I’d get in there and check your droplets, and do a manual snapshot if need be. Because until it gets fixed, you might well find that your log looks like this…
Event Initiated Execution Time Backup about 3 hours ago Action Did Not Complete Backup about 3 hours ago Action Did Not Complete Backup about 5 hours ago Action Did Not Complete Backup about 6 hours ago Action Did Not Complete Backup about 14 hours ago Action Did Not Complete Backup about 16 hours ago Action Did Not Complete Backup about 16 hours ago Action Did Not Complete Backup about 18 hours ago Action Did Not Complete Backup about 20 hours ago Action Did Not Complete Backup about 22 hours ago Action Did Not Complete Backup about 23 hours ago Action Did Not Complete Backup about 23 hours ago Action Did Not Complete Backup 1 day ago Action Did Not Complete Backup 1 day ago Action Did Not Complete Backup 1 day ago Action Did Not Complete Backup 1 day ago Action Did Not Complete Backup 1 day ago Action Did Not Complete Backup 1 day ago Action Did Not Complete Backup 1 day ago Action Did Not Complete Backup 1 day ago Action Did Not Complete Backup 1 day ago Action Did Not Complete Backup 1 day ago Action Did Not Complete Backup 2 days ago Action Did Not Complete Backup 2 days ago Action Did Not Complete Backup 2 days ago Action Did Not Complete Backup 2 days ago Action Did Not Complete Backup 2 days ago Action Did Not Complete Backup 2 days ago Action Did Not Complete
(…and so on and so on)
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Thanks for sorting - it worked for one day, but unfortunately seems to have reverted to previous fault. Have updated ticket.
Hi!
Our support staff identified a bug related to backups in certain datacenters and escalated the issue to our engineering team. They have identified and resolved the issue. Any droplets created in the last day or so should not have this problem. Though droplets created prior to that which are experiencing this issue will need to follow the work around below. An update has been posted to the support tickets detailing the problem and solution.
You’re absolutely correct that we should have been providing timely updates. There was a failure to clearly communicate the issue and the ETA for its resolution. This is a problem we take seriously, and we will be putting processes into place to prevent this in the future.
We have developed a workaround to the problem which has been deployed to our systems. Unfortunately this requires you to fully power off and power back on your droplet. You can perform this action via our control panel by selecting your droplet, going to the Power tab, and issuing a power off followed by a power on. Again, the power cycle feature will not resolve this problem – it’s necessary to completely power off and power back on your droplet as separate steps.
Ah, I have been emailing them for the last couple of days with no response!
Glad someone else has the same issue.
Annoying thing is this was all working fine on the admsterdam server, thought I would move it to london to save a few ms per request!