Fortigate Automation Stitch Backup autoscript stop

Question

Hi guys, I am trying to configure the automatic tftp backup on our new 100F Forti. I followed a guide how to do the configuration but according to the syslog the process always gets somehow stopped and deleted by the autoscript. When I execute the command manual the backup works. We have two VDOMs, root for MGMT and 1 for production traffic. The configuration is done in the global level (I also tried with adding config global in the cli script).

Anyone has an idea where the issue can be? I am absolute cluesless :\

The Eventlogs I have says:

1. Automation stitch triggered
stitch:backup-stitch is triggered.

2. Autoscript stop automatically
script autod.6 stopped automatically

3. Autoscript delete result
User delete the result of script autod.6 from autod

The Config looks like this:

Trigger:

config system automation-trigger
edit "TFTP-Daily-Backup"
set description ''
set trigger-type scheduled
set trigger-frequency daily
set trigger-hour 16
set trigger-minute 54
next

Action:

edit "backup-action"
set description ''
set action-type cli-script
set minimum-interval 1
set script "execute backup config tftp FOLDERNAME/%%devname%%-%%date%%.conf 10.10.10.10"
set output-size 10
set timeout 0
set execute-security-fabric disable
set accprofile "super_admin"
next

Stitch:

config system automation-stitch
edit "backup-stitch"
set description ''
set status enable
set trigger "TFTP-Daily-Backup"
config actions
edit 1
set action "backup-action"
set delay 0
set required enable
next

ozkanaltas · Accepted Answer

Hello @ErrantOsi ,

I encountered the same problem in Fortigate with vdom. But I solved my problem by writing "config global". I think the "config global" spelling is important here.

this style
--------------------
set script "config global
execute backup config tftp FOLDERNAME/%%devname%%-%%date%%.conf 10.10.10.10"

not same this
-------------------------
set script "config global execute backup config tftp FOLDERNAME/%%devname%%-%%date%%.conf 10.10.10.10"

Which style did you try before? The correct one is the first style. If this thing didn't work in your environment. Could you run these commands and share the output with us?

exec auto-script stopall
diag debug reset
diag test app autod 1
diag debug cli 7
diag debug enable

exec auto-script start <stitch_name>

Markus_M · Answer

You could run a status output and see details of the script.

exec auto-script status <name>
exec auto-script result <name>
The script will stop if a condition is met:

output-size 10 (megabyte in memory)

set timeout 0 (unlimited)

Best regards,

Markus

Sign up

Login with SSO

Login to the community

Login with SSO