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.

Preparing for upgrade

This topic provides the information you need to prepare your environment for the upgrade process. It includes information about supported upgrade paths and instructions for preparing to upgrade the BMC Server Automation system, in particular the Application Servers. When you upgrade the Application Server, you also generate many of the files needed to migrate data.

The topic includes the following sections:

Build information

The following table lists information for the most recent BMC Server Automation version 8.5 build.

Release

Build number

EPD version number

Release date

Patch 5 for Service Pack 18.5.01.3048.5.01.005April 23, 2015
Patch 4 for Service Pack 18.5.01.2608.5.01.004January 5, 2015
Patch 3 for Service Pack 18.5.01.2508.5.01.003December 10, 2014
Patch 2 for Service Pack 18.5.01.2318.5.01.002October 15, 2014
Patch 1 for Service Pack 18.5.01.2188.5.01.001September 2, 2014
Service Pack 18.5.01.0968.5.01July 7, 2014
Patch 2 for version 8.58.5.00.4698.5.00.002May 6, 2014
Patch 1 for version 8.58.5.00.4618.5.00.001April 11, 2014

Base version 8.5

8.5.00.416

8.5.00

February 25, 2014

Supported upgrade paths

The following figures illustrate the supported upgrade paths to the various BMC Server Automation 8.5.x versions:

     
     
     
     
     
     
     
     

    In the above diagrams, abbreviations are defined as follows:

    • BSA stands for BMC Server Automation
    • SP stands for Service Pack
    • P stands for Patch

    Upgrade considerations

    Note the following environment-specific information prior to preparing the environment for upgrade:

    Note

    These tasks should be performed in order. Many steps are prerequisites for other steps that occur later in the process.

    • BMC strongly recommends that you back up the database before performing database migration and post-migration tasks.
    • If your BMC Server Automation environment includes BMC BladeLogic Decision Support for Server Automation, upgrade BMC BladeLogic Decision Support for Server Automation before upgrading BMC Server Automation.
    • Prior to upgrading, review the following considerations.

    Item Description
    Upgrade to version 8.5 does not grant DBMS_LOCK privilege to user

    While upgrading from a previous version to BMC Server Automation 8.5, ensure that the BMC Server Automation user is granted the DBMS_LOCK privilege. This privilege is required for carrying out a handshake between BMC Server Automation database and the BMC BladeLogic Decision Support for Server Automation ETL during database clean up. You can use the SYS user to grant the DBMS_LOCK privilege by entering the following command:

    GRANT EXECUTE on DBMS_LOCK TO <User>;

    Upgrade to version 8.5 disables PropertySync

    In BMC Server Automation version 8.5, the PropertySync feature has been deprecated. During migration of the database to version 8.5, the Data Migration Manager disables PropertySync and the migration results table displays the migration warning: PropertySync has been changed from true to false. Please contact BMC Support for further assistance.

    Upgrade to version 8.5 deprecates the Provision provisionDevice BLCLI command. Earlier releases supported the Provision:provisionDevice command. This command has been deprecated. BMC recommends that you use the ProvisionJob:createProvisionJob command instead.

    Upgrade to version 8.5 causes Citrix XenServer Provision Jobs to fail

    After an upgrade from BMC Server Automation version 8.3 or earlier to BMC Server Automation version 8.5, existing Citrix XenServer Provision Jobs fail (QM001706976). Failed jobs display the error message:

    com.bladelogic.om.infra.mfw .util.BlException: Proxy cannot be null, Error: Proxy cannot be null

    To workaround the issue, open the Provision Job in the content editor. On the Server Settings panel, browse the Server Properties option to select or create a valid agentless managed object (AMO). For more information, see Panel reference for Provision Jobs.

    Audit performed with snapshots captured using earlier versions of the RSCD agent can fail When capturing data from target servers, version 8.5.00 of BMC Server Automation skips IPv6 addresses and masks. After an upgrade to version 8.5.00 from version 8.3 or earlier, an audit performed with snapshots captured using older versions of an RSCD agent can fail if the targets had IPv6 enabled.

    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. Therefore, as part of the upgrade process, you must distribute the latest versions of the custom configuration objects that are not included as part of an RSCD agent.  The  product installation is automatically upgraded to the appropriate version when you upgrade the agent. However, you must upgrade any custom configuration objects that are not included with the agent by running a Distribute Configuration Objects Job. Configure this job to target servers to which custom configuration objects need to be distributed. F or a list of those objects that are included as part of an agent installation and those that are not included with the agent and require distribution, see Custom configuration objects.

    Upgrading custom configuration objects

    1. Run an Update Server Properties Job on the agents you have upgraded. For more information, see Creating Update Server Properties Jobs.
    2. Run a Distribute Configuration Objects Job to distribute the latest version of custom configuration objects stored in the Configuration Object Dictionary. The job should target agents that you have upgraded. The system prevents you from distributing custom configuration objects to agents running an incompatible version. For more information, see Creating or modifying a Distribute Configuration Objects Job.
    3. If you are not upgrading all of your agents at this time, make copies of all component templates, BLPackages, Snapshot Jobs, and Audit Jobs that reference custom configuration objects that have dependencies on agents running earlier versions. You must maintain a version match between component templates, BLPackages, Snapshot Jobs, and Audit Jobs and custom configuration objects and agents. The objects that you copy in this step are the objects that you can use to maintain the version match.
    4. To ensure that all configuration-object-based assets within existing content are upgraded, run an Upgrade Model Objects Job that targets any component templates, BLPackages, Snapshot Jobs, or Audit jobs that you want to upgrade. For more information about the Upgrade Model Objects Job, see Creating or modifying Upgrade Model Objects Jobs.

      Note

      Do not run the Upgrade Model Objects Job against the copies of objects that you created in step 3.

      If you open an existing component template, BLPackage, Snapshot Job, or Audit Job that references a custom configuration object and a later version of that custom configuration object exists, the system displays a message saying it will automatically upgrade the referenced custom configuration object. To maintain a version match with an earlier agent, close the component template, BLPackage, Snapshot Job, or Audit Job without saving.

      After executing the Upgrade Model Objects Job, display the results of the job run to see which assets were successfully upgraded and which were not. If you find that certain assets were not automatically upgraded, you must upgrade them manually. Perform the following steps:

      1. Open the object (template, package, or job).
      2. Manually remove the asset of the earlier version and add the asset of the latest version.
      3. Save the object.

    Upgrading virtualization configuration objects

    The Upgrade Model Object Job is not supported for upgrading virtualization configuration objects.

    To upgrade configuration objects that you distributed in prior versions, complete the following steps:

    1. Import the new version of the virtualization configuration object (for example, the VMware vCenter configuration object).
    2. Restart the RSCD agent on which the configuration object is distributed. This step is a prerequisite for successful upgrade of the configuration object on the target server.
    3. Run the Distribute Configuration Objects Job to distribute the configuration objects to the target agent (see Distributing configuration objects).
    4. To identify the configuration objects that failed, run the Upgrade Model Objects Job on all jobs, templates, and BLPackages that reference the configuration object.
    5. After the Upgrade Model Objects Job completes, open the objects for which the job failed.
    6. Remove the parts that are marked as failed and add new ones from the upgraded configuration object.

    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. Therefore, as part of the upgrade process, you must distribute the latest versions of custom configuration objects for the custom configuration objects that are not included as part of an agent.  The  installation are automatically upgraded to the appropriate version when you upgrade the agent. (See Custom configuration objects for a list of those objects.) You should upgrade any custom configuration objects not included with the agent by running a Distribute Configuration Objects Job. The job should target servers to which custom configuration objects should be distributed.

    To prepare the environment for upgrade

    1. Back up the BMC Server Automation database. The data upgrade occurs in place. If, for any reason, it should become impossible to complete the upgrade, the only way to restore the database to its pre-upgrade state is from the backups.
    2. Shut down the BMC Server Automation environment:
      1. Stop the Application Server
      2. Stop the PXE server. See Starting and stopping a PXE server.
    3. Back up the installation directories for all Application Servers and PXE servers. Note that the user who installed the earlier version of the product might have changed the installation directory from the default location, so ensure that you have the right location. If your current installation is already an upgrade from a previous version, the paths might be different, due to differences in these locations in earlier versions of BMC Server Automation. If you do not know the installation location for BMC Server Automation components view the contents of the /usr/lib/rsc/HOME file (on Linux or UNIX) or the %WINDIR%\rsc\HOME file (on Windows).

      The default installation locations are:

      • Application Server
        • (Windows) C:\Program Files\BMC Software\BladeLogic\NSH
        • (UNIX) /opt/bmc/bladelogic/NSH
      • PXE Server
        • ((Windows) C:\Program Files\BMC Software\BladeLogic\PXE
        • (UNIX) /opt/bmc/bladelogic/NSH
        • If you are upgrading the PXE server, follow the upgrade instructions for Windows or UNIX, to prevent loss of configuration settings.
    4. Back up the BMC Server Automation file server storage location. For example, copy the entire contents of the storage location to a directory other than the current storage location.

    Where to go from here

    Upgrade one or more Application Servers in your BMC Server Automation system. See Upgrading the Application Server on Windows and Upgrading the Application Server on Linux and UNIX.

    Related Knowledge Articles

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

    The AMIGO Upgrade Program is designed to assist you with the upgrade of BMC BladeLogic 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

    1. Jason Lamarre

      Is there a list of deprecated BLCLIs? Thank you

      Jan 20, 2015 11:01
      1. Fran Coughlin

        Hi Jason,

        Thank you very much for your comment. While the information you were looking for did exist in the wiki space, we agree it was not easy to find. We have re-titled and reformated the topic to make the information you were looking for easier to locate.

        BLCLI commands added, updated, or removed in recent versions

        Hopefully this will help others looking for the same information.

        Thank you once again for taking the time to comment, and for bringing this to our attention.

        Regards,

        Fran

        Jan 29, 2015 08:59
    2. R V

      This could be upgraded, e.g. BL 8.5 SP1 Patch 4: 8.5.01.260

       

      Jan 28, 2015 06:43
      1. Abhilasha Garg

         

         Thanks Reinhard, the section is updated.

         

        Jan 29, 2015 08:25
    3. Domenico Trovato

      hi, in "Build Information" section it is needed to update the information regarding the release dates:

      Patch 5 for Service Pack 18.5.01.3048.5.01.005April 23, 2014
      Patch 4 for Service Pack 18.5.01.2608.5.01.004January 5, 2014

      they should be 2015 for both. 

      thanks, bye

      Apr 28, 2015 10:20
      1. Fran Coughlin

        Thank you for catching that error, Domenico; we appreciate it!

        Dates have been corrected.

        Thanks and regards,

        Fran 

        Apr 28, 2015 10:25