The transfer of the mail spools has completed and server NC036 was brought back online at 12:12 UTC.
The transfer of the mail spools has completed and server NC036 was brought back online at 12:12 UTC.
The transfer of mail data between the old and new data centres is still underway. Considering the transfer of the same amount of data took 50 minutes over the weekend, and we are now at the 5-hour mark, it was impossible for us to predict that this would take so long.
I can assure you that I understand the frustration that you are feeling with this situation, but given the network problems in southern and central Africa that necessitated this emergency move, we had no choice but to act immediately rather than forcing many clients to do without mail until the weekend.
My best estimate at this point, based on how much data has transferred so far (55%) and how much is left, is that the transfer will complete at approximately 13:00 UTC. Assuming this is the case, the server will be back online and accessible at about 13:30 UTC.
I sincerely and deeply apologise for this situation.
The transfer is taking significantly longer than we anticipated, likely due to the greater distance between the two data centres.
We’re almost done. Just waiting for the mail spools to finish transferring, then a few checks (double-checks) to ensure that all is in order, and we’ll re-enable all services. Then more checks to ensure that mail is flowing as it should, and then we await feedback.
We’ve finished planning this emergency migration of the new mail server (NC036), and will be shutting it down within the next five minutes.
Over the weekend we successfully migrated all of the email accounts on old server NC027 to new server NC036. Except that for a large swathe of our clients, this migration was NOT a success.
We can tell you unequivocally that the new server is running and running well. It’s doing a much better job than the old server, and we splurged on a high-performance server with additional software to process mail quicker and to do a better job of filtering out spam and viruses. That part is all going great, and I can tell you that I am delighted about that part.
The part that’s not going great is that the data centre in which we placed the new server appears to have some serious networking issues for a large number of clients in southern and central Africa. We could spend the next week troubleshooting this and perhaps find the cause (and then work on addressing the cause), but you and we don’t have the luxury of that much time. Within the next few hours we will send troubleshooting instructions to affected clients, just in case.
What we are going to do to resolve this issue is use the wonders of modern technology to shut down the new server, take an image of it to preserve the time, effort and expense that has gone into creating it, and transfer it to new hardware in a different data centre. Ideally I would like to take a day to set up a test server in that data centre but, again, you can’t afford to have no or limited access to your email for a day.
Fortunately the process of moving to another data centre is quite straightforward, and will not require as much downtime as the full migration did. Copying the image from one data centre to another will be much like physically carrying the server to the new data centre; it’s already set up and configured, it just needs to be plugged in at the other end. The only thing that will not be quicker is that we have to use more traditional methods to transfer your mail spools to the new server. This took 50 minutes on the weekend, but with two equally powerful servers on both ends of the transfer it should be a bit quicker this time.
We will shut down the server at 01:00 UTC on Wednesday 6 June. Including the data transfer and some minor reconfiguration, I sincerely hope to have it back online by 03:00 UTC.
Please keep an eye on this status blog, where we will post important updates during the process.
Thank-you for your extraordinary patience.
My apologies for not getting an update out sooner, but there have been some inevitable issues.
Finally, one last apology for promising this migration three weeks ago and not actually delivering until now, and for not having all of the issues ironed out well in advance of Monday morning.
We’ll likely have additional information to post here later, but in the meantime you are welcome to contact us if you are having any issues not covered by the above.
Mail started flowing again at about 04:00 UTC. We will have some further details as time permits in the next couple of hours.
One apology: I’ve been using the wrong server number in the titles of the last few posts.
We are in the final stages of the migration to server NC036. We expect to have your email back online within the hour after finishing up testing.
After numerous delays — not the least of which is that Microsoft never did actually remove our new mail server’s IP address from their blacklist despite their saying that they had — we are finally going to migrate all email from NC027 to NC036. This will start within the next few minutes.
During the migration you will not have access to either the new or old mail servers, and you will not be able to send email. Incoming email will be held on the sending servers until the new server is live and everything is pointing to it.
As our own email on our primacy domain (niner.net) will also be down during the migration, please email us at support.201806@ninernet.net if you have any urgent queries. Note the similar but different domain.
Thank-you.
Systems at a Glance:
Loc. | System | Status | Ping |
---|---|---|---|
NC023 | Internal | Up? | |
NC028 | Internal | Up? | |
NC031 | Internal | Up? | |
NC033 | Operational | Up? | |
NC034 | Internal | Up? | |
NC035 | Operational | Up? | |
NC036 | Operational | Up? | |
NC040 | Internal | Up? | |
NC041 | Operational | Up? | |
NC042 | Operational | Up? |
Subscriptions:
Search:
Recent Posts:
Archives:
Categories:
Links
Tags:
Resources:
On NinerNet: