This documentation applies to the 8.1 version of Remedy ITSM Deployment, 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.

Working in a staging environment

Using an example scenario, this topic explains how to operate in a staging environment. The following topics are provided:

Scenario overview

The following diagram illustrates how to operate in a staging environment if you are upgrading from version 7.6.04 or later. In this scenario, the staging environment comprises separate staged development, QA, and production servers.  

Types of servers in the the staging environment

The following table lists the types of servers that can be used during the parallel (with staging server) upgrade process. 

Type of serverDescription
ProductionYour current production environment.
Staging development serverStaging server on which you will perform the actual upgrade.
Staging QA serverStaging server on which you will perform QA testing and UAT.
Staging production server

Staging server that will go live.

Note:

Depending on your upgrade strategy, you can also use the staging development or QA server to go live.

 Stages

The following table lists the stages in the upgrade process in the staging environment:

StageDescription
Prepare the staging environment

During this stage, you set up your staging servers duplicating the installations of the current production server. To duplicate the installations, choose one of the following methods:

  • Accelerated
  • Duplicated
Perform the actual upgrade

You perform the actual upgrade on the staging development server. During this stage:

  1. Apply restrictions.
  2. Complete the source and and destination server configurations, and restore the production database in staging environment.
  3. Complete the preupgrade and configuration checks.
  4. Take a snapshot of the validated copy.
  5. Perform the upgrade.
  6. Restore the upgraded database on all the staging servers.
  7. Complete the postupgrade tasks.
  8. Perform the first delta data migration (DDM) between the staged production server and the production server.
Validate

Typically, you perform the validation on the staged QA server. During this stage:

  1. Complete the QA testing and fix all the QA defects on the staged development server. After QA testing is complete, you must import the def on all the staging servers.
  2. Complete the user acceptance testing (UAT) and fix the issues on staged development server. After the UAT is complete, you must import the def on all the staging servers. However, you must import def only after completing another round of DDM.
  3. Complete the final testing and perform DDM again.
Deploy

During the deployment stage:

  1. Freeze user activity on the production server.
  2. Perform the final DDM.
  3. Go live with the staged production server.

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.

Comments