The migration has completed. After midnight UTC we will perform the sweep mentioned earlier, and then disable migrated domains on the old server.
The migration has completed. After midnight UTC we will perform the sweep mentioned earlier, and then disable migrated domains on the old server.
One more note, in case it wasn’t made clear earlier. All new email to migrating and migrated domains is being delivered to your accounts on the new server, unless it is sent by someone using the old server. This means that email from contacts not hosted with NinerNet will arrive in your account on the new server. However, email from clients still hosted on the old server — and from people on migrating/migrated domains who are still using old email settings to send email — is being delivered to the accounts on the old server. Avoiding this overlap is why we had hoped to complete this migration on the weekend, but it will be rectified by the sweep we will make at the end of the day today.
As always, we’re here to help if any of this is confusing. Please contact support if you have questions.
Due to a mis-configuration in a script managing the migration, no email was transferred from the old server to the new, so we have restarted the migration. This means it may not complete until approximately 15:00 UTC on 7 October. At this time email is definitely transferring, and domains starting with “G” have just started migrating. As the day goes on you will notice email from the old server (if you had mail stored there) appear in your mail boxes on the new server.
Because the migrating domains are still active on the old server — they need to be for their mail boxes to be accessed from and transferred to the new server — we’ll be doing a sweep at the end of the day to make sure we transfer over any recently arrived mail. After that all migrated domains will be disabled on the old server, and only the new configuration settings for your email program will work.
Speaking of that, we have had some feedback on the new settings, mostly reports of success. Those where there have been problems were solved by making sure that the settings we have provided to you via email were set EXACTLY. When configuring email settings, there is no such thing as “close enough”. All of the settings are there for a reason and need to be set exactly as they are shown in the configuration instructions — with the one correction we made earlier to set TLS in Outlook rather than SSL. Please keep this in mind if things are not working, and compare your settings very carefully with those we have provided.
Thank-you for working with us to move your email to a new, faster more secure server.
The migration has been in progress for over hour. At this time all new email sent to those domains being migrated is being delivered to the new server. Please follow the instructions you received in your email last week to reconfigure your email program NOW.
As the start of the business day approaches in some times zones please note that, if you were expecting to find old messages in your mail box, they may not be there yet. They will appear over the next few hours.
After the last migration we had some reports that Outlook was downloading multiple copies of old messages. Please note that this is an issue with Outlook, and we have no control over it.
There is also a correction to the instructions you have received: If setting SSL on the outgoing (SMTP) server does not work for you, please use TLS. We had reports that some versions of Outlook only worked with TLS set instead of SSL.
Please contact us if you are having any problems. Please see the email you received with our email address, phone number and Skype user name. If you are not our contact for your company, please deal with the person who is our contact, and we will assist them. If they are unable to help you, they will refer us to you.
We again started experiencing Internet connection issues with our ISP at our office shortly after the scheduled start time of the migration, so we are packing up and moving to a new location. This means that we are again late getting this migration started.
We apologise again for the delays and any inconvenience.
Due to connection issues at our office with our ISP (not at the data centres where the servers are located), we are delaying this migration 24 hours. Although this ISP is generally very reliable, we will be prepared to relocate to use a different ISP tomorrow should the problem with our usual ISP continue.
We apologise for the inconvenience, and will try again at 19:00 UTC on Sunday.
NC027 is back online. It was down for 19 minutes between 20:35 and 20:54 UTC.
Server NC027 will be down for approximately 20 of the next 30 minutes while we assign additional memory to it to accommodate the email accounts that are being migrated to it.
Following the successful migration of some email accounts earlier this week, we will be migrating the email for a number of other domains to the new mail server (NC027) this weekend. If your domain will be included in this migration, you will receive an email with details.
This migration will take place at 19:00 on 5 October 2013 UTC. Please check the World Time Server for a conversion to your time zone.
The best news about this is that we will do this migration without shutting down SMTP on the old server (NC018). Therefore there will be no disruption to the accounts remaining on server NC018, or those that have already been migrated.
However, for those domains that will be migrated, there will be changes required to the configurations of your email programs. These details will be provided in the emails we will send to you before the migration starts.
It your domain is included in the migration, you will be moving to a much newer, faster and more secure server.
Updates will be posted here leading up to, during and following the maintenance. Please inform colleagues, employees and anybody else using email on your domain.
If you have any questions, please contact support and we’ll be happy to assist.
Thank-you.
Maintenance on server NC027 to increase its memory has been successfully completed. The server was down from 01:39 to 01:55 UTC.
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: