DIMEnoc UK Server Moves

  • Thursday, 12th July, 2012
  • 12:26pm

 

*****Maintenance has now been Completed - Please open a helpdesk ticket if you see anything unusual*****

 

This page will give information related to the major maintenance we have planned for today and tomorrow. All users have received an email giving details on this.

Please note events here are listed in time order so start from the bottom and work up for a chronological timeframe of events

========================================================

Sunday 15 July 2012 - 8.26am

All cloud servers are showing as on line. Some may take a little time for services to start up.

========================================================

Sunday 15 July 2012 - 8.17am

60% of cloud servers are now started up. Please be patient as these servers boot up and services start.

========================================================

Sunday 15 July 2012 - 8.10am

Over 30% of our cloud servers are now on line. The rest will be started shortly in batches to keep loads lower. Nearly there..

========================================================

Sunday 15 July 2012 - 7.54am

The OnApp Cluster servers are starting up now. Please note as there are many of them we are starting just a few on each Hypervisor at a time to keep loads down. You may see elevated I/O wait time on the SAN for the next while but this will quickly subside.

========================================================

Sunday 15 July 2012 - 7.35am

The OnApp Cluster CP (Control Panel) Server is now pinging (109.73.167.31). Hypervisors and the SAN will shortly be brought on line and then all Virtual Machines will be started up.

========================================================

Sunday 15 July 2012 - 7.12am

All servers are now back on line the exception being the OnApp Cluster. This is a more complex setup so was always going to take the longest to move and reconfigure. Technicians are working on this now and we will have an update soon.

========================================================

Sunday 15 July 2012 - 6.56am

Shared Server 22 is now back on line.

========================================================

Sunday 15 July 2012 - 6.51am

VPS3 Node has just come up. Containers will need to recalculate quotas as they reboot (a disadvantage of OpenVZ) so the containers will start up in sequence. There will be elevated load while this happens on all containers that are online

========================================================

Sunday 15 July 2012 - 6.48am

Server 14 has just come back on line. Others will follow

========================================================

Sunday 15 July 2012 - 6.24am

VPS2 Node just came up. Containers will start shortly. Please note a disadvantage of OpenVZ is that before a container can start it needs to re-calculate quotas. Therefore it may take up to an hour for all containers to start up and for all VPS servers on this node to start and come on line.

========================================================

Sunday 15 July 2012 - 6.19am

Sorry we grabbed a few hours sleep apologies for lack of updates here - we left the techs on the helpdesk in charge as there was nothing we could do while the technicians in the data centre racked the servers, switches etc.

Services are coming back up. At this time Server 18 is back. Other servers will be coming back shortly.

========================================================

Sunday 15 July 2012 - 3.28am

Dennis H - The Vice President of Operations at DIMEnoc/Hostdime just spoke to us and they are racking the servers right now in their Kent facility.

========================================================

Sunday 15 July 2012 - 3.20am

Nicholas D - a DIMEnoc rep has just informed us that all our servers should be ready to be booted within the hour. As soon as we have more details this will be posted here.

========================================================

Sunday 15 July 2012 - 2.52am

We are still here. Apologies for lack of updates. DIMEnoc technicians continue to work at the server move and will have services back up soon. Thanks for your patience.

========================================================

Sunday 15 July 2012 - 12.44am

We have just spoken to the technicians at DIMEnoc in Kent and the servers have not arrived yet and are still in transit. We will have an update as soon as we have some more information for you.

========================================================

Saturday 14 July 2012 - 11.04pm

Maintenance has started and all Maidenhead servers are being gracefully shut down prior to being removed from the racks and driven to Kent.

========================================================

Saturday 14 July 2012 - 10.52pm

The technicians will be starting the maintenance shortly and services will go off line momentarily. Please check this page regularly for updates. Thank You!

========================================================

Saturday 14 July 2012 - 8.10pm

We have just spoken to a senior technician who is assisting with the server moves overnight. All is set to happen starting at around 11pm or slightly beforehand. All affected servers will be gracefully shut down at start of maintenance and will then be driven from Maidenhead to DIMEnoc new facility in Kent.

We apologise once again for these moves but our reasons were explained in the emails we sent to clients recently. If anyone needs a copy of that email please open a support ticket and we will gladly send it again.

========================================================

Saturday 14 July 2012 - 4.00pm

While doing some preparation work a number of sites on Business 1 Server are throwing internal server errors. We discovered for some reason file ownerships were changed. We ran a script to change these back and everything is fine again. For those clients on this server you will already know this server is being replaced on Tuesday of next week. We know this server has been causing some annoying issues of late and we know the replacement server on Tuesday will ensure no further load issues for the longer term.

========================================================

« Back