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.

Preparing for zero downtime upgrade

For zero downtime upgrade you need to perform the following additional tasks as part of the preparing activities:

Restrictions for zero downtime upgrade

You must follow these restrictions during the upgrade process:

  • Do not restart non-primary servers during the entire upgrade process. You won't be able to connect to the server. 
  • Do not preload the BMC Remedy Midtier during the upgrade. The active server will get terminated. 
  • You must not perform any operations described in the Restrictions after restoring the database on the upgrade server.

Preparing mid tier for zero downtime upgrade

Perform the following settings to ensure that BMC Remedy Mid tier has the entire cache till the upgrade is complete.

  1. Open the Mid Tier Configuration tool. See Accessing the Mid Tier Configuration Tool.
  2. Click AR Server Settings to open the AR Server Settings page.
  3. Select the server > click Edit > Select the Pre-load check box. 
  4. Click Cache Settings to open the Cache Settings page.
  5. Ensure that the Enable Cache Persistence check box is selected.
  6. Sync the cache. 
  7. Click the AR Server Settings to open the AR Server Settings page.
  8. Select the server > click Edit > Clear the Pre-load check box. 
  9. Click Cache Settings to open the Cache Settings page and complete the following changes:
    1. Clear the Perform check check box.
    2. Clear the Synchronized Definition Change Check check box.
    3. Set Update Flashboard Definition Interval (Seconds) to your upgrade duration.
    4. Set the Resource Check Interval (Seconds) to your upgrade duration.

BMC Remedy AR System configuration changes before performing zero downtime upgrade

Note

Perform these activities after you complete all the development and QA activities.

  1. Complete the following changes on the primary server:
    1. In the ar.conf  add is-ZDT:T parameter.
      When you add this parameter, a server restart is not needed. This parameter must be added for the installer to understand that zero downtime upgrade is initiated.
    2. Configure the admin server such that it does not failover and the admin capability remains with the primary server even if it is shut down. 
      In the AR System Server Group Operation Ranking form you must set the primary server to rank 1 and keep the ranking for other servers blank. 
      See,  Setting failover rankings for servers and operations  in BMC Remedy AR System online documentation. 

      Note

      To reflect the changes, restart the servers that were configured for admin server failover. This should be planned in advanced before performing the upgrade.

    3. Configure the primary server to not signal other servers on definition changes and remove the primary server from the server group.
      Open the AR System Administration > Server Information form, and click the Configuration tab.
      1. Select the Disable ARSignals check box.
      2. Clear the Server Group Member check box.
    4. Open the AR System Administration > Server Information form, and click the FTS tab.
      1. Select the Disable FTS Indexer check box.

        Note

         You must perform this setting for all the indexers in the server group environment. You must revert this setting after you upgrade all the servers and specifically after running the ardbutils_zdt utility.

    5. You may choose to restart the server. However, the installer will anyways restart it during the installation.
  2. Complete the following changes on the non-primary server(s):
    1. In the ar.conf  add is-ZDT:T parameter.
      When you add this parameter, a server restart is not needed. This parameter must be added for the installer to understand that zero downtime upgrade is initiated.
    2. Set the thread queue size with min = max.  For example, if for fast thread 390620 minimum is 3 and the maximum is 5, then set the minimum to 5.

      1. Open the AR System Administration > Server Information form, and click the Ports and Queues tab.

      2. In the Server Queue section, update the Min Threads entries to match the Max Threads entries.
        See,  Defining queues and configuring threads  in BMC Remedy AR System online documentation.

      3. Similarly update all the other private queues and threads. For example, Plugin-ARDBC-Threads, Plugin-AREA-Threads, or Plugin-Filter-API-Threads.
        You must ensure that no new threads are created on the non-primary server(s). 

Note

As part of the go-live stage, apart from step 1a and 2a, you must revert all the changes.

Related topics

 Upgrading platform components with zero downtime

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

Comments

  1. Andreas Mitterdorfer

    There is a minor typo, obviously a "do" is missing:

    ...will anyways the restart it during ..

     

    Regarding 1a) and 2a) is-ZDT:T

    Do we need to signal this configuration change to the secondary servers via arsignal or is it sufficient to add it to ar.cfg/ar.conf?

    Aug 31, 2015 08:55
    1. Hemant Baliwala

      Hi Andreas, 

      Thanks for your comment. 

      I have updated the topic. 

      You need to update the is-ZDT parameter only on the primary server. 

      Thanks, 

      Hemant

      Sep 01, 2015 03:39
      1. Andreas Mitterdorfer

        Hello Hemant,

        Thanks for the update however I'm confused now as

         

        2. Complete the following changes on the non-primary server(s):

        a. In the ar.conf  add is-ZDT:T parameter.

         

        is still in place? Does this mean we only need to add the parameter in ar.conf and do nothing else (no restart and no arsignal)?

         

        Br,

        Andreas

        Sep 01, 2015 08:37
        1. Hemant Baliwala

          Hi Andreas, 

          My bad. You need perform the changes on all the servers. 

          No restart is needed. You just need to update the file. 

          I have updated the topic. 

          1. In the ar.conf  add is-ZDT:T parameter.
            When you add this parameter, a server restart is not needed. This parameter must be added for the installer to understand that zero downtime upgrade is initiated.
          Sep 02, 2015 04:26
          1. Andreas Mitterdorfer

            Thanks for clarification, appreciated. (smile)

            Sep 02, 2015 05:10
  2. Igor Svetek

    I have a problem with the following steps:

    >> 9. a. Clear the Definition Change Check Interval (Seconds) check box.

    This is not a check box, it is a number field. Does this mean that we need to clear any value that is present (it is OOTB value 86400)?

    >> 9. e. Clear the Synchronised Definition Check Interval check box.

    There is no such check box or field present on this or any other page inside MidTier.


    My MidTier version is 8.1.00 201406060250 Hotfix

    Aug 13, 2018 08:56
    1. Manash Baruah

      Hello Igor,

      Thank you for the comment.

      We have reviewed the section as per your feedback and have updated accordingly.

      Thanks,

      Manash

      Mar 27, 2019 11:23