Oracle DIVAdirector: How To Check Why DIVADirector Postgres DB Backups Increase in Size or are Larger Then Postgres DB Size on Disk
(Doc ID 2047861.1)
Last updated on MAY 06, 2019
Applies to:Oracle DIVAdirector - Version 5.2 and later
Information in this document applies to any platform.
DIVADirector Postgres DB Backups are expected to be x2 to x4 larger than the database itself. This is due to the fact that DB Backups are stored in plain text.
However, when the relative size of the database grows quickly, or when Postgres DB Backups are increasing significantly from day to day, one could suspect a DB table bloat or unwanted size increase.
Such DB table increases can be linked to:
- Significant addition of new Objects in DIVArchive => DIVADirector discovers these new objects.
- Significant drop of metadata text in DIVADirector.
- Full population of tc_breaks per Proxy => adds a lot of space to the backups since these are stored as raw byte arrays.
- Configuration change increasing the number of stored additional frames per Proxy.
- Previous backups were running into space constraints on the disk and were not as large as they should have been.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document