Administrator Guide

a. Right-click the computer where the drive should appear and select Manage.
b. In the Computer Management navigation tree, expand the Storage entry.
c. Select Disk Management.
d. If the drive does not appear, select Action→ Rescan Disks.
5. Use the Exchange Management Shell to recover the mailbox database:
a. Create a database pointer for the recovery files.
b. Specify the path to the exposed files.
For example:
C:\>new-mailboxdatabase -recovery -name Emailrecovery1 -server ex2010-mb1 -EdbFilePath
“h:\replay users\replay users.edb" -logfolderpath "h:\replay users"
Where Emailrecovery1 is the database name, ex2010-mb1 is the server name, and h:\replay users is the path of the exposed files.
6. Use the ESEUTIL program to put the database into a clean shutdown.
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).
7. In the Exchange Management Organization Configuration/Mailbox dialog box, right-click the recovered database and select
Mount Database.
8. 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 [e-mail] 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
Related tasks
Expose a Restore Point (Windows Extensions Only) on page 38
Replay Sizes and Storage Center Storage Profiles
By default, Storage Center is configured to use a 2 MB page size. The default page size works best for most storage requirements.
However, for some applications, such as Microsoft Exchange Servers, the Storage Center defaults may result in larger than expected
Replay sizes.
Customers who experience larger than expected Replays (for example, 75% or greater of database size) can consider using the Storage
Center 512 KB page option for Microsoft Exchange volumes on the Storage Center. The smaller page size will reduce the amount of
blocks that can write to a page, thus reducing Replay sizes. For information on configuring and using a Storage Center Storage Profile
with a smaller page size, see the Dell Storage Manager Administrator’s Guide.
Microsoft Hyper-V
The Hyper-V extension included with the Replay Manager installation leverages the Hyper‐V VSS Writer to provide enhanced backup and
recovery of Hyper-V virtual machines. The Hyper-V VSS writer can take snapshots both in an online and offline operation:
• Online backups use the Hyper-V VSS writer to perform the snapshot while the server is online and does not cause an interruption in
service.
• Offline backups (on Windows NT 4.0 or Windows 2000 guests) require that the machine be put into a saved state while the snapshot
takes place and does require a service outage.
56
Replay Manager Best Practices