Enterprise Vault™ Setting up SMTP Archiving
- About this guide
- Introducing Enterprise Vault SMTP Archiving
- Installing SMTP Archiving
- Configuring SMTP Archiving
- Configuring the Enterprise Vault SMTP Servers in the site
- Adding an SMTP Archiving task and holding folder
- Configuring retention categories and retention plans
- Creating SMTP policies
- Configuring archives for SMTP messages
- Provisioning users for SMTP Group or SMTP Mailbox Journaling
- Using the SMTP dashboard
- PowerShell cmdlets
- Appendix A. Configuring target address rewriting
Assigning multiple archives to spread the archiving load across servers
In Enterprise Vault 12.3 and later, you can assign multiple archives to an SMTP Journaling routing address, or an SMTP Group Journaling provisioning group to spread the archiving load over several archives and Enterprise Vault storage servers. In previous releases of Enterprise Vault, you could only implement target address rewriting to do this.
The SMTP Archiving task stores messages that are sent to the SMTP target address based on the following criteria:
If the SMTP target address is assigned to multiple archives, the task running on the server always archives to the archive that is local to that server.
If multiple local archives are found on the server, the task chooses the archive that has the least number of items.
If any of the local archives are not available due to temporary errors such as storage is busy, the vault store is in backup mode, and so on, the task chooses a remote archive that is assigned to the SMTP target address.
As archiving continues, the task maintains a cache of archives along with the number of items in each archive. This cache is refreshed every 10 minutes. The task then switches to the archive that has the least number of items.
When the temporary errors are resolved, the task starts archiving to the local archive. If none of the assigned archives are available, the SMTP task reports an error in the event log.
You can assign multiple archives when you create the routing address or provisioning group, or by editing the target properties.
To spread the archiving load optimally, we recommend that you assign each routing address or provisioning group to archives in different vault stores hosted on different Enterprise Vault storage servers.
If you have a software or hardware load-balancing solution, you need to configure it to receive messages addressed to the routing addresses, and distribute the messages to the Enterprise Vault SMTP servers.