Something that is annoying me for some time now is that we often see running jobs with a job update time that is lacking behind for 15 min. and more. This has an effect on the information like average speed and also gives a "incorrect” indication to the end-user performing a backup/recovery. Especially during a restore this is seen so a user has no idea how long the recovery will take.
I did some investigation already but without results. Anyone an idea if there is something to tweak?
Best answer by Stuart PainterView original