Need to migrate Release Management Server?

Need to migrate Release Management Server?

  • Comments 4

In order to migrate Release Management Server, follow these steps in sequence:

1. Backup existing Release Management server DB. (Learn about How to: Back Up a Database)

2. Export crypto key.  (For more details on the RSA crypto key export, check ‘Exporting an RSA Key Container’ section of Importing and Exporting Protected Configuration RSA Key Containers)

      To export the crypto key, run the command [admin mode]         

 aspnet_regiis -px "{AB903235-97E6-4B1F-AC8E-0EE51124D84F}" keys.xml –pri

 

3. Import the earlier exported crypto key. (For more details on the RSA crypto key import, check 'Importing an RSA Key Container’ section of Importing and Exporting Protected Configuration RSA Key Containers)

    To restore/import the crypto key before restoring the SQL RM DB on to different machine than the original one: Run the command [admin mode]

 aspnet_regiis -pi "{AB903235-97E6-4B1F-AC8E-0EE51124D84F}" keys.xml

 

 

4. Restore Release Management server DB on to another server. (Learn about How to: Restore a Database Backup)

5. Install RM server and configure it.

6. Configure existing client with the new Release Management Server. 

Leave a Comment
  • Please add 5 and 4 and type the answer here:
  • Post
  • Hello Anand,

    We are planning to upgrade Release management from 2013 update 2 to update 3.

    I followed the steps mentioned above, but i get the error " Object already exists" when i try to import the RSA keys. And also, when i configure the server, it will automatically try to create a "Release Management" database, but fails as it is already created from the backup. When i delete the backup and run the configuration , it throws again " Object already exists" message.

    Could you please help me fix this issue.

    Thanks in advance!

    Thanks!

  • These instructions do not work as of 1/27/2015, for Release Management 2013 Update 4.

  • I tried moving the RM Server provided by Brian Keller VS ALM to azure. It works without step 2 & 3.

    What scenario do you think I would require step 2 & 3?

    Just that, the existing Release Templates were connected to a particular TFS Build, and the Release Template did not allow me to change the Build information, even when I clone the Release Template and try to change the build definition.

  • These steps needs to be followed only when RM server is moved from one machine to another. You don't need to follow these instructions (a) If you are moving RM database from one machine to another, or (b) Upgrading RM from 2013 update 2 to update 3 or to update 4 etc., provided your RM server is not moved from one machine to another.

Page 1 of 1 (4 items)