Copying and restoring the backup files

Before you begin

Install a supported version of Red Hat Enterprise Linux Server on the server as described in Operating system upgrade overview.
Upgrade the Primary EPM server as described in Upgrading the Primary EPM software interactively.
Ensure that you have the location details of the Experience Portal backup files.

	Note:
	This procedure is applicable only for the Primary EPM server.

Procedure

Log in to the server locally as root, or log in remotely as a non-root user and change the user to root by running the su - command.

Copy the backup package created before the upgrade to a temporary location on the local hard drive.

	Note:
	This step is applicable only if you did not complete Staging the Experience Portal 6.x or 7.x backup files on the Primary EPM before upgrading Experience Portal prior to running the aepinstall.sh script.

The folder name of backup packages created by Voice Portal is pkgVP<Version>_<XXXXXXXXXXXXX> and the folder name for backup packages created by Experience Portal is pkgEP<Version>_<XXXXXXXXXXXXX>. Where,

<Version> is the version number of the software that the backup was created with.
<XXXXXXXXXXXXX> is a 13 digit timestamp that is not in a human readable format.

	Note:
	The Experience Portal installation script identifies the Experience Portal version and the configuration information available on the server based on the folder name.

Restore the database backup.

	Note:
	This step is applicable only if you did not complete Staging the Experience Portal 6.x or 7.x backup files on the Primary EPM before upgrading Experience Portal prior to running the aepinstall.sh script.

For details on Database Restore Utility, see Administering Avaya Experience Portal

	Note:
	Restoring the database is applicable to both Red Hat Enterprise Linux and Avaya Enterprise Linux upgrades.

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.