Enterprise Vault.cloud™ Legacy Import Guide

We recommend that your organization provide the Veritas data management team with a list of user email addresses and their respective PST files. The Veritas data management team can use this list to map the PST files to user accounts.

Duplicate copies of interoffice email messages or messages that use common names may be retained in Enterprise Vault.cloud. The duplicate copies appear when the same message is imported and journaled to Enterprise Vault.cloud. Each message that is added to Enterprise Vault.cloud is given a unique hash key containing information about the Company ID, Subject, Date, Sender, and Recipient of the message. Since an imported interoffice message with only a common name has a different hash key than the same journaled message, the messages are not recognized as duplicates.

Legacy email messages that are sent to a Global Address List (GAL) contact are assigned to a user account using a common name. Since the message header of an email message that is sent to a GAL contact contains only a common name, there is no SMTP address in the message header. As a result, duplicate copies of these messages may be assigned to multiple user accounts.

If two users have the same common name, legacy email messages may be assigned to the wrong user account if assignment by common name is used. A forced-mapped PST file legacy import is required to address this issue.