cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted

Migrate Data from FNMS 2017R3 to new FNMS 2019 (not upgrade)

Hello Experts,

We have an instance of FNMS 2017 R3 with 1500+ licenses created and 9500+ purchases already being managed.

Customer doesn't want to upgrade the existing 2017 R3 but wants to implement FNMS 2019 R1 as a fresh installation on a new server setup with new hostnames.

In this case, how can we get all the licenses (with PURs configured), purchases, contracts..etc., imported to new FNMS 2019 R1 with out any issues and with out recreating licenses and reprocessing PO's ? What is the best way to achieve this?

I'm guessing that the "database migration" may be crucial in this case, so first install new FNMS 2017 R3 using restored existing FNMS 2017 R3 database on whole new setup and then upgrade this to 2019 R1, but I'm not sure if it can bring all licenses/PO's..etc., in GUI with out any issues.

Regards

Rajesh Ponnala

0 Kudos
10 Replies
Flexera mgunnels1
Flexera

Re: Migrate Data from FNMS 2017R3 to new FNMS 2019 (not upgrade)

Good Morning,

I would …

  1. Back up the existing datawarehouse and fnmscompliance databases and restore to the new SQL environment.
  2. Build out the remaining databases fresh. (contentstore, fnmsinventory , snapshot)
  3. Upgrade the restored databases to 2019 R1.
  4. Update the complianceconnection table to point to the correct FNMSinventory and Datawarehouse databases)
  5. Update the compliancesettings table and change the batchschedulerhostname to the correct server.
  6. Install the required software
  7. Run the configuration scripts

 

Optionally to remove old inventory

  1. Delete the 3rd party inventory sources from data inputs. This will delete the associated inventory.

Re: Migrate Data from FNMS 2017R3 to new FNMS 2019 (not upgrade)

@mgunnels1 

Thanks for your response. Can you please guide me how to do the following.  Can you please share any SQL query or steps to achieve

  1. Update the complianceconnection table to point to the correct FNMSinventory and Datawarehouse databases)
  2. Update the compliancesettings table and change the batchschedulerhostname to the correct server.

I'm hoping that if we follow the above all steps as you mentioned, all the licenses (including custom metrics), PO's (processed & unprocessed) will be imported to FNMS GUI with out any additional work. Agree ?

0 Kudos
Moderator mgunnels Moderator
Moderator

Re: Migrate Data from FNMS 2017R3 to new FNMS 2019 (not upgrade)

Good Morning,

Attached is a sample script for updating the FNMScompliance database when moving to a new location.

(Always test a script on a development environment prior to running in production.)

This process will not modify the configuration of purchase orders or licenses.

mfranz
Analyst

Re: Migrate Data from FNMS 2017R3 to new FNMS 2019 (not upgrade)

This is exactly how I would proceed in this case. @rajeshponnala please consider marking the original answer as solution.
Another thing to consider: If FNMS agents are used widely, you may want to plan ahead to let them know about the new beacon/server in time. Some options would be:

  • Manually inserting the new beacon location to the beacon table to have it automatically pushed to all agents.
  • Or leave a beacon in the old location, pointing to the new environment until all agents are aware, then removing it.