Upgrade Procedure for Skype for Business

This topic provides instructions for upgrading a Skype for Business (SfB) monitoring deployment from Prognosis 11.1, or later, to Prognosis 12.0. Simple deployment scenarios (such as 1- tier) will upgrade seamlessly without any manual intervention, while more complicated scenarios (such as 2-tier and 3-tier) may require manual intervention after the upgrade (such as making changes to an ini file or re-running the setup scripts) to get the SfB ecosystem up and running again.

All upgrades should be made from the latest patch of the relevant Prognosis version. The currently supported upgrade paths are from:

Upgrade with HA Consulting Solution

If the HA Consulting Solution is deployed with Prognosis 11.4 or earlier, it may be necessary to contact the IR Consulting team for any steps required to migrate the HA Consulting Solution to the new High Availability functionality introduced in Prognosis 11.5.

Upgrade from 11.1, 11.2 or 11.3

For each multi-tier upgrade scenario, ensure that all servers have the same set of certificates. This can be accomplished by completing the following steps.

Upgrade top level Management Server to Prognosis 12.0

Open and login to the Web Application - Administration tool.

Open the MESSAGING Configuration.

Click the Start on RabbitMQ Nodegroup button.

By doing this, the Management Server will distribute certificates to all servers that it is managing.

By executing the Steps above, the broker URL field will be overwritten. This will affect the Alerting feature if it is enabled. To fix this, the URL field needs to be realigned with the Regional Server by carrying out the following steps on each Regional Server

Open and login to the Web Application - Administration tool.

Open the MESSAGING Configuration.

Modify the URL in the ADD BROKER statement to point to the Regional Server.

Click the Start button.

Open the PROGNOSIS Configuration and disable irmapsrv.exe and irqsnmpsrv.exe processes.

Repeat Steps 5 to 9 on each Regional Server.

Upgrade from 11.1 or 11.2

For multi-tier deployments, ensure that the envvars statement in the irmsmgs.ini file is configured correctly with the following parameters before the upgrade is commenced.

  • On the global server: "AUTH_FQDN=<global-server-fqdn>"

  • On the regional server: "AUTH_FQDN=localhost", "AUTH_LIST=<global-server-fqdn>;localhost"

The irmsmgs.ini file can be found in the following folder path:


Known Issues

Upgrade from 11.1

All deployments:

To automatically update the MS Windows firewall during the upgrade, it will be necessary to ensure that the following firewall rules are configured (names must match and each rule is for TCP):

  • "Prognosis - RabbitMQ In" - inbound, local port 5672,

  • "Prognosis - RabbitMQ Out" - outbound, remote port 5672,

  • "Prognosis - PQL In", inbound, local port 6767,

  • "Prognosis - PQL Out", outbound, local port 6767.

Data Migration

When upgrading from Prognosis 11.1, 11.2 or 11.3, to 12.0, the 'conversations history' can be migrated with the sfbDataMigrator tool.

In 11.1, or later, the 'conversations history' is the contents of the conversations collection of the MongoDB 'ir' database. From 11.4 onwards, the 'conversations history' is stored in the PostgreSQL database, the data migration tool is responsible for this MongoDB to PostgreSQL database migration.

The data migration tool is to be run after the 12.0 upgrade has completed successfully and Skype for Business monitoring by Prognosis 12.0 is running. All Prognosis services should be running, this includes PrognosisPostres, PrognosisRabbitMQ, Prognosis and High Availability service (if deployed in a HA environment). Migration runs in the background and Prognosis will continue to monitor Skype for Business.

The data migrator should be run on the database server(s), for HA deployment, the data migration tool must be run on the Active server in the HA Pair only.

The sfbDataMigrator tool is located in %PROGNOSIS_HOME%\Server\Configuration\microservices\sfbDataMigrator. To view the help for this tool, execute:

> sfbDataMigrator.bat --help
-h, --help Display this usage guide

Prognosis 11.x migration options:

-m, --mongo Migrate backed up Prognosis 11.x MongoDB conversations collection
-r, --restore restore mongodump of Prognosis 11.x MongoDB conversations collection
-p, --mongorestore string path to mongorestore utility
-g, --gzip specify gzip option for mongorestore
-b, --mongodump string path to mongodump of Prognosis 11.x MongoDB conversations collection
-d, --backupdatabase string restored 11.x mongodump database name
-c, --backupcollection string restored 11.x mongodump collection name
-s, --batchsize number number of rows in each PostgreSQL batch insert
-w, --waitfactor number time to wait between batches as a fraction of previous batch insert time


> sfbDataMigrator -m Migrate Prognosis 11.x MongoDB conversations collection

During the backup phase of the upgrade, a mongodump of the conversations collection from the 'ir' database will be created. Mongodump is a tool that compresses and optionally zips the contents of MongoDB data. The dump is copied to the backup directory and during the restore phase of the upgrade the dump is copied to %PROGNOSIS_HOME%\Server\Configuration\mongodb\Backup. In the restore phase of the upgrade, the dump is loaded into the mongo database in the collection conversationsBackup.

The data migration tool will read the conversationsBackup collection and put the data into the PostgreSQL database.

From Prognosis 11.4 onwards, the PrognosisMongoDB service is no longer required and will be removed.

To run the tool, open an administrative command shell and cd to %PROGNOSIS_HOME%\Server\Configuration\microservices\sfbDataMigrator. To migrate the conversationsBackup collection execute:

> sfbDataMigrator -m

This will read all conversations from the backup collection and insert transformed conversations into the PostgreSQL database. Conversations in the backup collection will be deleted as they are transformed.


Restore Phase Failure

In the case of a failed upgrade, where the restore phase did not complete and as a result, there is no conversationsBackup collection. The data migration tool is able to load the mongo dump into MongoDB before running the standard migration phase. Please run the following command:

> sfbDataMigrator -m -r -g

This will mongorestore the gzipped output of the mongodump preserved by the backup phase of the upgrade.

Backup Phase Failure

These flags can also be utilized to support migration after a failed upgrade or a non-standard upgrade, possibly involving the physical movement of data from one Prognosis Server to another. If an upgrade fails, or prior to the migration, mongodump can be run manually. cd to %PROGNOSIS_HOME%\MongoDB and execute:

> mongodump --port 9117 --db ir --collection conversations --out c:\temp --gzip

This backup can then be restored on a new or different 11.4 installation. To restore the dump created above execute:

> sfbDataMigrator -m -r -g -b c:\temp\ir\conversations.bson.gz

The default value for -p is the relative path to the mongorestore utility from the sfbDataMigrator directory, the default value for -d is 'ir' and the default value for -c is conversationsBackup. It should not be necessary to set the -p, -d or -c parameters.

Data Migration

All output (including any errors) are output to the command shell from which the utility has been started.

The data migration will display the number of conversations to migrate as well as the expected time to completion, as shown below:

Migrating conversations collection from MongoDB
Connected to Mongo
Transfering 14274737 conversations from conversationsBackup collection to Postgres...
1000 rows, 0.01% in 2 m 4 s. Estimated finish at 06:33:11 in 1 d 12 h 26 m 56 s...

This indicates that the migration has started. In the case of an unexpected failure (server restart, closed command window etc.) and the data migrator was in the 'Migrating conversations collection from MongoDB' state, the following command should be executed:

> sfbDataMigrator -m

Note that the options -r -g are not needed as conversationsBackup collection is restored.

Provide feedback on this article