This procedure applies to the Experience Portal system in which the EPM software runs on the same server as the MPP software. If you need to move the EPM or MPP software in a system where the EPM and the MPP run on different servers, see Move the EPM software to a different server machine or Moving an MPP to a different dedicated server.
Important:
You must complete the following steps in the order given below or you may encounter errors during the procedures.
Step |
Description |
1 |
On the old Experience Portal server, back up the Experience Portal database. For more information, see System Backup Overview. |
2 |
If you want to transfer the MPP log files, pack them on the old server as described in Packing MPP logs and transcriptions in a TAR file. |
3 |
If possible, set up the new server so that it has the same IP address and hostname as the old Experience Portal server. |
4 |
On the new server, install the Experience Portal software. For more information, see Installing the Avaya Experience Portal software topic in the Implementing Avaya Experience Portal on a single server guide.
Important:
Make sure you select the same options you selected for the previous installation, and that you go through the same configuration steps after you install the software. For example, if Avaya Services maintains this Experience Portal system, make sure you set up the Avaya Services access requirements as described in the Configuring the Avaya Service accounts topic in the Implementing Avaya Experience Portal on multiple servers guide.
|
5 |
On the new Experience Portal 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 server. |
6 |
Restore the Experience Portal database from the backup you made on the old EPM server as described in Database Restore utility and system backup. |
7 |
If you archived the MPP log files, restore them by unpacking the TAR archive created by the Pack command as described in Restoring packed MPP log files. |
8 |
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. |
9 |
Reestablish the link between the EPM and the MPP as described in Reestablishing the link between the EPM and an MPP. |
10 |
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. Otherwise, verify that the new EPM server can contact the WebLM server by selecting from the EPM main menu and clicking Verify on the Licensing page. |
