When needing to transfer an installation from one server to another, there are a few ways that moving an install can be done. These following steps represent the best way to perform this without losing data and prevent future upgrade issues. These steps assume that the database will also be changing - whether SQL Server is installed on the IIS server or not.

Before starting, make sure that you have:

  • A copy of the installer for the same version of the application you are moving.
  • A copy of the latest installer for the application you are moving. If you are not upgrading versions, then this is unneeded.

Steps to move the application follow. If you run into any errors or any unexpected results, review all the steps up until that point, and then contact our support department.

  1. On the original server, backup the Attachments directory. You can find the location for this in Administration -> General Settings.
  2. On the new server, run the installer for the same version of the application that you have on the old server, with the following settings:
    1. Full or Custom Install.
    2. Select to Create a Database.
    3. Point installer to new database server.
  3. On your original database server, create a full backup of your application's database.
  4. On the new database server, perform a database restore. Overwrite the existing database with the backup. (Use the 'WITH REPLACE' option.)
  5. It not upgrading to the most recent version, jump to step # below.
  6. Do NOT try to access the application at this time! It will error out, this is expected!
  7. Run the installer for the new version of the application on the application/IIS server. Treat it as a normal upgrade and point it to the curent install path.
  8. The upgrade should complete successfully.
  9. Try to access the application. If you get an error stating that the database/user can not be accessed, please preform Step #4 in KB16: How do I move my SpiraTest/Plan/Team database to another server.
  10. Log in as an Administrator, and verify that the Attachments path is correct - that it exists on the new server and can be read by the IIS user.
  11. Copy the backed up Attachment files into the new server's Attachments directory.