Section I: TSCO installation options to automatically migrate Manager runs
The TSCO_ConsoleSilentInstallOptions.txt options file includes a property that will automatically migrate the existing Manager runs (and any existing Agent List files) from the current BHCO Gateway Server version.
The property is here:
###################################################################################
# Migrate Agent list and Manager runs
#
# Required only for the upgrade of Gateway manger
# Default value is true
#
# Default value if not set:
# - True
# Legal values are:
# - True - Migrate Agent list and Manager runs invoked by installer.
# - False - Migrate Agent list and Manager runs invoked by b1config.
#
###################################################################################
-J PERFORM_UNIX_MIGRATE_AGENT_LIST=True
When this option is selected it will automate the migration of the existing Manager runs from the existing release to the newly installed version (this is handled by the b1configVVVV.sh root configuration script).
See https://docs.bmc.com/docs/capacityoptimization/btco2002/upgrading-the-gateway-server-using-the-wizard-914177982.html
Section II: TSCO Gateway Server post upgrade Manager run migration
The TrueSight Capacity Optimization (TSCO) Gateway Server includes a migration script that can be used to migrate the existing Manager runs to the new console version.
IMPORTANT: To use the migration script you must leave the old version of the TSCO Gateway Server installed on the machine when you install the new TSCO Gateway Server console version. Therefore, do not select the Remove existing version of Perform option on the Performance Migration Options page when you install the new console version.
Step 1
After installing the new TSCO Gateway Server console change directory to $BEST1_HOME/bgs/scripts.
Step 2
Run the migrate script './migrateManagerRuns.pl' command.
Output will look something like this:
INFO: There are currently 1 old manager runs and 0 new manager runs scheduled
Select Which Manager Run to Migrate
[1] operations_daily.vcmds
[2] ALL : Migrate All Manager Runs
[3] NONE : Do not migrate any runs (Exit) ENTER A NUMBER [1..3] followed by <Enter> key ?
In the above example there is only one Manager run scheduled called 'operations_daily.vcmds'.
Select the specific Manager runs to migrate from the old console version to the newly installed console version by entering the number associated with the Manager run, or select the ALL option to migrate all Manager runs.
Step 3
Verify the migration of the old manager run. The script migrates any Manager runs you select by executing a run.quit for the old Manager run, and submitting the run to the version 7.4.00 console. Once the migration is complete you can verify that the Manager runs have been scheduled in the new console by executing the following script:
> $BEST1_HOME/bgs/scripts/listManagerRuns.pl
where $BEST1_HOME is set to the installation directory path for the new version of the console (for example, /usr/adm/best1_10.7.00 for the TSCO Gateway Server version 10.7. The script returns a list of Manager runs that are now scheduled for version 10.7.00.
When the Manager run is migrated to the new console, the new console assumes ownership of the existing data collection request that was registered on the remote node by the previous console version. The migrated Manager run transfers that data to the console and process it using the new console version.
This migration path results in a seamless migration to the new console version without any loss of data.
Related Products:
- TrueSight Capacity Optimization (Gateway Server)
- BMC Performance Assurance for Servers