Re: [Veritas-bu] netbackup master single threaded vs. multithreaded

I've noticed the same thing, and it seems to be worse when your number of clients is high and other factors are working against you. I recall reading other threads on the same subject, and some said it was due to how NBU tries to contact all clients during this process and if you have any dead clients it must timeout before continuing. When I was experiencing this problem personally, it was with NBU 5.x and I did have some dead clients configured in a policy that was not scheduled to run. I had about 120 unique clients configured and about 2/3 of them were in the same backup window and the system used an Ultra Sparc III processor.

-Jon

From: Kevin Corley <Kevin.Corley AT apollogrp DOT edu>
To: veritas-bu AT mailman.eng.auburn DOT edu
Sent: Thursday, June 25, 2009 2:07:47 PM
Subject: [Veritas-bu] netbackup master single threaded vs. multithreaded

Hello,
Has anyone here had performance problems with 6.5 masters running on Solaris with T5220 or T2 Sparc class processors? I have noticed that during periods of heavy job load the nbrb evaluation cycle, which appears to handled via a single threaded dbsrv9 process, can take forever and leave jobs stuck between requesting & granted resources states. Sometime for 15 minutes a time, depending on the job load.

I am familiar with nbrb.conf tweaks, however this doesn't make much difference in my environment where we have many disk-based destinations. Seems like in large environments, the master needs to be on a processor better suited for single threaded performance.

Thoughts?

This message is private and confidential. If you have received it in error, please notify the sender and remove it from your system.

_______________________________________________
Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu