Exchange 2010 no longer has the notion of Storage Groups, which were used in Exchange 2007 and 2003 to contain logical groupings of databases. E2010 now simply lets you create databases on mailbox servers. E2010 Standard Edition lets you create up to 5 databases per server. The Enterprise Edtion scales up to 100 databases per server.
In Exchange 2003/2007 you could restore a database "on top" of an original database to replace the existing database, or you could restore the database "along side" the existing database to recover select mailboxes or items. You can do the same thing with Exchange 2010. The difference is that in Exchange 2003/2007, you created a Recover Storage Group (RSG) to restore the database into. In Exchange 2010, you simply restore the database and connect to it as a Recovery Database (RDB). Here's how you do it in Exchange 2010.
Note: Ross Smith IV has a great article on single item recovery in Exchange 2010. This assumes that the item can be recovered from the dumpster. This article covers how to restore from a backup when the item cannot be recovered from the dumpster. For example, on the rare occasion when a user realizes he/she deleted a folder or item past the dumpster retention period.First, you have to have a good backup that contains the item to be recovered. Windows Server 2008 and Windows Server 2008 R2 have the built-in Windows Server Backup feature. I cover how to use WSB to backup Exchange here.
Now you must restore the data, but redirect it to another location. In Windows Server Backup, this is done by choosing to recover the Exchange application (detailed in my previous article) and recovered to another location. Typically, this is a new folder on the same Exchange server:
Now you need to add this database to the Exchange mailbox server as a Recovery Database. Currently, this is done using the Exchange Management Shell (EMS), as there is no way to do this from the GUI. Run the following command to create a Recovery Database:
New-MailboxDatabase -Recovery -Name RDB1 -Server EX1 -EdbFilePath "D:\Recovery\Mailbox Database 1882717321.edb" -LogFolderPath "D:\Recovery"This will cause Exchange to create a new recovery database named RDB1 on server EX1 using the database and logs in D:\Recovery. Once this command is run, you will see the recovery database in the Exchange Management Console (EMC), but it must be brought into a clean shutdown state before it can be mounted.
To bring the database into a clean shutdown state, use ESEUTIL /R to perform a recovery of the database. Often, I've seen that Exchange is unable to perform a successful recovery, giving the following error:
Operation terminated with error -1216 (JET_errAttachedDatabaseMismatch, An outstanding database attachment has been detected at the start or end of recovery, but database is missing or does not match attachment info) after 11.625 seconds.In these cases, I have run an ESEUTIL /P (repair) to force the database into consistency. Once the database has been successfully recovered or repaired, mount the database in EMC or using the Mount-Database cmdlet.
Now we're ready to recover deleted items from the recovery database. In order to do this, though, you need Organization Management rights in Exchange 2010. The following are cmdlet examples for recovering items from the RDB:
This example restores a mailbox for user Keith Johnson, overwriting the existing mailbox:
Restore-Mailbox -ID 'Keith Johnson' -RecoveryDatabase RDB1This example restores Keith Johnson's mailbox content into an Investigation mailbox:
Restore-Mailbox -ID 'Investigation' -RecoveryDatabase RDB1 -RecoveryMailbox 'Keith Johnson'This example restores only the mail with the word "contract" in the subject and the word "CompanyABC" in the body of the message from the Inbox or Saved folders.
Restore-Mailbox -ID 'Keith Johnson' -RecoveryDatabase RDB1 -SubjectKeywords 'contract' -ContentKeywords 'companyabc' -IncludeFolders \Inbox,\SavedThere are a lot of different options in the Restore-Mailbox cmdlet and recovery databases that make it a powerful tool for recovery. Take the time to learn them before you need to use them. 2:35 PM