Ingesting the same pst multiple times

[pjglick]

We are manally importing pst files into mailboxes and then letting the archive tasks handle the move to the archive.  We have a situation where pst may not have been imported.  If we import the pst into the users mailbox what would happen within the archive if this is the second time a pst has been imported?  Will there be duplicates within the archive if the messages are imported back into the same folders within the mailbox?

Paul

[TonySterling]

Yes, if you copy the data to the inbox again then there will be duplicate messages in the archive.

What is the process you are using to move the pst to the mailbox?  Are you putting them under a specific folder so you could check to see if it is already there?

[pjglick]

Since we are new to this my thought we be to do the following.

Export the users entire archive to PST file

Delete the Archive

Ingest archived pst file back into the users mailbox (does this change the create date)

Re-ingest original pst files.  (Duplicates should be handled via this process)

Re-enable the user for archive

Will there be any issues when archiving is re-established since the evault system will know that there is a deleted archive for this user?  Will it be seen twice in the list of archived users?

Thanks

Paul

[TonySterling]

Hi Paul,

Could you clarify why you are doing this?  What I don't understand is why you would export the archive to a PST when you could export it back to the mailbox.  Seems like a few extra steps are being taken.

Also, if you are doing some sort of migration or re-org our Archive Shuttle product might be of interest.

Any hoo, if you let us know why you are doing this we might be able to provide some more suggestions.

Best,

[pjglick]

We are doing this because a specific user had multiple PSTs and the technician who did the ingestion may not have gotten all of them but we dont know which one were ingested or not so we were trying to start the process over again from a period of time befoe the user was archived so we dont have duplicates in the archive.

The reason we are not ingesting back into the mailbox is that the create date changes and then wojuld not be eligible for archive for 6 months, which is our current policy.

Paul

[TonySterling · Accepted solution]

If you set the IgnoreEVDates registry key the items will be archived.

Create  the REG_DWORD IgnoreEVDates in HKEY_LOCAL_MACHINE\SOFTWARE\KVS\Enterprise Vault\Agent.  (remember if 64 bit it goes under WOW6432Node)
Set the value of IgnoreEVDates to 3 (decimal), then restart the archiving task.

Also covered here:

How to Force archiving based on the Received Date of email.

When archived items are restored, they will get re-archived based on the Archived Date property as opposed to the Sent/Received Date. This feature can by bypassed by using the IgnoreEVDates registry key to tell the ArchivingTask to ignore this property when evaluating messages eligibility for archiving.

TECH76532 | 2012-03-23 Technical Solutions | CMS-XML