Before You Move to Performance Cloud Servers (Checklist)

Performance Cloud Servers offer a step up in drive and networking speed, but there are some considerations before moving your current environment. This checklist offers some ideas to consider to make sure you are ready to move.

Consider Before You Migrate:

  • Performance Cloud Servers are not able to resize, so making sure that you are architected well from the start is very important. Best practices would be splitting your Web and Application Servers from your Database server and putting them behind a Load Balancer. This will allow you to easily scale horizontally in the future without resulting in downtime or requiring DNS changes.


Things to do

  • If you currently have a First Gen cloud server, you will need to back up your data with Cloud Backup before you manually migrate your server. If you want to build a Linux-based server, you may move your data with rsync once your new server is built.
  • If you have a Next Gen Server, you may be able to create an image to migrate to Performance Cloud Servers. Consult the below table:
Existing Next Gen Server’s Size (RAM) Can create a Performance Cloud Server of this size via image:
512 MB 1GB or higher
1 GB 2GB or higher
2GB or higher Cannot use image to build a Performance Cloud Server


  • Check and ensure that any automation you have set up allows for a 40 GB system drive.
  • Audit your current and future storage needs to determine how to best organize the data with the Performance Cloud Server configuration. You will have multiple disks, instead of the single monolithic disk. A few options you may consider: Use the system disk only, use both the system and data disks, create a single RAID 0 volume out of the multiple data disks on larger servers, or leverage Cloud Block Storage for portability.
  • If you use Cloud Backup, ensure that all of your data is backed up when you create your new Performance Cloud Server.
  • If you have disk monitoring set up, you will have to set up monitoring for your system disk and data disk(s) separately.

Was this content helpful?

© 2011-2013 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