What is Journal Commander for?
With the mass adoption of Office 365, there’s a growing desire to ‘bring data home’ and migrate journal archives to the Microsoft cloud.
Quadrotech has planned and executed some of the largest Office 365 migration projects in the world. Our unique combination of powerful software and an experienced delivery team can help modernize the use of legacy archives in your cloud environment.
What does Journal Commander do?
Journal Commander migrates a journal archive to a target environment in a special way that fans-out the recipient / custodian list. If an original message was addressed to three different people, then the item is exported, and ingested into up to four target containers.
Here are some reasons you might want to use Journal Commander:
- It causes deliver/ingest messages to be sent to user mailboxes in the same way the Exchange or Office 365 modules do in regular migrations, rather than a separate mailbox.
- If a user’s data becomes corrupt or lost, journal archives can be used to recreate the user’s data.
- It can be used for leavers who lack archives.
- It’s easy to distinguish external email addresses.
- It can help fulfill legal/compliance/regulatory requirements.
How does Journal Commander work?
A journal archive usually contains meta data related to the real message. The real message is usually an attachment. This wrapper message with the meta data is called a P1 and the real message is called a P2.
Example of metadata: The P2 might be sent to DL-Sales. But, 3 years later you won’t know who was in that DL at the time the message was sent. Well, the P1 will tell you who received the message, because it has a list of the distribution list members.
Typically, a journal archive is a flat archive (there’s no folder structure). Everything is in the inbox of the archive. Typically that’s the only folder in the entire archive.
As with any other archive, the journal archive has an owner, but in this case it’s usually a service account. Therefore, it really means no users have access to the journal archive.
Journal Commander reads the journal archive’s P1 data and uses it to deliver P2 messages to each sender/recipient archive in the new environment. It’s worth noting Journal Commander places the P2 into a hidden portion of the sender/recipient mailbox.