Anyone else hit by Dallas233 migration? [resolved]
Anyone else get their migration botched?
5 Replies
caker
Linode Staff
Sorry to hear of the problems with that host. Our staff is available 24/7/365, regardless of holidays. We respond to all tickets within minutes, so if you had a specific question that didn't get answered perhaps look at the ticket history and see what happened. And as always, throw an update back to us and we'll get right back with you. I'm certain the team will do whatever they can to help you.
-Chris
Basically some Linode sysadmin did not remember to boot up my VM after they fixed the botched migration. After about 24-hours when I inquired an update from my ticket, a ticket agent said something to the effect of "whoops! Forget to power up your vm", and this was after another agent told me not to do anything until I hear back from them (24-hours ago!) to fix the botched migration. Fortunately I can show my client that this was Linode's fault and that I took due diligence. I hope in the future Linode does a better job of tracking issues because something internally failed regarding their communications.
Lesson learned from this: Be vigilante and persistent about your tickets. Nag them because they may forget about you, even when they say they'll get back to you.
Case closed
I've never had a Linode fail but I've had disks fail on dedicated machines. Off-site backups made the difference between significant downtime and being back within 2 hours.
@sednet:
Also, keep up to date backups that you can restore to another server fast should you need to.
I've never had a Linode fail but I've had disks fail on dedicated machines. Off-site backups made the difference between significant downtime and being back within 2 hours.
^this. RAID 10 is redundant, but it's not failproof. If the wrong 2 disks fail at the same time, you're screwed without a backup.