Hello, we're in the initial phases of deploying EmailXtender, and I have a question about archiving/journaling of messages in the Information Store. We initially ran an archive task globally on the entire information store. I'm curious if you need to run a task like this on a periodic basis to ensure your archive data is in synch with production? Thanks

Well, it depends if you plan on utilizing "real time" journaling. If we are real-time journaling, then we will be pulling in messages into Journaling mailbox once they pass the Mailstore.

Therefore, it would not be necessary after the initially enabling journaling.

However, if you do run a task, EmailXtender grants each message a unique MD5 identifier and this ID is stored in SQL. Each message is checked upon the archive process to ensure the same message does not get archived twice.

If we are NOT using Journaling, then archive tasks will be the only method of bringing new data into the system.

Hope this helps

Chris

The advice is helpful. We do have journaling enabled, and I realize this will provide the 'mirroring' so to speak, between production and archive. But I also wanted to be sure that duplicate entries were not created if we do run a one-time global archive task. Thanks again.