Best Practices - Domino Mailbox Archiver

Migration Archiving

For migration archiving scenarios, it is strongly recommended that the Do Not Create Stub rule in the Archive Rules | Stub Rule tab remain deselected. This configuration ensures that users can recover any migrated messages by double-clicking the stub icon created during the archive process. If you choose not to create a stub for archive messages by selecting the Do Not Create Stub option, you must manually browse for any archived messages.

Recovering to a Different Client

During the archive phase, Design Documents are not archived and users are not able to see the recovered data, if using out-of-place recover.

The workaround is to create a replica of the original database in the destination client, then perform out-of-place recover with overwrite option.

Creating Multiple Subclients to Reduce Backup Time

If the setup is huge (like having more than 2K mailboxes, 1 TB database and 500 TR logs/day), then it is useful to split the database into multiple subclients. This will reduce the backup time considerably by running the backups on all the subclients simultaneously. However, your server should be powerful enough to tolerate the load of all the backups running simultaneously.

Configuring Subclients for Department Based Auto Discovery

If your mailboxes belong to a particular department in a subclient, then it is advised to configure subclients for department based auto discovery rather than running a manual discovery each time a mailbox is added.

Using Notes Add-In for Offline Archiving

It is recommended to use Notes Add-In for offline archiving, so that you can retrieve your emails even when you are not connected to the Domino.

Using Proxy to Reduce Domino Load

Use a proxy machine to reduce load on your Domino by triggering the binaries on the proxy machine.

DAOS links are not preserved during Domino Mailbox Archiver Agent recoveries. To reintroduce these links, the following compact operation must be performed:

load compact -C -daos on test.nsf

For offline archival purposes, it is recommended that the attachments are integrated into the NSF files prior to archiving using the following command.

compact -c -daos off

Disabling Directory Assistance to Reduce Archiving Time

If Directory Assistance (DA) is enabled on the Domino, then use dDisableDADB key to skip scanning all the directories. After enabling this key, the archiver looks only for the primary Domino Directory (NAMES.NSF) and skips all the other directories which are there in the DA database. To enable this key, set the value to one.

Configuring Domino Database to Delete Duplicate Emails on IMAP Clients Before Archiving

If you use an IMAP client to access your emails, you can configure the Domino database to get rid of the duplicate emails before archiving your emails.

For steps to configure the Domino database, go to the Knowledge Center website, Using the conversion utility to add IMAP summary attributes to messages.

Domino Mailbox Restore Consideration

In a Domino environment, data restored on one server will not propagate to other servers within the Domino environment. In such cases, the restored mailboxes will be overwritten by the existing mailboxes during replication. To avoid these conflicts, perform any restore operations using the out-of-place restore method.

After upgrading to a new Commvault software service pack, it is a best practice to restart the Domino Server to kill the running processes, if any. Else, you might face issues with backup and restore operations after the service pack upgrade.

Shut Down the Domino Server

If the Domino Mailbox Archiver is installed on the client where you plan to install the service pack, shut down the Domino server to avoid errors during the installation.