Migrating Goliath Performance Monitor & Local SQL to a New Server

This article was updated to support v12.1.1 of Goliath Performance Monitor.

This article provides step by step instructions for migrating your existing Goliath Performance Monitor and local SQL database to a new server. These steps must be completed in the following order or else configuration errors will take place. If you have problems along the way, please feel free to reach out by creating a support ticket for assistance. 

Please Note: This article is only applicable for configurations where the Goliath Server is also running a local SQL Server. Before proceeding, also please make sure that your existing Goliath Server is running the latest version.

1. Download SQL Management Studio on the old/existing & new Goliath servers if it is not installed already 
2. Log onto the old/existing Goliath Server
3. Confirm that is running version 12.1.1 or later
   1. If it is not, please see the latest release section of the support center to update
4. Open up Windows Services and stop the MonitorIT Server Service and the MonitorIT Agent Service  
5. Log onto the new Goliath server and do the following:
   1. Install Goliath Performance Monitor
      1. Please have your license key at hand as it will be required to proceed further. If you do not have your license key please create a support ticket requesting it.
      2. SQL Database Options:
         1. If you will be using a local Full SQL Server, select Manual Configuration on the ‘Goliath Performance Monitor SQL Database Options' Page
         2. If you will be using a local SQL Express, select SQL Express on the ‘Goliath Performance Monitor SQL Database Options' Page to install the embedded SQL Express.
      3. After the install completes, do not click on the Goliath Performance Monitor desktop icon
   2. If you will be using local Full SQL Server, please make sure that the SQL Server is installed before proceeding further
6. Log onto the old/existing Goliath Server and do the following:
   1. Copy over the GPMServer.cfg file from the old server and replace the file on the new server
      1. Default Location is C:\Program Files (x86)\MonitorIT\Bin or C:\Program Files\MonitorIT\Bin
   2. Use SQL Server Management Studio to detach the local database
   3. Copy the database file & transaction log to its proper new location on the new server
7. Log onto the new Goliath Server and do the following: 
   1. Attach the database file to the SQL Server (full or express)
   2. Create the database ODBC connection
      1. Launch ODBC Data Sources (64-bit) from Windows Administrative Tools
      2. Once open, go to the System DSN tab 
      3. Next click Add and scroll through the list to select the driver type ODBC Driver 18 for SQL Server
      4. Name the connection with the information listed below, when finished click Next
         1. Define the Name as BreakoutRPM
         2. Define the Description as PrimaryGPM Database
         3. Define the SQL Server name and instance
      5. Keep the default settings to use the Integrated Windows authentication to connect to the database and select Next
      6. Check the box next to Change the default database to and select the appropriate database name from the drop down menu.  Click Next
         1. The most common names are "MonitorIT", "Goliath", "GoliathDB"
      7. Select the Test Data Source button to validate the connection. Click OK to close all windows
8. Shut down your old Goliath Server 
9. Update the new Goliath Server machine to be assigned with the IP address of the old Goliath Server 
   1. This is required for all of the agents automatically check into the new instance and for the product to launch. 
10. The product is now ready to be launched, click the Goliath Performance Monitor icon on the new Goliath server to launch the product.