Received email announcement regarding AMS1 migration to AMS2.
The only thing you did not say, and it would be interesting for all:
Will migrated server to AMS2 keep the same IP address ?
As a continuation of our infrastructure performance and reliability upgrades, we have decided to deprecate the AMS1 region.
All existing Droplets in AMS1 will join the AMS2 region and will undergo a physical migration to the AMS2 data center on a new code-base. We want you to be as informed as possible regarding a few upcoming changes, below we’ll outline what it means for you and a timeline in which this will occur:
On September 11, we will be disabling all new Droplet creates in AMS1. In effect your Droplet will be located within the AMS2 network. Over the next week we’ll be converting all Droplet images to be compatible with our newest codebase. As a benefit of this, you’ll be able to leverage private networking in AMS2 on all brand new hardware.
After the conversions are completed on September 17, you’ll have the opportunity in the control panel to manually migrate your Droplet to the new codebase. This migration will also physically move your Droplet from AMS1 into the AMS2 facility. We’ve setup a direct link between the data centers to ensure this happens quickly!
If you choose not to manually migrate your Droplet, you’ll receive a notice 7 days ahead of the scheduled migration, and our system will automatically migrate your Droplet. Throughout a period of approximately 6 hours all the Droplets on the hypervisor where your Droplet resides will be migrated to a new host. We spread out the migrations to ensure that each of them run in a timely manner and completes successfully.
When your specific Droplet is queued for migration it will be powered off and you can expect about 1 minute of downtime per GB utilized of your Droplet’s disk size.
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.