11-15-2017 11:27 PM
i'm monitoring our duplication status and noticed that the speed varies from 5KBps to 50KBps. at times it hits 80KBps. then i had a look at the details tab and saw the below.
on a duplication, why does it spend time reading? shouldn't it be writing?
11/16/2017 07:16:56 - Info bptm (pid=19826) INF - Waiting for positioning of media id ABP376 on server ovmmanager for writing.
11/16/2017 07:16:58 - begin reading
11/16/2017 07:35:26 - end reading; read time: 0:18:28
11/16/2017 07:35:26 - begin reading
11/16/2017 08:00:10 - end reading; read time: 0:24:44
11/16/2017 08:00:10 - begin reading
11/16/2017 08:49:35 - end reading; read time: 0:49:25
11/16/2017 08:49:35 - begin reading
11-15-2017 11:35 PM
Images need to be read from disk, followed by writing to tape.
You will see 2 bptm processes with different PIDs one for the read process and one for the write process.
bptm log will log each pid where you can see where the bottleneck is.
My guess - read speed from disk.
11-16-2017 12:47 AM
and each "begin read" "End read" is the time used for reading one fragment. Fragment size can be seen in storage unit configuration.
11-16-2017 01:35 AM
there's a lot of info in the bptm log, what should i be looking for?
11-16-2017 07:25 AM
I would start by filtering the bptm logs by the BPTM PID#'s of the jobs that you want to look at. I would suggest using a 3rd party log viewer and not trying to read them in notepad, my suggestion would be to use LogExpert, its free and is extremely helpful once you get it setup.
If you have any questions on how to use it or how to set it up feel free to pm me.
11-17-2017 12:24 AM
Seems we've been through this before:
https://vox.veritas.com/t5/NetBackup/is-it-the-tape-drive-or-NBU-that-is-slow/m-p/830661