Gibberish Backup

[ronio]

Hi,
I am trying to figure out why every time I'm trying to import a backup from my Fortimanager/fortianalyzer the backup is imported on "Gibberish".
The "encryption" option is obesely disabled, also the file format is like it should be (on conf file) but still, the backup looks like this:

[srajeswaran]

FortiAnalyzer and FortiManager backups in .dat format. Please unzip/decompress the file and then open it.

[ronio]

ok, I saw on internet that the file format should be conf.

by default the file is downloaded with .dat format and its still not working..

[srajeswaran]

did you unzip/decompress the .dat file?

[ronio]

First off all, thank you very much.

after ive done unzip and open the file the file was opened in english.

do you have an idea why on fortimanager is acting this way but on fortianalyzer\fortigate the back import correctly?

[srajeswaran]

FortiManager backup is not just config file, if you really want to see whats included in the .dat file, you may use sqllitestudio or some other similar application and open it (not recommended). You will be able to see more than the configuration file.

Ideally the backup file from Fortimanger is meant for another fortimanager device to restore in case required.

[Faiza_Emam_Delhi]

ou are encountering an issue where the backup file from your FortiManager/FortiAnalyzer is being imported as gibberish. This could be caused by a few different factors, including encoding issues or file corruption.

Here are some steps you can take to troubleshoot this issue:

1. Verify that the backup file is not corrupted. Try opening the backup file in a text editor and see if the contents are readable. If the file is corrupted, you may need to create a new backup file.

2. Check that the encoding of the backup file matches the encoding of the system you are importing it to. For example, if the backup file was created on a system using UTF-8 encoding, make sure that the system you are importing it to is also using UTF-8 encoding.

3. Check that the file format of the backup file is correct. For example, if the backup file is a .conf file, make sure that the system you are importing it to recognizes it as a .conf file.

4. Try importing the backup file using a different method. For example, you could try importing the backup file using the FortiManager/FortiAnalyzer GUI instead of the CLI.

5. Consider reaching out to Fortinet support for further assistance. They may be able to provide more specific guidance based on your specific situation.

By following these steps, you can further isolate the issue and determine the root cause of the problem.