How can we help you today? How can we help you today?

Activity History details

Hi,

Can you please confirm the source of the values for the Duration column please?

Is it the time taken to do the backup?

It doesnt seem to relate to the duration of the whole job - ie backup, verify and copy to network location.

I think that the column name should change or the value displayed should be the whole job or the accuracy needs reviewing - SSMS says the job took 18m, v6 Activity History Duration says 00:00:47 :?
fatherjack2
0

Comments

2 comments

Sort by
  • mattchandler
    Hello,

    You're quite right that the duration column of the activity history just shows the time taken for the backup part of the task - not the copy or verify parts. This was also the case in SQL Backup 5.

    Out of interest, it sounds like your job spent a lot of time copying/verifying compared to the time taken to back up. Could I ask if this performance is typical compared to what you would expect from SQL Backup version 5, or whether its taking more time than you would normally have expected?

    Thanks for the feedback,
    mattchandler
    0
  • fatherjack2
    Hi Matt,

    Its a bit tricky to compare our test rig to production. We have it mainly for functionality testing rather than performance testing. The h/w is so different I wouldnt look to compare the figures too closely.

    Test rig is a virtual server with single CPU little RAM and single HDD, production is 2 dual core 8 HDD split in 3 arrays and 20GB RAM.

    The test I just ran was a backup to local HDD followed by verify and then copy over WAN to DR site. While it ran a ping on the line was showing 5% lost packets. The WAN is 4Mbps but has QOS on it for our main app so I dont know exactly what bandwidth would have been available.

    I have since run a backup straight to the DR site and that completed (Duration) in 07:45 with SSMS showing 16:28 so its marginally quicker to backup direct to network than backup and then copy. Would you expect that?

    Also testing on different (smaller) database so as to not take too much out of WAN in work hours. Production job takes 1:45 (Duration) to backup live db but SSMS says job finishes in 2:00:00. Its currently doing a copy of 3.1GB (v5 comp level 3) so getting level 4 from v6 is hopefully going to be a big gain for us.

    regards

    Jonathan
    fatherjack2
    0

Add comment

Please sign in to leave a comment.