Move Foglight external backend database to another server (Migrate Foglight | Migrate Database) (42249)

The database will move to another server, the database name and user/password will stay the same.

Which changes are required on the Foglight Management Server (FMS) and clients?

There are no changes required on the clients.

The FMS configuration file "$FGLHOME/config/server.config" (in older FMS versions the file called foglight.config) contains the database configuration information.

If the existing database has been removed on a different host, only the "server.database.host" (older version "foglight.database.host" parameter requires a change to the proper hostname.

server.database.host = "localhost";

If the database name and/or port number were going to change, respectively change the following parameters in the \fms_home\config\foglight.config file:

foglight.database.port = "xxxxxx";
Note:  For SQL Server, the foglight.database.port, could be replaced with the named instance name (ie, FGL_Named_Instance instead of standard port "1433")

foglight.database.name = "foglight";

The following values are also present in server.config, you need to set the username and password on the database user account if they have been changed too:

server.database.user = "foglight";
server.database.password = "q25f5a0c606fa55f9ee9dc65f698d8e6d";

The password is set in a MD5 encrypted string - the above string is equal to the word 'foglight' - if the string is different, remember the password that was set and set that at the new database location or go through 71462 to reset it.

For SQL Server, verify that the "foglight" database is set as the default database for the foglight user and that the 'foglight' user has the needed permissions on the foglight database. In SQL Management studio navigate to "Security | Logins", right-click on the foglight user and select "Properties", verify that the default database for the foglight user is the foglight database and 'foglight' user has dbo permissions.

FMS Hostname/IP Address Change - FMS and Client side changes:
see solution 50479

Move a FMS:
see solution 56684