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

This article provides a clear step-by-step procedure to migrate a Foglight Management Server (FMS) to a new host. It covers scenarios where the hostname, IP address, installation path, or backend repository database may change, and outlines required updates for Agent Managers (FglAMs), embedded components, and high availability (HA) environments.

Migration may be required due to: 

• Server replacement or hardware upgrade 
• Migration to a new virtual machine or datacenter 
• Hostname or IP address change 
• Storage or infrastructure changes 

Foglight operation depends on three components: 

• Installation files ($FMS_HOME)
• Repository database (embedded or external)
• Server identity (hostname/IP) 

All components must remain consistent after migration. 

Important:

• Migration between operating systems (Linux ↔ Windows) is not supported
• If the hostname changes, a new license may be required
• Contact: license@quest.com with your Site ID
• Ensure sufficient disk space and required network ports are available on the new server

Migration Steps 

Step 1: Stop Foglight and Back Up 

Stop the FMS: 

Linux: 

$FMS_HOME/bin/fmsShutdown.sh 

Windows: 

$FMS_HOME\bin\fms.exe -s 

Verify it is stopped: 

ps -ef | grep -i foglight 

Back up the entire $FMS_HOME directory. 

Important: Do not copy while Foglight is running.

Step 2: Copy to the New Server

• Copy the full $FMS_HOME directory to the new server 

• Ensure the copy completes fully and no files are skipped 

• Preserve file permissions (Linux) 

Windows example: 

robocopy \\source\\Foglight D:\\Foglight /E /ZB /COPYALL 

Step 3: Start Foglight on the New Server 

Linux: 

$FMS_HOME/bin/fmsStartup.sh 

Windows: 

$FMS_HOME\bin\fms.exe -s 

Step 4: Update Server URL (if hostname or IP changed) 

In the Foglight UI: 

• Navigate to: Administration -> Rules & Notifications -> Manage Registry Variables 

• Update this registry variable to the new hostname or IP
  CATALYST_URL = http://<new-host>:8080 

Step 5: Update Embedded Agent Manager 

Edit: 

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

Replace the old hostname or IP with the new value. 

Step 6: Update External Agent Managers (FglAMs) 

If the hostname or IP changed: 

• Edit fglam.config.xml on each FglAM ($FMS_HOME/fglam/state/default/config/fglam.config.xml) 

• Replace the old FMS address with the new one 

Note: Agents will not automatically reconnect after a hostname change and will remain disconnected until updated. Refer to Solution 4248557 for details.

Best practice: Use a DNS alias to avoid updating all agents in future migrations.

Step 7: Apply License (if required) 

Install a new license if the hostname has changed. 

Step 8: Validate the Migration 

Confirm the system is working correctly: 

• Log in to the Foglight UI 

• Verify dashboards load properly 

• Confirm all agents are connected 

• Any disconnected agents indicate configuration updates are still required 

• Check logs for errors:
  $FMS_HOME/logs/foglight.log 

• Verify new data is being collected 

Database Considerations 

Embedded Database 

• Requires a clean shutdown before copying to avoid corruption 

External Database 

• If you are also moving the external backend database, update database connection settings if the database location changes. Refer to Solution 4260799 for details.

• Confirm connectivity before starting Foglight 

High Availability (HA) 

If using HA: 

1. Stop all nodes 

2. Migrate each node (as described above)

3. Update hostnames/IPs in configuration if required (Solution 4228980)

4. Start the primary node in HA mode first

5. Start secondary nodes after the primary is fully running 

6. Verify that primary server is up and peers are connected; for more information refer to Solution 4276240.

Networking Requirements 

Ensure connectivity between FMS and Agent Managers: 

• 8080 / 8443 (UI access) 

• 1099 and RMI communication ports 

• Database port (if using external DB)  

Historical Data 

If the same Foglight repository database (embedded or external) is reused, all historical data is preserved. After migration, it is immediately available in the Foglight UI without any additional steps. 

Summary 

Migration follows a consistent pattern:

Stop -> Copy -> Restore -> Start -> Update connections -> Validate 

Move Linux Foglight from old server Datacenter 1 to Datacenter 2

---