iApp F5-Automated-backup on 15.1.7

[Lidev]

Hi folks,
We try to use iApp F5-Automated-backup on F5 BIG-IP v15.1.7 (https://github.com/f5devcentral/f5-automated-backup-iapp)
Everything works fine (see the log below) but UCS was not copy on remote server.
During our testing, manual SCP copy works well, no permissions problems and when the iApp is launched, the UCS in /var/local/ucs is copied and visible.

Aug 1 16:01:00 f5-bigip info logger[7512]: f5.automated_backup iApp f5.automated.backup: STARTED 
Aug 1 16:01:00 f5-bigip info logger[7519]: f5.automated_backup iApp f5.automated.backup: f5-bigip_20230801.ucs GENERATING 
Aug 1 16:01:02 f5-bigip warning tmsh[7545]: 01420013:4: [api-status-warning] ltm/classification/signature-update-schedule is deprecated 
Aug 1 16:01:03 f5-bigip warning tmsh[7545]: 01420013:4: [api-status-warning] security/log/profile, properties : deprecated : application/local-storage
Aug 1 16:01:03 f5-bigip warning tmsh[7545]: 01420013:4: [api-status-warning] sys/ecm/cloud-provider is deprecated
Aug 1 16:01:08 f5-bigip info logger[9568]: f5.automated_backup iApp f5.automated.backup: f5-bigip_20230801.ucs SAVED LOCALLY (/var/local/ucs)
Aug 1 16:01:08 f5-bigip info logger[9576]: f5.automated_backup iApp f5.automated.backup: f5-bigip_20230801.ucs REMOTE COPY (SCP) STARTING 
Aug 1 16:01:09 f5-bigip notice logger[9783]: f5.automated_backup iApp f5.automated.backup: f5-bigip_20230801.ucs REMOTE COPY (SCP) SUCCEEDED
Aug 1 16:01:09 f5-bigip info logger[9788]: f5.automated_backup iApp f5.automated.backup: FINISHED 

Anyone has anyone ever run this iApp in v15.x ?
Any idea @JRahm ? 

Regards

[JRahm]

Do you have any diagnostic data on BIG-IP or remote server? I'm not sure what condition here is not covered in the iApp:

exec echo "f5.automated_backup iApp TMSHAPPNAME: $fname_log REMOTE COPY (SCP) STARTING" >> /var/tmp/scriptd.out
exec logger -p local0.info "f5.automated_backup iApp TMSHAPPNAME: $fname_log REMOTE COPY (SCP) STARTING"
if { [catch {exec $scriptfile}] } {
    exec echo "f5.automated_backup iApp TMSHAPPNAME: $fname_log REMOTE COPY (SCP) FAILED ErrorCode: $errorCode" >> /var/tmp/scriptd.out
    exec echo "f5.automated_backup iApp TMSHAPPNAME: $fname_log REMOTE COPY (SCP) FAILED ErrorInfo: $errorInfo" >> /var/tmp/scriptd.out
    exec echo "f5.automated_backup iApp TMSHAPPNAME: $fname_log REMOTE COPY (SCP) FAILED (check for errors above)" >> /var/tmp/scriptd.out
    exec logger -p local0.crit "f5.automated_backup iApp TMSHAPPNAME: $fname_log REMOTE COPY (SCP) FAILED (see /var/tmp/scriptd.out for errors)"
} else {
    exec echo "f5.automated_backup iApp TMSHAPPNAME: $fname_log REMOTE COPY (SCP) SUCCEEDED" >> /var/tmp/scriptd.out
    exec logger -p local0.notice "f5.automated_backup iApp TMSHAPPNAME: $fname_log REMOTE COPY (SCP) SUCCEEDED"
}

[Lidev · Accepted solution]

Hi JRahm,

Digging more on remote server and the audit log, we found that when the remote copy (SCP) is running, iApp changed the path and add a dot . at the beginning of the path 🤔

type=EXECVE msg=audit(1690960028.843:897): argc=3 a0="scp" a1="-t" a2="./f5-backup"

We removed the dot . in BACKUPDIRECTOR iApp section, updated iApp and it's finaly works 😊

BACKUPDIRECTORY/${fname_noext}BACKUPFILENAMEEXTENSION_WITHDOT* \${username}@\${server}:./\${directory} 2>> /var/tmp/scriptd.out\n\tscp_result=\$?\n\trm -f /var/tmp/TMSHAPPNAME_scp.key\n\treturn \$scp_result\n}\n\nscp_function" > $scriptfile

[JRahm]

Nice! Glad you got it working...