Prerequisites for upgrade


Before you upgrade your BMC Cloud Lifecycle Management solution to version 2.1, perform the following tasks:

  • Verify that all product host VMs are available. 

    Tip

    You should be able to access the host using Remote Desktop.

    Back up product servers and databases so that, if you encounter errors during the upgrade process, you can restore your current environment.

  • Take snapshots of your VMs, so that you are able to revert to an earlier working snapshot.
  • Remove load balancers.
  • Update Distributed Server Option (DSO) information for BMC Remedy Action Request (AR) System server and BMC Remedy IT Service Management (ITSM) Suite -- Primary or BMC Remedy AR System server -- Cloud Database -- Primary products.

To create backups and snapshots

  1. From the host on which you installed Platform Manager,back up the Platform_Manager folder.
  2. From the host on which you installed the preboot executable environment (PXE) server, back up the TFTP folder.
     This folder is deleted on the target machine during the upgrade process.
  3. Before you upgrade PXE server, back up your data store 

    Note

    Make sure that you specify the correct data store location.

  4. For all products that you want to upgrade in the solution:
    1. Take a snapshot of the host on which you installed the product.
    2. Back up the product database, if one exists.
       For example, for BMC Atrium Core - Web Registry components, take a snapshot of the host on which you installed the web registry and back up the BMC Atrium Core Web Service database.

To remove the load balancer setting for BMC Remedy AR System Server

Note

Before you install the AR Extension, you must remove the load balancer setting for BMC Remedy AR System Server.

  1. Go to ARSystemserverInstallationdirectory\Config.
  2. Open the ar.config file and remove the following entries: 


    Server-Connect-Name: vw-pun-cdl-qa12.bmc.com
    Map-IP-Address: 10.128.253.183 10.128.105.209
    Map-IP-Address: 10.128.106.166 10.128.105.209
  3. In the ar.config file, set the Server-Name parameter to the local host on which you installed the BMC Remedy AR System server and BMC Remedy ITSM Suite -- Primary.

Update Distributed Server Option information

If you are using a load balancer in your environment, perform the following steps to update the distributed server option (DSO) information for BMC Remedy Action Request (AR) System server and BMC Remedy IT Service Management (ITSM) Suite -- Primary or BMC Remedy AR System server -- Cloud Database -- Primary products.

  1. In a web browser, open the BMC Remedy User client.
  2. Go to AR System Administration Console > System > General > Server Information > Connection Settings tab.
  3. In the Plugin Server Settings table, reset Server Name to the local host name on which you installed the cloud database.
  4. Click the Configuration tab.
  5. Clear the Server Group Member box.

Note

Restart the BMC Remedy Action Request System Server service on both hosts after you remove the load balancer and change the DSO information.

Prerequisites for the BMC Remedy AR System Server and BMC Remedy ITSM Suite

Before you upgrade the BMC Remedy AR System Server and BMC Remedy ITSM Suite host, add the BMC Remedy AR System server host name information in the AIS Global Preference form.

  1. Open the AIS Global Preferences form, using the following link:
    http://\* (http://*)midTierHost{}:8080/arsys/forms/{}arSystemServerhost{}/AIS:GlobalPreferences.
  2. Create an entry for the BMC Remedy AR System Server and BMC Remedy ITSM Suite host name in fully qualified domain name format.

Prerequisites for BMC ProactiveNet and Performance Manager

Perform the following steps while upgrading BMC ProactiveNet and the BMC ProactiveNet Data Collection Host in the BMC Cloud Lifecycle Management environment.

  1. Ensure that all the BMC ProactiveNet servers and the BMC ProactiveNet Data Collection Host systems with domain names can be pinged by one another.
  2. If the BMC BladeLogic database and the BMC BladeLogic Application  Server reside on different systems, ensure that they are synchronized.

Note

    
 Upgrade of BMC ProactiveNet version 8.6.01 (a version of the product which was released to a limited number of customers) to version 8.6.02 for a Proof of Concept deployment is not supported.

For fixing issues with the BMC ProactiveNet and Performance Manager upgrade, see Upgrade-issues-with-BMC-ProactiveNet-Performance-Management.

 

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