Preparing to upgrade individual components on Microsoft Windows
This topic provides the information you need to prepare your environment for the upgrade process on Microsoft Windows systems using the individual component installers. It includes information about supported upgrade paths and instructions for preparing to upgrade the TrueSight Server Automation system.
The topic includes the following sections:
Step 1: Review requirements and limitations
Prior to upgrading, it is important to carefully review the following requirements and limitations.
Category | Requirement |
---|---|
Product integrations | If your TrueSight Server Automation environment includes TrueSight Smart Reporting for Server Automation, upgrade TrueSight Smart Reporting for Server Automation before upgrading TrueSight Server Automation. For more information, see the TrueSight Smart Reporting for Server Automation online technical documentation. |
Supported platforms | For a complete list of platforms supported by the individual component installers, see Supported-platforms. |
Install mode | If you are using Microsoft Windows 2003 or 2008, you must upgrade in Install mode instead of Execute mode, see Using-Install-mode-instead-of-Execute-mode. |
Configuration objects | 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. For 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. To upgrade custom configuration objects To upgrade virtualization configuration objects |
Potential issues | |
Certificate issue | If your id.pem certificate was created with a key size of 1024 bits (or less), you will need to regenerate it with a higher key size (2048 or higher). This is due to a change in the FIPS requirement for minimum key length (now 2048 bits). |
Step 2: Prepare the database
During an upgrade process, core data is migrated to the upgraded TrueSight Server Automation database. To ensure that this migration completes successfully, you must prepare your database before performing the upgrade. To prepare your database, review the following list of prerequisite tasks and perform the tasks that are relevant for your environment.
Task | Description |
---|---|
Back up the TrueSight Server Automation database. | You must back up before beginning the data upgrade process. The data upgrade occurs in place. If, for any reason, it should become impossible to complete the upgrade, the only way to |
Remove unnecessary deployments | The migration process uses the database system ID information in the _template deployment to identify the database to migrate. In addition, Certain deployments are transitory and can be removed before an upgrade as they are not needed for normal operation.
|
Ensure that the database configuration information on the deployments of the Application Server is up-to-date | Before upgrading the Application Server, ensure that the database configuration information on the deployments of the Application Server is up-to-date. You can use the blasadmin utility to check the database related and file server related information for each of the deployments (except _launcher). You can use the following blasadmin commands. If either of these commands returns an error, you can use the blasadmin utility to
If these commands return an error, use the blasadmin utility to correct the configuration so that those commands do not return an error. |
Ensure that the blgroup table does not contain duplicate entries | Before you start the upgrade, connect to the database and run the following query: select name, parent_group_id, group_type_id, count(*) If the above query returns any rows, contact BMC Support for further actions. |
(Oracle only) Ensure that the sufficient free space, which is required for migration to 21.3 or later versions, is available on the tablespaces | Before you start the upgrade, connect to the database and run the following query: select table_size_mbs, table_space_free_space_mbs If the value returned by the table_space_free_space_mbs column is lesser than the value returned by the table_size_mbs column, increase the tablespace size. |
(Oracle only) Grant privileges explicitly to the user account | For an Oracle database, you must grant certain privileges explicitly to the user account (typically BLADELOGIC) that will be used during the upgrade. Some of the privileges can be revoked after database migration is performed during the upgrade. For the complete list, see List-of-required-database-permissions. |
(SQL only) Configure the database to use the simple recovery mode | For information about configuring the simple recovery mode, see the appropriate Microsoft documentation. |
(SQL only) Shrink the transaction log file. | For more information, see the appropriate Microsoft documentation. |
Step 3: Prepare the automation environment
Perform these tasks in order. Many steps are prerequisites for other steps that occur later in the process.
- Back up the TrueSight 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.
- Ensure that your connection to Microsoft SQL database is not encrypted. TrueSight Server Automation does not support using an encrypted Microsoft SQL database connection at the time of upgrade. However, after the product is upgraded successfully, TrueSight Server Automation can use an encrypted connection to communicate with the Microsoft SQL database.
- Shut down the TrueSight Server Automation environment:
- Stop the Application Server.
- Stop the PXE server. See Starting-and-stopping-a-PXE-server.
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 TrueSight Server Automation. If you do not know the installation location for TrueSight Server Automation components view the contents of the %WINDIR%\rsc\HOME file.
The default installation locations are:
- Application Server: C:\Program Files\BMC Software\BladeLogic\NSH
- Ensure that there is an RSCD agent installed on each Application Server to avoid potential errors in the upgrade process.
- Ensure that there is an RSCD agent and NSH are installed on the PXE server.
- If you are upgrading an RSCD agent in a domain controller environment, perform the following tasks:
- Change the BladeLogicRSCDDC password as per your company's password policies by using the chapw command. For instructions on changing the password, Changing-the-BladeLogicRSCDDC-account-password-on-domain-controllers.
- Ensure that Administrators do not have the Delete permission on the HKEY_LOCAL_MACHINE\SAM\SAM node in the Windows Registry. By default, Administrators have the Read Control and Write DAC registry access permissions.
- Make sure that you have 4 GB on disk with temp space and 4 GB on disk with installation directory.
- Ensure that you have disabled the NSH proxy on all Application Servers in the environment to avoid failure during upgrade. To disable the NSH proxy, run the following command on the NSH client:
secadmin -m default -p 5 -T encryption_only -e tls -appserver_protocol clear
This command temporarily removes the appserver_protocol=ssoproxy entry from the default line in the secure file (in the rsc folder).Note: After the upgrade completes, remember to add this entry back into the secure file. You can use the following command:
secadmin -m default -p 5 -appserver_protocol ssoproxy
- To preserve the Live Reporting dashboard environment, back up the cacerts file (for example, C:\Program Files\BMC Software\BladeLogic\appserver\NSH\jre\lib\security\cacerts for Windows) to a separate safe location on the TrueSight Server Automation server. You must do this because the TrueSight Server Automation upgrade overwrites the existing cacerts.
- Ensure that Microsoft Visual C++ 2015 Redistributable Update 3 is installed on the server. For more information, see Installing an RSCD agent (Windows).
Where to go from here