Earlier this week, the entire UnifiedBlue wiki went offline for a period of 24 hours or so. The reason? It would seem a failed network card (according to iWeb anyway). Although the network card itself was replaced within hours, as it took the system offline it seemed to cause HDD damage, and as such, my InnoDB suffered some page damage to one of the tables. Fortunately, the damaged table was only a cache table, but the whole saga taught me two important lessons.
The first was that I was neglecting to keep a current backup. I considered various ways to do this. Server side was one option, which involves having a secondary HDD installed in the server and having it automatically backup to that drive. It's an expensive route, but less consuming bandwidth wise. The other option was an online backup service such as DropBox. I've been meaning to give DB a try since reading a tutorial on being able to install the client text only. DB is a great bandwidth-saving zero cost option, but requires a lot of maintenance and is currently lacking in certain features.
The third option, and the one I decided to go for was the good old school method of regular downloads through phpMyAdmin. Using a secure HTTPS connection I am able to just log in monthly and download a copy, saving it to my DropBox location. Although its not the most practical, its probably the easiest option right now!
Recovering from the actual corruption was interesting, and I've detailed it on UFB here. For a good couple of hours I thought that I had possibly lost the entire thing, which was not a nice thought at all... at least its prompted me into action.
0 comments:
Post a Comment