[JavaJunkee]

I'm having a tough time finding good instructions on upgrading 5.0 to 5.0.1 -

I'm running a test BES 5.0 (high availability). Since the upgrade will modify the DB, what's the order of events on upgrading the primary and standby servers.

All I could find, was to shut down services on the standby and upgrade it first. Then manually fail over and upgrade the (former) primary.

But during the standby upgrade the DB is modified and yet the primary will be running and pointed to the DB? Doesn't seem right. What am I missing?

[besadmin23]

This is absolutely correct. Only schema changes happen to a DB while upgrade occurs. This does NOT mean that the primary BES can't be using it at the same time. If you feel more comfortable and have the option to have ~15 mins of down time, just stop the BES services on the primary BES as well then upgrade the standby.

I am guessing you have BAS installed on both nodes? If you only have it on one of them, THAT is the one that has to be upgraded first.

This has always been the case with upgrades of the DB in multi-BES environments. Think about it. If you had 20 BES servers all attached to one DB, it would be a nightmare to have to stop all of them at the same time just to upgrade the DB. RIM has a good design allowing the upgrade while other machines are connected.

No worries!!

[JavaJunkee]

Thanks for the reply!

Yeah, previous to 5.0, I would take down our two BES by stopping the services. Upgrade one, allowing the DB changes, then upgrade the second one.

We're only a two (450 - 500 users), BES environment, so it's not too much trouble to take down the whole thing after hours.