Backing up data

About this task

Red Hat Enterprise Linux Server does not support upgrading from 32-bit to 64-bit versions of Red Hat Enterprise Linux Server.

To save your Experience Portal configuration while doing a fresh installation of a supported version of Red Hat Enterprise Linux Server, ensure that you create a backup of Experience Portal.

	Note:
	Backing up data is a customer responsibility.

Procedure

Backup the Experience Portal database. For the upgrade procedure, you must use the System Management > System Backup menu in the EPM Web interface to create the backup.

For more information on system backup, see Administering Avaya Experience Portal on the Avaya Support site.
If you are upgrading from Experience Portal 6.x or 7.x on a supported version of Red Hat Enterprise Linux, you must manually backup the Avaya Experience Portal configuration files from the Primary EPM for the installation script to automate the upgrade.
- $AVAYA_IA_HOME/config/version.xml
  
  For example, /opt/Avaya/InstallAgent/config/version.xml
- /opt/Tomcat/apache-tomcat-*/webapps/ROOT/voiceportal_info.jsp
- $POSTGRESQL_HOME/data/PG_VERSION
  
  For example, /var/lib/pgsql/data/PG_VERSION
- /var/www/html/easg_info.php (Optional)
- $POSTGRESQL_HOME/vp_upgrade.export
  
  For example, /var/lib/pgsql/vp_upgrade.export
If you have manually modified any Voice Portal or Experience Portal properties files, back up those files. You must manually merge the changes after the upgrade is complete.
If any Tomcat configuration files in /opt/Tomcat/tomcat/config have been manually modified, back up those configurations so that you can manually merge them back after the Experience Portal upgrade is complete.
(Optional) If you have previously changed the Session timeout (minutes) in Home > User Management > Login Options, record these settings before upgrading Experience Portal.
(Optional) If you have previously changed the Purge and Retention options in Home > System Configuration > EPM Servers > Alarm/Log Options , record these settings before upgrading Experience Portal.
(Optional) If you had previously enabled Organizations for the system, record these settings under User Management > Organizations.
(Optional) If you have previously deployed and configured any Managed Applications, re-install and deploy the managed application after the upgrade is complete.

It is recommended to take a backup of the managed application, for example, Avaya Proactive Outreach Manager, as per the managed application documentation.

(Optional) If you have previously deployed and configured the co-residing application server, create a backup of the deployed application and application support runtime libraries files from the co-resident application server before the system is upgraded.

	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.