Staging the Experience Portal 6.x or 7.x backup files on the Primary EPM before upgrading Experience Portal

About this task

If upgrading to Experience Portal 8.1 from Experience Portal 6.x or 7.x on a Red Hat Enterprise Linux Server, you must manually stage the database backup and configuration files on the fresh installation RHEL server of the Primary EPM. You must do this before you run the aepinstall.sh script for upgrading the Primary EPM server to Experience Portal 8.1.

For more information on the database backup and configuration files, see Backing up data.

	Note:
	This procedure is only applicable to Red Hat Enterprise Linux upgrades from Experience Portal 6.x or 7.x. It is not required for Avaya Enterprise Linux upgrades. Staging of the files is required only for the Primary EPM.

Procedure

Rename the vp_backupaa backup file to vp_upgrade.export and copy the file to /var/lib/pgsql/vp_upgrade.export.
Copy the version.xml file to /opt/Avaya/InstallAgent/config/version.xml.

Create the directory if it does not already exist.

For example, mkdir -p /opt/Avaya/InstallAgent/config/.
Rename the voiceportal_info.jsp to voiceportal_info.php and copy to /var/www/html/voiceportal_info.php.

Create the directory if it does not already exist.

For example, mkdir -p /var/www/html/.
Copy the PG_VERSION file to /var/lib/pgsql/data/PG_VERSION.

Create the directory if it does not already exist.

For example, mkdir -p / var/lib/pgsql/data/.