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.
| |
|---|
| 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. |
| For a complete list of platforms supported by the individual component installers, see Supported-platforms. |
| |
| 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
Click here to see the steps for upgrading custom configuration objects.
- Run an Update Server Properties Job on the agents you have upgraded. For more information, see Creating Update Server Properties Jobs.
- 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.
- If you upgrade to the latest version of TrueSight Server Automation and you are using TrueSight Server Automation for virtual environments, you must immediately update the RSCD agent on the system used for the integration and add the new configuration object version for the integration. For example, for the vCenter server, you must upgrade the RSCD agent on either the Windows vCenter server or the AMO proxy and add the new VMware configuration object to the vCenter server object in TrueSight Server Automation.
- 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:
- Open the object (template, package, or job).
- Manually remove the asset of the earlier version and add the asset of the latest version.
- Save the object.
To upgrade virtualization configuration objects
Click here to see the steps for 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: - Import the new version of the virtualization configuration object (for example, the VMware vCenter configuration object).
- 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.
- Run the Distribute Configuration Objects Job to distribute the configuration objects to the target agent (see Distributing-configuration-objects).
- To identify the configuration objects that failed, run the Upgrade Model Objects Job on all jobs, templates, and BLPackages that reference the configuration object.
- After the Upgrade Model Objects Job completes, open the objects for which the job failed.
- 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. |
|
Click here to review a list of potential issues you can encounter during an upgrade.
- Upgrade to version 8.6 or later does not grant the DBMS_LOCK privilege to user - Before you start upgrading from a previous version to TrueSight Server Automation 8.6, ensure that the TrueSight Server Automation user is granted the DBMS_LOCK privilege. This privilege is required for carrying out a handshake between TrueSight Server Automation database and the TrueSight Smart Reporting 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.6 or later disables PropertySync - As of TrueSight Server Automation version 8.5, the PropertySync feature has been deprecated. During migration of the database, PropertySync is disabled and the migration results table displays the migration warning: PropertySync has been changed from true to false. Contact BMC Support for further assistance.
- Upgrade to version 8.5 or later 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.6 or later causes Citrix XenServer Provision Jobs to fail - After an upgrade from TrueSight Server Automation version 8.3 or earlier to TrueSight Server Automation version 8.5 or later, 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 work around 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).
- Audit performed with snapshots captured using earlier versions of the RSCD agent can fail - When capturing data from target servers, version 8.6.00 of TrueSight Server Automation skips IPv6 addresses and masks. After an upgrade to version 8.6.00 or later 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.
- In a multiple application server (MAS) environment, if the RSCD Agent is not present on the secondary node and the primary node is using PsExec version 2.43, upgrade to version 21.3 or later on the secondary node fails. To fix the issue, perform one of the following tasks:
- Install RSCD Agent on the secondary node and start the upgrade process again on the secondary node.
- Use PsExec version 2.2 instead of version 2.43 on the primary node, and start the upgrade process again on the secondary node.
|
| 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). |
Back to top
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.
| |
|---|
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
restore the database to its pre-upgrade state is from the backups. |
Remove unnecessary deployments | The migration process uses the database system ID information in the _template deployment to identify the database to migrate. In addition,
the configurations from each existing deployment are processed, so each deployment present in the Deployments directory should have the correct configuration. Certain deployments are transitory and can be removed before an upgrade as they are not needed for normal operation. _install, _postmig, and _util can be removed from the deployments directory if present, and provided that an installation, postmigration process, or blcontent process is not being run. (optional) _launcher is for the Application Server Launcher. This does not include database configuration information. Both _spawner and _pxe include database configuration information. The _template deployment is used to create new deployments, including those used during migration. However, you can delete them for stale deployments (user created deployments that are not in use anymore).
|
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
correct the configuration information and proceed with the upgrade. - blasadmin -s <deloyment name> show database all (for the _pxe deployment use blasadmin -s _pxe show pxe all)
- blasadmin -s <deployment name> show file all
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(*)
from blgroup
group by name, parent_group_id, group_type_id
having count(*)>1; 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
from(select sum(bytes)/1024/1024 table_size_mbs
from user_segments us
where segment_name in(select ut.table_name
from user_tables ut
where ut.table_name in (select column_value
from table(LANG_UTIL.STR_TO_ARRAY('JOB_RUN_EVENT,COMPLIANCE_RULE_RESULT'))))
) tab_size,
(select sum(dfs.bytes)/1024/1024 table_space_free_space_mbs
from dba_free_space dfs
where dfs.tablespace_name = (select tablespace_name from user_segments where segment_name = 'JOB_RUN_EVENT')
group by dfs.tablespace_name
) free_space; 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. |
Back to top
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
PXE Server: C:\Program Files\BMC Software\BladeLogic\PXE
If you are upgrading the PXE server, follow the upgrade instructions for Windows or UNIX, to prevent loss of configuration settings.
Important
Ensure that all files and folders in the installation directory and its sub-directories do not have the read-only attribute enabled. The upgrade might fail, if the read-only attribute is enabled on any file.
- 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).
Note
As a prerequisite to install Microsoft Visual C++ 2015 Redistributable Update 3 on Windows 2012 R2, you must have the following patches installed on your server:- KB2919442 (Required for 2919355)
- KB2919355. This patch requires several other patches: clearcompressionflag.exe, KB2919355, KB2932046, KB2959977, KB2937592, KB2938439, and KB2934018. This are all available on the download page for KB2919355.
For more information about the prerequisites for Microsoft Visual C++ 2015 Redistributable Update 3, refer to the Microsoft documentation here.
Back to top
Where to go from here
Upgrading-product-components-on-Microsoft-Windows