Adding additional disk space to the Experience Portal system

Last Updated : Jun 15, 2021 |
Prolog information
Metadata
Keywords:
You can expand the amount of space in the root file system of Experience Portal. The root file system is where /opt/Avaya is installed which includes log partition.
You can enable additional disk space for the following:
  • Systems deployed using one of the 8.x OVA’s (Primary, Auxiliary, or MPP)
  • Systems deployed from the 8.x AVL ISO using the fresh installation option
Note:
You cannot enable disk expansion on any system upgraded from Experience Portal 6.x or 7.x.
Use this procedure to expand the size of the root partition to add additional disk space to the Experience Portal system.
  1. Deploy Experience Portal OVA/AVL.
    ADDITIONAL INFORMATION:
    For more details on deploying the Experience Portal virtual application, see the Deploying Experience Portal in an Avaya Customer Experience Virtualized Environment guide.
  2. Power down the system.
  3. Using a hypervisor tool (such as VMware), dynamically increase the size of the disk.
    ADDITIONAL INFORMATION:
    Note:
    You can only increase the existing disk size, but not decrease the disk size.
    VMware does not allow the expansion of disk size when there are snapshots present.
  4. Power on the system.
  5. Log on to the Experience Portal server as a user with root privileges.
  6. Run the df / command to check the partition size.
    ADDITIONAL INFORMATION:
    If the disk is full, there may be system instability. You need to enable expansion before running out of space.
  7. Run the /opt/Avaya/LinuxInstaller/bin/expand_root.sh command and monitor the messages the system displays on the screen.
    ADDITIONAL INFORMATION:
    For example,
    [AEP ~]# /opt/Avaya/LinuxInstaller/bin/expand_root.sh
    ok to expand, let’s keep processing...
    Let’s expand the space by 640716802 sectors.
    Space expanded
    The expand_root.sh script verifies the ability for the disk to expand. If there are any reasons to prevent expansion, the system displays a message and exits.
    For example:
    • Expand only supported when '/' is the last partition on the drive
    • Expand only supported for new builds, not updates from AAEP 7.x
    • Stop: the disk is fully utilized, nothing to do.
  8. Do the following to reboot the system to enforce the new drive size in all locations:
    ADDITIONAL INFORMATION:
    Note:
    If EPM/MPP is not yet installed on the server, you can directly reboot the system.
    1. Log into the Primary EPM web interface as a user with the Administration role.
    2. If the MPP was expanded, do the following:
      ADDITIONAL INFORMATION:
      • Click System ManagementMPP Manager.
      • On the MPP Manager page, reboot the MPP server.
    3. If the EPM was expanded, do the following:
      ADDITIONAL INFORMATION:
      • Disable the EPM server.
        • If the EPM server contains an email processor, use the Email page to disable the EPM server.
        • If the EPM server contains an SMS processor, use the SMS page to disable the EPM server.
      • Click System ManagementEPM Manager.
      • On the EPM Manager page, reboot the MPP server.
        Note:
        After rebooting the Primary EPM server, you need to log into the EPM web interface again.
      • Enable the EPM server.
        • If the EPM server contains an email processor, use the Email page to enable the EPM server.
        • If the EPM server contains an SMS processor, use the SMS page to enable the EPM server.
  9. Log on to the Experience Portal server as a user with root privileges.
  10. Run the df / command to check the partition size.
    STEP RESULT:
    You can view the system with the new increased disk size.