About the Author

Paul Cunningham

Paul is a former Microsoft MVP for Office Apps and Services. He works as a consultant, writer, and trainer specializing in Office 365 and Exchange Server. Paul no longer writes for Practical365.com.

Comments

  1. Natharsha

    Hi Paul Thanks for this knowledge base.

    Please help me to figure out the issue

    Is there a way to implement second exchange server in an organization that will act as a backup. If the primary exchange server fails then the backup will come to play providing high availability like additional domain controller in AD environment.
    Please share in detail as I am a novice in exchange environment.

  2. Their might be several reasons behind corruption of exchange server database that causes loss of significant data, its really nice that you have provided adequate knowledge regarding how and for what backup and recovery is necessary.

  3. Jens

    Nice article, thanks!
    We are using Microsoft DPM Server to backup exchange. It is working good for us.

  4. Paul

    Hi Mark, thats one approach. There can be disadvantages to that approach though, for example:

    – uses more (a lot more in some cases) backup capacity than is really required. For a single Exchange server this is probably not much concern, but as you scale up it becomes a cost issue.

    – if your image based backup is not properly application aware then your recovery options may be limited. For example, ability to recover a single mailbox database, or single mailbox item.

    Have no experience with StorageCraft Shadow Protect to make any specific comment about it.

  5. Mark

    Hi Paul,

    I’ve skimmed through your articles, looks like some impressive work you have put together 🙂

    One quesiton though, wouldn’t an image backup solution that makes a backup of the whole disk (OS, apps and data files) do a lot of the work already so you don’t need to make “backup exceptions” or “things not to forget” ? (We use StorageCraft ShadowProtect http://www.storagecraft.co.uk)

    Cheers,
    Mark

Leave a Reply