Need help on Pega instance Availability post VM Server Migration from one location to another location
Hi,
Currently we are having a Pega instance (installed on tomcat8 webserver) hosted on a VM Server at location A. We would like to take the image level backup of complete VM server and restore the same backup on the newly created host at location B. New Host will have the new hostname and new IP address. Post Server migration from location A to location B, can I be able to access the pega instance or is there any chance that instance will get corrupted or failed? Where and What are the changes that I'm supposed to do post migration?
***Edited by Moderator Marissa to update platform capability tags***
Pegasystems Inc.
IT
No corruption is expected but the instance may fails to start if, by any chance, the database is not reachable, the paths are not correct etc. These are recoverable scenarios that will resolve once the root cause is corrected.
Once migration completed and before starting the node apply the steps below:
- Truncate the pr_sys_statusnodes table in the DATA schema
- Remove the ES index files in ${pega.tmpdir}/PegaRULESIndex
Start the node and ensure it bootstrap correctly. This is confirmed by the following log message:
...(ervlet.WebAppLifeCycleListener) INFO - Web Tier initialization is complete.
Once the node starts correctly the steps to apply (logging in as [email protected]) are:
- Update Resource URLs with new hostname or ip address
- Delete old node
- Explorer bar > Records > SysAdmin > System Node
- Provide a meaningful Node Short Description:
- Explorer bar > Records > SysAdmin > System Node > Edit System Node then click on the link
- Full Text Search Re-index:
- Designer Studio > System > Settings > Search
EvonSys India Pvt. Ltd.
IN
Hello @DomenicoGiffone_GCS,
Thanks alot for quick response. Can you please elaborate how can I perform the below activity
- Remove the ES index files in ${pega.tmpdir}/PegaRULESInde
Pegasystems Inc.
IT
If the node being cloned was an indexing node you need to re-index if the node ID is being changed.
That said the previous index files placed in ${pega.tmpdir}/PegaSearchIndex can be removed as they are not used anymore and represent a waste of disk space.
To do so you need to identify the path of the Pega temporary directory (usually it is defined by the -Dpega.tmpdir JVM argument or in Tomcat installations by default it's placed in $CATALINA_BASE/work/Catalina/localhost/prweb/) and remove the content of the PegaSearchIndex (PegaRULESIndex was the directory name up to Pega 7.1.6. From Pega 7.1.7 onward it is named PegaSearchIndex)