Move the EPM software to a different server machine

This procedure applies to moving the primary EPM software in a dedicated server configuration. If you need to:

Move the EPM software in a system where the EPM and the MPP software runs on the same server, see Move a single-server Experience Portal system to a different server.
Move the auxiliary EPM software, simply install the software on the new server as described in Configuring an auxiliary server.

	Important:
	You must complete these steps in the order given below or you may encounter errors during the procedures.

Step

Description

On the old EPM server, back up the Experience Portal database as described in System Backup Overview.

If possible, set up the new server so that it has the same IP address and hostname as the old EPM server.

On the new EPM server, install the operating system and the EPM server software as if this was a new installation. If at all possible, the new EPM server should have the same hostname and IP address as the old EPM server in order to minimize the number of manual changes you will need to make.

Important:

Make sure you:

Perform all software prerequisites, such as synchronizing the time between the new EPM server and the MPP servers.
Select the same options you selected for the previous installation.
Go through the same configuration steps after you install the software. For example, if you synchronized the old EPM server with an external time source, make sure you configure the new server to use that time source as well.

On the new EPM server, configure the backup and restore scripts as described in Verifying the backup server mount point. Make sure that you specify the same mount point and shared directory that you used on the old EPM server.

Restore the Experience Portal database from the backup you made on the old EPM server as described in Database Restore utility and system backup.

If you could not use the same hostname and IP address for the new EPM server, change the information in the Experience Portal database as described in Changing the hostname or IP address on a dedicated primary EPM server.

If you could not use the same IP address and hostname for the new server, you need to connect each MPP server with the new EPM server as described in Reconnecting an existing MPP server with the EPM server.

If your WebLM server ran on the old EPM server, install the Experience Portal license file on the new EPM server as described in the Installing the license file topic in the Implementing Avaya Experience Portal on multiple servers guide.

Otherwise, verify that the new EPM server can contact the WebLM server by selecting Security > Licensing from the EPM main menu and clicking Verify on the Licensing page.