Ignite Global Support Home
How can we help?
  1. FogBugz Support
  2. Fogbugz Legacy
  3. FogBugz For Your Server (FYS)
  4. Migrating Servers and Databases

Moving FogBugz For Your Server (FBFYS) to Another Server


Central Support
  • Updated
Follow

Overview

This article provides a guide to move the FogBugz application (site) to another server. This guide addresses a variety of server/database scenarios and makes reference to the Accessories directory, located in your FogBugz directory.

 

Information

This process applies to scenarios where you will be using the same database after moving FogBugz 6, 7, or 8. For older versions, please contact us for assistance. If you only need to move your database, please check the procedure for MS SQL Server or MySQL Server.

Before You Start

Please make a full backup of your database before performing any upgrades or moves, and verify the backups. Having backups ensures you can rollback to your previous states if necessary.

Upgrading FogBugz

Since FogBugz will upgrade any outdated database when it runs against it, you can make the move and upgrade in one step. That said, we 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 the licenses installed. Then, shut down the old FogBugz, move your database, and point the new FogBugz installation to your FogBugz database.

After Moving FogBugz

Make sure that the permissions on the FogBugz account are correct. If anything is wrong with the permissions, everything may look fine at first, but problems may appear later on (e.g., case attachments may fail).

Changing Database Types

If you are switching from MySQL to MS SQL Server or vice versa, please contact us to discuss a plan for converting your database.

Back to top

 

Process

Linux and macOS

  1. Run Setup on the new machine and install a new FogBugz database.
  2. Get everything working, so you know the installation was successful with this new database.
  3. Start FogBugz. (Check the instructions for starting and shutting down FogBugz in Linux.)
  4. Set up the database:
    1. If you are moving your database, follow the instructions to move it to a new instance.
    2. Edit the sConnectionString line in /[path to fogbugz]/Accessories/application.data to reflect the correct database information.
  5. Stop FogBugz.
  6. Reinstall your licenses if prompted.
  7. When everything is working, delete the empty database created in step 1.

Back to top

 

Windows

MS Access Database

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 a new database (even if you plan to point this installation at an existing one). This will make a standalone installation.
  2. Install your licenses.
    NOTE: Your licenses are not tied exclusively to one server. Our licensing guidelines allow multiple simultaneous FogBugz installations for testing purposes.
  3. Stop the Maintenance Service on the old FogBugz server:
    • Go to 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 in to FogBugz as an administrator, navigate to Admin > Site Configuration (in version 6, navigate to Settings > Site), 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 created in step 1.

 

SQL Server Database - Same Database Server

  1. Run Setup on the new machine. Select SQL Server as your database and create a new database (even if you plan to point this installation at an existing one). This will make a standalone installation.

    NOTE: If in your old installation you 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: Your licenses are not tied exclusively to one server. Our licensing guidelines allow multiple simultaneous FogBugz installations for testing purposes.
  3. Stop 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:
    1. Open the Services Control Panel in the Administrative Tools menu and stop the Fog Creek Maintenance Service.
    2. Set the startup type to disabled, so it does not try to run if you reboot the machine.
  5. Configure the new FogBugz installation to point at the old database as below:
    • If FogBugz is accessible via localhost, then log in to your new FogBugz as an administrator. Navigate to Admin > Site Configuration (in version 6, navigate to Settings > Site), and edit the connection string in the Database tab to point to the correct database.
      • Windows Authentication: In the SQL Server tab, change the server name and database name to that of your existing database.
      • SQL Server Authentication: In the Source tab, enter the appropriate connection string, specifying the user ID, password, etc.
    • If FogBugz is set up to use a different IP address than the localhost address, you will need to edit the connection string in the registry. Navigate to HKLM\Software\Fog Creek Software\FogBugz\[FogBugz install directory] and edit the sConnectionString key. If you are not sure what your string should be, you may contact us or check using ConnectionStrings.com.
  6. Reinstall your licenses if prompted.
  7. When everything is working, delete the empty database created in step 1.

 

SQL Server Database - Moving Databases

  1. Run Setup on the new machine. Select SQL Server as your database and create a new database (even if you plan to point this installation at an existing one). This will make a standalone installation.

    NOTE: If in your old installation you 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: Your licenses are not tied exclusively to one server. Our licensing guidelines allow multiple simultaneous FogBugz installations for testing purposes.
  3. Stop 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:
    1. Open the Services Control Panel in the Administrative Tools menu and stop the Fog Creek Maintenance Service.
    2. Set the startup type to disabled, so it does not try to run if you reboot the machine.
  5. Move your database, as mentioned below:
    1. Against the old database, run the SQL Enterprise Manager. Right-click your existing FogBugz database, select All Tasks > Detach Database.
    2. Against the new database, run the SQL Enterprise Manager. Find the empty FogBugz database created in step 1, select it and press the DELETE key in your keyboard to delete it.

      image-0.gif

    3. On the new database, right-click the Databases item. Select All Tasks > Attach Database.
      1. A dialog box will appear, click ... and select your MDF file.
      2. In the Specify database owner drop-down, select the FogBugz account you created or used during setup.
      3. Click OK.

        image-1.png

  6. Navigate to your FogBugz site in your web browser. If at this point you get an error message, please re-read the above steps and verify that you did not do something differently. Running Setup creates an empty database named FogBugz and points to that. So, if the database that you copied over has a different name, you will need to specify that name by editing the registry.
  7. Reinstall your licenses.
  8. Go to the site page, verify the information in your site settings, and make sure you click OK on that page so FogBugz saves the information. This is important even if everything already looks ok. Click the OK button. Also, make 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, follow the steps below:

  1. Navigate to Server Manager > Roles > Web Server (IIS) node (left-pane).
  2. Scroll to the Role Services window and check if the Static Content role service is installed.

 

What If I Have Kiln Too?

Follow the instructions to move Kiln to another server. Please feel free to contact us if you have any questions about it.

Back to top

 

Related Articles

Moving FogBugz For Your Server (FBFYS) Database to A New MS SQL Server Instance

Back to top