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

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



Preparing the AR System server for a server group upgrade

If you are upgrading a server group during an outage window, perform the instructions in this section before you upgrade. 

However, if you are performing a zero-downtime upgrade of the platform, go to Preparing for zero-downtime upgrade of the platform.  


  1. Before starting the upgrade, stop all the email engines running on the non-administrative AR servers. For instructions, see Starting and stopping the email engine.
  2. After setting up your upgrade servers in case of staged upgrade or before upgrading your production servers during an outage window, stop all the non-administrative AR servers. For instructions, see Starting and stopping the BMC Remedy AR System server.
  3. Start the primary server and ensure that the AR System Server Group Operation Ranking form, the primary server Rank must be set to 1 and set the ranking for other administrative failover servers set to null (empty value).

    If the ranking form is not auto-populated, manually add the entries for the primary server. To manually update the entries, Setting failover rankings for servers and operations

  4. Start the non-administrative servers one by one and ensure the following:
    • Administration, CMDB, and Approval operations have the same ranking within a non-administrative server.  
    • In version 9.x or later, for each server in the server group ensure that the server-connect-name parameter of Centralized Configuration is auto-populated with the specific sever host name. This is required to uniquely identify each server in the server group. In versions prior to 9.x, ensure ar.cfg or ar.conf is populated with the server-connect-name set to the primary server. 

Where to go from here

Next task

Proceed with Upgrading the platform.

Up to process
 

If you are finished upgrading the platform, return to the appropriate upgrade process:

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

Comments

  1. Sirisha Dabiru

    Hi Thomas Arndorfer,

    Sorry for the delay in my response. This is regarding the following comment posted by you:

    CommentResponse
    After which step of the upgrade procedure should we return to the regular ranking values of the secondary servers? What would be the consequence if we would remain with the normal value of 2 in the ranking of secondary servers during the upgrade?

    After completing the upgrade process, apply ranking. The following reference topic provides the required info about ranking.

    Setting failover rankings for servers and operations


    During the upgrade, process if ranking 2 remains for a server, it becomes admin server. Having another admin server during upgrade is not recommended.


    Regards,

    Sirisha

    Oct 03, 2018 03:00
  2. Sirisha Dabiru

    Hi Thad Esser,

    Here is the response for your comment:

    CommentResponse

    In Step 3, the instructions say to set the rank of all secondary servers to null for all operations. In step 4, the first bullet point, it says to ensure that the mentioned three operations have the same rank on all secondary servers. Does that mean we should set just those three operations to a non-null value?

    Users must set those operations to null value only.


    Regards,

    Sirisha

    Mar 12, 2019 07:40