[Dobbin]

I have 4 BES instances running on 4 physical servers, I have also installed another 4 BES servers at a remote site which are online with the BES services installed but services stopped.

If something happens at site A I start the services on site B and BB service is resumed to users. Fantastic. When I need to apply operating system patches to site A I failover to site B, patch site A then run from B until I need to patch B. In a V4.0 world I had created a script which stopped and disabled the services on site A and started them on site B. Nice and easy out of hours change to run a script - minimal service impact for users.

In a 4.1.2 world, for each physical server that will run the BB service an MDS and IM connector (if you chose to install IM) are created. In your Blackberry manager console you have the domain and then the servers container within, and at the top (in shiny blue) is your BES instance. Great. Beneath that you will have an MDS and an IM connector for each physical box that has been installed, e.g. :

Blackberry domain
-----Servers
---------BESName
---------Server1_MDS-CS_1
---------Server2_MDS-CS_2
---------Server1_BBIM_1
---------Server2_BBIM_2

So, I stop the services on server1 and attempt to start them on server2, but I cannot start the MDS and IM servs on server2 as the services are still mapped to server1! I have to open the Blackberry manager, click on the domain, service control & customisation, and finally the MDS and then IM to BES mapping. After I amend the services to be mapped to server2, I can start the MDS and IM services. Clearly, this stops my nice automated (but manually initiated) failover from being automated!

I presume this mapping to be in the config database, but running a SQL trace at the time of making the changes turns nothing up. Although I love overtime and could do with the dosh, there is a drive to remove manual processes at my place of work, and this would be one I could automate - if I could find out how! Have any of you managed to automate this at all?