DRAG DROP
You have an Exchange Server 2013 organization that contains four servers named EX1, EX2, EX3, and
EX4. All of the servers are members of a database availability group (DAG) named DAG1.
Each server has a copy of a mailbox database named DB1. DB1 has the following characteristics:
• The replay lag time on Ex4 is set to 14 days.
• Single item recovery on all of the servers is set to 14 days.
• None of the servers have Volume Shadow Copy Service (VSS) backups.
Ex4 has a folder named F:\RDB that is used to store database files during restore operations.
Twenty days ago, a user named User1 deleted an email message that had a subject of “Sales
Report”.
You need to restore the deleted email message to the mailbox of User1.
You copy the lagged database and the log files that are older than 20 days to F:\RDB.
Which three actions should you perform?
To answer, move the three appropriate actions from the list of actions to the answer area and
arrange them in the correct order.
Answer: See the explanation.
Note:
Box 1:
* You can use the Shell to create a recovery database, a special kind of mailbox database that’s used
to mount and extract data from the restored database as part of a recovery operation. After you
create a recovery database, you can move a recovered or restored mailbox database into the
recovery database, and then use the New-MailboxRestoreRequest cmdlet to extract data from the
recovered database. After extraction, the data can then be exported to a folder or merged into an
existing mailbox. Using recovery databases, you can recover data from a backup or copy of a
database without disrupting user access to current data.
* This example creates the recovery database RDB2 on the Mailbox server MBX1 using a custom
path for the database file and log folder.
New-MailboxDatabase -Recovery -Name RDB2 -Server MBX1 -EdbFilePath
“C:\Recovery\RDB2\RDB2.EDB” -LogFolderPath “C:\Recovery\RDB2”
* From scenario: Ex4 has a folder named F:\RDB that is used to store database files during restore
operations.
* The database and log files containing the recovered data must be restored or copied into the RDB
folder structure that was created when the RDB was created.
Box 2:
* The database must be in a clean shutdown state. Because an RDB is an alternate restore location
for all databases, all restored databases will be in a dirty shutdown state. You can use Eseutil /R to
put the database in a clean shutdown state.
Box 3:
A recovery database (RDB) is a special kind of mailbox database that allows you to mount a restored
mailbox database and extract data from the restored database as part of a recovery operation. After
you’ve created an RDB, you can restore a mailbox database into the RDB by using your backup
application (or if you have the database and its log files in the file system, by copying them to the
RDB file structure). Then you can use theNew-MailboxRestoreRequest cmdlet to extract data from
the recovered database. After being extracted, the data can then be exported to a folder or merged
into an existing mailbox. RDBs allow you to recover data from a backup or copy of a database
without disrupting user access to current data.
Reference: Create a Recovery Database
Reference: Restore Data Using a Recovery Database
Deletion the check point file and running eseutil to perform the soft recovery needs to happen before you can mount the database.
Anybody who worked with Exchange (even rookie Exchange engineers) should know that you perform eseutil /r while database is dismounted. You do that to replay the logs into database before you mount the database.
I have no idea why the answer would suggest mounting the database first and then perform eseutil /r.