This documentation applies to the 8.1 version of Remedy IT Service Management Suite, which is in "End of Version Support." You will not be able to leave comments.

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

Stage 1 - Setting up a staging server for upgrades without overlays already present

The following topics explain the implementation of staging environment for upgrade:

The following topics provide the steps for setting up a staging server for upgrade:


If you are performing an in-place upgrade without using a staging server, perform all of the stages and steps listed in this section, but skip the staging server setup. Whenever the documentation refers to the staging server (or StagingServer), use your production or development server instead. The rest of the in-place-upgrade process is the same as the staged-upgrade process.

Understanding staging environment implementation for upgrade

The staged-upgrade process allows you to upgrade your application and create overlays or otherwise address pre-existing customizations to your BMC Remedy AR System server objects while your production server remains available to users. The following illustrations shows the set of servers that might be required to perform the upgrade.

Understanding staging server implementation

For setting up a staging environment, you can use one of the following method:

When upgrading using staging server, consider the following: 

  • Whether you use the accelerated staging server setup or the duplicated staging server setup, you must copy your entire production database to the staging server.
  • At the end of the process, the staging server becomes the new production server.
  • Make sure that the staging server you will use, meets the specifications required for the upgrade. See, System requirements.

When you create the staging server, use the same server name to avoid naming issues when you promote the staging server to production. If you change the name, follow the process outlined in Changing a server name when using a duplicated or migrated environment. Also, if you are using the same server name, you need to be careful that the users are not pointed to the staging server during the upgrade process.

Understanding reference server implementation

If you are implementing the reference environment, you might require another server (referred to as the upgrade comparison server) to host upgraded applications. These additional servers do not have to be production quality, but they must have compatible software and a compatible database to hold referenced copies of the BMC software and database objects. The reference server and upgrade comparison server are temporary servers and are not needed after the entire upgrade process is complete.

Where to go from here

Restrictions after restoring the database on the staging server without overlays

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.


  1. Kelly Logan

    Looks like the first note is missing some beginning text. It starts with

    ing server, skip the staging server setup stage.

    Also, the illustration right after that says "? Unknown attachment"

    Aug 05, 2014 01:56
    1. Catherine Siderine

      Thanks, Kelly.

      I have forwarded your comment to the person who maintains this page.



      Aug 06, 2014 05:52
    1. Hemant Baliwala

      Hi Kelly, 

      Thanks for your comment. I have fixed the topic. 



      Aug 08, 2014 04:30