Using FogBugz On Demand? We've recently rolled out a new sidebar as part of taking FogBugz forward. Please see this article for details on what's new, what's changed, and where you can find all your favorite things.
This guide applies to FogBugz 6, 7, and 8
For older versions, please contact us directly for assistance.This guide is for moving the FogBugz application (site). If you only need to move your database, see this article for SQL Server or this one for MySQL.This guide addresses a variety of server/database scenarios, and makes reference to the Accessories directory, located in your FogBugz directory. The following scenarios assume that you will be using the same database after moving.

Before doing anything: Please make a full backup of your database before performing any upgrades or moves, and verify those backups. Having backups makes sure you can roll back to your previous state if necessary.

Upgrading FogBugz: Since FogBugz will upgrade any outdated database when it runs against it, you can do the move and upgrade in one step. That said, we do recommend you upgrade in place before moving (to minimize the number of things changing at each step.

Minimizing Downtime: You can continue to use the old FogBugz installation until the new one is set up with licenses installed; then, shut down the old FogBugz, move your database, and point the new FogBugz installation to your FogBugz database.

After you move FogBugz: To be sure that permissions on the FogBugz account are correct, please step through this guide. If anything is wrong with the permissions, everything may look fine at first but problems may show up later, e.g. case attachments may fail.

Changing database types: If you are switching from MySQL to MS SQL Server or from MS SQL to MySQL, you will need to contact us to discuss a plan for converting your database.

Linux and Mac OS

  1. Run Setup on the new machine and install a new FogBugz database.
  2. Get everything working so you know the install succeeded with this new database.
  3. See To Start under Linux in How Do I Start and Shutdown FogBugz
  4. Setup the database:
    • If you are moving your database, follow the instructions here to move it to the new instance.
    • Edit the sConnectionString line in /[path to fogbugz]/Accessories/ application.data to reflect the correct database information
  5. See To Stop under Linux in How Do I Start and Shutdown FogBugz
  6. Reinstall your licenses if prompted.
  7. When everything is working, delete the empty database that setup created.

Windows

Access database

  1. FogBugz is no longer supported on MS Access databases.

MySQL database

  1. Run Setup on the new machine. Select MySQL as your database and Create new database (even if you plan to point this install at an existing one). This will make a standalone install.
  2. Install your licenses. (Note that your licenses are not tied exclusively to one server. Our licensing guidelines do permit multiple simultaneous FogBugz installations for the purposes of testing.)
  3. Stop the maintenance service on the old FogBugz server: open the Services control panel in the Administrative Tools menu and stop the Fog Creek Maintenance service.
  4. If you are moving your database, move it to the new machine.
  5. Log into FogBugz as an administrator and go to Admin -> Site Configuration(Settings -> Site in version 6) and edit the connection string in the Database tab to point to the correct database.
  6. Reinstall your licenses if prompted.
  7. When everything is working, delete the empty database that setup created.

SQL Server database – SAME database server

  1. Run Setup on the new machine. Select SQL Server as your database and Create new database (even if you plan to point this install at an existing one). This will make a standalone install.
    • If in your old install you are/were using Windows authentication when connecting to your database, using a domain account for the FogBugz IIS user, you may want to specify that same user account here in your new installation to simplify your switch-over.
  2. Install your licenses. (Note that your licenses are not tied exclusively to one server; licensing guidelines do permit multiple simultaneous FogBugz installations.)
  3. Cease using the old FogBugz. (Stop the website in IIS.)
  4. If you have mailboxes configured in your old FogBugz, stop the Fog Creek Maintenance Service on the old FogBugz server: open the Services control panel in the Administrative Tools menu and stop the Fog Creek Maintenance service. Set the startup type to disabled so it doesn’t try to run if you reboot the machine.
  5. Configure the new FogBugz installation to point at the old database
    1. If FogBugz is accessible via “localhost” then log into your new FogBugz as an administrator and go to Admin -> Site Configuration (Settings -> Site in version 6) and edit the connection string in the Database tab to point to the correct database.
      1. Windows authentication: In the SQL Server tab, change the server name and database name to that of your existing database.
      2. SQL Server authentication: In the Source tab, enter the appropriate connection string, specifying the uid and pwd, etc.
    2. If FogBugz is setup to use a different IP than the localhost address, you’ll need to edit the connection string in the registry. You can do so by going to HKLM\Software\Fog Creek Software\FogBugz\[FogBugz install directory] and editing the “sConnectionString” key. If you’re unsure what your string should be, you can contact us directly or check out ConnectionStrings.com.
  6. Reinstall your licenses if prompted.
  7. When everything is working, delete the empty database that setup created.

SQL Server database – MOVING database

  1. Run Setup on the new machine. Select SQL Server as your database and Create new database (even if you plan to point this install at an existing one). This will make a standalone install.
    • If in your old install you are/were using Windows authentication when connecting to your database, using a domain account for the FogBugz IIS user, you may want to specify that same user account here in your new installation to simplify your switch-over.
  2. Install your licenses. (Note that your licenses are not tied exclusively to one server; licensing guidelines do permit multiple simultaneous FogBugz installations.)
  3. Cease using the old FogBugz. (Stop the website in IIS.)
  4. If you have mailboxes configured in your old FogBugz, stop the Fog Creek Maintenance Service on the old FogBugz server: open the Services control panel in the Administrative Tools menu and stop the Fog Creek Maintenance service. Set the startup type to disabled so it doesn’t try to run if you reboot the machine.
  5. Move your database
    1. Against the old database, run SQL Enterprise Manager. Right click your existing FogBugz database, choose All Tasks -> Detach Database.
    2. Against the new database, run Enterprise Manager. Drill down to the empty FogBugz database that was created by Setup. Select it and press the Delete key to delete it.3
    3. On the new database, right click the Databases item. Choose
      All Tasks -> Attach Database.

      • In the dialog which appears, click “…” and select your MDF file.
      • In the Specify database owner dropdown, choose the FogBugz account that you created or chose during Setup. Click OK.5
  6. Bring up FogBugz in your web browser. If at this point you get an error message, please re-read the above steps and verify that you didn’t do something differently. Running setup creates an empty database named FogBugz and points to that, so if your database that you copied over has a different name, you will need to specify that name by editing the registry.
  7. Re-install your licenses.
  8. Go to the site page and verify the information in your site settings and be SURE to hit OK on that page so FogBugz saves that information (this is important, even if everything already looks ok, hit the OK button). Be sure that your FogBugz Maintenance URL is reachable and correct.

IIS 7.x

You may need to install the Static Content role service if it does not already exist. To do that, select the:

– Server Manager
– Roles
– Web Server (IIS) node from the left pane
– scroll to Role Services window

See if the Static Content role service is installed.

Great, but what if I have Kiln, too?

Please follow these instructions from the Kiln Knowledge Base. Please feel free to contact us if you have questions about it!