Overview
This article outlines how to move Kiln to a different server.
If you are changing versions during the move, we highly recommend that you upgrade before you move. Alternatively, install the same version you are using on the destination server, perform the migration, and upgrade afterward. This is because of changes that are external to the database.
Resolution
- Stop Kiln, Stop FogBugz which includes stopping the Kiln Storage Service, the Kiln Queue Service, Apache Tomcat (for Kiln 2.7), and the FogBugz Maintenance Service on the old server.
- After stopping the services, make sure that the following processes have all been terminated:
- Kiln 2.7.x:
- backend
- memcached
- redis-server
- queueservice
- tomcat6
- Kiln 2.9.x:
- backend
- redis-server
- java
- queueservice
- FogBugz:
- FogBugzMaint
- Kiln 2.7.x:
- Move your KilnRepositories folder to the new server.
- Follow these instructions to move FogBugz to another server.
- Change these steps to run the Kiln installer on the new server instead of the FogBugz-only installer.
- Also, detach and reattach the Kiln database when you move the FogBugz one.
NOTE: Do not forget to Enable CLR integration if you are moving to a new SQL Server.
Related Articles:
Moving the Kiln Database (without moving the Kiln Server)