We’re going to switch to the new database server tomorrow evening 23-Sep-2013 at 2000Z. However, the switch over takes sometime to propagate around the internet.
First the old database server will be locked against further user updates at 1900Z. Shortly after this the database will be backed up and restored to the new server. There will be a new login page which will tell you that the server is locked.
AT 2000Z we will update the DNS. It can take between 24-48hrs for this to reach all DNS servers worldwide.
How will you know if it is OK for you to login? Easy, when you try to login you will see either the old server or new server depending on if you are seeing old or new DNS information. If you see a message on the login screen saying the database is locked you are seeing the old server. Try again in a few hours.
If you don’t see the message then you should be able to login.
The only thing that users need to do is to demonstrate a little patience during the switch over.
I’ll open this thread for comments once the switch over is complete. Please don’t email me about login problems until 48hrs after the start over the switch, i.e. after 25-Sep-2013 2000Z
In reply to WH6LE:
DAtabase came up earlier today and worked fine. Now getting an Internet Information Service screen IIS7. Haven’t noticed any other postings.
Pete
Pete
WH6LE I got the same thing Pete. Andy said it could take 24 to 48 hours for things to shake out on this end. Nice to hear you om. Hope you are recovering well. All the best. Scotty KG3W
If sotadata.org.uk does not work, it is worth trying www.sotadata.org.uk, and vice versa. They should be the same, but they are cached independently so you get two chances. If you normally use one, the other is less likely to be cached.
This is exactly the state of one of my many connections to the net I
can make.
I’ve just cured one of mine by restarting the browser.
The machine’s nameserver demonstrably had the correct new address, yet it still wasn’t working right. Flushing the Windows DNS cache (ipconfig /flushdns) did not help. But restarting Firefox did.