Archiving vs. Journaling
-
Anyone have a guess why journaling in Microsoft Exchange is a user mailbox whereas archiving can be its own database? Seems like journaling would perform better if it were a database and you were trying to return search results. I'm guessing there is a logical reason between it being a user mailbox and a mailbox database...
-
Usually you will place a journaling mailbox on its own mailbox database due to the load of emails going to it for incoming and outgoing emails. The performance is not the goal but rather compliance as it gathers information as soon as it is sent or received.
An archive will tale what is already on or many mailboxes every so often that will allow for losing information at times.
-
@Eltolargo said in Archiving vs. Journaling:
Usually you will place a journaling mailbox on its own mailbox database due to the load of emails going to it for incoming and outgoing emails. The performance is not the goal but rather compliance as it gathers information as soon as it is sent or received.
An archive will tale what is already on or many mailboxes every so often that will allow for losing information at times.
I understand why it should be isolated, but why put a journaled user mailbox on it's own database? Why can't it just be its own database like how an archive database exists on its own?
-
@BBigford If we are talking about Office 365 Journaling is outdated while Litigation Hold and Compliance is the way to go. YOu can also still have a Mailbox Archive for each mailbox, but litigation hold will make it that any changes are not deleted from the mailbox.
http://windowsitpro.com/blog/why-exchange-online-hates-journal-mailboxes
