This forum post details how to migrate from the St. Louis (STL) datacenter to the Chicago (ORD) datacenter. This post outlines the following:
• Migration windows period
• Importance of self migration
• Migration process overview and step-by-step migration process
• Frequently-Asked Questions
MIGRATION WINDOWS PERIOD
As previously communicated, all Slices in the St. Louis (STL) datacenter will be migrated to the Rackspace Chicago (ORD) datacenter. Migration windows will open January 16, 2012 and will continue throughout the first quarter of 2012 until all customers are successfully migrated. Migration windows will vary for each customer. You will receive an email the day before your migration window opens.
IMPORTANCE OF SELF-MIGRATION
Migrating your own Slice(s) allows you to be in control of when your Slice migrations take place. Additionally, it will minimize the impact to your service or business. This allows you to prepare for changes to both your Slice's private and, if applicable, public IP addresses.
If you do not self-migrate your Slice(s) at the end of your migration window, your Slice(s) will automatically be migrated.
For all Slices, the migration will result in a private IP change. If both your public and private IP must change, however, it is in your best interest to self-migrate since you will need to update your DNS entries to your new IP address. Please note that only slices in STL-A with IP addresses in the range 126.96.36.199 - 188.8.131.52 will have to change their public IP addresses. All other slices in STL-A and STL-B will not have to change their public IP addresses.
MIGRATION PROCESS OVERVIEW
You will receive an email the day before your migration window opens. You will be given a two-week migration window for all your Slices. Additionally, you will be able to choose when each Slice is migrated within that window.
In preparation of migrating your Slice(s) take a few minutes to review this Migration Best Practices article.
After you receive your open migration window announcement you will need to log into SliceManager and click on the "DataCenter migration" link. This will take you to the Slice Migration page, where you can select the Slice(s) that you would like to have migrated. After you have migrated a Slice, you will receive an email requesting you to confirm that your new Slice is working properly. You will then verify it has been properly migrated in the SliceManager. Once verified any backups or snapshots associated with the Slice are copied to ORD.
Once your last Slice has been migrated, a final email will be sent to you indicating completion of your migration.
The datacenter migration process will work much like the Slice resize process. A new Slice will be created in ORD and your data will be synchronized to the new Slice from the old Slice. Your old Slice will be shut down and any differential data changes will be synchronized as a final step before finalizing your new Slice. The difference from the current Slice resize process is that instead of changing Slice flavors you will be changing datacenter locations.
MIGRATION STEP-BY-STEP PROCESS
Step 1. Locate the new "DataCenter Migration" link on the left hand side of SliceManager once your migration window opens.
Step 2. Once you click the "DataCenter Migration" link you will see a list of all your Slices that are eligible for migration. Both your previous IP address and your new IP address will be listed for each Slice.
Step 3. Select your Slice(s) by checking the check box for the Slices you would like to have migrated.
Step 4. Click the "Migrate" button to begin the migration process.
Step 5. You will see that your Slice(s) have moved from the "Slices to Migrate from St. Louis to Chicago"" to the "Slices Migrated to Chicago" section. Here, you will be able to watch the status of your Slice through the migration process real time (you will need to refresh your browser).
Step 6. After your migration has completed you will receive an email asking you to validate that your Slice(s) migrated successfully. Check to see if your Slice(s) is working properly.
Step 7. Click the "Verify" button under the "Action" header to confirm that your Slice(s) is working properly. If you encounter problems with your Slice(s) click the "Revert" button and your Slice(s) will rollback to the original Slice in STL.
PLEASE NOTE: If you do not verify that your Slice(s) has been successfully migrated within 24 hours, it will be auto-verified. If after auto-verification you need to revert your Slice you will need to contact Slicehost Support to assist with reverting your Slice back to STL.
Step 8. After clicking either the "Verify" or the "Revert" button you will see a confirmation box asking you to confirm your decision.
Verify Confirmation Box:
Revert Confirmation Box:
Step 9. After verifying your successful Slice(s) migration, the status of your Slice(s) will change.
Step 10. After your successful migration, your Slice(s) are Active and have the new IP address listed.
Q: Will there be down time associated with this migration?
A: Yes, you will incur down time while the differential data updates and gets synchronized to your new Slice. The datacenter migration process will work much like the Slice resize process. A new Slice will be created in ORD and your data will be synchronized to the new Slice from the old Slice. Your old Slice will be shut down and any differential data changes will be synchronized as a final step before finalizing your new Slice. The difference from the current Slice resize process is that instead of changing Slice flavors you will be changing datacenter locations.
Q: What happens to IP addresses?
A: Your public IP address may not change, however, your private IP address will change. You will be able to view your current and new IP addresses in the SliceManager once the migration window opens. Once your Slice is migrated, the public IP address will automatically point to the new Slice. For customers currently leveraging private IP addresses for inter-slice communication, you may temporarily shift to using public IPs BEFORE the migration. This will enable individual Slices to be migrated and still be able to communicate with other Slices. Once all Slices have been migrated, you can shift communication back to using the new private IPs.
Please note that only slices in STL-A with IP addresses in the range 184.108.40.206 - 220.127.116.11 will have to change their public IP addresses. All other slices in STL-A and STL-B will not have to change their public IP addresses.
Q: What happens if something goes wrong?
A: If you notice errors or the Slice isn't working properly there will be a "Revert" button for you to select. Choosing to revert will reactivate your Slice in the STL datacenter. Also remember we are here to help, so don't hesitate to start a chat or submit a ticket if you need additional assistance.
Q: How will communication be handled prior to the migration windows?
A: The day before your migration window opens you will receive an email that will include the exact start and end date of your migration window. You will also see a new "DataCenter Migration" link in SliceManager. This page will list all Slices that will be eligible for migration. These Slices will list the current public and private IP addresses and the new public and private IP addresses that will be used during the migration. For most customers the public IP address will be the same for current and new.
Q: What happens if I do not migrate my Slice(s) during this two-week window?
A: If you do not migrate your Slice during your two-week window, it will be automatically migrated for you on the last day of your migration window. If the Slice is not working properly, you must submit a ticket to have the migration rolled back and your STL Slice reactivated.
Thanks again for your understanding and feedback during these changes. If you have any questions or concerns please contact us at email@example.com.