This topic explains the process for upgrading products from BMC Cloud Lifecycle Management 2.1.x or 3.0.x to 3.1.x (including the latest service pack). For a visual representation of the upgrade process, see the flow diagram in Upgrade-options.
Important
The procedures described in the following topics apply to upgrading to version 3.1 or upgrading to the latest version 3.1 service pack, unless otherwise specified.
The following topics are covered in this section:
Before you begin
Before you start the upgrade process, ensure that you review the following details:
- You can perform this process for multiple deployment environments, such as for development, quality assurance, and production.
- You can upgrade all products in the BMC Cloud Lifecycle Management solution except the BMC Capacity Optimizer product, which is not a part of BMC Cloud Lifecycle Management.
- Before starting the data migration ensure that all host VMs or physical machines on which you installed BMC Cloud Lifecycle Management are available.
Summary of the upgrade
Based on the time and resources you have available for the upgrade, plan to use an in-place, staged, or staged lite approach for your upgrade. For details about these types of upgrades, see Upgrade-options. The following table summarizes the activities you must follow for each type of upgrade.
| |
|---|
| - Verify all pre-requisites are met.
- Integrate all BMC Cloud Lifecycle Management components using the Installation Planner and start the upgrade.
- Migrate your data.
|
| - Verify all pre-requisites are met.
- Obtain the resources required for creating a staging environment.
- Integrate and upgrade Zone 1 products using the Installation Planner.
- Perform sanity testing.
- Create the staging environment for Zone 2 components (a replication of your production environment).
- Perform sanity testing if the staging environment is functioning properly.
- For High Availability components, reconfigure the cluster on each node to run the clusters only on one node.
- Integrate and upgrade staged components using the Installation Planner.
- Migrate your data.
- Perform sanity testing.
- Perform delta data migration.
- Put the staging environment into production.
|
| - Verify all pre-requisites are met.
- Obtain the resources required for creating a staging environment.
- Integrate and upgrade Zone 1 products using the Installation Planner.
- Perform sanity testing.
- Create the staging environment for Zone 2 components, using a new node or existing primary nodes of each component. If you use secondary nodes for this step for the AR System and the Cloud AR System Extensions components, you must modify your upgrade of those components with the following steps:
- Before upgrading the Cloud AR System Extensions in the staging environment, in the ARSystemInstalledConfiguration.xml file change the BMC_IMPORT_NO_SCHEMA parameter to 0.
- Cloud AR System Extensions cannot be upgraded on secondary nodes, since there is no BMCCloudLifeCycleManagement directory on the Cloud AR System Extensions machine. Copy that folder and the ProductRegistry.xml and ProductRegistry.xsd files from the primary server to the secondary server before upgrading.
- Just before starting the AR System upgrade, in the ARSystem-ini-template.txt file change the –J BMC_IMPORT_NO_SCHEMA option to 0.
- For High Availability components, reconfigure the cluster on each node to run the clusters only on one node.
- Perform sanity testing if the staging environment is functioning properly for each component.
- Integrate and upgrade staged components using the Installation Planner.
- Migrate your data.
- Perform sanity testing.
- Move primary nodes of Zone 2 components to the staging environment by directing them to the Database on the staging environment.
- Integrate and upgrade newly added nodes in the staging environment.
- Perform delta data migration.
- Put the staging environment into production.
|
Where to go from here
Upgrading-BMC-Cloud-Lifecycle-Management