Upgrading

The topics in this section provide information and instructions for upgrading the components of the BMC Server Automation system. The following table provides a high-level description of the process for upgrading components of the BMC Server Automation system and includes links to topics with detailed instructions.

The Related Knowledge Articles section includes links to Knowledge Articles from BMC Customer Support that may be of interest when upgrading.

Step Description Supporting topic
Prepare the environment for upgrade

Review the supported upgrade paths and upgrade considerations and perform the preliminary upgrade steps, such as shutting down the BMC Server Automation environment and backing up the installation directories for all Application Servers and PXE servers.

Preparing for upgrade 

Upgrade at least one Application Server

Do not restart the Application Server until you complete the database migration. Additional upgrades that occur at this point depend on where the Application Server resides:

  • On a Microsoft Windows computer, an upgrade of the Application Server also upgrades the Network Shell. 
  • On a Linux or UNIX computer, an upgrade of the Application Server also upgrades all components that were installed as part of the earlier installation of the Application Server. These components can include the Network Shell, the RSCD agent, and the PXE server.

Upgrading the Application Server on Windows

Upgrading the Application Server on Linux and UNIX

Upgrade BMC Server Automation Console Upgrade at least one BMC Server Automation Console. Upgrading the BMC Server Automation Console
Migrate the BMC Server Automation database to the current release

Run the Data Migration Manager using the version 8.3 external files to upgrade your Oracle or SQL Server database to version 8.2. 

Migrating core BMC Server Automation data and Migrating your database by using BMC BladeLogic Data Migration Manager

Upgrade the database to a service pack level compatible with the Application Server

If you are upgrading directly to an 8.2.x service pack level (later than 8.2.00), run the SQL scripts provided in the 82-<SP level>-SQL_Update_Scripts.zip file (where <SP level> can be one of the following values: SP1, SP2, SP2-P1, or SP3). This .zip file is available from the EPD. Run these scripts as the BMC Server Automation database owner (as provided to blasadmin), according to the instructions provided for your database type in the readme file in the .zip.

Running the SQL update scripts
Perform any related conditional steps

In the following upgrade scenarios you must run the postmigration (.exe or .sh) file to migrate various types of rules that were defined in the earlier version of BMC Server Automation:

  • If you are upgrading from a pre-8.0 version of BMC Server Automation, after you complete the basic migration of database data using the BMC BladeLogic Data Migration Manager, you must run the postmigration file. This file migrates the pre-8.x compliance rules and discovery signatures stored in the core BMC Server Automation database and converts them to the new rule format introduced in BMC Server Automation version 8.0.
  • If smart group conditions were defined in any earlier version of BMC Server Automation, you must run the postmigration file to migrate and update smart group conditions. This step eliminates future problems in database cleanup processes after you delete smart groups.
Migrating compliance rules and discovery signatures
Upgrade the BMC Server Automation provisioning system If you have upgraded the provisioning server (the Application Server enabled for provisioning), upgrade the components that BMC Server Automation uses in provisioning operating systems to bare metal machines.

Upgrading the Provisioning System.

Upgrading a PXE server on Windows

Upgrading a PXE server on Linux or UNIX

Upgrade additional components

Upgrade the other BMC Server Automation Application Servers, consoles, RSCD agents, and other components in your enterprise (including on any file servers or virtual servers). 

Note: If the BMC Server Automation file server resides on a different computer from the Application Server, upgrade the RSCD agent on the computer on which file server resides. The file server and the database must be at the same version before you run BMC Server Automation.

Upgrading the Network Shell or RSCD agents

Upgrading the file server 
Upgrade custom configuration objects

Upgrade any custom configuration objects that you have created and distributed.

Upgrading to a new release can potentially create mismatches between the version of a custom configuration object, an agent, and any model objects that reference custom configuration objects. For more information, see Upgrading custom configuration objects.
Upgrading custom configuration objects
Upgrade Compliance Content Perform an over-the-top installation of the new Compliance Content add-ons. Installing Compliance Content add-ons

Related Knowledge Articles

AMIGO Upgrade Program Introduction for BMC Server Automation environments (Knowledge Article ID: KA403108)

The AMIGO Upgrade Program is designed to assist you with the upgrade of BMC Server Automation environments. The process begins when you open an AMIGO Starter Issue and are provided with this document which contains a brief description of the process, a checklist of environmental information to capture and consider when planning your upgrade and links to other documents and manuals which will be helpful in performing your upgrade. The end result is for you to create a written Upgrade Plan which has been reviewed by BMC Support in advance of your upgrade.

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

Comments