How to Migrate Foglight Management Server (FMS) to a New Server (4310144)

1. Stop the FMS and Back Up Installation

   1. Stop FMS.

   2. Back up the entire $FMS_HOME directory, including the embedded database (if used).

2. Restore on New Host

   1. Restore the backup to the desired directory on the new server.

   2. Note: If the directory path differs, update the startup scripts:

      1. $FMS_HOME/bin/fmsStartup.sh

      2. $FMS_HOME/bin/fmsShutdown.sh

3. Stop Embedded Database (if applicable)

   1. Use ps -ef | grep -i foglight to check for embedded MySQL/PostgreSQL processes.

   2. If running, stop the database with:

       

      $FMS_HOME/bin/shutdownDb.sh

4. Start FMS

    

   $FMS_HOME/bin/fmsStartup.sh

5. Install New License

   1. If the hostname changed, log into Foglight and apply a new license.

6. Verify FglAM Connectivity

   1. Ensure all connected FglAMs are registering successfully.

   2. If hostname changed, edit each fglam.config.xml file to point to the new FMS.

7. Review Logs

   1. Check $FMS_HOME/logs/ for hostname or connection-related errors.

Migration Steps: Windows-based FMS

1. Stop FMS and Back Up Installation

   • Stop FMS.

   • Back up the entire $FMS_HOME directory.

2. Restore on New Host

   • Copy the backup to the new server.

   • Use Robocopy to avoid path length issues:

     robocopy \\sourcehost\Quest_Software\Foglight E:\Quest_Software\Foglight /E /ZB /V /COPYALL /DCOPY:DAT /LOG:"E:\Quest_Software\log.txt" /TEE 

3. Start FMS

   $FMS_HOME\bin\fms.exe -s 

4. Install New License

   • If the hostname has changed, install the new license.

5. Verify FglAM Connectivity

   • Confirm agent managers are connecting and agents are active.

6. Review Logs

   • Check $FMS_HOME\logs\ for hostname or IP-related issues.

7. Optional: Install FMS as Windows Service

   $FMS_HOME\bin\fms.exe -i 

8. Update Windows Shortcuts

   • Adjust any shortcuts to point to the new FMS location.

9. Registry Considerations for Upgrades

   • During upgrades, the Windows registry may not reflect the migrated installation.
     Point the installer manually to the existing Foglight directory.

10. Firewall Configuration

• Ensure all required ports are open between the new FMS and FglAMs.

Note: Migration across different operating systems (e.g., Linux to Windows) is not supported.

Updating Embedded FglAM Configuration

If FMS hostname or IP changes:

• Edit:

  $FMS_HOME/fglam/state/default/config/fglam.config.xml 

• Replace the old FMS address with the new one.

• Prevent the embedded FglAM from registering with the outdated hostname.

Refer to Solution 4248557 for details.

Update FglAM Client Configuration

All external FglAMs must update their fglam.config.xml files to point to the new FMS location.

See Solution 4228980 for the full procedure.

Update FMS Server  URL

After the move:

1. Log in to the FMS console.

2. Go to:
   Dashboards > Administration > Rules & Notifications > Manage Registry Variables

3. Locate and update the variable: CATALYST_URL

   • Set it to the new hostname or IP (e.g., http://fms2.domain.com:8080)

Migrating FMS Backend Database (External)

If you are also moving the external backend database:

• Update Foglight to point to the new DB instance.

• Refer to Solution 4260799 for details.

Additional Information

Example: Migrating Linux FMS between Data Centers

Old server (Data Center 1):

cd /apps/foglight/FMS_HOME/Server/bin
./fmsShutdown.sh
tar -cvf foglight.tar /apps/foglight

New server (Data Center 2):

useradd foglight
tar -xvf foglight.tar -C /apps/
chown -R foglight: /apps/foglight
cd /apps/foglight/FMS_HOME/Server/bin
./fmsStartup.sh

Update:

• CATALYST_URL registry variable

• Install the new license