Forum Discussion

GertjanA's avatar
GertjanA
Moderator
13 years ago

Import PST into Journal Archive

I might have a need to import user pst files into a journal archive. As far as I know, this should be possible using EVPM.

Is that correct?

Thanks.

Gertjan

  • Yes evpm is the only way you can do it, other people will suggest turning it into a shared archive and using the wizard to import but that would mean stopping journaling for a short while But honestly your best bet is to create a new journal tatty and import the the pst file there The problem you have is if you import a pst file in to an archive you won't have things like undisclosed recipients and the envelope processed, you won't have dl expansion occur or any of that stuff that is processed normally So for instance in 2003 envelope journaling and any journaling for 2007 and 2010 you would have the P1 message which has all the recipients etc and then the P2 message which is the physical msg file and any attachments, EV would archive the P2 message and store the P1 message as an XML stream It would then take the recipients list from the P1 message and compare it to the TO and CC lines and the DL's, if the recipient in the envelope does not match any of those recipients in the message then it is assumed they are undisclosed/BCC recipients If you have envelope messages and you import the pst in to a journal archive the message will be archived as is, the P1 will not be discarded and you can't search attachments of the main message because the main message is an attachment of the envelope So normally when an envelope message is journalled, because the P1 is removed you have Message -> Attachments and EV indexing will index those attachments But an import would have Envelope (P1} -> Message (P2) -> Attachment EV would not index that third level and therefor the contents would no be searchable as the pst migrator does not know how to process an envelope, only the journal task does

2 Replies

  • Yes evpm is the only way you can do it, other people will suggest turning it into a shared archive and using the wizard to import but that would mean stopping journaling for a short while But honestly your best bet is to create a new journal tatty and import the the pst file there The problem you have is if you import a pst file in to an archive you won't have things like undisclosed recipients and the envelope processed, you won't have dl expansion occur or any of that stuff that is processed normally So for instance in 2003 envelope journaling and any journaling for 2007 and 2010 you would have the P1 message which has all the recipients etc and then the P2 message which is the physical msg file and any attachments, EV would archive the P2 message and store the P1 message as an XML stream It would then take the recipients list from the P1 message and compare it to the TO and CC lines and the DL's, if the recipient in the envelope does not match any of those recipients in the message then it is assumed they are undisclosed/BCC recipients If you have envelope messages and you import the pst in to a journal archive the message will be archived as is, the P1 will not be discarded and you can't search attachments of the main message because the main message is an attachment of the envelope So normally when an envelope message is journalled, because the P1 is removed you have Message -> Attachments and EV indexing will index those attachments But an import would have Envelope (P1} -> Message (P2) -> Attachment EV would not index that third level and therefor the contents would no be searchable as the pst migrator does not know how to process an envelope, only the journal task does
  • for the thorugh explanation.

    This is another issue to convince the user to use some migration tool.. (transvault is what we're looking at)