If your ADOM data policy is set to keep logs for 365 days, but logs are being deleted too early, what is likely the issue?

When you set a data policy in an ADOM (Administrative Domain) to retain logs for a specified duration, such as 365 days, the actual retention is also heavily influenced by the disk quota configured for that ADOM. If the disk quota is too low, it can't accommodate all the logs generated within the desired retention period.

When the allocated storage reaches its limit, the system has to take action to free up space. This often results in the deletion of older logs prematurely, despite the configured retention policy stating that logs should be kept for 365 days. Hence, if logs are being deleted earlier than expected, checking the disk quota assigned to that ADOM is crucial, as it directly impacts the ability to maintain logs for the full duration specified in the data policy. Properly adjusting the disk quota can help ensure that logs are retained as intended.