Enterprise Vault.cloud™ Archive Administration Help
- Getting started with Archive Administration
- Archive Overview
- Customer Dashboard
- My Config
- About Provisioning
- About Managed Tags
- About Account Management
- Archive Collectors
- About Exchange Online Archiving
- About Bloomberg Archiving
- About Microsoft Teams Archiving
- Role Management
- Policy Management
- Import Data
- Authentication Management
- AD FS Configuration Guide
- Retention Management
- Continuity Management
- Reports Management
- Notification Management
- Personal.cloud Deployment for IBM Notes
- Archive Administration Updates in Previous Releases
- Archive Administration Known Issues
About Import Data
Every company has existing emails, whether located in active user mailboxes, personal stores, document management systems, or other communication libraries. You can consolidate some or all of these legacy email sources into your Archive. This section outlines the data import process, explaining how your company's legacy email can be transferred to the Archive correctly-- and in its entirety.
Legacy email refers to data sitting on local archives on desktops or laptops, email storage on servers, or email on backup tapes. By moving your legacy email into the Cloud Archive, you have a complete, living record of your past and present email history.
The legacy email has context, unlike active email that is saved into your Archive via journaling. A journaled message is captured in transit and saved in its original, pristine form, while legacy email may have been altered before it is placed in the Archive. Legacy messages have previously arrived within the user mailbox and may have been copied into a folder, forwarded to other recipients, or otherwise acted on by the user.
Messages may also have metadata fields altered when information is copied into .PST files. To capture the additional information of a legacy message, the import process into the Archive is entirely different than the transfer of journal email. During this process, all legacy email contextual elements are preserved.
You can import legacy email into the archive using Enterprise Vault.cloud Archive Administration. You can use the Import Data feature to import items into archives. You can upload items up to 12 GB per calendar year (January 1 to December 31). Over the period of one year, you may choose to upload an item of 12 GB in one go or upload multiple smaller items with a collective size of a maximum of 12 GB.
You need to collect the legacy email in the proper format from your email environment and then send-- either electronically or physically-- to Veritas for import into the archive in the following scenarios:
If the .PST file that you want to import is larger than 12 GB and less than 20 GB.
If the file format is .EML, .MSG, or .NSF
Guidelines to use the Import Data feature:
.PST file names should not contain commas. However, special or double-byte characters are allowed.
.PST files need to be 12 GB or less in size.
.PST files cannot be password protected.
Run scanpst.exe, a utility included with Microsoft® Outlook, to determine if your PST files are corrupt before uploading the data to ensure the ingestion of the PST's into the archive.
A message size limit of 50 MB is applicable for imported and journaled email messages. Any oversized messages will not be imported. A report is provided for any message that exceeds this limit.
Non-email items such as drafts, tasks, and calendar entries are not imported. Read receipts and calendar notice acceptances can be imported.
The Import Data feature is available for administrators of those customers for whom the Enable Import Data check-box is selected while creating or updating the customer. The users who have the Import Data privilege can view the Import Data option.
Summary and detailed report for the uploaded .PST files with the count and size of emails imported is available in the reports section of Manage Archive. See Creating a Messaging Report..