Configure VaultBoxes

To use the Historical Mail feature, you must deploy one or more VaultBox systems in your environment.

The VaultBox coordinates the transfer of data from your organization’s Exchange servers to the data center. You can view VaultBox status and set parameters governing data transfer using the VaultBox Console.

To launch the VaultBox Console, select Start > Programs > Aurea > VaultBox Console on the machine on which it is installed.

From the VaultBox Console you can:

  • Start and stop Storage Management and edit Storage Management settings. If your organization uses the storage management feature, you must configure additional VaultBox settings. See Configure Scanning and Data Transfer for Storage Management Policies for more information.
  • Start and stop User Classification Retention and edit User Classification settings. If your organization uses the user classification retention feature, you must configure additional VaultBox settings. See User Classification Retention Policies for more information.
  • View Transfer Service Status fields. These include the following parameters:
  • Queue — The number of messages to be transferred to the data center
  • Rate — The transfer speed, in messages/second and KB/second
  • Free Space — The amount of space remaining on the VaultBox

Change data transfer settings

  1. In the VaultBox pane, click Configuration.
  2. Click the VaultBox tab to display data transfer settings.
  3. VaultBox configuration tab

  4. The Outbound Bandwidth pane controls data transfer between the Transfer Service and the data center.
  5. In the Number of connections field, use the up/down arrows to alter the number of connections (threads) used by the process.
  6. In the Bandwidth utilization limit field, change the amount of bandwidth used for data transfer.

    NOTE

    A setting of 0 in the Bandwidth utilization limit field allows unlimited usage.

  7. The Free Space Margin pane configures the VaultBox to send a warning message to the server when free space on the VaultBox machine falls below the set margin. In the Minimum available space field, set the threshold below which the storage management task should send a warning.
  8. Click OK.

Monitoring VaultBoxes

Typically, you monitor VaultBox status through the VaultBox Console and AMS Admin Console. However, if your organization uses a third party monitoring tool, Support recommends that you also monitor the data described in the table below.

NOTE

Several of the troubleshooting suggestions below require you to telnet to the [hostname] of the data center used by your organization: Chicago Data Center (CAWS), London Data Center (LAWS), Plano Data Center (PAWS).

Data Type Description Alert When Troubleshooting Suggestions

Free space on each designated VaultBox system

Ensure that adequate free space remains on both the C drive of the VaultBox system (where IIS puts intermediate files), the drive location of the VaultBox cache directory, and the Compression Directory.

Drive is 10% full

  1. Clean up disk space outside of [Data Drive}:\activemailbox\compressiondir*.*
  2. If used disk space still exceeds 10%, verify the Vaultbox can connect to the data center, as follows: telnet [hostname]22
  3. If you do not get an OpenSSH response, the port is likely blocked; check the firewall.
  4. If the connection is good, shut down, then restart the transfer service.
  5. Wait one hour. If the disk space has not reduced, collect the SRTransferService.log files, and contact Support.

Number of files in a directory

[Data Drive}:\activemailbox\
compressiondir*.*

More than 1000 files are present

  1. Verify the Vaultbox can connect to the data center, as follows: telnet [hostname]22
  2. If you do not get an OpenSSH response, the port is likely blocked; check the firewall.
  3. If the connection is good, shut down, then restart the transfer service.
  4. Wait one hour. If the number of files has not reduced, collect the SRTransferService.log files, and contact Support.

Timestamp of files in a directory

{Data Drive}:\activemailbox\compressiondir*.*

Oldest file is older than 60 minutes

  1. Verify the Vaultbox can connect to the data center, as follows: telnet [hostname]22
  2. If you do not get an OpenSSH response, the port is likely blocked; check the firewall.
  3. If the connection is good, shut down, then restart the transfer service.
  4. Wait one hour. If newer timestamps do not appear, collect the SRTransferService.log files, and contact Support.

CPU utilization

Using the Windows Performance Monitor, verify that the Total instance of the% Processor Time counter of the Processor performance counter object is less than 80 percent.

Performance counters

The Message queue size counter of the Transfer Service object should be less than 10,000. Other counters under the Transfer Service are also useful for determining daily message volume.

Services

If you are using a separate monitoring tool, include the following services for your VaultBox system:

SMTPSVC, which appears as Simple Mail Transfer Protocol (SMTP)

srtransfersvc, which appears as Selective Replication Transfer Service

Selective Replication Transfer Service stops

  1. Restart transfer service
  2. Examine general system logs for other service failures or system errors
  3. If service fails to restart, or fails again within a 24-hour period, contact Support

Store driver and IIS SMTP service

Mail is not reaching the Vaultbox, or is not being transferred to the data center

  1. Verify the SMTP service on the Vaultbox is running.
  2. Verify that the POP3 service on the Vaultbox is NOT running.
  3. Verify the Store Driver is connected to the SMTP Service (the AMS Admin Console Readiness check will indicate an error).

Messages rejected by a VaultBox

Messages are being rejected by the VaultBox, with error messages in the following form:

<xxxxx.xxx@ems-1.activemailbox.net>: 554 5.7.1

<xxxxx.xxx@ems-1.activemailbox.net>: Recipient address rejected: Access denied

These are fatal delivery errors most commonly caused by incorrect DNS configuration. Your SMTP server will not attempt to redeliver the messages to the VaultBox. You must take action to get these failed messages into the archive.

Any message of this form is thrown.

  1. Contact AMS Support to correct your DNS configuration.
  2. Work with AMS Support to schedule a historical import to get the failed messages into the archive.