Duration column in Activity History is not accurate
pbezanson
Posts: 8
We've just upgraded from SQL Backup 4 to SQL Backup 5 and have noticed that the value in the Duration column of the Activity History grid is inaccurate for backups done by the conventional SQL Server Backup utility. (Times appear to be accurate for backups performed by SQL Backup 5, however). For example, a backup that took 26 minutes to complete is reported by the grid to have taken only 5 seconds!
The time line shows an accurate representation of the backup duration for both backup utilities, however, suggesting that accurate duration info is available to the client application.
Since we use both backup utilities, the inaccurate duration times for SQL Server Backup is a significant limitation. (We have to use SQL Server Management Studio to look up durations using the job history window.)
Is this a known bug? Is there a fix for it?
Thanks in advance.
The time line shows an accurate representation of the backup duration for both backup utilities, however, suggesting that accurate duration info is available to the client application.
Since we use both backup utilities, the inaccurate duration times for SQL Server Backup is a significant limitation. (We have to use SQL Server Management Studio to look up durations using the job history window.)
Is this a known bug? Is there a fix for it?
Thanks in advance.
Comments
I've looked into this issue further and the problem is due to the way SQL Backup is handling the "duration" of native backups, recording just the seconds component of the duration rather than all of it (hence 00:05 rather than 26:05). This doesn't affect the timeline as that uses different values for the calculation.
This should be fixed for the full 5.2 release in a few weeks time. However, you will need to repopulate your GUI's data store so that the durations can be recalculated (I can give you details of how to do this if you require them), which should resolve the problem.
Hope that helps,
Jason
Do you happen to know if this fix will require us to install version 5.2 on our servers or will installing the client application on our local machines suffice?
Thanks, again.
The fix is in the user interface rather than the server components, so you will be able to install the 5.2 GUI, and once your cache is cleared this will start working correctly - even if you are still using version 5.0 or 5.1 of the server components.
Hope that helps,
Jason