Veritas Enterprise Vault™ Setting up SMTP Archiving
- About this guide
- Introducing Enterprise Vault SMTP Archiving
- About Enterprise Vault SMTP Archiving
- About SMTP Journaling
- About Selective SMTP Journaling
- About SMTP Mailbox Journaling
- Configuring SMTP Journaling and SMTP Mailbox Journaling
- Configuring Selective SMTP Journaling and SMTP Mailbox Journaling
- Using Exchange Server to journal messages to Enterprise Vault
- Installing SMTP Archiving
- Configuring SMTP Archiving
- Configuring target address rewriting
- PowerShell cmdlets
About target address rewriting
If a high volume of SMTP traffic is sent to Enterprise Vault using one or two SMTP routing addresses, you can use a load balancing solution to distribute the incoming messages across a number of Enterprise Vault SMTP servers. For example, a simple load balancing solution is to configure equal preference MX records in DNS for the Enterprise Vault SMTP servers.
In Enterprise Vault SMTP Journaling configurations that use a single SMTP routing address to send messages to Enterprise Vault, all the messages are stored in the archive that is associated with the routing address. You can implement target address rewriting on each SMTP server to distribute the archiving load over several archives and Enterprise Vault storage servers. With target address rewriting, the messages that arrive at each SMTP server are redirected to a different target address and archive.
The instructions in these sections describe how to set up target address rewriting on the Enterprise Vault SMTP servers. Instructions on how to set up DNS MX records for load balancing are not included in this guide.
Figure: SMTP Journaling without address rewriting shows an example environment where equal preference MX records provide basic load balancing of incoming messages across several Enterprise Vault SMTP servers. The example Enterprise Vault environment is configured as follows:
All SMTP messages are sent to the same SMTP routing address, SMTPjournal@example.com.
SMTP messages for SMTPjournal@example.com are evenly distributed across the different Enterprise Vault SMTP servers.
In the Enterprise Vault Administration Console, SMTPjournal@example.com is configured as an SMTP target address, and enabled for archiving. The archive that is configured for this target is SMTPjournal.
With this configuration, all the SMTP messages are stored in the one archive, SMTPjournal.
In the above example, the SMTP traffic is distributed across several Enterprise Vault SMTP servers, but all of the servers store the messages in the same archive. To spread the archiving load over several archives, you can implement target address rewriting on the SMTP servers. This is illustrated in the following example.
The example environment in Figure: SMTP Journaling with address rewriting is configured as follows:
As in the previous example, all SMTP messages are sent to the same SMTP routing address, SMTPjournal@example.com.
In the Enterprise Vault Administration Console, SMTPjournal@example.com is configured as an SMTP target address. As address rewriting will send the messages to different target addresses and archives, this target address is not enabled for archiving.
To implement address rewriting, alias entries are added manually to the aliases files on each of the SMTP servers. On the first SMTP server, for example, the alias might be SMTPserver1. The target routing address in each message that is received by this server is then rewritten as SMTPserver1@example.com.
On the second SMTP server, if the alias is SMTPserver2, the target routing address in each message that is received by this server is rewritten as SMTPserver2@example.com, and so on.
In the Enterprise Vault Administration Console, the alias address for each server, SMTPserver1@example.com, SMTPserver2@example.com, and SMTPserver3@example.com, is configured as an SMTP target address, and enabled for archiving.
Enterprise Vault stores the messages in the archive that is associated with the target address. The archive SMTPjournal1 is associated with the target SMTPserver1@example.com, the archive SMTPjournal2 is associated with the target SMTPserver2@example.com, and so on.