The following table introduces the terminology that is used throughout Journal Commander documentation, videos, and the user interface.

TERM ITEM + DESCRIPTION
Link Enterprise Vault
A Link is a Vault Store
Exchange
A Link is an Exchange database
Office 365
A connection to Office 365
PST
A connection to a PST Output Area
Proofpoint
A connection to a Proofpoint output area
EAS
A connection to an EAS IIS ServerMetalogixA connection to a Metalogix server
Container Enterprise Vault
A Container is a Vault / Archive
Exchange
A Container is an Exchange mailbox
Office 365
A Container is an Office 365 mailbox or Personal Archive
PST
A container is a PST file
Proofpoint
A container currently has no applicable context
EAS
A container is an archive relating to a user.MetalogixA container is an archive
Item Enterprise Vault
An Item is an archived Item.
Exchange
An Item is an item in the mailbox
Office 365
An Item is an item in the mailbox or personal archive
PST
An item is an item inside a PST file
Proofpoint
An item currently has no applicable context
EAS
An item is a message in the archiveMetalogixAn item is a message in the archive
 Archive A journal archive targets a journal mailbox. 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.
 Migration Moving data (in this case, a journal archive) from one location to another.
 Journal Splitting If a journal archive is extremely large, it might need to be split into two or more parts. The parts can be migrated separately (maybe even simultaneously), so the entire journal can be migrated more quickly.
Journal A journal mailbox typically contains a copy of every message that leaves your outbox. That’s messages to people inside and outside your own organization, and also meeting requests with other people (but not your own appointments, or contacts, or tasks).
Journal Transformation A journal transformation takes every email exported from a journal archive and places a copy into the mailbox of every associated address. This has added complexities compared to journal splitting or migrating archives. Transformation projects require the process and review of every address associated with every message in the environment so that a copy can be written to all appropriate mailboxes.
Print Friendly, PDF & Email