Feature request : More explicit message when "backup start failled"


#1

Hello

When starting a manual backup from server :
On the status page, could the message be more explicit ? (important)
I noticed a few possible cause :

  • Server key not on client
  • Server just restarted and client not yet attached to server
    In case of multiple server :
  • Client discovery not enabled for that client, thus client doesn’t attach to server
  • Client already backuping to another server

Could the start failed be logged on the logs tab (avg important)?

Could the message stay on the status page when switching tab (low importance)?

Also if i stop a client and manually start a backup from a server, get :

  • Status indexing,
  • In the logs “CONNECT error during filelist construction”, so server knows client is offline
  • But on status page client still show online, can it be shown offline?

#2

It can; normally it is in relation to the machine not contacting the server - this can be done when the server pings the clients and receives no response, or if the server key doesn’t link with the client.

So, your first four messages can sometimes be mitigated by that offline/online tab.[quote=“orogor, post:1, topic:2836”]

  • Server key not on client
  • Server just restarted and client not yet attached to server
    In case of multiple server :
  • Client discovery not enabled for that client, thus client doesn’t attach to server
  • Client already backuping to another server
    [/quote]

That error isn’t always associated with the client being offline; sometimes the service isn’t running, or there is a problem with the drive or file system - or possibly in your case, the connection was abruptly stopped.

But, I wholeheartedly agree with you that more explicit messages would be nice. At the very least, it would benefit troubleshooting a lot more.