100% Utilization - iFolder/Java/Etc

[rga...@acnm.org]

If it were just one of the two servers that would make sense - but this is
happening to two different servers with different motherboards and
different hardware, and started immediately when we moved up to SBS6.
It's really frustrating.

- Rob Gates
ACNM

> Sigh... I remember fighting this for a solid week once, round the clock,
> etc.
>
> What happened in my case was a bad motherboard. I'd suspect either
hardware
> or drivers as a start.
>
> Tim Wohlford, CNE
>
>
> <rga...@acnm.org> wrote in message
> news:yu0fb.1722$L41....@prv-forum2.provo.novell.com...
> > I'm hoping someone might have some insight since the knowledgebase was
> > rather unclear on what we might need to try....
> >
> > We're a small non-profit association and have two servers running SBS6,
> > one is a primary file server, the other a groupwise server. We've
> > experienced 100% utilization problems/server freezes about once a week
> > since we moved to SBS6 in May. It took us a while, but we eventually
> > recognized a potential pattern in that it seems to occur only if one of
> > our remote users tries to utilize one of the web access tools (iFolder
> > type stuff on the file server, groupwise web access on the Groupwise
> > server). It doesn't happen *every* time these tools are used, but it
only
> > seems to happen if these tools are in use.
> >
> > Any thoughts/suggestions?
> >
> > Thanks,
> > Rob Gates
>
>

[Splash]

We have this problem on multiple servers on different networks
If you check the offending process I believe you will find it is JAVA
Java - EXIT followed by TOMCAT33 commands should cure the 100% utilization
immediately and bring your GW web access back on line
The problem occurs with NSBS 6 SP3 and Backup Exec v9
We have found that the problem never occurs when Backup Exec is stopped
Any errors during the backup also seem to trigger the problem
Plus, take a look at the processor utilization during the verify cycle
You will see it jump to 100% and stay there !
Veritas deny any knowledge of the problem, yet the forums are stuffed with
guys experiencing these difficulties
I have two solutions
1) Use CRON to unload backup Exec immediately after completing the backup
2) Upgrade to Backup Exec v9.1
Hope this helps

Splash