In-Place upgrade

This section provides a high-level overview on how to adopt the In-Place strategy to upgrade products in the production environment. This upgrade requires minimal additional hardware and other resources. You can spread the upgrade across several periods of maintenance time and there is no need to track data changes during the upgrade process. However, the production environment needs downtime. 

After you upgrade the products using the BMC Cloud Lifecycle Management installer, you might need to perform manual tasks, such as migrating a database, for certain products to complete the upgrade. To complete upgrading products in zone 1, complete the following tasks:

See the following BMC Communities video (8:01) about best practices for upgrading BMC Cloud Lifecycle Management in a production environment using the in-place approach.

Before you begin

  • If you are running an environment with two AR System servers (Enterprise-AR and Cloud-AR), use the 2AR1AR utility to merge the servers into one AR System server before you start the upgrade. For more information, see Merging two AR System servers into one AR System server.
  • Update the customer range field IDs before you start upgrading. Otherwise, the upgrade will likely fail.
  • Do not run the installer on the same VM where you install the products; use a separate VM. You can recover this VM later, after you finish the cloud installation.
  • If you used the same 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.
  • On Windows hosts, delete old files from the C:\Windows\Temp folder.
  • Accept the default values in the installer unless you have a good reason to change them.
  • Do not mix IP addresses and hostnames during product select in the Host Information panel. Enter all IP addresses or all hostnames, but do not combine them.
  • Some special characters create problems during installation. For more information, see Restricting the use of certain characters in passwords.
    • For BMC Network Automation, do not use special characters except _
    • For BMC Server Automation, do not use #
  • 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. 
  • Review the known and corrected installation issues to avoid potential problems during upgrade.
  • Prepare the installation environment. For example, delete all the files from the C:\Windows\Temp folder, make sure that the installer can connect to all the targets, and so on.
  • TrueSight and BMC ProactiveNet products is not supported in version 4.5 or later and cannot be upgraded with the install planner. You must use the standalone installer to manually upgrade TrueSight or BMC ProactiveNet; you can download the installation files from EPD with assistance from BMC Customer Support. 
  • Before you upgrade BMC Remedy IT Service Management Suite, review the CPU and RAM recommendations on the BMC Remedy IT Service Management documentation portal. 
  • 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.
  • If you plan to upgrade Platform Manager using HTTPS/SSL with third-party certificates, import RootCA.crt into the Planner JRE (for example, <Planner_Install_Directory>\Planner\windows\Disk1\files\jre\lib\security).

To use the In-Place strategy to upgrade products in a production environment

  1. Review the appropriate upgrade requirements in Preparing for upgrades.
  2. Take a snapshots of your VM or backup your physical machine on which the product is installed.
  3. Take a database backup of the product itself and back up the databases.
  4. Put the BMC Cloud Lifecycle Management production environment in maintenance mode.
  5. Copy the BMC Cloud Lifecycle Management installer on the installer host.
  6. Make sure that there are no processes running and that the BMC BladeLogic Remote System Call Daemon (RSCD) Agent default port is not blocked on the target host.
  7. Launch the BMC Cloud Lifecycle Management installer and integrate the products.
  8. Upgrade the products in the following order:
    1. BMC Server Automation
    2. Atrium Orchestrator - CDP
    3. Enterprise-AR and Cloud-AR
    4. Mid Tier
    5. BMC Atrium Core - Web Registry Components
    6. BMC Network Automation
    7. Cloud Database Extensions
    8. Cloud Platform Manager
    9. Cloud Portal AR Extensions
    10. CLM Portal Web Application
    11. CLM Self-Check Monitor
  9. Run data migration.

  10. (BMC Server Automation onlyPerform the manual tasks required to complete the upgrade.

Where to go from here

End-to-end upgrade process - In-Place strategy

Was this page helpful? Yes No Submitting... Thank you