rsc will be added automatically, if you add rsc yourself, then the result should be filename.rsc.rsc
also, there is a little problem with export command issued over API when saving to file. export without arguments should return !done, as it is doing it now.
Any progress on this issue. When I issues “/export =file=myconfig” from the API I get a 8600 byte file. When I issue “/export file=myconfig” from the command line (telnet or ssh), I get a 17215 byte file.
Apart from graphs, what else is not backed up? Presumably the httpdocs?
You may want to brush up your use of terminology…
The configuration is exported, the system is backup-ed.
So… when you do export, the file system in general, be it HTTP docs or just script files laying around, won’t be exported. Also, passwords and modules.
A backup AFAIK includes also files, passwords and modules, but is intended to be restored on the same system (except, potentially, a new HDD). In contrast, an export can be used on a different system, and a different version even, as long as the commands used are compatible.
how to do you backup using the API?
The answer to this question is still of interest to me.
Following the CLI command:
/system/backup/save
=name=backupFileName
And for exporting, you have the syntax shown above.
Is there any progress with API and export? We have PHP side where we would like to send / export… and download via FTP afterwards, but very often we receive onyl file with interrupted lines.
Or, Is there any process how to reach full export?
Thank you
You could use PHP to create a scheduler script that does /export after a second or so, and removes itself. The fact that it will be the scheduler that does it (rather than the API) will create a proper file that you can then download with FTP.
Is there really no way to retrieve the running-config from a RouterOS device without first writing the file out to disk?
I want to use the API to schedule a regular export of the configuration from all my devices, but writing to disk every time is going to burn out my flash.
Is there any traction or a resolution found for this? I would like to ultimately use napalm to retrieve the config thus it must be via Python API and not another workaround.