Fortinet Document Library

Version:


Table of Contents

6.2.0
Download PDF
Copy Link

Allocate quota and set log retention policy

Ensure your quota settings is sufficient to fulfill your log retention policy. You must keep enough log data to meet your organization’s reporting requirements. Configure quota settings and the log retention policy to ensure there is enough time to generate all scheduled reports.

Log View > Storage Statistics shows graphs with trends to help you with this planning.

If you are using ADOMs, ensure the quota is sufficient for every ADOM. Allocating insufficient quota to an ADOM might cause the following issues:

  • Prevent you from meeting your log retention objective.
  • Waste CPU resources enforcing quotas with log deletion and database trims.
  • Adversely affect reporting when quota enforcement acts on analytical data before a report is complete.

For analytics, ensure the quota is sufficient and the retention period is long enough to complete all scheduled reports. When reports are generated and the log retention period is past, there is no need to keep analytical data since it can be regenerated from the original archived log data.

Note

It is recommended that archive data be retained for a longer period than the analytic log data. The archive data is needed to regenerate analytic data in the event of a rebuild, such as may occur automatically during firmware upgrade.

Allocate quota and set log retention policy

Ensure your quota settings is sufficient to fulfill your log retention policy. You must keep enough log data to meet your organization’s reporting requirements. Configure quota settings and the log retention policy to ensure there is enough time to generate all scheduled reports.

Log View > Storage Statistics shows graphs with trends to help you with this planning.

If you are using ADOMs, ensure the quota is sufficient for every ADOM. Allocating insufficient quota to an ADOM might cause the following issues:

  • Prevent you from meeting your log retention objective.
  • Waste CPU resources enforcing quotas with log deletion and database trims.
  • Adversely affect reporting when quota enforcement acts on analytical data before a report is complete.

For analytics, ensure the quota is sufficient and the retention period is long enough to complete all scheduled reports. When reports are generated and the log retention period is past, there is no need to keep analytical data since it can be regenerated from the original archived log data.

Note

It is recommended that archive data be retained for a longer period than the analytic log data. The archive data is needed to regenerate analytic data in the event of a rebuild, such as may occur automatically during firmware upgrade.