Sipherx wrote:
I know there is a way to use mysql as master and a slave server, so whenever the master db is updated it automatically updates the slave server. So what you could do (if u use mysql) you could have linode's entire mysql db updating a slave db on an entirely diffferent network and server and whenever the linode.com site goes down, just change the dns to the new server, and it would be an exact up to date copy. Now what you could do from there, is set restrictions on this site, to not allow people to loging to the Members section, since their linode could or could not be down, and things like that. Just a suggestion, I could be way off, you guys may not even use mysql.
So what you're saying, in more words is:
1. Become a customer of someone other than Linode for your "backup."
2. Most linode outages are long enough to exceed your DNS TTL.
As for #1, I sure don't want to bring in another provider until it's absolutely necessary. It may be approaching that.
As for #2, my DNS TTLs are mostly around one day, in some cases longer. My DNS zones are quite static. If there was a linode outage longer than a day, your approach would probably not be inaccurate -- I'd be migrating my mySql servers to another provider for good.
Neither address the fact that it seems Linode is using a lot of equipment that shouldn't be in a for-profit environment. A *known* flaky power unit shouldn't be left in service. ATA/SATA drives might not be the best choice for these servers if: 1. they have a documented higher failure rate than SCSI/FC, and 2. the RAID controllers used in linode servers do not support hotswap replacements or rebuilding. (A failed disk led to two recent outages because of the fix procedure provided by linode.)