Unsupported content This version of the product has reached end of support. The documentation is available for your convenience. However, you must be logged in to access it. You will not be able to leave comments.

Upgrade considerations

This section lists items for you to take into consideration as you plan your upgrade to version 4.x or the latest service pack.

Note

BMC Cloud Lifecycle Management uses specific field IDs in the BMC Cloud Lifecycle Management Portal applications and the CMDB extension forms. If you created custom fields as part of your customizations with these same field IDs and you try to upgrade or apply an extension, the upgrade will fail. See Updating-customer-range-field-IDs to run a new utility that connects to the AR System server, detects all fields provided by BMC that are in the Customer ID range and resets the IDs for those fields.

Execute DDM before you migrate data – Staged upgrades only

With Staged upgrades, always execute DDM before you run migration. If you execute DDM on top of migrated data in your staged environment, you corrupt the upgraded system. 

DDM is not required for In-Place upgrades. 


Flushing cache after upgrades

When you finish upgrading, inform your user community to flush the cache on their browsers. Otherwise, they run the risk of seeing a confused mix of old and new functionality in their browsers. 

Changing deployment types

When you upgrade your current environment by adding products from previous environments, you can upsize the deployment type. For example, if you installed a Small deployment type, you can change the deployment type to Medium when you add products to the version 4.x environment. For more information, see Changing-or-upsizing-deployment-types.


Oracle database migration error during BMC Server Automation Linux upgrade

Oracle is not able to execute the Oracle-supplied package DBMS_METADATA, which loads the XSL stylesheet data in the Oracle data dictionary when it runs. As a result, the Oracle migration fails with error message ORA-39212 unless you resolve the issue before you start the upgrade:

  1. Connect to the Oracle database with the following credentials:
    • User: SYS
    • Role: SYSDBA
  2. To reload the stylesheets, execute the following SQL command: SQL> exec dbms_metadata_util.load_stylesheets;
  3. Rerun the migration.

Upgrading with HTTP/SSL

If you plan to upgrade using HTTP/SSL with third-party SSL certificates, you have the following options.

  • Import RootCA.crt into Planner\Disk1\files\jre\lib\security\cacerts:

    Planner\Disk1\files\jre\bin\keytool.exe -import -alias root -keystore
    Planner\Disk1\files\jre\lib\security\cacerts -trustcacerts -file c:\keys\RootCA.crt
  • Copy the existing keystore to a different location. During the upgrade (for example, Platform Manager or CLM Self Check Monitor), select the Use Existing Certificate option and then provide the path to the keystore location along with the password details. 
    For example:
    CustomCACertificateConfiguration2.jpg 

 

Note

You do not need to perform this step if you upgrade using HTTP/SSL with self-signed certificates.

For more information, see Using-CLM-applications-with-third-party-Certification-Authority-certificates.

Installer skips SLM and ITSM, cannot upgrade TrueSight or ProactiveNet

In the 4.x release, the installer skips BMC IT Service Management and BMC Service Level Management during upgrade by default, thus reducing upgrade time significantly.

  • To upgrade BMC Remedy IT Service Management on an E-AR server, use the following command to launch the installer: setup.cmd -J skip_itsm=false 
    The command with this option can detect an older version of BMC Remedy IT Service Management, and then integrate and upgrade it as part of Enterprise-AR. n
  • To upgrade BMC Service Level Management, you must use the standalone installer from EPD. 

In addition, BMC Cloud Lifecycle Management no longer supports the installation or upgrade of TrueSight or BMC ProactiveNet products. If you install or upgrade TrueSight Infrastructure Management Server, BMC ProactiveNet Central Server, or BMC ProactiveNet Server, you must download the standalone installer from EPD and integrate them through Cloud Vista integration.

Using individual AO content installer causes upgrade to fail

Note that the installation of BMC Atrium Orchestrator content (not part of BMC Cloud Lifecycle Management stack) using the individual installer corrupts the AMREPO PlatformInstalledConfiguration.xml and ProductRegistry.xml files. This causes the upgrade installation to fail. Contact support for more information (reference defect QM001765785).

Compact deployment upgrade considerations

Note

When upgrading Compact Deployment, you upgrade one AR System server to one AR System server.  You must upgrade all products in the stack.

  • Make sure that you take snapshots of your VM when the installer prompts you. These snapshots are valuable if you encounter an error during the upgrade. You can save an enormous amount of time by simply reverting to the saved snapshot, fixing the problem, and then continuing with the upgrade. 
  • Do not run the installer on the Compact Deployment host where you upgrade the products; use a separate VM. You can recover this VM later, after you finish the upgrade.
  • If you used this VM to install earlier versions of BMC Cloud Lifecycle Management, perform the following tasks before you run the upgrade.
    1. Uninstall the install planner.
    2. Back up or delete the C:\Windows\ProductRegistry.xml file.
    3. Delete %temp% files.
  • Review the known and corrected installation issues to avoid potential problems during upgrade.
  • Accept the default values in the installer unless you have a good reason to change them.
  • On-board at least one tenant in BMC Cloud Lifecycle Management before you start upgrading. 
  • If you want to onboard existing VMs or if you have already onboarded VMs, any service offerings that you want to use or have already used for the VM must include a requestable offering.

BMC Server Automation upgrade considerations

To ensure that you do not lose valuable data (for example, MaxHeapSize or any other customized settings) after the upgrade, you must back up the C:\Program Files\BMC Software\BladeLogic\RSCD\daal (Windows) or /opt/bmc/bladeLogic/rscd/daal (Linux) folders. You will use this information after you finish the upgrade to manually configure the settings. 

What issues do I face when I upgrade from a particular version?

Depending on what version of CLM you start with, you face specific issues. 

Upgrade considerations for BMC Cloud Lifecycle Management version 2.1.x


Note

You cannot upgrade directly from 2.1.x to 4.5.00. If you are starting with 2.1.x, first upgrade your environment to 4.1, as described in Upgrade considerations for BMC Cloud Lifecycle Management version 2.1.xin the 4.1.00 documentation. Then upgrade your environment to 4.5.00.


Upgrade considerations for BMC Cloud Lifecycle Management version 3.x

Note

  • When upgrading from 3.x, you upgrade two AR System servers to two AR System servers.
  • If you are upgrading Small or Medium Deployments, the planner cannot integrate the environment if Enterprise-AR and the Mid Tier are the same hostname. The planner expects that the Mid Tier is running on a separate host.
    Do not enter the Enterprise-AR host name in the AR System Mid-Tier field when you fill out the Host Information panel but leave the field empty. The planner then internally upgrades the Mid Tier that is running on the Enterprise-AR server, along with all the other components.


If you are upgrading from 3.x, review the following considerations for your upgrade strategy. 

Upgrade strategy

Considerations

Notes

 

  1. Complete all the prerequisites for the upgrade.
  2. Upgrade Zone 1 products.
  3. Create Zone 2 staging servers.
  4. Upgrade Zone 2 products. 
  5. Prepare for DDM.
  6. Run Live DDM.
  7. Run Final DDM.
  8. After DDM, perform data migration:
    1. Prepare for data migration.
    2. Prepare for 2.1.x migration.
    3. Migrate your data.
  9. Perform post-upgrade configuration.

For a helpful overall view of the Staging upgrade process, see 3-x-Staging-upgrade-process-flow-chart.

  1. Complete all the prerequisites for the upgrade.
  2. Upgrade all products in the solution. 
  3. Perform delta data migration.
  4. After upgrade, perform data migration:
    1. Prepare for data migration.
    2. Migrate your data.
  5. Perform post-upgrade configuration.

Use Staged-Lite upgrade strategy only for HA environments.


Upgrade considerations for BMC Cloud Lifecycle Management version 4.x

Note

  • When upgrading from 4.x, you upgrade one AR System server to one AR System server.
  • If you are upgrading Small or Medium Deployments, the planner cannot integrate the environment if Enterprise-AR and the Mid Tier are the same host name. The planner expects that the Mid Tier is running on a separate host.
    Do not enter the Enterprise-AR host name in the AR System Mid-Tier field when you fill out the Host Information panel but leave the field empty. The planner then internally upgrades the Mid Tier that is running on the Enterprise-AR server, along with all the other components.

If you are upgrading from 4.x, review the following considerations for your upgrade strategy. 

Upgrade strategy

Considerations

Notes

  1. Complete all the prerequisites for the upgrade.
  2. Upgrade all products in the solution. 
  3. After upgrade, perform data migration.
  4. Perform post-upgrade configuration.

When upgrading to 4.x, the migration prerequisite steps are now performed automatically by the installer.

  1. Complete all the prerequisites for the upgrade.
  2. Upgrade all products in the solution. 
  3. Prepare for DDM.
  4. Run Live DDM.
  5. Run Final DDM.
  6. After DDM, perform data migration:
  7. Perform post-upgrade configuration.
  • When upgrading to 4.x, the migration prerequisite steps are now performed automatically by the installer.
  • For a helpful overall view of the Staging upgrade process, see _4-1-x-Staging-upgrade-process-flow-chart.
  1. Complete all the prerequisites for the upgrade.
  2. Upgrade all products in the solution. 
  3. Perform delta data migration.
  4. Perform data migration:
  5. Perform post-upgrade configuration.
  • When upgrading to 4.x, the migration prerequisite steps are now performed automatically by the installer.
  • Use Staged-Lite upgrade strategy only for HA environments.


Back to top



BMC Remedy ITSM upgrade recommendations for pre-4.5 versions of BMC Cloud Lifecycle Management

Before you start your upgrade from a pre-4.5 version of BMC Cloud Lifecycle Management, the BMC Remedy ITSM application contains forms that you must clean out and at least one filter that you must disable. Otherwise, you run into timeout errors, installation failures, and other serious problems with the upgrade. Specific recommendations for ITSM include:

  1. Stop or disable the reconciliation jobs. 
  2. Disable the INT:ASIFND:ACT:UPDATEGROUPLIST_105_AST filter, if it exists.
  3. Archive or purge the data in the SYS:Action form. 

For a complete list of upgrade recommendations, see BMC-Remedy-ITSM-upgrade-recommendations.

Upgrade considerations for third-party providers


When you upgrade to BMC Cloud Lifecycle Management 4.5.00, ensure that you upgrade or use the compatible version of the corresponding third-party party provider such as Azure, OpenStack, or SoftLayer. During upgrade, some of the configuration files, which are used by the providers are overwritten. As a result, onboarded LDCs might become inaccessible.

For details about third-party provider compatibilty with BMC Cloud Lifecycle Management, see the following BMC Communities bog posts:

For troubleshooting tips, see BMC-ZipKits-for-Cloud-issues.


Preserving customization after upgrade

If you made extensive customizations to your production environment and want to preserve them, you must plan the upgrade accordingly. During upgrade, some but not all production configuration files are preserved.   

After you upgrade the AR System Server on both Enterprise-AR and Cloud-AR, see Creating-overlays-with-BPCU-for-existing-customizations to create overlays before you continue the upgrade. 

Finally, you might have customized one or several components in the solution to suit your business needs (for example, the Network Automation API). You must decide whether to replace your customizations or port them.

Backward compatibility of products in Zone 1 and Zone 2

BMC Cloud Lifecycle Management component products are categorized as backward compatible (Zone 1) or non-backward compatible (Zone 2). This topic explains your options when you decide to upgrade to 4.x. 

You must upgrade the products in the solution based on their backward compatibility. This means that when you upgrade a product to the latest version in the solution, that product will continue to be compatible with other products of the older version. For example, if you upgrade BMC Server Automation to version 8.5.00, it will continue to work with BMC Cloud Lifecycle Management 4.x. The upgraded BMC Server Automation product would not have any impact on the solution production environment.

4.x products

Recommendations

Zone 1 (Backward compatible products):

  • BMC Server Automation
  • BMC Network Automation
  • BMC Capacity Optimization (not included in BMC Cloud Lifecycle Management)

Because the products in Zone 1 are backward compatible, you can perform the upgrade in separate periods of maintenance time, or you can upgrade them all in the same maintenance period. An upgraded Zone 1 product will continue to work with other non-upgraded products in this zone, even if not all products are upgraded in the same maintenance period.

BMC recommends that you upgrade Zone 1 products in the production environment (in-place).

Zone 2 (Non-backward compatible products):

  • BMC Remedy AR System - Cloud Portal and Database (Enterprise-AR)
  • Cloud Platform Manager
  • BMC Atrium Orchestrator—Platform
  • BMC Atrium Orchestrator—Content

Upgrade products in Zone 2 only after you have completed the upgrade for Zone 1 products.

Because the products in Zone 2 are not backward compatible, you must upgrade these products in one maintenance period. If you upgrade one product in this zone and try to continue using the 2.1.x environment, the BMC Cloud Lifecycle Management solution will not work.

Because the time required to upgrade Zone 2 products is greater than the time to upgrade Zone 1 products, BMC recommends that you upgrade these products in a staging environment. Creating a staging environment and upgrading the products in that environment ensures that you are able to keep a 2.1.x environment running while you complete the upgrade process.

Back to top

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*