Legacy Archive Data Management

Document created by user.oxriBaJeN4 Employee on Sep 7, 2015
Version 1Show Document
  • View in full screen mode

Welcome to the Legacy Archive Data Management guide, which details the process and requirements to ensure a smooth, efficient and successful import of historical email data. As an existing Mimecast customer, you are either planning to or are already archiving your emails.  Legacy Archive Data Management is the process that allows you to import historical email data into your Mimecast archive.  In this way, users will be able to search through email data that was processed before Mimecast had been implemented for the organization.

 

Process Overview

StepProcessDescriptionResponsibility
Step 1: Collection of legacy dataExport and Collect Data

The data is collected from your environment using the guidelines specified for accepted formats, types and sizes. It is important to consider the advantages of grouping the data, and to follow the file naming and folder structure conventions. View the related article for additional information on de-duplication and common export methods.

 

The Legacy Archive Data Management team will then provide the appropriate transfer information for your Ingestion, and you are then able to transfer the data to Mimecast.

Customer
Step 2: Legacy Archive Data ManagementImport DataMimecast prepares to process and import the received data, and checks the information received for accuracy.Legacy Archive Data Management Team
Step 3: VerificationComplete and VerifyYou will be notified once the import is complete, and requested to verify that all information is now available to users.Customer

 

For assistance in collecting your historical data, contact your Mimecast representative to inquire about our Intelligent Data Migration (ID) service.

General terminology

The following terms will be used throughout this guide:

TermDescription

PU

Per User: Messages within PST file(s) or EML folder(s) are grouped by each individual user that should have access to them
NPUNot Per User: Messages within PST file(s) or EML folder(s) are not grouped per user, but are typically grouped by date and are often journal data
SJFStandard Journal Format: A standard copy of a journaled message (these message do not include the members of groups or BCC recipients)
EJFEnvelope Journal Format: A journaled message that contains all sender and recipient details including all SMTP addresses, BCCs and recipients distribution list members. The original message is attached to the envelope message
Journal DateThe specific date that Mimecast was archiving all of your emails, which includes inbound, outbound and internal emails (using Journaling).  This is commonly the date defined as the ingestion cutoff date
Cut-off DateMessages dated later than this date are not Ingested in order to reduce duplication of messages in the archive
Mailbox OwnerAccount that must have access to all messages within PU PSTs or PU EML folders
Mimecast accountThe account PU data is being ingested into which is typically their current full primary SMTP email address which they send and receive emails on and log onto Mimecast to view their messages
Single InstanceOne copy of an item irrespective whether it contains multiple recipients
LEDNLegacy Exchange distinguished names commonly known as exchange address
ADActive Directory

Attachments

    Outcomes