On Thursday, February 23, 2016 between 17:00 and 23:00 GMT we will be decommissioning node01, our first ever Cloud node, originally deployed in our Kent Science Park datacenter back in 2012.
This work will require that the Cloud Servers on this node be shut down, their disk images will then be copied across to newer, faster nodes in our Coventry datacenter where they will be assigned new IP addresses before being booted back up in their new location.
As node01 is an older node, most customer-owned Cloud Servers have already been migrated over the last couple of years, so most of what remains is our own infrastructure Cloud Servers. We will reach out directly to the few customers who still have Cloud Servers on node01 to ensure they are aware of this migration, and we will provide assistance with the move.
Websites and email accounts hosted on server03 will be unavailable for a couple of hours while things copy across. Customers who host DNS with us (ie, they use ns1.filesanctuary.net and ns2.filesanctuary.net as their domain's nameservers) won't need to do anything as we'll take care of all the changes. Our DNS TTL is 1 hour by default so this change should kick in within an hour of the move for those customers.
Customers who use an external DNS provider will need to ensure they update all DNS records with an IP of 126.96.36.199 to point to 188.8.131.52 during this maintenance window. External DNS providers may have a TTL of anywhere up to 24 hours, so you will need to contact your DNS provider for confirmation of their TTL. If you use an external DNS provider and you are able to reduce the TTL we recommend you reduce it to an hour or less now to minimise the disruption when the change happens.
If you have any questions or concerns about this maintenance just create a support ticket and we'll help you out.
We're extending the maintenance window by 2 hours until 01:00 GMT as the file transfers are running a little slower than we'd hoped.