If you have multiple Connection Brokers clustered around a common Microsoft SQL Server 2005 or 2008 database, you must individually update all Connection Brokers in the cluster.

Use the following procedure to update a cluster of Connection Brokers. Click here to download a PDF version of these instructions.

1. Determine a maintenance window when user activity will be low to update your Connection Brokers.
2. Snapshot all Connection Brokers in the cluster.
3. Backup the SQL Server database used for the cluster.
4. Make note of the Site ID for each Connection Broker in the cluster.
5. Switch all but one Connection Broker back to using an internal database.
6. If replication is turned on for the SQL Server database, turn replication off.
7. Update the Connection Broker that is attached to the external database.

   The update process modifies the database scheme to support the new Connection Broker version.

8. Update the remaining Connection Brokers, while they are still attached to the internal database.
9. Only after all Connection Brokers are updated, switch the Connection Brokers from their internal databases back to the SQL Server database. Ensure that you reconnect each Connection Broker using the same Site ID previously assigned to that Connection Broker.

Any Connection Brokers that you do not switch back to an internal database before beginning the upgrade enter maintenance mode after the first Connection Broker is upgraded. In some cases, you cannot log in to the Administrator Web interface of a maintenance mode Connection Broker to perform an upgrade.

If you encounter this problem, use the virtual appliance console to switch the maintenance mode Connection Brokers back to an internal database. Then, follow step 7 and 8 in the previous procedure to upgrade the remaining Connection Brokers in your cluster.