Restoring the software on the Primary EPM server or a single-server Experience Portal system running Avaya Enterprise Linux

Before you begin

Ensure that you have restored the operating system as described in Restoring the Avaya Enterprise Linux operating system.

Procedure

Log on to Linux on the Experience Portal Primary EPM server.
If you are an Avaya Services representative, and use Avaya Enterprise Linux, the Avaya Service accounts will not be available after the Avaya Enterprise Linux upgrade. The Avaya Service accounts will be available through EASG configuration during the Experience Portal upgrade.
- Log on to the local Linux console as root.
- Or log on remotely as a non-root user and then change the user to root by entering the su - root command.
Stop the vpms service by entering the systemctl stop vpms command.

You will see a series of messages as the command starts to shut down the EPM components. When the command has successfully stopped all relevant components, the system displays the message: VPMS Shutdown Status: [ OK ].
Check the status of the postgres service by entering the /sbin/service postgresql status command.
If the postgres service is running, stop it by entering the /sbin/service postgresql stop command.
Navigate to the pgsql directory by entering the cd /var/lib/pgsql command.
Rename the current data directory that contains the 6.x or 7.x data by entering the mv data data_OLD command.
In the pgsql directory, locate the backup directory that Experience Portal created when you installed the new version. The file name has the format data_vp_<backup_date>_<backup_time>.
Copy this backup directory into the main data directory by entering the cp -rp data_vp_<backup_date>_<backup_time> data command.
Start the postgresql service by entering the /sbin/service postgresql start command.
Wait for a few seconds for the database to start, then verify that it is running by entering the /sbin/service postgresql status command.
Start the vpms service by entering the systemctl start vpms command.
If you have previously changed the Session timeout (minutes) field in Home > User Management > Login Options, update this field again.

For more information, see Administering Avaya Experience Portal.
If you have previously changed the Purge and Retention field in Home > System Configuration > EPM Servers > Alarm/Log Options, update this field again.

For more information, see Administering Avaya Experience Portal.
If you have previously enabled Organizations for the system, re-enable it by executing the following script:

$AVAYA_HOME/Support/VP-Tools/EnableOrganizations

For more information on Enabling organization level access in Experience Portal, see Administering Avaya Experience Portal.

If you are restoring a co-resident application server on the Experience Portal server, follow the steps in Optional: Updating the co-resident application server.

	Note:
	For major version upgrades of Tomcat, it is also recommended that the deployed applications and application support runtime libraries are re-generated for the updated version of Tomcat.

If you have previously deployed and configured any Managed Applications, re-install and deploy the managed application.