Users Guide
NOTE: In the preceding example, the directory H:\Replay Users contains both the log and database les. If the les are
in dierent 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 link
Expose a Restore Point (Windows Extensions Only)
Replay Sizes and Storage Center Storage Proles
By default, Storage Center is congured 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 conguring and using a Storage Center Storage Prole 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 oine 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.
• Oine 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.
NOTE
: When using Replay Manager with Microsoft Hyper-V, only volumes hosting virtual hard disk (VHD or VHDX) les
are included in a snapshot. Virtual machine volumes are not included if the volumes are mapped to a virtual machine by
iSCSI or pass-through.
NOTE: Microsoft Hyper-V Replays create a view volume on the Storage Center for each Replay. All other Replay Manager
extensions do not create a view volume for each Replay. This is a limitation of the Microsoft Hyper-V VSS writer.
Microsoft does not provide guidelines for the number of virtual machines that can be snapped at a time or the best interval. Most
administrators perform snapshots once a day for most virtual machines, and more frequently on a limited number that require a tighter
recovery point objective. For more information on the specics of the support policies for Microsoft applications when virtualized, see
these links:
• Microsoft Server Software and Supported Virtualization Environments: support.microsoft.com/kb/957006/
• Support Policies & Recommendations for Exchange in Virtualization Environments: technet.microsoft.com/en-us/library/
cc794548.aspx
Using Replay Manager with Hyper-V on Front-End SAS
• Hyper-V hosts can use either single or multipath I/O on Front-End SAS.
• Hyper-V guests (VMs) can use only single path I/O. Multipath cannot be installed. These VMs must be gen 2. Gen 1 is not supported.
64
Replay Manager Best Practices