Which three actions should you perform?

DRAG DROP
You have an Exchange Server 2013 organization that contains a database availability group (DAG).
There are four copies of every mailbox database. One of the copies is a lagged copy configured to
have a replay lag time of 14 days. All mailboxes have single item recovery enabled. All databases are
configured to have a deleted item retention period of seven days. A company executive reports that
an email message, which was deleted 10 days ago, must be restored. You need to ensure that you
can recover the email message from the lagged copy of the mailbox database. The solution must
preserve the lagged copy of the mailbox database. 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.

Explanation:
Run the Suspend-MailboxDatabaseCopy cmdlet.
Run the vssadmin command.
Run the eseutil.exe command.

vssadmin
Displays current volume shadow copy backups and all installed shadow copy writers and providers in
the command window.
There could be VSS errors causing the datasources not to enumerate. If so, verify that all Exchange
Node and Exchange VSS components are functional. Ensure all databases are mounted and healthy
Run vssadmin list writers Move-ActiveMailboxDatabase
Use the Move-ActiveMailboxDatabase cmdlet to perform a database or server switchover.
This example performs a switchover of the database DB2 to the Mailbox server MBX1. When the
command completes, MBX1 hosts the active copy of DB2.
Because the MountDialOverride parameter is set to None, MBX1 mounts the database using its own
defined database auto mount dial settings.
Move-ActiveMailboxDatabase DB2 -ActivateOnServer MBX1 -MountDialOverride:None
The SkipLagChecks parameter specifies whether to allow a copy to be activated that has replay and
copy queues outside of the configured criteria.
eseutil.exe

The key to matching log files and databases is the signature. You can view log file signatures by using
the
Exchange Server Database Utilities (Eseutil.exe) tool and viewing the log file header with the
command Eseutil/ml [log filename].
You can view database (.edb) and streaming database (.stm) file signatures by viewing the file
header with Eseutil /mh [database filename].edb.
A typical log file or database file signature looks like this:
Signature: Create time:12/17/2002 18:1:44 Rand:81060559 Computer:
Activating and recovering a lagged mailbox database copy is an easy process if you want the
database to replay all log files and make the database copy current.
If you want to replay log files up to a specific point in time, it’s a more difficult operation because
you manually manipulate log files and run Exchange Server Database Utilities (Eseutil.exe).
Suspend-MailboxDatabaseCopy Use the Suspend-MailboxDatabaseCopy cmdlet to block replication
and replay activities (log copying and replay) or activation for a database configured with two or
more database copies.
For a variety of reasons, such as performing planned maintenance, it may be necessary to suspend
and resume continuous replication activity for a database copy.
In addition, some administrative tasks, such as seeding, require you to first suspend a database copy.
We recommend that all replication activity be suspended when the path for the database or its log
files is being changed.
You can suspend and resume database copy activity by using the EAC, or by running the SuspendMailboxDatabaseCopy and Resume-MailboxDatabaseCopy cmdlets in the Shell.
EXAMPLE 1
This example suspends replication and replay activity for the copy of the database DB1 hosted on
the Mailbox server MBX3. An optional administrative reason for the suspension is specified.
Suspend-MailboxDatabaseCopy -Identity DB1\MBX3 -SuspendComment “Maintenance on MBX3”
NOT Move-ActiveMailboxDatabase
Not attempting to make a passive or lagged database active.
You need to ensure that you can recover the email message from the lagged copy of the mailbox
database.
The solution must preserve the lagged copy of the mailbox database.
STEPS
No need to use Move-ActiveMailboxDatabase
1. First Use the Suspend-MailboxDatabaseCopy cmdlet to block replication and replay activities (log
copying and replay)
2. 2nd use vssadmin to check that there could be VSS errors causing the datasources not to
enumerate.
3. 3rd Run Exchange Server Database Utilities (Eseutil.exe).
THIS LAST STEP NEEDS CLARIFYING