Could you please confirm if it is a new setup or was it working before.
The error message you received indicates that there was a problem sending the configuration file to the FTP server. Check the firewall settings on both the FortiGate and the FTP server to ensure that FTP traffic is allowed.
Verify that the FTP username and password are correct and have the necessary permissions to write to the backup folder. Verify that the backup folder exists and has the correct permissions.
Today a project for FortiGate config backup via ftp needed this %%date%%% so we tried backup from the cli and the result on the ftp server what FGT_Config-%%date%%%.conf. After a short check on the forums we found no solution for this issue. At the end we tried running our automation stitch and the variable %%date%%% worked. Try running the script in automation stitch with super-admin and will work. Our FortiGate cluster has version 7.0.13.
The command "execute backup config ftp backup.cfg 10.10.X.X backupfw test1" will generate a configuration backup file in the directory which is set in the FTP server. However the command "execute backup config ftp /backupFW/backup_%date%.cfg 10.10.X.X backupfw test1" will generate the backup in the directory /backupFW If there is no directory with such name the server will respond with the error.
Either you can create a directory /backupFW in which the configuration backup will be saved or you can remove the path so that the backup will be saved in the current directory which is configured in the FTP server.
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.