This documentation supports the 9.0 version of BMC Remedy ITSM Deployment.

To view the latest version, select the version from the Product version menu.

Upgrading secondary servers

When installing the secondary server and all servers afterward, the Server Group option is not displayed because the installer automatically detects this information based on the database details provided during installation and the installation continues. Remember that you are using a common database that the server group shares, as well as the database login information and database settings. All your AR System servers will connect to this database. BMC recommends that you upgrade the secondary servers one after the other and not in parallel. However, if you want to upgrade the secondary servers in parallel, you must point the secondary server to the Development server and the third server to the QA server. 

To upgrade secondary server

  • In your production enviornment if you have removed the primary server from the server group before you upgrade, you must update the ranking of the secondary server to the primary server ranking before you begin the upgrade.

    For example, server A is the primary server with ranking 1 and server B is the secondary server with ranking 2. So when you remove server A from the server group, you must update the ranking the server B to 1 before you upgrade server B.

  • Run the installers on the secondary server, without starting the existing BMC Remedy AR System server.
  • You must point the secondary server to the new production (staging server) database.
  • After you complete the upgrade you may add and modify the entries in the BMC Remedy AR System server group ranking form. 

Was this page helpful? Yes No Submitting... Thank you