Performing post-migration updates
If you are upgrading TrueSight Server Automation using the various component installers, you must run postmigration to perform additional upgrade related activities.
This topic contains the following sections:
Before you begin
Perform upgrade and post-migration activities in the following order. This order of steps ensures that all the Application Server steps are completed first, and that the need for a specific TrueSight Server Automation Console (RCP client) restart does not interfere with the postmigration script. For more information, see Upgrading-using-individual-component-installers.
- Before upgrading the TrueSight Server Automation Application Server, run the configurator utility.
- Upgrade the Application Server and then stop the Application Server.
- Execute the postmigration file as described in this topic.
- Stop the RSCD Agent, and then upgrade the TrueSight Server Automation Console.
- Ensure that the RSCD Agent is restarted after you upgrade the TrueSight Server Automation Console.
To execute postmigration on Windows
Warning: Prior to running the postmigration file, review the following Knowledge Article from BMC Customer Support to avoid running out of disk space on the Application Server: When upgrading TrueSight Server Automation to 8.5.1 Patch 4, 8.6, or 8.7, the postmigration utility fails with "No space left on device" (Knowledge Article ID: 000091406 )
Navigate to the postmigration file found within the TrueSight Server Automation installation directory:
<installDirectory>\NSH\bin\postmigration
- Run the postmigration file.
Progress messages regarding the relevant component templates are displayed on-screen and are also written to the postmigration.log file stored in the same location as the postmigration file.
To execute postmigration on Linux
Warning: Prior to running the postmigration file, review the following Knowledge Article from BMC Customer Support to avoid running out of disk space on the Application Server: When upgrading TrueSight Server Automation to 8.5.1 Patch 4, 8.6, or 8.7, the postmigration utility fails with "No space left on device" (Knowledge Article ID: 000091406 )
- Navigate to the postmigration file found within the TrueSight Server Automation installation directory:
<installDirectory>/NSH/bin/postmigration - Run the postmigration file.
Progress messages regarding the relevant component templates are displayed on-screen and are also written to the postmigration.log file stored in the same location as the postmigration file.
Where to go from here
- If you have upgraded the provisioning server (the Application Server enabled for provisioning), upgrade the components that TrueSight Server Automation uses in provisioning operating systems to bare metal machines. For more information about this task and other upgrade tasks, see Upgrading-using-individual-component-installers.
- Starting from version 21.3, TrueSight Server Automation no longer supports 32-bit DLLs when using ActivClient or 90meter for PKI authentication. Therefore, after you upgrade the TrueSight Server Automation console to 21.3 or later, update the sunpkcs11.cfg file to store the path to the 64-bit DLLs. For instructions, see Implementing-PKI-authentication.
- If TrueSight Server Automation is integrated with TrueSight Orchestration, enable the HTTPS support for TrueSight Orchestration on TrueSight Server Automation again.