Restoring data backed up from System Backup

Last Updated : Jun 05, 2026 |

Before you begin

The Experience Portal software version must be the same version that was used to create the backup.

Verify the do_MntDrv script. For further information, see Verifying the backup server mount point.

For more information, see Backup Server page field descriptions.

Procedure

  1. Log on to Linux on the Experience Portal Primary EPM server.

    • If you are an Avaya Services representative, and use Avaya Enterprise Linux, or if the Avaya Service accounts are installed on this server, log on to the local Linux console as root.

    • Otherwise, log on remotely as a non-root user, and then change the user to root by entering the su - root command.

  2. Stop the vpms service by entering the /sbin/service vpms stop command.
  3. Stop the avpSNMPAgentSvc service by entering the /sbin/service avpSNMPAgentSvc stop command.
  4. If there is an application server installed on the system, enter the /sbin/service appserver stop command to stop the application server.
  5. Navigate to the backup directory located in $AVAYA_HOME by entering the cd $AVAYA_HOME/Support/Database/DBbackup command.
  6. If the backup package is on a remote server:
    1. Enter the bash do_MntDrv command.
    2. Restore the database by entering the bash do_RestoreData command.

    If the backup package is on a local server:

    1. Enter the do_RestoreData -f <backup file name> command. For example, enter the do_RestoreData -f /opt/Avaya/backup which indicates that you want to restore the contents of backup folder located in the /opt/Avaya directory.
      Note:

      The command will first clean the database.

      The list of existing backup packages saved in the backup server is displayed.

  7. Select the package for Experience Portal data restore.
  8. Press Enter to continue.

    The script completes the restore process.

  9. If the script displays a message to restart the postgresql service for the changes to take effect, then manually restart the postgresql service by running the /sbin/service postgresql restart command.
  10. Perform the following steps if the hostname or IP address of the server running the EPM or MPP software has changed since you created the database backup:
    1. To navigate to the do_UpdateHost script directory, enter the cd $AVAYA_HOME/Support/UpdateHostAddress command.
    2. To change the hostname in the database to the hostname of the current server, enter the bash do_UpdateHost command .
  11. Restart the vpms service by entering the /sbin/service vpms start command.
  12. Restart the avpSNMPAgentSvc service by entering the /sbin/service avpSNMPAgentSvc start command.
  13. If there is an application server installed on the system, restart the application server by entering the /sbin/service appserver start command.
  14. Reconnect each MPP server with the EPM server.
  15. Reestablish the link between the MPP and the EPM by trusting the MPP's security certificate.
  16. Reconnect each auxiliary EPM server with the primary EPM server as described in Reconnecting the primary and auxiliary EPM servers.
  17. If you are restoring your Experience Portal database to a new server, you need to install a new license file on the server. For further information, see Installing the license file section in the Implementing Experience Portal on multiple servers or the Implementing Avaya Experience Portal on single server guide.
    Note:

    This step is not required if you are using a Standalone WebLM.

  18. To unmount the shared directory, enter the bash UmntDrive command.