08-22-2014 08:25 AM
Hi all,
Do any of you know if Netbackup does, or will have the capability to show KB / second with regards to duplications? I can see thsi info for all other jobs, but, not duplications. Would be nice to know how fast they are gonig, so , figured to ask.
Thanks
Seth
Solved! Go to Solution.
08-25-2014 01:12 AM
You can actual see what speed duplicate are running at - indirectly.
The detailed part of the activity monitor will have a text like this:
25-08-2014 09:18:10 - begin reading
25-08-2014 09:31:48 - end reading; read time: 0:13:38
25-08-2014 09:31:48 - begin reading
25-08-2014 09:45:15 - end reading; read time: 0:13:27
25-08-2014 09:45:15 - begin reading
25-08-2014 09:58:58 - end reading; read time: 0:13:43
25-08-2014 09:58:58 - begin reading
In this scenarios we use a 50G fragment size (tape duplication) so dividing 50000/823 seconds (13:43) = 60MB/sec. But as Marianne pointed out there are both read speed and writing speed when it comes to duplication.
And the writing of different backup images will vary in speed. Small images will show a lower speed than big images. Use it as a guideline
08-22-2014 08:42 AM
yes, you can only see this info when netbackup version is 7.6
see the below comment from Riaan on other discussion
https://www-secure.symantec.com/connect/forums/no-showing-kbytessec-rate-slp
08-22-2014 02:31 PM
I tested this the other day for the same question on NBU 7.6
There was no kb/s during any duplication.
I am unaware if it has been added at 7.6.x, but as /x releases should only be patch updates (eg. EEB fixes) I suspect not.
When I next get my paws on a higher build, I'll test it.
M
08-23-2014 10:08 PM
My notes in above post:
So... SLP consist of 2 processes - a read process and a write process.
Which one should be displayed?
IMHO, this is the the reason for kbytes/sec not being displayed.
08-24-2014 03:48 PM
Not sure of why, when I next speak to someone in Engineering who looks after this area, I'll ask them ...
08-25-2014 01:12 AM
You can actual see what speed duplicate are running at - indirectly.
The detailed part of the activity monitor will have a text like this:
25-08-2014 09:18:10 - begin reading
25-08-2014 09:31:48 - end reading; read time: 0:13:38
25-08-2014 09:31:48 - begin reading
25-08-2014 09:45:15 - end reading; read time: 0:13:27
25-08-2014 09:45:15 - begin reading
25-08-2014 09:58:58 - end reading; read time: 0:13:43
25-08-2014 09:58:58 - begin reading
In this scenarios we use a 50G fragment size (tape duplication) so dividing 50000/823 seconds (13:43) = 60MB/sec. But as Marianne pointed out there are both read speed and writing speed when it comes to duplication.
And the writing of different backup images will vary in speed. Small images will show a lower speed than big images. Use it as a guideline
08-25-2014 09:54 AM
Good suggestion. I'll follow this until NB comes out with a proper solution.