×
 
 
  •  
$helper.renderConfluenceMacro('{bmc-global-announcement:$space.key}')

Unsupported content

 

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.
BMC Cloud Lifecycle Management 3.1 ... Upgrading Preparing for upgrade

Upgrade sequence

When you launch the BMC Cloud Lifecycle Management installer to upgrade the products in the solution, host names are displayed for each product. BMC recommends that you select only one product at at time to upgrade, based on the sequences in the following section:

The sequences in the tables include products from both the Control Tier and Workload Tier. In an upgrade scenario, the emphasis is more on the upgrade order instead of on available products within a tier.

Before you begin

Before you start upgrading the products, make sure that you review the upgrade prerequisites. Because not all products are available in each of the deployment types, the upgrade order that you must follow depends on the deployment type that you chose.

Note

Because you can upgrade to BMC Cloud Lifecycle Management 3.1 from two different paths: 2.1 and 3.0, the products to upgrade and the upgrade steps might differ. Therefore, you must carefully review the information documented in the prerequisites for the upgrade topic. For upgrading to 3.1 SP1, see Preupgrade tasks.

Upgrade sequence for POC deployments

The upgrade order listed in the following table applies to the proof of concept (POC) deployment type.

Order for upgrade for POC deployments

Unknown macro: {multi-excerpt}

Upgrade sequence for Small, Medium, and Large deployments

The upgrade order listed in the following table applies to the Small, Medium, and Large deployment types. To learn more about which deployment type works best for your requirements, see deployment architecture. This sequence applies to all upgrade methods: in-place, staged, and staged-lite.

Order for upgrade for Small, Medium, and Large deployments

Sequence

Product

Order of tasks for upgrade

1

BMC Server Automation – File Server

No manual tasks required for this product. Directly upgrade to 3.1 using the BMC Cloud Lifecycle Management Solution Installer.

2

BMC Server Automation – Application Server & Console

  1. Shut down the appserver and spawner service before you start the upgrade on BMC Server Automation – Application Server & Console:
    • On Linux, type the following command:
      /etc/init.d/blappserv stop, /etc/init.d/blprocserv stop
    • On Windows, stop the services by using the services.msc.
  2. Stop the PXE server, BMC Server Automation – Multiple Application Server (MAS), and BMC Server Automation – Advanced Repeater services, if available. 
  3. Upgrade the following components in order using the BMC Cloud Lifecycle Management Solution Installer:
    1. BMC Server Automation Application Server
    2. BMC Server Automation Console
  4. Manually perform BMC Server Automation database migration.
  5. Complete the BMC Server Automation post-upgrade configuration in the installer.
  6. Manually upgrade the Virtual Center (VC) agent.
  7. Manually upgrade the BMC RSCD Agent on the source VM Template.
    After upgrading the RSCD Agent, ensure that the Exports file mappings are appropriately configured.

3

BMC Server Automation – (MAS)

  1. Upgrade BMC Server Automation – Application Server.
  2. Perform post-installation configuration tasks after the upgrade.

4

(Optional) PXE server

  • Upgrade the PXE server only after you have upgraded all application servers.
  • On Windows, make a backup copy of the TFTP folder, which is located in the <PXE Server Installation directory>. During the 3.1 upgrade, the PXE server uninstalls the existing TFTP folder before installing the latest version.

5

(Optional) BMC Server Automation – Advanced Repeater

No manual tasks required for this product. Directly upgrade to 3.1 using the BMC Cloud Lifecycle Management Solution Installer.

6

BMC ProactiveNet Central Server

  • If you installed BMC ProactiveNet Performance Management 8.6.02 using the BMC Cloud Lifecycle Management Solution 3.0 installer, you can directly upgrade to BMC ProactiveNet 9.0 using the using the BMC Cloud Lifecycle Management Solution 3.1 installer.

    However, if you installed BMC ProactiveNet Performance Management Enterprise license or if you installed BMC ProactiveNet using the standalone installer, you must first manually apply BMC ProactiveNet Performance Management 8.6. SP2 and then manually upgrade to version 9.0.

  • If you recieve any port errors during the upgrade, see the Upgrade issues with BMC ProactiveNet Performance Management topic.

7

BMC ProactiveNet Server

  • If you installed BMC ProactiveNet Performance Management 8.6.02 using the BMC Cloud Lifecycle Management Solution 3.0 installer, you can directly upgrade to BMC ProactiveNet 9.0 using the using the BMC Cloud Lifecycle Management Solution 3.1 installer.

    However, if you installed BMC ProactiveNet Performance Management Enterprise license or if you installed BMC ProactiveNet using the standalone installer, you must first manually apply BMC ProactiveNet Performance Management 8.6. SP2 and then manually upgrade to version 9.0.

  • If you recieve any port errors during the upgrade, see the Upgrade issues with BMC ProactiveNet Performance Management topic.

8

BMC ProactiveNet Data Collection Host

  • If you installed BMC ProactiveNet Performance Management 8.6.02 using the BMC Cloud Lifecycle Management Solution 3.0 installer, you can directly upgrade to BMC ProactiveNet 9.0 using the using the BMC Cloud Lifecycle Management Solution 3.1 installer.

    However, if you installed BMC ProactiveNet Performance Management Enterprise license or if you installed BMC ProactiveNet using the standalone installer, you must first manually apply BMC ProactiveNet Performance Management 8.6. SP2 and then manually upgrade to version 9.0.

  • If you recieve any port errors during the upgrade, see the Upgrade issues with BMC ProactiveNet Performance Management topic.

9

BMC Atrium Orchestrator – Configuration Distribution Peer

Perform the following steps for BMC Atrium Orchestrator – Configuration Distribution Peer when upgrading BMC Cloud Lifecycle Management from version 2.1 to 3.1:

  1. Upgrade the following components in this order using the BMC Cloud Lifecycle Management Solution Installer:
    1. Access Manager and Repository
    2. Configuration Distribution Peer
    3. Atrium Orchestrator Content 
    4. RCP Client
  2. Manually activate the BMC Atrium Orchestrator adapters.
  3. Stop the HACDP service before you start the upgrade on BMC Atrium Orchestrator – Configuration Distribution Peer.
    Perform the following steps for BMC Atrium Orchestrator – Configuration Distribution Peer when upgrading BMC Cloud Lifecycle Management from version 3.0 to 3.1:
  4. Upgrade the following components in this order using the BMC Cloud Lifecycle Management Solution Installer:
    1. Atrium Orchestrator Content 
    2. BMC Server Automation Console
  5. Manually activate the BMC Atrium Orchestrator adapters.
  6. Stop the HACDP service before you start the upgrade on BMC Atrium Orchestrator – Configuration Distribution Peer.

10

Atrium Orchestrator – Configuration Distribution Peer for High Availability (HA)

  1. Upgrade the BMC Server Automation Console.
  2. Upgrade the Configuration Distribution Peer.

11

BMC AR System & BMC Remedy IT Service Management Suite – Primary

Note: Before you start the upgrade, review Known issues [defect QM001778426] for possible issues.

  1. Remove server group settings on BMC Remedy AR System & BMC Remedy IT Service Management Suite Primary and Secondary servers.
  2. Restart the BMC Remedy AR System & BMC Remedy IT Service Management Suite Primary and Secondary servers.
  3. Upgrade the following BMC Remedy AR System & BMC Remedy IT Service Management Suite components in this order using the BMC Cloud Lifecycle Management Solution Installer:
    1. AR System server
    2. BMC Atrium Core
    3. Atrium Integrator
    4. BMC Remedy ITSM, if it exists in the 2.1 or 2.1 SPx implementation
    5. BMC Remedy Service Request Management
    6. BMC Remedy Service Level Management, if it exists in the 2.1 or 2.1 SPx implementation
  4. Perform the post-upgrade configuration steps for the AR System server using the installer.
  5. Perform DSO mapping using the installer.

12

BMC Remedy AR System Cloud Database – Primary
Note: Before you start the upgrade, review Known issues [defect QM001764172] for possible issues.

  1. Remove server group settings on BMC Remedy AR System Cloud Database – Primary and Secondary servers.
  2. Restart the BMC Remedy AR System Cloud Database – Primary and Secondary servers.
  3. Upgrade the following BMC Remedy AR System & BMC Remedy IT Service Management Suite components in this order using the BMC Cloud Lifecycle Management Solution Installer:
    1. AR System server
    2. Atrium Core
  4. Perform the post-upgrade configuration steps for the AR System server using the installer.
  5. Perform DSO mapping using the installer.

13

BMC AR System & BMC Remedy IT Service Management Suite – Secondary
Note: Before you start the upgrade, review Known issues [defect QM001764172] for possible issues.

  1. Remove server group settings on BMC Remedy AR System & BMC Remedy IT Service Management Suite Primary and Secondary servers.
  2. Restart the BMC Remedy AR System & BMC Remedy IT Service Management Suite Primary and Secondary servers.
  3. Upgrade the following BMC Remedy AR System & BMC Remedy IT Service Management Suite components in this order using the BMC Cloud Lifecycle Management Solution Installer:
    1. AR System server
    2. Atrium Core
    3. Atrium Integrator
    4. BMC Remedy ITSM, if it exists in the 2.1 or 2.1 SPx implementation
    5. BMC Remedy Service Request Management
    6. BMC Remedy Service Level Management, if it exists in the 2.1 or 2.1 SPx implementation
  4. Perform the post-upgrade configuration steps for the AR System server using the installer.

14

BMC Remedy AR System Cloud Database – Secondary
Note: Before you start the upgrade, review Known issues [defect QM001764172] for possible issues.

  1. Remove server group settings on BMC Remedy AR System Cloud Database – Primary and Secondary servers.
  2. Restart the BMC Remedy AR System Cloud Database – Primary and Secondary servers.
  3. Upgrade the following BMC Remedy AR System & BMC Remedy IT Service Management Suite components in this order using the BMC Cloud Lifecycle Management Solution Installer:
    1. AR System server
    2. Atrium Core
  4. Perform the post-upgrade configuration steps for the AR System server using the installer.

15

BMC Remedy Mid Tier

No manual tasks required for this product. Directly upgrade to 3.1 using the BMC Cloud Lifecycle Management Solution Installer.

16

BMC Atrium Core – Web Registry Components

No manual tasks required for this product. Directly upgrade to 3.1 using the BMC Cloud Lifecycle Management Solution Installer.

17

BMC Network Automation

Note: Upgrading the BMC Network Automation server in an HA environment is not supported by the BMC Cloud Lifecycle Management installer. Therefore, you must perform the upgrade using the BMC Network Automation product installer.

  1. Upgrade the BMC Network Automation – Primary server where the cluster and application service is active.
  2. Failover the cluster.
  3. In the silent.ini file, set the SKIP_DB_UPGRADE option to true. You use this option to skip the database update step on the secondary servers. For more information, see [running the installer in silent mode].
  4. Perform the upgrade using the BMC Network Automation product installer, see [preserving the application server database].

18

(Optional) BMC Network Automation – Device Agent

No manual tasks required for this product. Directly upgrade to 3.1 using the BMC Cloud Lifecycle Management Solution Installer.

19

Cloud Database Extensions

No manual tasks required for this product. Directly upgrade to 3.1 using the BMC Cloud Lifecycle Management Solution Installer.

20

Cloud Platform Manager

If you have installed Cloud Platform Manager in an HA environment, you need to upgrade only the Cloud Platform Manager – Primary server.

21

Cloud Portal AR Extensions – Primary

Upgrade the following Cloud Portal AR Extensions components in this order using the BMC Cloud Lifecycle Management Solution Installer:

  1. Cloud Portal AR Extensions – Primary.
  2. Using the Cloud Upgrade Migration option in the installer, migrate the BMC Cloud Lifecycle Management data.
    Note: Make sure that you have your Cloud administrator credentials ready before you begin the Cloud upgrade migration using the installer.

22

Cloud Portal AR Extensions – Secondary

No manual tasks required for this product. Directly upgrade to 3.1 using the BMC Cloud Lifecycle Management Solution Installer.

Where to go next

Product versions and compatibility

Was this page helpful? Yes No Submitting... Thank you
Last modified by John Stamps on May 01, 2014
service_pack1

Comments

Log in or register to comment.

Prerequisites for upgrade
Product versions and compatibility
© Copyright 2024 BMC Software, Inc.
Legal notices

Powered by Atlassian Confluence and Scroll Viewport

© Copyright 2005-2024 BMC Software, Inc. Use of this site signifies your acceptance of BMC’s Terms of Use . BMC, the BMC logo, and other BMC marks are assets of BMC Software, Inc. These trademarks are registered and may be registered in the U.S. and in other countries.