[mbana]

Is it possible to have 2 BES versions pointing to the same database?

We are currently using 4.1.0.38 and want to upgrade to 4.1.6.

the plan is to setup a new BES with 4.1.6 and point it to the the database that is currently hooked up to 4.1.0.38. The database is remote sql 2005. We would then move users over..

i have a srp already to setup the new BES. Is this safe to do or should i bring up the new server with the same version then move then upgrade?

Thanks

All BES that use the same configuration database need to be at the same version.

[qc_metal]

I don't believe that is true...but I am not sure. For example, my BESMgmt database is at 4.1.2, whereas my BES Server is at 4.1.5. My guess would be as long as the BES Server console is running from the same base database version, then it is fine. Older BES Server versions just would not use newer fields and tables. If this were NOT the case, then you would effectively have to migrate all of your BES servers to new versions simultaneously in order to limit your user's downtime.

[TargetIT]

I would guess how much has changed - if fields are just added, you're fine. If existing fields change (type, length), then it wouldn't work.

[knottyrope]

You can have 2 BES on the same database but why bother having 2 if your moving them anyway?

Just upgrade the old server to 4.1.6 then do a knife edge to the new hardware.

[x14]

I don't think you can have 4.1.0 and 4.1.6 together. There was a big db schema change in 4.1.3.

I've had 4.1.4 and 4.1.6 using the same db with no issues.