This topic illustrates the effect of archiving on the contents of your repository and describes a possible archiving strategy.
Effect of archiving
The following figure illustrates the effect of an archive whose start date is January 8, 2008 and whose end data is January 10, 2008.
An Archiving Strategy
Decide on an archive strategy and frequency that is appropriate for your volume of data. You should also decide if you want your archive to commence immediately or not.
For example, let's say you decide to keep up to 4 months worth of data in your FortiDB repository. In this case, you might wait 4 months after installing FortiDB before archiving for the first time, then specify (in the Archive Period field of the Archive tab) "3 Month(s) and older".
Three months' worth of data would then remain in your repository.
You could either run a "3 Month(s) and older" archive manually every month, or automate the process by scheduling it to occur at an interval or on a specified day of the week or month.
