End-to-end tasks for parallel (with staging server) upgrade on a single server without overlays already present

When viewing the latest version of a product on the Electronic Product Download (EPD) site, you see only the components (including licensed add-ons) that are covered under the licenses associated with your Support ID or EPD profile.

Ensure that you download the latest service pack and patch.

Decide which of the following

• Accelerated staging server
• Duplicated staging server 

You choose the server method based on your configuration.

At the end of the process, the staging server becomes the new production server.

If you are upgrading using the accelerated staging server method, you must create a copy of the production server database in the staging environment only. The BMC Remedy AR System server installation must then be done on the staging server against the copy of the production server database.

You must run the installer in Install mode so that the AR System server is upgraded, not reinstalled.

If you are upgrading using the duplicated staging server method, you must create an exact duplicate of your production server, installing the AR System server and all of the BMC Remedy IT Service Management suite applications and components, and any other applications such as BMC Service Impact Manager, integration for BMC Remedy Service Desk, or BMC ProactiveNet Performance Management, before starting the upgrade. 

You must run the installer in Upgrade mode.

(If you are using the duplicated staging server)

Ensure that you have backups of all versions listed.

Set up a reference server with unmodified versions of the same applications and components that are on the staging server.

Suspend all administrative operations until the upgrade is complete

You must install the AR System server to obtain the Best Practice Conversion Utility (BPCU).

Do not install any BMC Remedy AR System components or applications other than the AR System server. If you do, your customizations might be overwritten.

Run the Best Practice Conversion Utility (BPCU) to create overlays:

• If you have copied BMC Remedy AR System objects and prefixed the copies with a string, run BPCU to convert these prefixes.
• If you have copied BMC Remedy AR System objects and suffixed the copies with a string, run BPCU to convert these suffixes.

After you perform these actions, run BPCU for any remaining objects.

You acquire unmodified origin objects and then compare them to the overlays on your server to see exactly what has changed in any object.

Remove all overlays that are the same as the object that they overlay, and all overlays that contain changes that are no longer needed. Minimizing overlays reduces the number of customizations that must be maintained during future application upgrades.

This action upgrades the AR System server, Approval Server, Assignment Engine, Email Engine, and Flashboards. It also installs the following plug-ins: AREA LDAP, ARDBC, Web Services, SNMP, and FTS.

All BMC Atrium Core versions have steps in common. You must comment out the entries in the armonitor and ar configuration files. Also, perform a complete health check of the AR System server and BMC Atrium CMDB.

This procedure installs BMC Atrium CMDB, Reconciliation Engine, and Normalization Engine.

You cannot install BMC Atrium CMDB on a remote AR System server; you must perform the installation on the computer on which BMC Remedy AR System is installed.

From the BMC Atrium Core Maintenance tool, run a health check to ensure that the upgrade was successful.

When you upgrade from version 7.5 or later, you must choose a new installation directory for the upgrade that is not below the BMC_AR_SYSTEM_HOME directory. 

The old installation directory is now obsolete and should be deleted to avoid confusion.

• If you have installed the earlier version of BMC Atrium Core Web Services on a separate computer, upgrade BMC Atrium Core Web Services on that computer after you have upgraded BMC Atrium CMDB on the primary stack.
• If you have installed the earlier version of BMC Atrium Core Web Services on the same computer on which you have installed BMC Atrium CMDB, BMC Atrium Core Web Services is upgraded when you upgrade BMC Atrium CMDB.

For upgrade from 8.0 to 8.1: Before running the Atrium Integrator server installation program, set Max Attach Size in the AR System Server Information window to 0 MB or 100 MB. If Max Attach Size is set to a value other than 0 MB or 100 MB, the Atrium Integrator server installation does not complete.

For upgrade from 7.6.04 to 8.1: When you upgrade Atrium Integrator 7.6.04 to 8.1, a backup of your old jobs and transformations is created and saved to the ARSystem directory. The upgrade then proceeds like a fresh installation. The backup might complete or fail at times, depending on which you may need to perform additional tasks in case of failure.

Review this section if you are

Review this section if you are

This section provides information about the forms into which BMC Software loads new or modified data and about the ARX files.

For BMC Remedy ITSM Suite 7.6.04 and later, the ARX files have been consolidated to improve installer performance.

As of BMC Remedy ITSM Suite 7.6.04, the field deletion driver scripts have been changed, and fields are now deleted using the Cascade option. This option not only deletes referenced fields, but it also deletes all associated fields in all join forms.

If you customized the BMC Remedy ITSM suite,

before you start the upgrade.

If you are using DB2,

• To install the update later, after the upgrade finishes (the installer gives this option if your environment has more than 20 million records)
• To run the multi-tenancy updates against the migrated delta data
• To restart the update utility, if data errors cause the utility to stop running (you must troubleshoot the data errors before restarting the update utility)

The update to the multi-tenancy model is not supported if BMC Service Request Management is installed by itself as a stand-alone product or if BMC Service Request Management is installed on a mixed-version stack. 

 The multi-tenancy update utility is integrated with the BMC Remedy IT Service Management suite and application installers. You can also start the multi-tenancy update utility manually in the following situations:

• To install the update later, after the upgrade finishes (the installer gives this option if your environment has more than 20 million records)
• To run the multi-tenancy updates against the migrated delta data
• To restart the update utility, if data errors cause the utility to stop running (you must troubleshoot the data errors before restarting the update utility)

When upgrading from BMC Service Request Management 7.6.04 to 8.1.00, you must reconcile the custom advanced interface form (AIF) workflows.

Importing data from BMC Service Request Management versions earlier than 7.6.03 directly into BMC Service Request Management 8.1.00 is not supported.

To export BMC Service Request Management data from versions earlier than 7.6.03, you must first upgrade the application to BMC Service Request Management 7.6.03 (or later). You can then export the data from that system and import it to a BMC Service Request Management 8.1.00 system.

You must rebuild your customizations before you can delete all of the BMC Remedy ITSM suite attributes from the BMC Atrium CMDB while performing an upgrade.

Update overlays on the staging server for overlaid objects that were changed during the upgrades.

1. Use BMC Remedy Migrator to compare overlaid objects on the staging and primary servers. Create a list of objects that were changed.
2. Use one copy of BMC Remedy Migrator with this list to compare overlaid objects on the staging and primary servers.
3. Use one copy of BMC Remedy Migrator with this list to compare overlays to overlaid objects on the reference server.
4. Using differences in the copies of BMC Remedy Migrator, either delete the overlay or modify it on the staging server.

Perform feature and functionality validation and performance testing.

Restore the backed up upgraded staging server database after the testing is complete.

Perform any required changes based on issues found in testing.

• You must have administrator privileges for the machine on which you are installing BMC Remedy Migrator. You must install BMC Remedy Migrator 8.1 and the latest binary fix to perform the full migration.
• Always download and install the latest BMC Remedy Migrator version available when you are migrating delta data.

• Use the same Admin user account to log in to both servers.
• You can run the Delta Data Migration tool one time or multiple times. BMC recommends that you run the tool at least twice: once before you start your production outage, and again after the production outage begins.

• Use the same Admin user account to log in to both servers.
• You can run the Delta Data Migration tool one time or multiple times. BMC recommends that you run the tool at least twice: once before you start your production outage, and again after the production outage begins.

For known and corrected issues, see

For troubleshooting tips, see

For logging information, see

For error message description, see

For known and corrected issues, see

and

For troubleshooting tips, see

For logging information, see

For error message description, see

For known and corrected issues, see

For troubleshooting tips, see

For logging information, see

For error message description, see

For known and corrected issues, see

For troubleshooting tips, see

For logging information, see

For known and corrected issues, see

For troubleshooting tips, see

For logging information, see