IGA limiting snapshot sizes for database retention

Idea ID 2783481

IGA limiting snapshot sizes for database retention

Are there ideas in place for future releases to limit how fast the db grows with snapshots...

Such as having a master snapshot that isn't touched and then just have deltas written out for consecutive snapshots. If a new identity or application source, etc, is detected it takes a new master snapshot and the old master snapshot is held for retention values for the customer to clean up as desired.

Idea is that if an environment is fairly stagnant but they run collections often, you wouldn't have a lot of snapshots, just deltas.

Customer is concerned with how fast the snapshots grow the database and how much retention they can have for reporting, etc. Granted, this is my limited knowledge of the architecture and
scalability factors.
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.