[cwensell]

THese 2 services for the Blackberry Administration Service are causing major problems on the BES server. The server is Virtual on a VMWARE 3.5 cluster. THE server itself is Windows Server 2008 SP1, with 2 CPU's and 16 GB of RAM. Still the server is pegged at 100% CPU usage and memory is at 90% usage as well. Not sure what else to do!?

Any help

[daphne]

Moved to BES Admin Corner

[icontech]

Did you ever figure out the issue? I'm having a similar problem with memory utilization on my BAS and primary BES server using 5.0.2. Thanks

[icontech]

Originally Posted by icontech

Did you ever figure out the issue? I'm having a similar problem with memory utilization on my BAS and primary BES server using 5.0.2. Thanks

Well after increasing memory from 4gb to 6gb its still using 90-95%. So this has to be an application related issue. Is it designed to use most of the memory on the server? Java?

I called TSupport and they had no idea. He told me to increase the memory.

[noname]

BAS services are resource intensive, everybody knows that. Actually the better (if not the best) or a more scalable configuration is distributed one like this:-

(1) Computer A - BES Core services (primary BES)
(2) Computer B - BES Core services (standby BES)
(3) Computer C - BAS services
(4) Computer D - MDS-IS service (Optional)
(5) Computer E - BES Monitoring services (Optional)
(6) Computer F - SQL 2005 SP3 Principal Server
(7) Computer G - SQL 2005 SP3 Mirror Server

BES 5.0 is nothing but just replacing BlackBerry Manager with the web-based BAS with more feaures to support the BlackBerry OS 5.

[icontech]

Originally Posted by noname

BAS services are resource intensive, everybody knows that. Actually the better (if not the best) or a more scalable configuration is distributed one like this:-

(1) Computer A - BES Core services (primary BES)
(2) Computer B - BES Core services (standby BES)
(3) Computer C - BAS services
(4) Computer D - MDS-IS service (Optional)
(5) Computer E - BES Monitoring services (Optional)
(6) Computer F - SQL 2005 SP3 Principal Server
(7) Computer G - SQL 2005 SP3 Mirror Server

BES 5.0 is nothing but just replacing BlackBerry Manager with the web-based BAS with more feaures to support the BlackBerry OS 5.

Our setup is exactly as you describe except we have BAS and Monitoring on the same box. Our primary BES with just the core services is maxing out the memory too. Everything is working fine, but it concerns me that its using that much memory. We only have 600 users, which they say requires 3GB of memory. I would just like a definitive answer from TSupport that this is normal behavior.

[noname]

Originally Posted by icontech

Our setup is exactly as you describe except we have BAS and Monitoring on the same box. Our primary BES with just the core services is maxing out the memory too. Everything is working fine, but it concerns me that its using that much memory. We only have 600 users, which they say requires 3GB of memory. I would just like a definitive answer from TSupport that this is normal behavior.

That's why the recommendation is for a distributed installations! Because these are expected, they know BES 5.0 is heavy weight.

Imagine what will happen to your BES if BAS + BES Core are all in one box

[icontech]

Originally Posted by noname

That's why the recommendation is for a distributed installations! Because these are expected, they know BES 5.0 is heavy weight.

Imagine what will happen to your BES if BAS + BES Core are all in one box

Our original plan was to run BAS + BES on the same box. I made a last minute decision to separate BAS onto its own box.

I have yet to find an answer on the high memory usage.

[icontech]

Bump....I'm hoping the original poster figured out the problem and can explain.

[jjbova]

We are having the exact same issue, with a VERY similar setup. To be honest, I am really thinking it has to do with the Virtual Enviroment. We have a ticket open with RIM.... NO HELP THERE!!! They just keep saying "Reintall BAS..... reinstall the BES..... ok, try to reinstall BAS again".... grrrrr.

Today we are going to put it on a physical server (It is running on an ESX3.5 with Virtual Center 2.5). I will let you know what we find out....

Also, not only will the memory and CPU run high, but after a little bit the BAS quits too.....

[nobody7290]

Originally Posted by jjbova

We are having the exact same issue, with a VERY similar setup. To be honest, I am really thinking it has to do with the Virtual Enviroment. We have a ticket open with RIM.... NO HELP THERE!!! They just keep saying "Reintall BAS..... reinstall the BES..... ok, try to reinstall BAS again".... grrrrr.

Today we are going to put it on a physical server (It is running on an ESX3.5 with Virtual Center 2.5). I will let you know what we find out....

Also, not only will the memory and CPU run high, but after a little bit the BAS quits too.....

I had something similar to your problem, maybe this helps you too ?
http://www.blackberryforums.com/bes-...-bas-dies.html

[icontech]

We're not seeing any issues with email delivery or the BAS....I was just concerned that the primary BES and standalone BAS servers have 90-95% of their physical memory utilized.

[nobody7290]

Originally Posted by icontech

We're not seeing any issues with email delivery or the BAS....I was just concerned that the primary BES and standalone BAS servers have 90-95% of their physical memory utilized.

Sorry, my Answer was only meant for "jjbova", because he is telling his BAS quits after some time.

[jjbova]

Your post didn't fix our issue, but it was good to know. We did follow it and everything was already set up right in the SQL tables. We got a hold of RIM again, and after about 3-4 hours on the phone, they deemed it was the MDS-IS service, and that since it wasn't truely supported, there was no reason to have it installed. Once we removed that, it cleared ALL our backed up tasks, and the server ran much better. But now our problem has changed.

The services are running better and when the BAS-AS is up, it runs GREAT, but it still restarts the service every 15-20 minutes, and then takes about 5-10 minutes to come up. It's like hitting the console is a "hit or miss" kinda thing. So we are still searching for an answer, but your post did help. Once we fix all these little problems, we might be able to see what the REAL issue is, lol.