What are the primary considerations when moving the BMC Helix Continuous Optimization (BHCO) or TrueSight Capacity Optimization Gateway Server (BPA console) from one machine to another? |
The things to consider when moving the BMC Helix Continuous Optimization (BHCO) or TrueSight Capacity Optimization (TSCO) Gateway Server console from one machine to another machine are very similar to the considerations required when upgrading from one release of the Gateway Server to another. The primary considerations are:
(A) The migration of the Gateway Server itself (B) The transition of the existing Gateway Server VIS parser ETLs (assuming AutoETL) associated with the existing Gateway Server to new Gateway Server VIS parser ETLs associated with the new Gateway Server Section I: Unix consoleMigrating custom filesThere are several files that will need to be migrated from the existing Perform console to the new machine. The most common files to migrate are:
One best practice recommendation is to build a directory structure that contains all of those files outside of the $BEST1_HOME directory and separate the files used as part of the nightly Manager runs from the files used in ad hoc Manager runs. The default and best location for files for nightly runs are: /usr/adm/best1_workspace/automation - Input files such as the *.vcmds, *.an, and *.dmn files /usr/adm/best1_workspace/repository - The console UDR data repository directory /usr/adm/best1_workspace/results - The Manager Output directories It can then be useful, but not required, to create a parallel directory structure for ad hoc runs. For example: /usr/adm/best1_workspace/
- /adhoc - /automation - /repository - /results Another option is to leave the files in the same directories, but clearly name them to make it obvious which ones are associated with nightly Manager runs and which are associated with ad hoc Manager runs. Migrating Manager runs Let's start by assuming that Manager runs have been submitted using Agent List files. This means that under Administration -> Gateway Manager -> Gateway Servers -> [Select the Gateway Server]. Note the Agent List names as those will be used to define the Manager run. One can obtain a list of the currently scheduled Manager runs using the 'listManagerRuns.pl' command: > $BEST1_HOME/bgs/scripts/listManagerRuns.pl -p MANAGER_COMMANDS_FILE OUTPUT_DIRECTORY
#MANAGER_COMMANDS_FILE,OUTPUT_DIRECTORY, /usr/adm/best1_workspace/automation/tsco105labs.vcmds,/usr/adm/best1_workspace/results/May-08-2020.19.43_tsco105labs, /usr/adm/best1_workspace/automation/tsco107labs.vcmds,/usr/adm/best1_workspace/results/May-08-2020.19.43_tsco107labs, /usr/adm/best1_workspace/automation/tsco100labs.vcmds,/usr/adm/best1_workspace/results/May-08-2020.19.44_tsco100labs, /usr/adm/best1_workspace/automation/tsco103labs.vcmds,/usr/adm/best1_workspace/results/May-08-2020.19.44_tsco103labs, /usr/adm/best1_workspace/automation/tsco2002labs.vcmds,/usr/adm/best1_workspace/results/May-08-2020.19.37_tsco2002labs, /usr/adm/best1_workspace/automation/tsco2002labs1.vcmds,/usr/adm/best1_workspace/results/May-08-2020.19.37_tsco2002labs1, /usr/adm/best1_workspace/automation/tsco2002labs2.vcmds,/usr/adm/best1_workspace/results/May-08-2020.19.37_tsco2002labs2,
where 'manager.vcmds' is the name of the Manager run to start. Step 1
Once a run has been migrated to the new console you can terminate it on the old console by creating a zero-length file called 'run.quit' in the Manager Output Directory for the run. > cd [Manager Output Directory]
> touch run.quit That will stop the run. If when you submitted the run on the new console you specified a Start Date of the current day (not tomorrow) the new console will take ownership of the data already being collected on the remote nodes and that data will be transferred to the new console and processed. Section II: Additional InformationOnce the run migration is complete, one can check the manager runs via the following commands:
Note that it is important that once the runs have been migrated successfully to the new console they must be stopped on the old console (as described above). That can either be done by:
- or -
Section III: Steps necessary if the 'Pending Collection' requests issues from the previous console must be clearedThe steps listed above will work as long as you don't try to clear the 'pending' data collection requests. The new console will issue duplicate collection requests to the existing pending data collection requests and the remote node will collect the data as expected. The pending data collection requests don't really care which console issued the collection request since they just relate to the parameters of data collection - the console handles data transfer separately in Manager.
If there is some reason to clear the pending collection requests (such as one of the collection parameters needs to be changed (the sample rate, the spill interval, the daily collection start time, or the daily collection end time) then would be be necessary to clear the active collection requests. If you need to clear the pending collection requests (which typically isn't necessary) then you'll need to do things a little differently. Terms:
On day X, you clear the pending collection requests registered on the remote node from console A. The easiest way to do that would be a script that issued the following command console A as the user under which the Manager runs are scheduled: $BEST1_HOME/bgs/scripts/best1collect -n [remote node] -k
You can get a list of the remote nodes via the following command run on console A: $BEST1_HOME/bgs/bin/udrCollectStat -D -d MM-DD-YYYY -f "%n"
Where MM-DD-YYYY is the current date such as 06-02-2009. Note that this will stop the active data collection request on the machine, so during this transition period there won't be any active UDR data collection happening on the machine. Step 2 Start the Manager runs on console B with a Start Date of today, and End Date way in the future, and with the normal Begin/End times for collection (00:00 - 23:59). Step 3 On console A (the old console):
Step 4 At this point you are done. The new console should transfer the data from the remote nodes and process it that night. Related Products:
|