+1
Hi,
Each job gives Read, Write, Network, and DDB lookup metrics.
I’ve always understood “Network” to be “waiting on data transfer from the Client to the MA.”
But I have a Client which is its own MA, and does parallel copy directly from itself to S3--but the “Network” number is still sometimes the highest percentage.
What does “Network” mean in this context? (The DDB does live on a different MA.)
Thanks!
Sheree
+23
Hi
So this still is reporting on a true network statistic, with the transfer between the agent (database in your example) and the Media Agent. Commvault processes will transfer data over the loopback adapter on the same machine (the same adapter responsible for 127.0.0.1). Depending on which OS you are running, the performance can vary wildly. We have seen some irregularities with some operating systems and patch levels.
There is one thing you can try to see if it improves performance. You can switch from using the loopback to using shared memory transfer instead. Its pretty easy to do - but I do not recommend this if this Media Agents is processing a lot of jobs, as the number of parallel operations will also be limited (a separate setting on the MA). Follow the instructions here and ensure the checkbox is de-selected to disable the use of the loopback adapter. You don't need to restart services, just pause/resume or restart the job to after changing the checkbox either way.
+1
I do not recommend this if this Media Agents is processing a lot of jobs
That makes sense. This is basically a Client; the Media Agent package is only installed as a prerequisite for Oracle Synthetic Fulls. It’s limited to just a few jobs; no more than one DB and a few DB logs at a time. To the best of my ability, I have it configured to not participate in any other jobs besides self-backups.
shared memory transfer
Does that mean this config is capable of hogging the machine’s RAM?
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
