Troubleshooting Tip: Cannot restore backup from one FortiClient EMS server to another FortiClient EMS server migration in version 7.2

Description

This article describes Issues that can be faced when migrating from one windows server 2016 to another windows server 2022 using FortiClient EMS on-premise for version 7.2.

Scope

FortiClient EMS on-premise.

Solution

When loading FortiClient EMS on-premise backup database to a new server (backup from windows server 2016 to windows server 2022 ) the restore may failed.

This issue can be related to FCM logical name may already be incorrect, It’s something Microsoft SQL Server creates automatically during a restore, and it usually signals a file/filegroup conflict.

To avoid database restore issues, it is recommended restart the FCEMS_Monitor service after waiting for 10 minutes after the restore is finished on the new windows server.

If issues persist, get a database backup from an old server (windows server 2016 for example) and open a ticket (see Customer Service Tip: How to create a ticket for Fortinet TAC) for further troubleshooting.