‎Sep 17, 2017 06:50 AM
‎Sep 21, 2017 11:22 AM
‎Sep 21, 2017 07:34 PM
cgrinton wrote:
Key steps to do once the compliance database from one FlexNet Manager Suite instance has been restored to be used by another instance are:
[LIST=1]Run the Config.ps1 script to apply configuration settings as appropriate for the new instance Review and update inventory data source connection details in the beacon UI Review and update any remaining connection details in the dbo.ComplianceConnection table in the database; this will at least include the Data Warehouse connection details (this requires you to manipulate data directly in the database - there is no FlexNet Manager Suite UI for this) Configure & register beacons in the new instance environment
Chris @ Flexera
‎Oct 06, 2017 02:34 AM
Do we need to run Config.ps1 in the DB server?
Cause, if we have multi-server environment and in that DB as separate server.
Do we need to run Config.ps1 script in DB server post restore of PROD DBs into QA and then the other changes?
Also to test an upgrade, do we need to restore all the DBs or FNMSInventory, FNMSCompliance and FNMSDataWarehouse should be enough into QA from PROD?
‎Dec 12, 2019 08:48 AM
The Config.ps1 script would normally be run on the FNMS application server, not the database server. Check the FlexNet Manager Suite Installation Guide for information about that script.
Which databases to restore will depend on your exact scenario and use case, but restoring all the FNMSInventory, FNMSCompliance and FNMSDataWarehouse databases would be common.
‎Dec 12, 2019 09:35 PM
‎Jun 22, 2020 06:44 AM
‎Jun 22, 2020 09:09 PM
Hi Bhanu,
Moving databases between stages DEV/UAT/PROD, is done by some of our customers. The act of restoring a copy to a test environment itself pretty straight forward. A few things to consider:
Best regards,
Markward
‎Dec 13, 2019 02:25 AM