|
While upgrading Experience Portal on Red Hat Enterprise Linux, the Experience Portal database upgrade uses approximately four times the size of the database backup. For example, a system with a backup of 10 GB needs approximately 40 GB of free space to successfully upgrade the database.
To prevent upgrade failure due to space constraints, monitor and estimate hard disk space usage during the upgrade process. The system retains some of the files used in the upgrade process for backup. However, you may either delete these files, or move these files to a different location during or after the upgrade to maximize the available hard disk space. The following table describes some of the database files used during upgrade, their locations, their approximate sizes relative to the database backup, and if you can delete or relocate these files safely. Avaya recommends you to retain these files in a different partition or hard drive, for backup purpose.
| Description | Location | Size compared to database backup | When it is safe to delete |
|---|---|---|---|
| Experience Portal backup file | You can select the location | – | You may delete this file after you run the script RestoreProps.sh successfully. |
| Database export file |
/var/lib/pgsql/vp_upgrade.export_vp_<date>
Where <date> is the date of installation. |
Same as the database backup. |
After the Experience Portal prerequisite installer successfully installs the updated
PostgreSQL database.
Ensure that the PostgreSQL field indicates Success. |
| Experience Portal database | /var/lib/pgsql/data | The size varies from 10% to 100% larger than the database backup directory. | Do not delete this directory. Deleting this directory causes loss of data. |