You need to identify what prevents DB2 from mounting on EX1

You have an Exchange Server 2013 organization that contains two servers named EX1 and EX2.
EX1 and EX2 are the members of a database availability group (DAG) named DAG1. DAG1 contains
two mailbox databases named DB1 and DB2. DB1 is active on EX1. DB2 is active on EX2.
A disk on EX2 fails. DB2 fails over to EX1.
Users who have mailboxes in DB2 report that Microsoft Outlook can no longer connect to the
Exchange Server organization.
You discover that DB2 is dismounted on EX1.
When you attempt to mount DB2 on EX1, the operation fails.
You need to identify what prevents DB2 from mounting on EX1.
What should you do?

You have an Exchange Server 2013 organization that contains two servers named EX1 and EX2.
EX1 and EX2 are the members of a database availability group (DAG) named DAG1. DAG1 contains
two mailbox databases named DB1 and DB2. DB1 is active on EX1. DB2 is active on EX2.
A disk on EX2 fails. DB2 fails over to EX1.
Users who have mailboxes in DB2 report that Microsoft Outlook can no longer connect to the
Exchange Server organization.
You discover that DB2 is dismounted on EX1.
When you attempt to mount DB2 on EX1, the operation fails.
You need to identify what prevents DB2 from mounting on EX1.
What should you do?

A.
Run the Resume-MailboxdatabaseCopy cmdlet.

B.
Run the Update-MailboxdatabaseCopy cmdlet.

C.
Run the eseutil.exe command and specify the A parameter.

D.
Run the eseutil.exe command and specify the/mft parameter.



Leave a Reply 4

Your email address will not be published. Required fields are marked *


techguy

techguy

Not sure how B makes sense since the disk holding DB2 on EX2 is down what would you be pulling updated files from? A obviously doesn’t make sense because in the question you already tried mounting it. C doesn’t make sense as the A parameter is when repairing the database but question asks you to identify the issue first. D I can’t find much info on but think maybe this is the answer and question might have the parameter incorrect. /M is for used for identifying issues with database files so think this might be the answer. Can anyone confirm?

bielik

bielik

I think D is a distractor

Anna

Anna

How about A?
It might try to resume database “after maintenance” and show you reason why it didnt work.

Update-MailboxdatabaseCopy cmdlet serves for seeding/reseeding.
Not sure how it can help..

Even google doesnt recognize eseutil /mft, otherwise switch /mh check the state, might it be a typo?

Jamie

Jamie

eseutil has no A parameter so C. is wrong. See parameters below:-

Identity: [PS] C:\Windows\system32>eseutil

Usage Error: No mode specified.

Extensible Storage Engine Utilities for Microsoft(R) Exchange Server
Version 15.00
Copyright (C) Microsoft Corporation. All Rights Reserved.

DESCRIPTION: Database utilities for the Extensible Storage Engine for Microsoft(R) Exchange Server.

MODES OF OPERATION:
Defragmentation: /d [options]
Recovery: /r [options]
Integrity: /g [options]
Checksum: /k [options]
Repair: /p [options]
File Dump: /m[mode-modifier]
Copy File: /y [options]
Restore: /c[mode-modifier] [options]

<<<<>>>>
D=Defragmentation, R=Recovery, G=inteGrity, K=checKsum,
P=rePair, M=file duMp, Y=copY file, C=restore
=>