The Zimbra-archiving package can be installed and configured on an existing single-server deployment or on a multi-server deployment as an upgrade to ZCS, and archiving is enabled on each MTA in your ZCS deployment.
If the mailbox server and the MTA server reside on the same node, you configure and enable archiving as a single upgrade process. If your mailbox and MTA servers are on separate nodes, the zimbra
-archive package is installed first on at least one mailbox server and then the archiving component is enabled on each MTA in the deployment.
In this upgrade process, it is assumed that the LDAP, MTA, mailstore and archiving servers are on the same node. To install archiving in a single-server deployment, you have to:
|
3.
|
Type Yes for zimbra-archiving when presented with the packages to be installed.
|
The following upgrade scenario assumes that the LDAP server, MTA server(s), and mailstore server(s) have ZCS installed correctly. You are now adding a new server that will be dedicated as a archiving server to this environment.
When you add archiving and discovery to an existing ZCS multi-server environment as a dedicated archiving server, you install the zimbra-archiving package and the zimbra-store package on the dedicated server, and you enable archiving on each MTA server in your deployment.
Before beginning the install process, note down the following information. You need this when you install the archiving server. Run the
zmlocalconfig -s command to find the information.
|
2.
|
Type y and press Enter to install the following packages:
|
|
3.
|
Type y and press Enter to modify the system.
|
|
5.
|
Select the Common Configuration menu and configure the LDAP Hostname, LDAP password, and LDAP port.
|
|
6.
|
Select the zimbra-store menu and configure the Admin password and the License file location.
|
Complete the installation process following the steps under Installing Zimbra Mailbox Server. At this point the Discovery feature is installed and can be used.
After the archiving package has been installed on the archiving server, you must enable archiving on each MTA server in the deployment. Complete the following on each MTA server. This is run as zimbra.
In a multi server deployment with a dedicated archive server, you create a dedicated archive COS for the server. This COS is set up on the archive server as a dedicated host. The server is removed from the COS server pool so that the archive server is not randomly assigned to new accounts.
You can create the COS from the administration console or from the CLI. Attributes can be configured in the COS to set mailbox features, quotas, and password, turn off spam and virus checks and to hide the archive accounts from GAL. In addition to setting these attributes, you remove the archive server from the COS server pool.
Create a new dedicated COS configured correctly for your archive accounts. To remove the server from the server pool, in the Server Pool tab deselect the archive server.
zmprov gs -e local host.com zimbraID
|
The amavisd-new server process controls account archiving as well as antivirus and antispam processes. The
zmarchivectl command can be used to start, stop, restart or obtain the status of the amavisd-new server process that controls account archiving. Caution should be taken when starting or stopping the archiving process as it is a shared server process between archiving, antivirus, and antispam processes. Performing actions on any of them affect any of the other services that may be enabled in your deployment.
To set up archiving for a mailbox two attributes are configured on the primary user’s mailbox. One attributed enables archiving and the second shows where messages are being archived.
|
•
|
zimbraArchiveAccount — Any previous and current archive addresses that this mailbox was archived to.
|
In order to construct archive account names, Zimbra supports two attributes that establish the archive naming conventions. These attributes are used to create and manage archive accounts naming scheme. You can set up these attributes either by COS or by account. For COS, these attributes can be changed using
zmprov mc.
For accounts, use
zmprov ma.
|
•
|
zimbraArchiveAccountDateTemplate. This attribute sets the date format used in the name template. The default is yyyyMMdd. Adding the date to the account name makes it easier to roll off older data from the system to backups.
|
|
•
|
zimbraArchiveAccountNameTemplate. This attribute sets up how the archive mailbox name is created. The default value is ${user}-${date}@${domain}.archive. The archive account address would be like this example: user-20070510@example.com.archive. If you change the default value, you must use syntax that creates a valid email address. We recommend that you add .archive to all archive accounts to create archive mailboxes in a non-routable domain to prevent spoofing of the archives.
|
Archive mailboxes are created using the CLI, zmarchiveconfig. The following archiving scenarios enable archiving for an account:
|
2.
|
Type zmarchiveconfig enable <account@example.com> archive-cos <cosname>
|
|
•
|
The attribute zimbraIsSystemResource is added to the archive account and set to TRUE.
|
|
2.
|
Type zmarchiveconfig enable user@example.com.
|
|
2.
|
Type zmarchiveconfig enable <account@example.com> archive-address account-archive@offsiteserver.com archive-create false.
|
When the archiving and discovery feature is installed, you can search across mailboxes using the discovery tool either from the administration console or through the command line interface.
The discovery tool, Search Mail, is added to
Tools on the administration console Navigation pane when the archiving package is added. When you click
Search Mail, a search wizard opens, allowing you to configure the following information:
|
•
|
Target mailbox and folders. One target mailbox and folder is created automatically. You can use this mailbox for all your search results and create new folders for each search, or you can create a new target mailbox for each separate search.
|
Note: A target mailbox is like any other mailbox and can have any features or preferences that are defined by the COS or by account. Target mailboxes are listed in the administration console Accounts list. You may want to give the target mailboxes account names that identifies them as target mailboxes for cross-mailbox searches and configure a COS specific for target mailboxes to be able to manage access. For example: CMS_user1.example.com. CMS is a prefix that means
cross
mailbox
search. With this practice, all target mailboxes are listed together
|
•
|
The Maximum number of messages field can be used to limit the number of messages that are returned from the search. If this field is blank or 0, all messages that meet the search criteria are returned.
|
|
•
|
You can select to automatically notify interested parties when the search is complete. The email notification includes the search task ID and status on the subject line and you can specify the type of to include in the message, such as the number of messages found, the list of addresses resulting from the search and the search query used.
|
|
•
|
Create the search query. You can search outgoing and incoming email by date, from, to, cc, subject, keywords, and attachments. Advanced Search can be used to quickly create a query to search by name, dates and time ranges, distribution list, aliases. For a list of the search grammar that can be used see the Zimbra Wiki, Search Tips article.
|
When you use the discovery feature in the administration console, the tool makes copies of messages in the target mailbox you create. The messages occupy server space, increasing the size of your server. You may want to delete these messages from the target mailbox when they are no longer needed.
Use the CLI command, zmarchivesearch to run the cross mailbox search from the command line.
For more information about zmarchivesearch, refer Appendix A, Command-Line Utilities.
Copyright © 2008 Zimbra Inc.
