Cloud Server Maintenance and Upgrade Steps for Migration
We routinely perform maintenance on the infrastructure running the Cloud. The majority of maintenance is performed transparently but there are rare cases where a reboot of customer instances is required.
When we know we will be inconveniencing our customers Rackspace seeks to provide flexibility and options for customers to navigate the timing of maintenance around their business procedures and objectives.
The self-initiated automated migration process described here is one of those ways customers can structure maintenance to minimize its impact. Once we enable the process for your account, you may complete the process either through the API or the control panel. Either way you prefer, please make sure to wait until you receive notice from Rackspace that we have enabled your account for self-initiated automated migrations.
We expect customers to use this functionality in the following likely scenarios:
- To control when the maintenance occurs to match the least busy time of the week for their business
- To perform the maintenance of any critical redundant systems piece by piece so as to avoid application downtime.
- To test this maintenance on a small number of instances before rolling it out to the bulk of their servers
- To take preparatory steps to mitigate the duration of the migration and any potential downtime
If you choose to use our New Cloud Control Panel, please log in as you would normally. You can also log in to your control panel by clicking here.
Once logged in click on the Servers option in the top menu, click the gear menu for your server, and select Reboot Server.
For the devices that are included in the maintenance notification choosing this option will result in the completion of the required maintenance.
Next, you will want to select the soft reboot option.
Please note: Pushing the Reboot Server button kicks off processes in the background that need to complete before the reboot can start. You will be able to monitor the status of your maintenance through the New Cloud Control Panel by watching the server list.
These statuses will be shown as:
- Queued for move
- Preparing to Move
These background processes will cause a delay between the moments when you push the button to when your Cloud Server will actually reboot. The delay will vary in duration depending on the size of your server and the time you push the button so please be prepared for the reboot to happen up to 30 minutes after you initiate the process.
Once your maintenance is successfully completed you will receive an email letting you know the process has been completed.
If you have additional questions or have issues with the process please contact our Support teams via chat, phone or by opening a ticket.
© 2014 Rackspace US, Inc.
Except where otherwise noted, content on this site is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License
See license specifics and DISCLAIMER