Overview
The Archive Store Schedule enables you to set the frequency with which Archiver automatically starts archiving emails to a new Archive Store.
IMPORTANT
Changing these settings can affect performance. We recommend configuring your Archive Stores to roll-over on a Bi-Monthly schedule. This way, databases should stay at a more manageable size, which is beneficial if there is a need to move the database or rebuilding its search index. A Bi-Monthly archive store should also have some performance gains when searching. For example, to search for an email dated February 2012, GFI Archiver searches a small Bi-Monthly database instead of a large yearly database, hence providing faster retrieval.
GFI Archiver changes the Archive Store based on a specifically configured time schedule. This feature is available for all types of databases used with Archive Stores. The available options are:
- Monthly;
- Bi-Monthly (default);
- Quarterly;
- Half yearly;
- Yearly.
NOTE
If an Archive Store exceeds the maximum database size, GFI Archiver automatically creates a new Archive Store based on the configured New Archive Store Settings. This feature is only available for Archive Stores based on SQL Server® Express databases.
Solution
To change the Archive Store Schedule, follow the steps below.
1. From the Configuration tab, click Archive Stores.
2. Select Schedule Archive.
3. Select one of the available options and click Save.
Verify whether the desired option is selected accordingly.
Testing
Make note of when the next occurrence of the scheduled time will occur by navigating to the following.
- From Configuration tab, click Archive Stores.
- Select Schedule Archive.
- Verify or Select from one of the available options; Monthly, Bi-Monthly (default), Quarterly, Half yearly, Yearly and click Save.
For example if you selected Monthly, at the beginning of the next month navigate to the database location and verify the new database was created. Depending on the type of database configured in New Archive Store Settings verify the database is created in the appropriate location.
For example when configured to use SQL, launch SQL Server Management Studio and confirm a new database with the naming convention configured via the above rules is created at the specified interval.