There is something else that I thought everyone should know. The All Local
Hard Drives directive is handled very differently in 5.1. BPSCHED needs to
resolve this with each server on a serial basis before a job even gets into the
queued state with 5.1.
Ergo, if you have any network issues, this resolution will pause throughout
your timeout values and BPSCHED can take a lot longer than normal while it
works in the background before you even see jobs queued. In other words, if
you submit a backup of 100 Windows Servers using All Local Hard Drives, it has
to resolve and detect All Local Drives across all 100 servers before the jobs
will even hit the queue and you will see it. BPSCHED is taking a lot longer to
run these days.
This has an even greater affect if your master/media servers are HP due to an
HP Unix OS limitation. Feel free to email me if you use HP-Unix and I can
share additional feedback and tuning parameters and patch levels.
Is it obvious that I've been fighting 5.1 issues for 9 weeks? We installed 5.1
MP2 binaries before it was GA. I feel an ownership to give back to the
community, so any questions you have or anything you want me to test, just ask.
I owe you !!!
Brian
-----Original Message-----
From: DIVEN, BRIAN
Sent: Saturday, January 29, 2005 8:16 PM
To: DIVEN, BRIAN; veritas-bu AT mailman.eng.auburn DOT edu
Subject: RE: [Veritas-bu] Issues Upgrading 4.5 FP7 to NBU 5.1 for Large
Environments
Please reference http://support.veritas.com/docs/274544
-----Original Message-----
From: veritas-bu-admin AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu]On Behalf Of
briandiven AT northwesternmutual DOT com
Sent: Saturday, January 29, 2005 6:20 PM
To: veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] Issues Upgrading 4.5 FP7 to NBU 5.1 for Large
Environments
TechNote 274544 provides ideas to reduce the burden on the NBU 5.1 software in
large environments. Since our upgrade 9 weeks ago, we have been bouncing NBU
almost daily due to hung backups and we are a large 24x7 environment and have
seen limited improvements after 9 weeks of an open case with Veritas - and then
seeing this TechNote. I find it ironic that the re-branding of 5.1 to
Enterprise Server and a technote that says not to stress BPSCHED in Enterprise
Server environments can occur, so I'd like to see if I'm alone here.
We have had several issues upgrading to NBU 5.1 MP1 and now MP2 where we are
unable to submit many backups (queued or active) at once. The recent TechNote
274544 fits our account perfectly and I am wondering if any other large NBU
shops are experiencing similar issues. I have a hard time believing this
TechNote was generated just because of us. Veritas shows no desire to address
this other than to wait until release 6.x and I could use some friends that
will either state that they have an issue or help me push a fix through.
Veritas backline also stated that they won't support us backing off of 5.1 MP1
to 4.5 FP7 where we had a stable environment. They test MP2 to MP1 uninstalls,
but when you upgrade from release 4 to release 5, they don't test this and
there are some inherent undocumented catalog changes that could mess us up and
not be able to recover a 5.1 backup to a 4.5 restore. They only want to fix
and go forward. We had many MP2 binaries prior to them being released and then
moved to MP2 and we still can't get through a night if we submit all of our
backups.
We have exercised every recommendation in this technote and remain unsuccessful.
I need some of my friends to contact me with similar issues to get this fixed
if we are to fix and go forward. We need to push Veritas on this issue as a
group of large Enterprise Server companies.
Brian
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
|
