Restoring the software on a dedicated Primary EPM server or a single-server EPM system running Red Hat Enterprise Linux Server

Last Updated : Sep 07, 2022 |
Prolog information
Metadata
Keywords:
Note:
If your installation uses a dedicated Primary EPM server, you should always restore the Primary EPM server first and then you can restore each Auxiliary EPM and MPP server separately.
Before you begin
Ensure that you have access to the backup files taken before the upgrade. For more information about backing up the existing data, see Backing up data.
  1. Install the previous version of Red Hat Enterprise Linux Server using the Red Hat Enterprise Server installation CD-ROM and the exact options you used for the 6.0.x, 7.0.x, or 7.1 software installation.
  2. Reinstall the EPM software from your 6.0.x, 7.0.x, or 7.1 software installation DVD.
    ADDITIONAL INFORMATION:
    Ensure that you select the same options that you selected during the first install.
  3. Restore your Experience Portal database from the backup as described in the document Upgrading to Avaya Experience Portal 8.1.
  4. If you have changed the default log and alarm retention periods, reset those values as described in Administering Avaya Experience Portal.
  5. If you have previously changed the Session timeout (minutes) field in Home User Management Login Options, update this field again.
    ADDITIONAL INFORMATION:
    For more information, see Administering Avaya Experience Portal.
  6. If you have previously changed the Purge and Retention field in Home System Configuration EPM Servers Alarm/Log Options, update this field again.
    ADDITIONAL INFORMATION:
    For more information, see Administering Avaya Experience Portal.
  7. If you have previously enabled Organizations for the system, re-enable it by executing the following script:
    ADDITIONAL INFORMATION:
    $AVAYA_HOME/Support/VP-Tools/EnableOrganizations
    For more information on Enabling organization level access in Experience Portal, see Administering Avaya Experience Portal.
  8. 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.
    ADDITIONAL INFORMATION:
    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.
  9. If you have previously deployed and configured any Managed Applications, re-install and deploy the managed application.