The following are the best practices for Experience Portal and POM:
Experience Portal and POM are real-time applications. Ensure that Experience Portal and POM are not running when you take a snapshot or revert to a snapshot.
To prevent side effects, shut down the virtual machine when you take or revert to a snapshot. Otherwise, the running systems can experience side effects, such as dropped calls, web sessions, and servers that are out of synchronization.
If you take a snapshot of a live EPM virtual machine and then revert the snapshot, you must restart the EPM service from the command line to resynchronize the Experience Portal environment.
Note:
Log in to the console as sroot.
To start POM, run the POM start command.
To stop POM, run the POM stop command.
To restart POM, run the POM restart command.
To see the running status of POM, run the POM status command.
If you take a snapshot of a live MPP virtual machine and then revert the snapshot, you must restart the MPP to re-synchronize the system.
Note:
Restart the MPP from the page in EPM.
After reverting a snapshot, and when the system runs, ensure that you delete all snapshots for the virtual machine in Snapshot Manager. The overhead of running with snapshots can impact the system performance, especially with disk I/O.
For more information, see best practices for using virtual machine snapshots in the vSphere environment article in the VMware knowledge base.
