Skip to main content
DanieleS99
DanieleS99
Explorer
February 1, 2022
Solved

Backup Problem with Automation Stitch

  • February 1, 2022
  • 2 replies
  • 5872 views

Hi,

I have a problem with a job backup by the Automation Stitch.

When i execute the backup by automation stitch i see this error:

 

"Connect to ftp server 192.168.50.50...

Error code 1: File not found

Send config file to tftp server via vdom root failed.

Command fail. Return code -1"

 

But if i copy and paste the command in the cli console, the backup work correctly.

Any idea?

 

Thanks

 

 

Best answer by DanieleS99

Thanks for the reply Alex, 

in the end I managed to understand the problem and it did not center partially with the fortigate.
In the sense that, our tftp server, for write rights, wants an empty file to be created first with the name of the file configuration.
Only, since the fortigates are clustered, when the backup is done, the fortigate job adds the serial number in the configuration file name plus the name of the file conf create.
Consequently the configuration name did not match the empty one on the tftp server.
Thanks again.

2 replies

AlexC-FTNT
Staff
AlexC-FTNT
Staff
February 7, 2022

If the commands are the same, the problem is likely with routing. 

Check that you can reach the ftp server over the correct interface from root vdom, or look in the routing table of the root vdom (this is the management vdom in your case, can't run on a different one):

get router info routing-table detail 192.168.50.50 

    DanieleS99
    DanieleS99AuthorAnswer
    Explorer
    February 7, 2022

    Thanks for the reply Alex, 

    in the end I managed to understand the problem and it did not center partially with the fortigate.
    In the sense that, our tftp server, for write rights, wants an empty file to be created first with the name of the file configuration.
    Only, since the fortigates are clustered, when the backup is done, the fortigate job adds the serial number in the configuration file name plus the name of the file conf create.
    Consequently the configuration name did not match the empty one on the tftp server.
    Thanks again.

      Terms & ConditionsAccessibility statement