| Solution |
When restoring the EMS DB, the following process occurs:
After it completes, EMS redirects the user to the login page:
Afterwards, EMS may still be in its previous state (before restoration) and may not have restored the actual configuration. For example, certain endpoint profiles/policies are expected, but not present.
To verify the issue, follow these steps:
- After restoring the DB, navigate to C:\Program Files (x86)\Fortinet\FortiClientEMS in the Windows Server.
- Run EMSDiagnosticTool.exe to collect EMS_Diagnostic_Result.
- Extract the EMS_Diagnostic_Result.
- Open the extracted EMS_Diagnostic_Result folder and go to db_import_attempts:
- You may find the folder inside is blank:
- Next, go back to the old EMS server (where the DB backup file was taken from), navigate to C:\Program Files\Microsoft SQL Server\MSSQL14.FCEMS\MSSQL\DATA, and check if any of the DB size is over 10GB.
If FCM_root or FCM_default is over 10GB, the EMS backup cannot be done properly. If this is the case, remediate the issue:
- Take a VM snapshot and open a command prompt with administrator privileges, then run the following command to shrink the database size:
sqlcmd -E -S.\fcems -d fcm_root
1> DBCC SHRINKDATABASE(fcm_root,10)
2> go
- Afterwards, the FCM_root or FCM_default DB size should be significantly shrunk (below 10GB):
- Take another new EMS DB backup file from the EMS GUI if desired.
- Restore the new EMS DB backup file to the new EMS server if desired. It will restore all of the configuration from the old EMS server.
|
