To recover an individual mailbox, Expose the
restore point as a drive letter or mount point. Once the snapshot
is exposed, an administrator can recover a mailbox using a Recovery
Storage Group or Recovery Database and the built-in tools of Microsoft
Exchange Server.
Where Emailrecovery1 is the database
name, ex2010-mb1 is the server name,
and h:\replay users is the path of
the exposed files.
NOTE:In the preceding example,
all files residing in ”h:\replay users “ are
immediately available for recovery. If files outside that directory
are required, copy them into the path of the exposed files (in this
case h:\replay users).
Use the ESEUTIL program to put the database
into a clean shutdown.
In the Exchange Management Organization
Configuration/Mailbox dialog box, right-click the recovered
database and select Mount Database.
Create a restore request for the mailbox to
recover. For example, to restore an entire mailbox: H:\Replay
Users>new-mailboxrestorerequest -sourcedatabase emailrecovery1 -sourcestoremailbox
"John Hancock" -targetmailbox jhancock@2010test.local where
the target mailbox is the email address of the mailbox you are restoring.
NOTE:In the preceding example, the directory H:\Replay Users contains both the log and database files. If the files are in different
directories, use the /l /s and /d options to specify the correct directories.
This restore command queues the request. As messages
are restored, they appear in the user’s mailbox and can be accessed
when they are visible. Multiple restore requests can be queued, and
wild cards can be used to recover multiple mailboxes. The Exchange
server processes all requests until complete. This process can be
used to recover everything from a single message to an entire mailbox
store.
NOTE:To recover
from a corrupt database, create a blank database and use this procedure
to restore data to individual mailboxes. Database recovery is constrained
only by server performance, so messages are restored as fast as the
server can process them.
For more information about using the
Exchange Management Shell, see technet.microsoft.com
Data is not available for the Topic
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\