×
 
 
  •  
$helper.renderConfluenceMacro('{bmc-global-announcement:$space.key}')

 

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.
Remedy IT Service Management Suite 8.1 Upgrading

Planning the upgrade

BMC contributors content

For additional information, you can also refer to the following webinar conducted by BMC Support.

You can also connect with other users for related discussions on the BMC Community.

read-and-planThe following topics will help you to plan your upgrade: 

Upgrade paths

Note

You can upgrade directly to BMC Remedy ITSM 8.1.00 from BMC Remedy ITSM 7.0.03 patch 009, or a later version.

If, however, you are upgrading from a version earlier than BMC Remedy 7.0.03 patch 009, perform one of the following actions:

  • Do a fresh installation of BMC Remedy ITSM 8.1.00 and migrate the data.
  • First upgrade to BMC Remedy ITSM 7.0.03 patch 009 and then upgrade to 8.1.00.

You will be using one of these upgrade paths to get to the latest version of BMC Remedy ITSM. For each starting version, you must ensure that all components are the correct versions.

—

Upgrade pathDescription
Upgrade Path 1: From versions earlier than 7.6.04

This upgrade path involves the following process:

  1. Upgrade the BMC Remedy AR System server to the latest version. 
  2. Create overlays for all of your customizations. You can create customizations by using the Best Practice Conversion Utility (BPCU), which converts all of your customizations into overlays.
  3. Upgrade other components and applications to the latest versions.
Upgrade Path 2: From version 7.6.04 or laterIf you have already created overlays, you can directly upgrade each component to the latest version. The Best Practice Customization mode of BMC Remedy Developer Studio ensures that all customizations are saved as overlays.

Back to top

Upgrade phases

At a high level, the upgrade process is split into the following phases for better planning. These phases are valid for both upgrade paths:

Upgrade phaseDescription
Phase 1: Preupgrade readinessFor this phase, you must plan to ensure that you have prepared the entire environment for a successful upgrade.
See Planning preupgrade readiness tasks.
Phase 2: UpgradeFor this phase, you must consider the upgrade sequence and upgrade type.
See Planning upgrade tasks.
Phase 3: PostupgradeFor this phase, you must plan for postupgrade tasks such overlay reconciliation, performance optimization, and sanity testing.
See Planning postupgrade tasks.

Back to top

Planning preupgrade readiness tasks

Ensuring preupgrade readiness requires performing of the following tasks:

TaskAdditional information
Downloading the latest installers from www.bmc.com/support

See:

Completing the upgrade checklistsSee Completing the planning spreadsheet for an upgrade.
Ensuring that you meet all minimum version requirementsSee Reviewing the compatibility matrix before upgrading.
Executing the BMC Remedy Configuration utility for overall health check before upgradeSee BMC Remedy Configuration Check utility.
Backing up the operating systems and database (VM Snapshot)You must perform the backup before you install each component.
Practicing the upgrade on a test environmentSee Upgrade testing.
Freezing production rollouts from any administrative changes—
Backing up all of the customizations. You must export the customizations from Developer StudioSee Exporting objects. (This topic will open from the BMC Remedy AR System 8.1.00 space).
Resolving any known issues before the upgradeSee Known and corrected issues.
Performing server configuration adjustments per the documentationSee Preparing your components and applications for an upgrade.
Preparing for ITSM CI attribute and multi-tenancy changesSee Update to the multi-tenancy model.

For detailed information about preupgrade readiness tasks, see Preparing for upgrade.

Back to top

Planning upgrade tasks

The type of upgrade that you perform depends on which of the following scenarios describes your situation:

SituationAdditional information
You want to upgrade a single server or server group environment.—
You are upgrading with overlays already implemented or you want to implement them.See Upgrade and overlays.

You want to do an in-place (without staging server) or a parallel (with staging server) upgrade.

Here, you need to decide if you want to use an accelerated staging or duplicated staging environment.

See 

Note

Refer to the end-to-end steps for performing the upgrade that applies to your specific scenario. See Upgrade scenarios.

Back to top

Upgrade and overlays

In BMC Remedy Action Request System 7.6.04, the overlays feature was introduced to preserve application customizations during the upgrade process. During an upgrade, the upgrade installers ignore application overlays and change only the objects that were originally installed with the application or server. After the upgrade, the application or server continues to use the overlays instead of the origin objects for runtime operations so that the customizations are preserved. For more information, see Upgrading with overlays already present. 

When upgrading from a previous release that was customized without overlays, you will need to create overlays for existing customizations, acquire origin objects, restore origin objects on the staging server, and minimize the number of overlays on your system. For more information, see Upgrading without overlays already present.

The following terms will help you to understand the overlays implementation:

  • Custom object: A customer-created object that is not distributed by BMC.
  • Origin object: An original, unmodified object that is included with a released BMC product.
  • Overlaid object: An origin object that has an overlay associated with it.
  • Overlay object: A customized version of an origin object that is used in place of the origin object. In this case, the origin object becomes an overlaid object.

For detailed information about the overlays feature, see Customizing applications using overlays and custom objects in the BMC Remedy AR System documentation.

Back to top

Parallel versus in-place upgrade

The following table compares the parallel and in-place upgrade methods.

Parallel upgrade (with staging server)In-place upgrade (without staging server)

Uses a staging server, which 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

Additional staging hardware is not needed. Additional load balancer or configuration updates are not needed.

The original production environment is preserved, allowing fast fallback.You perform the upgrade in the production environment.
Minimal end-user downtimeMinimal overall upgrade time and complexity

Need to perform delta data migration

Delta data migration is not needed. Data validation is not needed.

Upgrade is not confined to a fixed upgrade window. Upgrade can be done over several days or weeks.

You can perform the upgrade in stages by initially upgrading the BMC Remedy AR System server or BMC Remedy Mid Tier.

For server group:

  • Users can be active throughout most of the process.
  • Users can start accessing each secondary server after it is upgraded and added to the Load Balancer.

For server group:

  • Users can start working after the primary administration server is upgraded.
  • Users can start accessing each secondary server only after it is upgraded.

Back to top

Accelerated versus duplicated staging server

The following table compares accelerated and duplicated staging servers.

Accelerated staging serverDuplicated staging server
To upgrade using an accelerated staging server (database-only upgrade), you create a copy of the production server database in the staging environment only.To create a duplicated staging server, you create an exact duplicate of your production server.
The AR System server must be upgraded on the staging server against the copy of the production server database only.You must perform a normal upgrade with file system.
BMC out-of-the-box configurations are applied after the upgrade in the staging environment.Configurations of the production environment are retained in the staging environment.

Back to top

Upgrade scenarios

The following diagram illustrates the upgrade scenarios.

Depending on your upgrade scenario, follow the end-to-end steps documented in one of the following topics:

Back to top 

Upgrade sequence

You must upgrade the BMC Remedy ITSM suite components in the following sequence:

This sequence implies that you must first upgrade the platform, then upgrade your CMDB, then your applications, and finally all clients that reside on your local computer. 

For information about different installers and the components they install, see BMC Remedy ITSM Suite components and installers.

Back to top

Planning postupgrade tasks

The following diagram shows the postupgrade tasks that you will perform:

TaskAdditional information
Base, overlay, and custom objects review

Compare new features with customizations and remove unneeded overlays.

Performance optimization
  • Complete the performance-tuning tasks. See Performance tuning for BSM. (This topic will open from the BMC Remedy AR System space).
  • Determine if you have any forms with large amounts of data that can be removed or archived.
Sanity testing
  • Perform end-to-end tests that utilize any of the new functionality added by the upgrade, as well as existing functionality that your end users will utilize. Ensure that you edit any existing test scripts so that they work in the new environment. 
  • Perform performance and stability testing to ensure that your system is ready to go live.

Back to top

Tools required for upgrade

You will need the following tools when you upgrade:

ToolDescription
Best Practice Conversion Utility (BPCU)Helps to identify platform and application customizations and convert them to overlays. See Creating overlays with the Best Practice Conversion Utility.
BMC Remedy Migrator toolHelps to synchronize data among your BMC Remedy AR System development, staging, and production systems. See Migrator tools.
Delta Data Migration toolAllows you to upload the data that changed on a production server during the time that a staging server was being upgraded. You will need this tool to perform the staged upgrade, whether or not overlays are implemented. See Migrator tools.
BMC Remedy Developer StudioRequired for all upgrades. BMC Remedy Developer Studio is an integrated development environment (IDE) for BMC Remedy AR System applications. See, Application development with BMC Remedy Developer Studio.
BMC Remedy Configuration Check utilityThe BMC Remedy Configuration Check utility is a centralized framework utility that validates the environment for BMC Remedy AR System installation or upgrade. This utility also validates the BMC Remedy AR System server configuration and customization, and generates a consolidated report. See BMC Remedy Configuration Check utility.
Snapshot plug-inTo obtain a list of all of the overlay objects that were modified in the latest release, obtain the Snapshot utility (a Developer Studio plug-in). This unsupported utility is available on the BMC Developer Network (https://communities.bmc.com/communities/community/bmcdn).
Maintenance ToolProduct diagnostic utility for performing health checks, collecting logs, and encrypting passwords. See, BMC Remedy ITSM Maintenance tool.

Back to top

·        

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.

Last modified by Hemant Baliwala on Jul 03, 2014
planning upgrade itsm

Comments

Log in or register to comment.

Upgrading
Preparing for upgrade
© Copyright 1996 - 2018 BMC Software, Inc. © Copyright 1996 - 2018 BladeLogic, Inc.
Legal notices

Powered by Atlassian Confluence and Scroll Viewport

© Copyright 2005-2024 BMC Software, Inc. Use of this site signifies your acceptance of BMC’s Terms of Use . BMC, the BMC logo, and other BMC marks are assets of BMC Software, Inc. These trademarks are registered and may be registered in the U.S. and in other countries.