I'm working on a custom backup script for an appliance, but I'm having an issue with SolarWinds SCP server. My custom device template does send the command which backs up the device and connects back to SolarWinds SCP server and writes the backup file. The problem is that the backup file is not renamed to what NCM is looking for, XXXXX.config so the file does not get associated with the device and it just remains in the SCP root.
The same issue happens even when I run the command manually:
scp /backup/backup.tar.gz user@1.2.3.4:/newfile.tar.gz
The result is the file is transferred successfully, but it is named backup.tar.gz; not newfile.tar.gz. When I run the same exact command onto a Linux SCP server, the file is written as newfile.tar.gz.
Anyone else run into this issue? I'm running Orion NCM v6.1 and SCP Server 1.0.1.4.
