Hi all

I have a question regarding the temadb.

Currently running BigFix/ILMT/SQL on the same server. This server is getting old and need to set up a new one.

If setting up a completely new BigFix/ILMT/SQL server (new FQDN, new masthead +++) will it be any reason to try to re-use the old temadb?

My understanding is that when you migrate the BigFix clients to new BigFix server (new masthead), all the software will be re-discovered. 

Then all software bundling etc in ILMT must be done all over. Based on this, I assume ILMT will think all this is completely new discovered software.

Further all the historical data in the old temadb (re-used on the new one) will not usable, since it will assume all BigFix clients are new. Will it be some kind of a cap etc when trying to export historical reports/snapshot on the new server . I assume it will think the "old" BigFix clients are deleted and the servers/software are removed/decom.

Will it be a better approach to export reports,snapshots, from the old one, up to the date when the new one is installed. And at the same time/date start the export from the new one.

Hope you can sched some light on this.

Thanks in advance.

Regards

Tommy

Hello Tommy,

Well, another approach would be to use Computer reconciliation mode (https://www.ibm.com/docs/en/license-metric-tool?topic=server-computer-reconciliation-mode).
In that case ILMT will assume that all those new BigFix clients are the same as an old one and will just remap the entries.
The only requirement for reconciliation mode is to keep this old BigFix setup up and running...so, it covers the scenario when you would setup this new BigFix environment on some other machine.
For reconciliation mode ILMT needs to be able to connect into those two BigFix environments simultaneously.
After successful reconciliation you can delete this old BigFix environment altogether.

Theoretically, for reconciliation to take place you could just use this new BigFix environment alone and connect the existing ILMT data source into it.
ILMT will shout about a difference in BigFix database timestamp (the so called database epoch) but this can be easily overcomed.
Nevertheless, such 'trick' is not officially supported so in case of any import issues you are on your own...

------------------------------
Thank you,
Oktawian

Oktawian Powązka, L3 Support
IBM License Metric Tool

Original Message:
Sent: Tue October 03, 2023 06:02 AM
From: Tommy Basnes
Subject: Reuse temadb on new environment

Hi all

I have a question regarding the temadb.

Currently running BigFix/ILMT/SQL on the same server. This server is getting old and need to set up a new one.

If setting up a completely new BigFix/ILMT/SQL server (new FQDN, new masthead +++) will it be any reason to try to re-use the old temadb?

My understanding is that when you migrate the BigFix clients to new BigFix server (new masthead), all the software will be re-discovered. 

Then all software bundling etc in ILMT must be done all over. Based on this, I assume ILMT will think all this is completely new discovered software.

Further all the historical data in the old temadb (re-used on the new one) will not usable, since it will assume all BigFix clients are new. Will it be some kind of a cap etc when trying to export historical reports/snapshot on the new server . I assume it will think the "old" BigFix clients are deleted and the servers/software are removed/decom.

Will it be a better approach to export reports,snapshots, from the old one, up to the date when the new one is installed. And at the same time/date start the export from the new one.

Hope you can sched some light on this.

Thanks in advance.

Regards

Tommy

------------------------------
Tommy Basnes
------------------------------