Upgrade question

[Anon]

Hi,
Can you please explain the following: When we upgrade Prognosis (last upgrade we did was from 10.2 to 10.4) we noticed that the thresholds and database where new fields were added to the record were not automatically updated with the new fields.

Meaning my 10.4 Prognosis server is running my 10.2 thresholds and do not provide visibility over the fields added for this record.

It generate a lot of additional validation and work from our team in order to manually check and proceed with any upgrade we have to do.

Please let us know if this in expected behavior and what is the most effective workaround.

Alain Roy

[Annie_Leduc]

Hi Alain,
This is a great question I will test the behavior in my environment and will ask people from my team to see if they can share solution and explain this behavior.

Annie

[Annie_Leduc]

Again Alain,
It was great question and we were lucky to have Val and Jamie from Sydney providing additional input

It can mostly be done automatically, but not always and as per now it still require to be done in a 2 steps process.

Step 1 Customization specific to your environment
Include but not limited to : modification od the message, the destination, the number of occurrence. For example, people will usually have to specify the SNMP destination, set up email profile that matches their dispatch configuration, change the value for a where clause to better suit their environment.
Database is also similar in regard to size and wrapping.

In Step one you would need to compare the current working version to the out of box version on the original install to determine the list of customization you made.
Trick: To avoid repetitive actions and this is only good if you are running the same thresholds on monitoring server. Do the modification on the management Node and then deploy the solution on all your Monitoring Node (drag and drop from the Managing Node or using TEA(script))

Step 2 Product changes
Prognosis release Note will identify any changes in packaged thresholds and databases (in the release notes), and advised customers how to manually copy over the changes to their working copy.

Those actions are not automated in the upgrade since it is hard to just replace them with the new ones as it is not easy to tell whether the upgrade changes we intended will interfere with the changes you made.

On a final note I would add that in the past we have done some specific scripted updates. Nothing approaching an automatic merge, though.

Hope this help

Annie

[Shoaib_Dilawar]

Hi Alain,

during backup we backup all the running thresholds and restore them from the backed up copy after restore. So it restores to previously running threshold. As any suggested, you'll have to manually run the modified thresholds.

In some cases, a threshold may not be restored if, for example, it uses a field that has been removed or modified or it uses a record that has been removed.

[Anon]

Hello Alain;

As Annie suggested; a copy of the release notes corresponding to the Software version will explain the Threshold record changes, thanks for the question.