How to: Migrate Agility from On-Demand to On-Premise

This feature is available in all editions

Background

Sometimes product owners find it valuable to take their Agility instance from On-Demand (Agility Hosted) to On-Premise. The most common scenario is when a product owner wants to start a trial quickly using our On-Demand environment but desires to bring it On-Premise to leverage their existing infrastructure.

The Process

Setup the Local Environment

1. Ensure your new server is set up according to the System Requirements section of the installation documentation
2. Follow the instructions in the installation documentation to create a new application instance. Don't forget to include copying the license! (If you haven't already received the installation files, then please contact your Account Manager.)
3. Log in with admin/admin to verify the installation completed successfully

Practice Migrating with your Production Data

1. We will provide you with a link to download your database backup. We now run SQL2008 R2 in our production environment, so we would also like to know if you're planning on using SQL 2005, 2008, or 2008 R2. If it's 2005 or 2008 (pre-R2), we can do a db conversion to that version of SQLServer as part of the process, but we'll need to know in advance.
2. Restore the backup to your application instance's database (overwriting that database).
3. Run the Agility install program on the webserver and upgrade the instance. See the installation documentation for more information.
4. Log in to verify the migration completed successfully

Final Migration

1. We will work with you to schedule the exact time window for your migration.
2. Schedule downtime for the migration with your users.
3. We will provide you with a link to your database backup during the scheduled migration window and shutdown your existing On-Demand instance.
4. Restore the database backup to your production instance's database (overwriting that database).
5. Download the latest installation package.
6. Run the Agility installation program and upgrade the production instance, making sure to select your restored database.
7. Log in to verify the migration completed successfully