There could be many reasons why you need to restore a database. Let’s look at some common reasons. The server has been re-installed, after failure. The database gets corrupted or is not mounting.

A litte backstory: We use Quest's MailArchive and the process failed for some time so the mailbox used for Archiving ballooned to about 78GB according to get-mailboxstatistics. We started the process, ...

Exchange Server 2010 incorporates a number of high-availability features that system admins will find useful, including a new database availability groups (DAG) feature. Mailbox databases and the data ...

Despite what your users might think, you're not limiting the size of their mailboxes as a form of punishment. Most users want to be able to keep all their e-mail messages indefinitely. On the other ...

Accidental deletion of a user mailbox, shared mailbox, public folder, or any other item is a common scenario in an Exchange Server environment. When a mailbox is deleted, its associated Active ...

Initially, when my Exchange 2007 email system was set up a few years ago, we setup two mailbox databases. Standard with a Box Size limit of 1GB VIP or Power User with a Box Size limit of 2GB Standard ...

With the release of Exchange 2007 and then 2010, Microsoft moved admins to a role-based model for deployment, with changes both to roles and services that admins should understand. Exchange 2013 takes ...

For this blog post, I’m going to jump right into a topic of most interest to organizations deploying Exchange Server 2010, which is Disaster Recovery of databases. New to Exchange 2010 is the concept ...

Only two years after Microsoft Exchange 2007 was released the first public beta of "Exchange 14" (Exchange 2010) has arrived. For those interested in trivia, Exchange 2007 was version 12 — so what ...

It is imperative to understand what would be at stake if your Exchange Server was compromised. Data is the primary at-risk component in these situations, but service interruptions also hamper business ...