Print

EPM running out of disk space

If the EPM server runs out of disk space, you can check the disk space usage and determine which proposed solution to follow to free up the disk space.

noteNote:

If none of the following recommended actions resolve the problem, contact your Avaya technical support representative for assistance.

Prerequisites

About this task

Prior to following any of the proposed solutions, you need to check the disk space usage. This will help you determine which proposed solution to follow.

noteNote:

Do not delete files from the server without analyzing the possible outcome.

Procedure

  1. Log in to Linux on the primary or auxiliary EPM server.

    If you are an Avaya Services representative, and are using Avaya Enterprise Linux or if the Avaya Service accounts are installed on this server:

    • Log in to the local Linux console as sroot.

    • Or log in remotely as a non-root user and then change the user to sroot by entering the su - sroot command.

    Otherwise, log in to Linux locally as root, or log in remotely as a non-root user and change the user to root by entering the su - command.

  2. Isolate the directory that uses the maximum disk space.
    1. Enter the du –b --max-depth=1 -h / command to display a list of top level directories on the server along with the currently-occupied disk space.
      The table below is an example of the output: 
      [sroot@vp-a11 /]# du –b --max-depth=1 -h /
20K /mnt
12M /tmp
1.8G /home
5.9M /bin
24K /root
9.3G /opt
995M /var
16G /
[sroot@vp-a11 /]#
    2. Check the output to determine which directory uses the maximum disk space. In the example given above, the /opt directory uses the maximum space.
    3. To further isolate the directory that uses the maximum space, enter the du –b --max-depth=1 -h /<directory name> command where <directory name> is the directory uses the maximum space.

      For example, enter the du –b --max-depth=1 -h /opt command to check the directories under the/opt directory.

      noteNote:

      Repeat the command to locate the specific directory or file that uses the maximum disk space.

  3. Analyze the information, and based on the observations follow up with the possible solutions, as mentioned in the steps below.
  4. If the /var directory uses maximum disk space, it is possible that the retention period for the report data (Call/Session, Application, and/or Performance), Alarm Logs, Event Log, or Audit Logs are set too high. When Experience Portal is initially installed, the retention period for these tables are set to default values. Depending on the system load and applications being run, these values may need change to retain less data and thereby use less disk space.
    noteNote:

    The database that Experience Portal uses is located in the /var directory.

    1. From the EPM menu, select Real Time Monitoring > System Monitor.
    2. In the Server Name column, select the link for EPM.
    3. Use the <EPM> Details page to view the detailed database status of the primary EPM server. The Database Status section shows the database tables that use the most disk space and the corresponding size, in bytes. The database tables are listed in descending order as per the size.
    4. Choose the Proposed Solution based on which table or tables is using more disk space than expected:

      • Use Proposed Solution 1 for the following tables:

        • CDR

        • SDR

        • vpapplog

        • vpperformance

      • Use Proposed Solution 2 for the following tables:

        • alarmrecord

        • cslog

        • csadminauditlog

      • Use Proposed Solution 3 for the vpreportresults table

  5. If the /opt/Avaya/InstallAgent/download directory uses the maximum disk space on Linux, use Proposed Solution 4 to free up disk space by removing the old ISO image files. Experience Portal stores a copy of the Experience Portal ISO image file in this directory.

    The ISO image file is used during a managed upgrade (only on Linux systems). As newer versions of Experience Portal are installed, the older ISO image files are not removed.

  6. If the /opt directory uses maximum disk space, then it is possible that there is a file that is abnormally using a lot of disk space. Experience Portal is installed in this directory (/opt/Avaya/ExperiencePortal by default. There are no Experience Portal related files in the /opt directory on Linux that use a large amount of disk space. But depending on other applications running on the EPM server, there may be components using the disk space.
  7. If another directory uses the maximum disk space, contact your Avaya technical support representative for assistance.
    importantImportant:

    Do not delete files unless the directory or file that uses the maximum disk space is identified.

Proposed Solution 1: Adjust report data retention and free disk space

Procedure

  1. Log in to the EPM web interface using an account with the Administration user role.
    importantImportant:

    As an alternative to steps 2 and 3, you can run the PurgeReportDataLocalDB and PurgeReportDataExtDB scripts. These scripts recover the disk space used by the database tables. The time taken to recover the disk space depends on the amount of data in the database tables. However, this activity purges all data in the CDR, SDR, vpapplog, and vpperformance tables. All existing data in these tables is permanently lost. For more information on purging report data, see Administering Avaya Experience Portal.

  2. From the EPM menu, select System Configuration > EPM Servers > Report Data.
    1. On the Report Data Configuration page, verify that the Purge Records option in the Report Database Record Data section is set to Yes.
    2. Depending on which table or tables has high disk use, adjust the Call/Session (CDR and SDR), Application (vpapplog), or Performance (vpperformance) retention period to a smaller number of days.
    3. Click Apply to save your changes.

      The scheduled purge tasks for the Call/Session, Application, and Performance logs are run at 02:00 hours by default, to purge records from the tables that are older than the configured retention period.

  3. After the scheduled purge task is completed (which is typically the day after you make changes to the Report Data Configuration page in EPM), stop the vpms service.
  4. To run the script, enter the $AVAYA_HOME/Support/VP-Tools/CleanLogsLocalDB <table name> command:

    The above command enables you to recover the unused disk space allocated to that table, where <table name> is the name of the table from which you want to recover disk space.

    For example: $AVAYA_HOME/Support/VP-Tools/CleanLogsLocalDB vpperformance

Proposed Solution 2: Adjust Alarm/Log/Audit retention and free disk space

Procedure

  1. Log in to the EPM web interface using an account with the Administration user role.
  2. From the EPM menu, select System Configuration > EPM Servers > Alarm/Log Options.
  3. On the Alarm/Log Options page, depending on which table or tables has the maximum disk use:
    1. Verify that the Purge Enabled option in the Alarms, Logs, or Audit Logs section is set to Yes.
    2. Adjust the Retention Period in the Alarms, Logs, or Audit Logs section to a smaller number of days.
    3. Click Apply to save your changes.

      The scheduled purge tasks for Alarms, Logs, or Audit Logs are run to purge records from the tables that are older than the configured retention period at midnight by default.

  4. After the scheduled purge task is completed, (which is typically the day after you make changes to the Alarm/Log Options page in EPM) stop the vpms service.
  5. Enter the $AVAYA_HOME/Support/VP-Tools/CleanLogsLocalDB <table name> command.

    The above command enables you to recover the unused disk space allocated to that table, where <table name> is the name of the table (alarmrecord, cslog, or csadminauditlog) from which you want to recover disk space.

    For example: $AVAYA_HOME/Support/VP-Tools/CleanLogsLocalDB alarmrecord.

    noteNote:

    The script may also take several minutes to run, depending on how much disk space is being recovered.

Proposed Solution 3: Adjust scheduled report output retention and free disk space

Procedure

  1. Log in to Linux on the primary or auxiliary EPM server. If you are an Avaya Services representative, and are using Avaya Enterprise Linux or if the Avaya Service accounts are installed on this server:

    • Log in to the local Linux console as sroot.

    • Or log in remotely as a non-root user and enter the su - sroot command to change the user to sroot.

    Otherwise, log in to Linux locally as root, or log in remotely as a non-root user and enter the su - command to change the user to root.

  2. From the EPM menu, select System Configuration > EPM Servers > Report Data.
  3. On the Report Data Configuration page, edit the Scheduled Reports section as follows:
    1. Set the Output Folder Size to a lower number in order to reduce the amount of disk space that the scheduled reports can use.
    2. Set all the Output Retention (days) settings to lower numbers to reduce the number of days the reports are retained and the amount of disk space the scheduled reports use.
    3. Click Apply to save your changes.

      The scheduled purge tasks for the reports are run at 02:00 hours by default, to purge records from the tables that are older than the configured retention period.

Proposed Solution 4: Remove older copies of the Avaya Experience Portal ISO image file

Procedure

  1. Log in to Linux on the primary EPM server.

    If you are an Avaya Services representative, and are using Avaya Enterprise Linux or if the Avaya Service accounts are installed on this server:

    • Log in to the local Linux console as sroot.

    • Or log in remotely as a non-root user and enter the su - sroot command to change the user to sroot.

    Otherwise, log in to Linux locally as root, or log in remotely as a non-root user and enter the su - command to change the user to root.

  2. Change directories to the location of the ISO image files:

    cd $AVAYA_IA_HOME/download

  3. Remove all ISO image files except the file with the newest version.
Comments on this document?
August 2025
© 2022-2025, Avaya LLC All Rights Reserved.