Please clarify which log.
Are you using scripts? They generally should run their own log if they want one, however
Where does script output go to (difference between BEFORE and AFTER?)
may help if you have a script that wants a log, but isn’t doing its own. Note timing matters:
Viewing the log files of a backup job refers to the backup itself. This log can be sent using
Reporting options
however I don’t thnk a transfer problem retrofits that log to indicate that it couldn’t be sent.
There is no queue/retry mechanism built in that I know of, which is why a lack of backup is reportable more reliably externally than by Duplicati itself. Its computer may even be down.
Are you writing CLI scripts using the GUI?
Scripting options exist either way, but basic GUI job is not a script. Please clarify your usage.
I don’t follow that, but there’s much here that needs clarification. Was there another warning?
Please clarify which option you have turned off. If you mean send-http-url, your usage with ingress.duplicati.com should always try to send. This allows detection of missed backups.
Unless there was some other warning you missed, the only loss was a mystery network outage (somewhat more assured because you spoke to the server admin on your other related issue).
Without that assurance, there’s a chance the server was down briefly, but even that would have difficulty taking DNS down (because DNS is spread more widely, throughout Internet services).
What OS is this? Some might cache DNS answers, which may help ride through some outages.
Are you backing up to a Storage Type that needs working Internet, or to something that’s local?