Backup job log output is confusing at save step

reported in forum

[2021-11-03 22:42:10] [5262c3a9-309b-4ea6-a37c-ee04ce438c4d.INFO]: Finished Cleaning up
[2021-11-03 22:42:10] [5262c3a9-309b-4ea6-a37c-ee04ce438c4d.INFO]: Finished created backup file: 20211103-224122-[1635979282 ](tel:1635979282)-15.0.17.55-812478796.tar.gz
[2021-11-03 22:42:14] [5262c3a9-309b-4ea6-a37c-ee04ce438c4d.ERROR]: Could not login with username: root, host: 192.168.194.2
[2021-11-03 22:42:14] [5262c3a9-309b-4ea6-a37c-ee04ce438c4d.INFO]: Saving to selected Filestore locations
[2021-11-03 22:42:14] [5262c3a9-309b-4ea6-a37c-ee04ce438c4d.DEBUG]:     Saving to: SSH:'mac mini' instance ,File location: /root/raspbxbk/20211103-224122-[1635979282 ](tel:1635979282)-15.0.17.55-812478796.tar.gz 
[2021-11-03 22:42:14] [5262c3a9-309b-4ea6-a37c-ee04ce438c4d.INFO]: Finished Saving to selected Filestore locations
[2021-11-03 22:42:14] [5262c3a9-309b-4ea6-a37c-ee04ce438c4d.DEBUG]: Generated Backup process result email to [x.x@gmail.com](mailto:x.x@gmail.com). Status: Failure

In the above snippet of the backup log, we see that backup tarball is set to save via SSH. Line 2 shows that ssh access failed (bad password) but the following lines look like the file was actually saved until the final line when it say failure. In the case where the backup destination is unreachable for whatever reason, can we suppress all the saving log lines so it's clearer that the upload failed?