So I'm glad that's over with. However, I'm also working on getting Lumpy (the old server and now the new auxiliary server) configured and ready to go. Sendmail's configuration is frickin' confusing!!! Took me forever to figure out how to configure Lumpy to relay ALL email for the nqig.net domain (including email officially destined for Lumpy) to Motoko except for root@lumpy.nqig.net, which is delivered locally, and then convincing it that's it should queue emails for up to 30 days. This basically allows Motoko to do her thing and if she goes offline, Lumpy picks up the slack and will wait 30 days for her to come back online so he can push all of the backed up email on to the users. I've setup the MX records so Motoko is MX priority 1 and Lumpy is MX priority 100, so lumpy should almost never be used (And even, if by a fluke, he is, he just forwards everything to Motoko anyway.) I've setup Lumpy as a secondary DNS server, but I won't be able to actually tell Network Solutions that my secondary's IP has changed until I actually get assigned an IP by my collocation partner. So for now lumpy is marked on Motoko as having my .155 address and I'll just change it later.
The only thing I'm having trouble with (besides finding time for sleep... *yawn* I hate it when I'm up till 1 AM and then get up at 6,) is figuring out how I'm going to handle the web site. See... If I try to make the website as a whole redundant, than I'm going to have synchronization issues with my databases, like the forum database, and the comment database here on my blog. If I use a blind failover onto Lumpy, even if lumpy has an up-to-date copy of the database, any changes made will be lost when Motoko comes back up online. Plus, the only way I can make the failover work is either by having control of the router over at qwest and have them redirect traffic to Lumpy, the other is by DNS. By making the www.nqig.net refer both to lumpy.nqig.net and motoko.nqig.net, I can have it randomly send a user to one or the other server, but then I'm stuck with having to make sure that they draw from the same database. But then, I loose all the advantage that I would normally have gained... :(
So... I think what I'm going to have lumpy do is backup my user directories, the database (By means of replication), and the website directories on a nightly or weekly basis (Probably weekly, except for DB Replication, which will happen nightly...) so that I don't have to worry about it.
Well. I have work to do...
Mood: Confused...