Restore custom navigation views after Prognosis reinstall

[Timon_Dennis]

Is it possible to backup the file(s) that store any custom navigation views that were created in the Web Admin UI and then restore that file(s) following a re-install of Prognosis on the management node?  Currently faced with a possibly re-install of Prognosis on the management node and trying to avoid having to re-create 30+ custom navigation views I have added via the Web Admin over time.

Thanks

[Adam_Annen · Accepted solution]

Hi Tim,

Those "Navigation Views" are stored in postgres and the easiest way to restore this from one install to another is the Prognosis backup and restore mechanism.

Backup and restore all of Prognosis - https://community.ir.com/t5/Payments-NonStop/Prognosis-Backup-amp-Restore-Commands/m-p/1862?advanced...

My recommendation is really to engage consulting services for this reinstall as it's an advanced one. Consulting may be able to move the data via postgres actions instead for you.

Hope this helps

Adam

[Timon_Dennis]

Thanks for the info Adam.  The re-install of Prognosis on the management node is being driven by a large number of issues we seem to be continually dealing with on this particluar node.  That said, my goal of the re-install is to start with clean install as much as possible.  I'm going to avoid the backup and restore only because I want to minimize the risk of injecting anything back in that may be contributing to some of our current issues.  The custom navigation views are an exception only because of the sheer number we have and cumbersome task to re-add.  Didn't know if it might be as simple as backing up and restoring a single file from within the WebUI directory, but doesn't sound to be the case.  Not the end of the world though.

Thanks!

[Adam_Annen · Accepted solution]

Hi Tim,

If any problems persist after the reinstall, please do engage IR Support on these. We can perform a health check and make some suggestions depending on the symptoms.

Tips:

1. After uninstall, check the "Add/Remove Programs list" and see if there are older c++ installs still there - Maybe removing those and letting Prognosis put the ones it needs is a good move. 

2. Ensure the AV on the System has exceptions for the Prognosis folders

3. Ensure the VM is configured correctly with quad or octa core ( As per blog: https://community.ir.com/t5/Prognosis-Blog/VMWare-Cores-Configuration-Does-the-Socket-amp-Cores-comb... )

4. Ensure the latest windows patches are installed

Hope this helps

Adam