You have an Exchange Server 2013 organization. The organization contains a Mailbox server that
hosts several databases, including a database named ExecsDB. ExecsDB contains the mailboxes of
the company executives.
The hard disk that contains ExecsDB fails.
You replace the hard disk with a new disk, and then you mount the database.
You create a recovery database in an alternate location, and then you restore the database files for
ExecsDB to the alternate location.
You need to ensure that all data is consistent before merging the mailbox data into the dial-tone
database.
What should you do first?
A.
Run the isinteg.exe command and specify the -fix parameter.
B.
Run the Move-ActiveMailboxDatabase cmdlet.
C.
Run the Update-MailboxDatabaseCopy cmdlet.
D.
Run the eseutil.exe command and specify the/R parameter.
A has been replaced by new-mailboxrepairrequest so I think this is wrong. But not sure what else it would be, maybe d?
0
0
http://www.exchangetooutlook.com/blog/how-to-recover-exchange-database.html
“Run Isinteg.exe to check the integrity of recovered EDB database”
0
0
There is no description about Exchange version they used. But on screens with eseutil is exchange version 14.02, that means Ex2010.
In Ex2013 isinteg was replaced by new-mailboxrepairrequest.
Eseutil /r commands are about recovery databases, specially to get the database to clean shutdown.
So my guess, D is correct answer.
0
0
https://technet.microsoft.com/en-us/library/ee332351(v=exchg.150).aspx
What do you need to know before you begin?
*
*
*
*
* 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 must use Eseutil /R to put restored databases into a clean shutdown state.
>>>>D<<<<
0
0