Technical Tip: Automated Configuration Backups Configured with Variable '%%log.time%%' Fail to Backup Configuration
| Description | This article describes an issue where FortiGate fails to perform backup configuration when the hostname or backup filename includes the variable '%%log.time%%'. |
| Scope | FortiGate v7.4.4, v7.4.5. |
| Solution | When using an automation stitch to perform configuration backups with the variable '%%log.time%%', which is intended to include the timestamp in the filename, the backup fails due to unsupported special characters: execute backup full-config usb MV-FW-Z3-fullconfig-USB-daily-%%log.time%%.txt<----- Using log.time. __cli_script_close()-121: cli script: Copy config MV-FW-Z3-fullconfig-USB-daily-08:19:29.txt to USB disk ...
execute backup full-config usb MV-FW-Z3-fullconfig-USB-daily-%%log.date%%.txt<----- Using only log.date. pid:225-__handle_msg()-414: Subscriber:4 received package. pubid:0 pkgid:178 pkg_index:191 Copy config MV-FW-Z3-fullconfig-USB-daily-2024-10-29.txt to USB disk ... Starting from v7.6.1, the variable '%%log.eventtime%%' has been introduced in place of '%%log.time%%', allowing the inclusion of the Unix timestamp in the filename without using unsupported special characters.
|