Tip

Exchange Server journaling -- segregation and migration

Exchange Server's native journaling feature lets you save all incoming and outgoing email traffic to a given mailbox for the sake of email archiving and retention.

While third-party email archiving products perform the same function, many administrators rely on Exchange Server journaling, because there's no additional cost and it's relatively easy to set up and use.

If you're

    Requires Free Membership to View

journaling in Exchange Server 2003 Enterprise Edition, you should move all mailboxes that are being journaled to their own store. (This is not possible with Exchange Server 2003 Standard Edition, because you can't create multiple mailbox stores.)

Segregating journaled Exchange Server mailboxes is a good idea for two reasons:

  • If there's a problem with one of the Exchange Server databases, the other databases have a better chance of surviving (whether they're journaled stores or not). The journaled stores can be backed up separately.

  • Segregating journaled Exchange Server data is more efficient in terms of storage -- you're not journaling anything that doesn't need to be journaled, so you're saving disk space overall.

In Exchange Server 2007, journaling has been reworked a bit. Instead of tying journaling to a given message store, it's now applied in the Hub Transport Server role. This means that journaling can now be applied to a broader range of objects (e.g., mail-enabled contacts).

Consequently, you have much more freedom in how journaling is set up in Exchange Server 2007. You can configure a given mailbox to be the journaling mailbox for one or more databases. You can also dedicate a whole database to the journaling mailbox (which you probably should do).

If you're migrating from Exchange 2003 to Exchange 2007, and also migrating your journaling settings, keep these expanded behaviors in mind. They'll give you more flexibility when designing your new storage group model and setting up journaling in Exchange Server 2007.

About the author: Serdar Yegulalp is editor of the Windows Power Users Newsletter.

Do you have comments on this tip? Let us know.

Related information from SearchExchange.com:

  • Tip: Native Exchange Server archiving limitations
  • Tip: Exchange Server event sink offers more granular message journaling
  • Tip: Outlook journaling -- a poor man's archiving tool
  • Tip: MailArchiva – open source email archiving for Exchange Server
  • Learning Center: Exchange Server archiving essentials

    Please let others know how useful this tip was via the rating scale below. Do you have a useful Exchange Server or Microsoft Outlook tip, timesaver or workaround to share? Submit it to SearchExchange.com. If we publish it, we'll send you a nifty thank-you gift.

    This was first published in December 2006

  • There are Comments. Add yours.

     
    TIP: Want to include a code block in your comment? Use <pre> or <code> tags around the desired text. Ex: <code>insert code</code>

    REGISTER or login:

    Forgot Password?
    By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
    Sort by: OldestNewest

    Forgot Password?

    No problem! Submit your e-mail address below. We'll send you an email containing your password.

    Your password has been sent to:

    Disclaimer: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.