One, or more of the following issues may be happening:
To determine the issue:
1. Run a Size Report
2. After the report is run, look for ASSET_HISTORY within sizereport.txt. Typically it shouldn’t be bigger than a few GB for SMAs with less than a few thousand nodes, but how long the appliance has been running also factors into the size as well. If unsure, check with our support team.
How much Asset History should I keep?
This really depends on the business needs.
Some business have certain requirements where all history of changes must be kept, but for most customers, they do not need to keep all history.
If all the Asset History is REALLY NEEDED, then by all means, keep all of it. Just know that this will cause performance issues over time.
Setting the Retention to anything other than Forever is best so that history doesn’t grow endlessly without getting pruned.
I set my retention down, but my Asset History is still too big. What should I look at?
Running a Reboot and Check Database may help by optimizing Database tables. This can be done by going to Settings | Appliance Updates | Reboot and Check Database
Note: Running this type of Reboot may take several hours to complete.
This should be done at least one day after the retention is lowered, to avoid disrupting the cleanup process mentioned above.
If after running the Reboot and Check Database and the size is still big, please contact Support.
