After applying this fix as well as the previous ones before it, is it necessary to update the client code as well?
It seems that after the fix, the client no longer shows the status correctly. For example, I started a full file backup job - the client gui status shows it is idle. However the job is actually running and i can see it in the server web interface.
This issue is not present in base version 1.4.8. Scenario:
In 1.4.8, an user can manually start a full file backup from the client gui and the backup running status will be shown immediately in the status gui.
However, after applying the fixes after 1.4.8, starting full file backup from client gui does not show the status correctly anymore. I can still start a full file backup from the client gui but the status still shows idle - i know the backup is still running because i can see the job running in the server interface’s activities.
Just to add it seems that this problem is caused after applying the fix for image read ahead (055cffc).
Also, this only occur when doing image backups. File backups are actually fine. When i start a full image backup, the client gui status will show backup running and then switch to idle after a few seconds. But at the server end, i can see the image backup task running under the activities tab.