Is it possible to activate lagged mailbox databases automatically

Dears,
I searched every where and couldn't found anyone talking about configuring the lagged mailbox databases for automatic failover, without going through the manuall setps mentioned in the following TechNet link
http://technet.microsoft.com/en-us/library/dd979786(v=exchg.150).aspx
Any Ideas,
Ayman Saleh
No, lagged copies are not considered highly available copies. I guess you could script something using some logic, but that is not their intent.
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Similar Messages

Activate one database and all databases activate on mailbox server?

We are having some performance issues on one of our mailbox servers. I think I've narrowed it down to disk latency so trying to activate half of the databases on one node of the DAG/cluster and have half active on the other node of the DAG/cluster.
But, when I try to activate just one database, all databases in that cluster fail over.
Any thoughts on why the server is doing this?
Exchange 2010 SP2 Rollup 8
8 mailbox servers, 6 CAS/HUB servers.
Jason Meyer

Hello，
This is the exchange 2013 forum. I will help you to move your issue to exchange 2010 forum.
If you have any feedback on our support, please click
here
Cara Chen
TechNet Community Support

Primary Mailbox Database fails to replicate after failing over to secondary copy in DAG

We had an issue yesterday on a primary mailbox database server when the drive the log files are located on filled up and took the databases off-line on the primary server bringing them up on the secondary.
After the issue was resolved and enough space was freed up, all but one database failed back. The one that would not come back showed Failed in the copy status. It remained mounted on the secondary server. I attempted several times to 'update' the copy and
it would run for aver 40 minutes and look like it was going okay then it would 'fail' and end up in a 'failed and suspended' state. The error would indicated it could not complete because the it could not find the source server.
The Update job was configured to point to the server holding the secondary copy as the source so should not have a problem.
Any idea on how I can get the primary copy working again? I thought about making the second copy the 1st to activate and removing the primary copy from the DAG and recreating it, but past experience doing that did not resolve the issue.
Thank you,
Nick
Nick Laurino

Find out why database file is missing, I doubt on antivirus and start looking at the antivirus sacanning exclusion to ensure it is properly set...
File-Level Antivirus Scanning on Exchange 2010
Then try to reseed the database copy from a good source, it might be possible that antivirus would be scanning file when it is getting reseeded and causing issue...
How to Reseed a Failed Mailbox Database Copy in Exchange Server 2010
Blog |
Get Your Exchange Powershell Tip of the Day from here

Healthy copy of mailbox Database in DAG acting as a seeding source for another Healthy copy Database in DAG

Overview of the architecture
We have Site (Primary & DR)
2 Database copies in primary site and 1 Database on the DR site (Primary site 2 copies one mounted and second healthy & on the DR site one healthy copy of Database)
Recently Due to Network Problem the DR copy got in to the easyncronous state and was removed from the DAG.
As company does not want the downtime we have followed the below steps to Restore Database at DR site.
1)Stopped the backup to Not trucate the log file
2)Took Full backup and in the restore mode we shipped the full backup to the DR site.
3)As the above process needs 2 days, manually copied the some Logs to the DR site (IN some drive as much possible to reduce seed time)
4)Added the mailbox database of the DR site back in the DAG as its seeds from the start, we manually suspend the process post the Database folder hierrachy gets created
5)Added the EDB and logs files in the recently created folders
6)Resumed the Database seed, so only the remaining logs were copied and seeded from primary site to DR site, In some hours DR site databse became healhty with no copy queue and replay queue.
7)trucated the logs which synced using DAG
Now Dag has copies as initial setup but the since we followed the above process the primary site healthy copy is acting as the seed-source and logs not truncating for the database
When restarts the Replication services on the Primary site server with healthy the state becomes healthy but again after some time it becomes seed- source.
Wanted to know when DR site copy is in healthy state why its acting as a seed-source continueously
Need Experts advice in manage Database copies in healthy state...
Thanks in Advance

Hi,
Based on your description, sometimes the content index state of passive database copy in primary site is healthy, but sometimes the state is crawling.
You can use the following command to reseed the catalog only to check result.
Update-MailboxDatabaseCopy -Identity Database -SourceServer EX -CatalogOnly
Best regards,
Belinda Ma
TechNet Community Support

Exchange 2010 - Moving mailbox database from exchange 2010 server to another exchange 2010 server

Hi,
I have a current existing exchange server running on 2008 R2. apparently the partition that holds the mailbox database is getting full and i need to move some user mailboxes to another environment ( exchange 2010 running on 2008 R2). i transferred some users
successfully to the new location, but am not able to transfer the rest. I am getting the errors:
Summary: 1 item(s). 0 succeeded, 1 failed.
Elapsed time: 00:00:00
Erastus XXXXX
Failed
Error:
The queue in 'MBX2010_STAFF' database already contains a move request for 'Erastus XXXXX', while AD reports the mailbox as not being moved. It is possible that someone created this move request recently, while targeting a different domain controller, and AD
replication did not yet occur. You can examine this move request by running 'Get-MoveRequestStatistics -MoveRequestQueue 'MBX2010_STAFF' -MailboxGuid f8023bc7-9d65-4194-9f6b-10e4780558b5 -IncludeReport | fl'. If you believe this to be an abandoned move request,
you can remove it by running 'Remove-MoveRequest -MoveRequestQueue 'MBX2010_STAFF' -MailboxGuid f8023bc7-9d65-4194-9f6b-10e4780558b5'.
Exchange Management Shell command attempted:
'xxxxxxxx.co.ke/Training Department/XXXXXXX/XXXXXXX/Erastus XXXXX' | New-MoveRequest -TargetDatabase 'OFFICE_STAFF_MB_DB' -BadItemLimit '0'
Elapsed Time: 00:00:00
AND
Summary: 1 item(s). 0 succeeded, 1 failed.
Elapsed time: 00:00:01
George XXXXX
Failed
Error:
Service 'net.tcp://win-u5bjh2oamaa.xxxxxxxxx.co.ke/Microsoft.Exchange.MailboxReplicationService' encountered an exception. Error: MapiExceptionNoAccess: Unable to open message store. (hr=0x80070005, ec=-2147024891)
Diagnostic context:
    Lid: 18969   EcDoRpcExt2 called [length=207]
    Lid: 27161   EcDoRpcExt2 returned [ec=0x80070005][length=202][latency=0]
    Lid: 32881   StoreEc: 0x80070005
    Lid: 50035
    Lid: 64625   StoreEc: 0x80070005
    Lid: 1494    ---- Remote Context Beg ----
    Lid: 26426   ROP: ropLogon [254]
    Lid: 56503
    Lid: 12716   StoreEc: 0x80070005
    Lid: 20794
    Lid: 28474   StoreEc: 0x80070005
    Lid: 22330   dwParam: 0x0        Msg: 14.01.0270.001:CPLSERVER
    Lid: 1750    ---- Remote Context End ----
    Lid: 23354   StoreEc: 0x80070005
    Lid: 25913
    Lid: 21817   ROP Failure: 0x80070005
    Lid: 26297
    Lid: 16585   StoreEc: 0x80070005
    Lid: 32441
    Lid: 1706    StoreEc: 0x80070005
    Lid: 24761
    Lid: 20665   StoreEc: 0x80070005
    Lid: 25785
    Lid: 29881   StoreEc: 0x80070005
Exception details: MapiExceptionNoAccess (80070005): MapiExceptionNoAccess: Unable to open message store. (hr=0x80070005, ec=-2147024891)
Diagnostic context:
    Lid: 18969   EcDoRpcExt2 called [length=207]
    Lid: 27161   EcDoRpcExt2 returned [ec=0x80070005][length=202][latency=0]
    Lid: 32881   StoreEc: 0x80070005
    Lid: 50035
    Lid: 64625   StoreEc: 0x80070005
    Lid: 1494    ---- Remote Context Beg ----
    Lid: 26426   ROP: ropLogon [254]
    Lid: 56503
    Lid: 12716   StoreEc: 0x80070005
    Lid: 20794
    Lid: 28474   StoreEc: 0x80070005
    Lid: 22330   dwParam: 0x0        Msg: 14.01.0270.001:CPLSERVER
    Lid: 1750    ---- Remote Context End ----
    Lid: 23354   StoreEc: 0x80070005
    Lid: 25913
    Lid: 21817   ROP Failure: 0x80070005
    Lid: 26297
    Lid: 16585   StoreEc: 0x80070005
    Lid: 32441
    Lid: 1706    StoreEc: 0x80070005
    Lid: 24761
    Lid: 20665   StoreEc: 0x80070005
    Lid: 25785
    Lid: 29881   StoreEc: 0x80070005
Exchange Management Shell command attempted:
'xxxxxxxxxx.co.ke/Training Department/xxxxxx/xxxxxxx/George xxxxxxx' | New-MoveRequest -TargetDatabase 'OFFICE_STAFF_MB_DB' -BadItemLimit '0'
Elapsed Time: 00:00:01
I have all the proper rights.
YOUR ASSISTANCE WILL BE HIGHLY APPRECIATED. THANX :)

0x80070005 is pretty standard access denied entries. I would start digging into ACLs on a handful
of mailboxes.
Is there another Admin that can give it a shot to test their permissions vs yours?
- If you find my post to be helpful, or the answer, please mark it appropriately. Thank you.
Chris Ream

Cannot add mailbox database copy to DR site - .edb file not getting created

I have a DR site setup that I want copies of 4 of my mailbox databases. 3 of the mailbox databases copied over successfully but the last and largest one which is really not that large 69Gbs keeps failing when i Update the database copy. Seems
to not be creating the .edb file. Is there another way to get the .edb file over to the server, possibly manually copying it then doing and update database copy? I have my backups turned off on all the servers that have the mailbox role on it now
thinking that was causing some issues with the database copy? Any suggestions is appreciated, thanks.
Michael Duhon

Yes manually copy the edb file and paste them in the DR server . Then try to update with for the incremental of database copy. Verify the database is clean shutdown that you are moving to the DR site.
What error message it throws when you performing update the database copy
Exchange Queries

Mail stuck in "Mailbox Database ..." queue

Hi guys
In our organization we have an Exchange Server 2013 CU6 with both server roles CAS and Mailbox installed (absolutely fresh deployment). Users from AD have successfully been assigned mailboxes. The authoritative domain of the server is set correctly to our
local domain. The DNS MX record to the Exchange-host exists and works well (tested with nslookup and setting q=MX). For testing purposes all the receive connectors allow connections from anonymous users.
I've tried to send an SMTP mail via telnet connecting to CAS via port 25. The connection is established and the sender and receiver are accepted by the server but when I submit the message (line containing only a single a full stop) I get the error:
451 4.7.0 Temporary server error. Please try again later. PRX2
I have sent the same massage to the Transport Service on the Mailbox Server via port 2525 and the message was accepted, but it was not delivered to the mailbox of the recipient. Instead it just got stuck in a queue named "Mailbox Database ...".
Its status is "Ready".
I have restarted all possible services and rebooted the system but that did not help. Do you have any idea what could be the matter? Thank you!
Cheers Dimitri

Hi JCvanDamme,
I recommend you refer to the following article and it may give you some hints :
http://blog.kloud.com.au/2013/11/22/exchange-2013-dns-settings-cause-transport-services-to-crash/
Note: Microsoft is providing this information as a convenience to you. The sites are
not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from
the above link.
Best regards,
Niko Cheng
TechNet Community Support

Unexpected DAG mailbox database failover

Good evening
I am running a three node Exchange 2013 server environment in a stretched DAG configuration. I have been experiencing a problem recently whereby failover is occurring unexpectedly. Below is a brief description of the environment.
Site 1 (Head Office)
2 x Exchange 2013 CAS/MBX (dual role servers, lets call them A and B)
Both are members of the only DAG we have
They both have copies of the only mailbox database we have
Server A has activation preference 1
Server B has activation preference 2
Site 2 (Datacenter)
1 x Exchange 2013 CAS/MBX (dual role server, lets call it C)
C is a member of the same DAG as above
It hosts a copy of the same mailbox database as above
Server C has activation preference 3 (although I have configured it to never automatically activate a database copy)
Server C will only be actively used in a disaster scenario where we lose both A and B in the head office for whatever reason
So recently I have noticed that when the mailbox database is mounted and active on server A after a period of not more than an hour or two, the database is automatically moved to server B. This has happened 3 times now.
I find these informational alerts in the event viewer on server A.
Event ID 2136
Log Name: Application
Source: MSExchangeRepl
Date: 14/11/2014 16:01:03
Event ID: 2136
Task Category: Service
Level: Warning
Keywords: Classic
User: N/A
Computer: ServerA.domain.internal
Description:
Unable to communicate with the Microsoft Exchange Information Store service to coordinate log truncation for database 'Mailbox Database 1\ServerA' due to an RPC communication failure. Error: 3355381764
Extended error: Failed to open a log truncation context to source server 'ServerA.domain.internal'. Hresult: 0xc7ff1004. Error: Error returned from an ESE function call (-1305).
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="MSExchangeRepl" />
<EventID Qualifiers="32772">2136</EventID>
<Level>3</Level>
<Task>1</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-11-14T16:01:03.000000000Z" />
<EventRecordID>4381652</EventRecordID>
<Channel>Application</Channel>
<Computer>ServerA.domain.internal</Computer>
<Security />
</System>
<EventData>
<Data>Mailbox Database 1\ServerA</Data>
<Data>3355381764</Data>
<Data>Failed to open a log truncation context to source server 'ServerB.domain.internal'. Hresult: 0xc7ff1004. Error: Error returned from an ESE function call (-1305).
</Data>
</EventData>
</Event>
Event ID 3169
Log Name: Application
Source: MSExchangeRepl
Date: 14/11/2014 16:01:04
Event ID: 3169
Task Category: Service
Level: Information
Keywords: Classic
User: N/A
Computer: ServerA.domain.internal
Description:
(Active Manager) Database Mailbox Database 1 was successfully moved from ServerA.domain.internal to ServerB.domain.internal. Move comment: Managed availability system failover initiated by Responder=RpsDeepTestPSProxyFailover Component=RPS.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="MSExchangeRepl" />
<EventID Qualifiers="16388">3169</EventID>
<Level>4</Level>
<Task>1</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-11-14T16:01:04.000000000Z" />
<EventRecordID>4381655</EventRecordID>
<Channel>Application</Channel>
<Computer>ServerA.domain.internal</Computer>
<Security />
</System>
<EventData>
<Data>Mailbox Database 1</Data>
<Data>ServerA.domain.internal</Data>
<Data>ServerB.domain.internal</Data>
<Data>Managed availability system failover initiated by Responder=RpsDeepTestPSProxyFailover Component=RPS.</Data>
</EventData>
</Event>
Does anyone have any ideas as to why this might be happening or whether there are any additional troubleshooting steps I can take?
Regards

Hi George,
Agree with Jared, running CollectOverMetrics.ps1 script is a good choice to troubleshoot the issue.
Except this method, you can also refer to the following article to troubleshoot the issue with other useful information, like mailbox database replication status information, HighAvailability channel event logs..
http://technet.microsoft.com/en-us/library/dd351258(v=exchg.150).aspx
Best regards,
Niko Cheng
TechNet Community Support

Remove mailbox database copy from DAG

Hi There,
We would like to remove the mailbox database copy from our exchange server as we are lack of the space on our fixed vhd and we hope to be able to free about 100GB from the passive database copies as we have deployed DAG. is there any guidelines or procedures
to safely remove the database copies? currently, we have 4 mailbox servers, HQMB01, HQMB02, SSMB01, and SSMB02. HQMB01 and HQMB02 is already part of DAG members by itself. however, on ssmb01 and ssmb02, we also add in HQMB01 and HQMB02 as the DAG member,
thus they can fail over to HQMB01 or HQMB02 if their server have issue. in this situation, SSMB01 and SSMB02 passive copies is also inside our HQMB01 and HQMB02. As the our HQMB01 and HQMB02 is lack of the disk space and we would like to remove SSMB01
and SSMB02 from the DAG, thus we could remove the passive database copies. The following is the picture of the activation preference for all servers. what is the procedures and the guidelines to remove mailbox database copy and also remove the server from
the DAG members? we are quite confuse and worry that after we are removing wrongly and cause the active database to lost as we understand that there is replication happening between them. as we have 4 mailbox servers from which server we should perform
the task? Wish to get some advises from the exchange guru from this forum. we are on exchange server 2010 sp1 and windows server 2008 R2.Thanks so much.
Name                 : HQDB01
Servers              : {HQMB01, HQMB02}
ActivationPreference : {[HQMB01, 1], [HQMB02, 2]}
ReplayLagTimes       : {[HQMB01, 00:00:00], [HQMB02, 00:00:00]}
TruncationLagTimes   : {[HQMB01, 00:00:00], [HQMB02, 00:00:00]}
Name                 : HQDB02
Servers              : {HQMB02, HQMB01}
ActivationPreference : {[HQMB02, 1], [HQMB01, 2]}
ReplayLagTimes       : {[HQMB02, 00:00:00], [HQMB01, 00:00:00]}
TruncationLagTimes   : {[HQMB02, 00:00:00], [HQMB01, 00:00:00]}
Name                 : SSDB01
Servers              : {SSMB01, SSMB02, HQMB01, HQMB02}
ActivationPreference : {[SSMB01, 1], [SSMB02, 2], [HQMB01, 3], [HQMB02, 4]}
ReplayLagTimes       : {[SSMB01, 00:00:00], [SSMB02, 00:00:00], [HQMB01, 00:00:00], [HQMB02, 00:00:00]}
TruncationLagTimes   : {[SSMB01, 00:00:00], [SSMB02, 00:00:00], [HQMB01, 00:00:00], [HQMB02, 00:00:00]}
Name                 : SSDB02
Servers              : {SSMB02, SSMB01, HQMB01, HQMB02}
ActivationPreference : {[SSMB02, 1], [SSMB01, 2], [HQMB01, 3], [HQMB02, 4]}
ReplayLagTimes       : {[SSMB02, 00:00:00], [SSMB01, 00:00:00], [HQMB01, 00:00:00], [HQMB02, 00:00:00]}
TruncationLagTimes   : {[SSMB02, 00:00:00], [SSMB01, 00:00:00], [HQMB01, 00:00:00], [HQMB02, 00:00:00]}

Hi Exchange Guru,
thanks so much for the prompt response..i have few queries to ask following your guidelines above:
1. from the show result above, I am still confuse which server that I should go to remove as this is involving 4 database copies. from what I understand from the truncation or replay lag times of SSDB01 and SSDB02, I can see that HQMB01 and HQMB02 are on
the third and fourth preference, which means that SSDB01 and SSDB02 will be able to failover to each of them when there is a failure and it cause the passive copies of both of SSDB01 and SSDB02 to be stored in the HQMB01 and HQMB02. what my purpose
is to remove both SSDB01 and SSDB02 passive copies in HQMB01 and HQMB02. in this case, should I login to SSDB01 or SSDB02 mailbox servers to perform the removal with your guidelines above?
2. is the command as below:
Remove-MailboxDatabaseCopy -Identity SSDB01\HQMB01 -Confirm:$False
Remove-MailboxDatabaseCopy -Identity SSDB01HQMB02 -Confirm:$False
Remove-MailboxDatabaseCopy -Identity SSDB02\HQMB01 -Confirm:$False
Remove-MailboxDatabaseCopy -Identity SSDB02\HQMB02 -Confirm:$False
will this cause the risk either of my HQDB01, HQDB02, SSDB01, and SSDB02 active copies accidentally being removed? I am sorry that I am a bit naggy and always want a confirmation as this is very critical and I must be super careful.
3. If after the removal successful, when is the best time to go to the drive where the passive copies stored and remove them so I can clear some space on my disk? and is it just as simple by going to the drive and do a folder file deletion manually?
because I just worry when I delete the file and the server is still replicating between each other, which will cause even corruption to the active database.
4. From point 3, you mention about when the server is empty. what do you mean by that? do you mean that when the passive copies are no more there? and what command that I used to check?
5. From point 4, is removing the server from DAG the last step to be performed? yes, I want to remove them from DAG, thus will left only HQMB01 and HQMB02 as one DAG and SSMB01 and SSMB02 as one DAG.
Thank so so much for your patient and attention.
Regards,
Henry

Moving the mailbox database copy from one exchange server to another exchange server 2010 DAG

Hello Team
is it possible to the move the passive copy of database and logs from one server to another exchange server in the same DAG with out removing and deleting the mailbox database copies in exchange 2010
normaly procedure is
Remove the mailbox database copies and manually delete the .edb files and logs from the physical location and re-add the mailbox database copy to the new server in the DAG.
is that any way to achieve to move the passive database copy to another exchange 2010 server in the same DAG ?

From your note, you appear to have a two-member DAG (with a server hosting your active database, and a second hosting the passive copy), and you want to move your passive database copy from the current passive server to another. Your note
about what "the normal procedure is" isn't 100% correct - there are many ways to handle this task, and all can be considered "normal". Why not just add the third server to the DAG and
add a database copy on that third server? Once it is fully seeded, you can remove the current passive copy. This way, you never lose your redundancy.
Yes i can add the third and fourth serve in DAG , but i cannot add the mailbox database copies to the 3rd and 4th mailbox server in DAG as am using RTM version of exchange 2010 which is allowing to have only 5 database inclding mailbox datbase copies
and also currently my lab setup is two member dag (with a server hosting your active database,
and a second hosting the passive copy) in the same site named SITE A
and recently i have created new SITE B and included the 3rd and 4th DAG members in the same DAG
i want the mailbox database copies from the mailbox server database in SITE A to
Mailbox server database in SITE B as passive copy
That is why i want to move the mailbox database without deleting / removing it manually
Hope you understand my situation!

Specifying separate UNC path for Exchange Archive Mailbox Database

Hi All,
In Exchange Server 2013 SP1, is it possible to specify UNC path to a separate hardware appliance ?
In this case I'd like to create the Archive mailbox database on the CIFS share hosted by EMC Data Domain to perform the hardware based data deduplication & compression.
Does this path must also be accessible on the DAG passive node in DR data center ?
/* Server Support Specialist */

Hi ,
most Scenarios are not supported while there is still some Scenario where you can use shares.
"If access to a disk resource requires that a share be mapped, or   if the disk resource appears
as a remote server by means of a Universal Naming   Convention (UNC) path
(for example,   \\servername\sharename)   on the network, the disk storage system is not supported
as a location for   Exchange Server databases. "
This is also true for the Arcive DB.
Please note that UNC directly with Exchange 2013 is possible with limited support only, and no
version of Exchange allows you to store databases on an UNC path (except the one when you map
SMB 3.0 shares to a VM) :
http://technet.microsoft.com/en-us/library/ee832792(v=exchg.150).aspx#Best
(Please also note the recommendation not to use deduplication by the storage.)
Don't try to do that, because even if you configure that you will run into a non-supported situation.
I strongly suggest you to avoid that.
In addition, there is a webcast from Scott Schnoll about virtualization and file Shares that makes it a Little more clear.
https://channel9.msdn.com/Events/TechDays/Techdays-2014-the-Netherlands/Exchange-Server-2013-Virtualization-Best-Practices
While the session is about virtualization, on 13:00 they start a discussion about storage.
There is the reasons discussed why not to use UNC for your databases. (Don't worry, they start discussion with NFS)
The presentation shown on 21:43 is what you need to think about when planning to use UNC resources.
Storing an Exchnage DB on UNC is not supported.
Regards,
Martin
Hi martin,
So how are we going to Deduplicate the data ? Any suggestion perhaps ?
My understanding is that Exchange Server 2010 onwards doesn't have data deduplication.
How about mapping the UNC path as mapped network drive ?
/* Server Support Specialist */

Exchande mailbox database is not getting mounted automatically after server is up

Hi,
Our exchange server is configured as follows:
- DAG with two Exchange Mail box servers member.
- Each server is mounted to mailbox database(m1-db & m2-db respectively) and the replication is activated on both server
My question is when one of the server goes down , the other server will take over but after the second is back online, the database which reside on it is not mounted automatically and both dbs are showing healthy status.
To resolve this issue we have to activate it manually.
Is there any solution or configuration to be performed to make the mounting occurs automatically.
Regards

Does it happens to all the Database on that server?
What is the activation preference you have set?
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Repair corrupt mailbox database

I have a standalone Exchange 2010 server (virtual server in vmware) with a corrupt mailbox database. The server (VMDK file) resides in a vmware HA cluster fiber connected to a SAN. The SAN experienced a hard drive failure (RAID 5 volume which
contained Exchange server). Replaced the hard drive and the volume rebuilt without error. However,
after the rebuild the Mailbox database started blowing errors about being corrupt. I ran a chkdsk /f /r on both the C: and D: drives. C: drive was clean. Chkdsk on D: reported that
Windows replaced bad clusters in the file mbdata1.edb (mailbox database) file.
I can see the following errors:
ESE Event 474, 2007
ExchangeStoreDB Event 203, 233
Storage Group Consistency Check Event 254, 306, 401, 403 and 405
MSExchangeIS Event 9782
I ran an integrity check (ESEUTIL /g) which completed with errors:
Integrity check completed.
Database is CORRUPTED, the last full backup of this database was on 12/17/2011 08:44:37
Operation terminated with error -1206 (JET_errDatabaseCorrupted, Non database file or corrupted db) after 631.407 seconds.
I am finding [what seems to me to be] conflicting information on how to proceed. It seems that I can attempt repair of the DB (using eseutil and isinteg) and risk possible additional damage to the file or create a new mailbox database and move
the mailboxes to the new database.
Looking for advice on how to proceed.

Good suggestions from Simon and a few additional points
1. Before doing any of the following I would ensure I made a complete backup of the appropriate files i.e. the EDB as well as the VMDK to ensure you have the possibility to do a rollback if needed.
2. Since this is a VMware system I would suggest to you verify the VMDK is without issue and there are different methods for this dependent upon the version of VMware that you are running. Just do a search in Google for something like "how to verify
a VMDK file"
3. ISinteg is no longer around in Exchange 2010 so the most you can do is to run eseutil to attempt to repair the EDB and if that did work you would need to do a move mailbox which has integrity checking built in as part of the move process
4. That said IF the database is still online and accessible I would suggest that you;
A: Create a NEW/FRESH VMDK
B: Then create a new DB on the NEW/FRESH VMDK
C: Start moving mailboxes from the old EDB into the new EDB. NOTE: You may want to temporarily enable circular logging during the move process to avoid log build up and then turn it off post process and get a new backup.
D: If you encounter errors in moving any mailboxes I would go on to the next and move all of them that you can and then come back and address the problem mailboxes.
E: if they all move then you can kill off the old EDB.
F: of course you will also want to modify your backup process to protect the new EDB
The other option as Simon pointed out would be to;
A: Take the DB offline and copy it off to a safe place
B: Recover from your last known good backup
C: Then take that copy of the database that you have, make a new copy and use the MS Recovery DB process
http://technet.microsoft.com/en-us/library/dd876954.aspx or a 3rd party product like Lucid8's DigiScope
http://www.lucid8.com/product/digiscope.asp to open the old damaged offline database so that you can merge the delta data into the restored database in the Production Exchange Server.
Troy Werelius
www.Lucid8.com
Search, Recover, & Extract Mailboxes, Folders, & Email Items from Offline EDB's and Live Exchange Servers with Lucid8's DigiScope

Migration from Exchange 2007 to 2013 gives error "Failed to communicate with the mailbox database'

I have been trying to migrate several databases from Exchange 2007 to Exchange 2013. The migration started successfully, and many of the mailboxes moved successfully (about 70). The remaining mailboxes, failed. Looking deeper, we found a few issues; The
two 2013 Mailbox servers were on different versions. The Server had run out of disk space, and the NIC drivers needed to be updated.
Now when we try to migrate a mailbox that had failed in the earlier batch, we get the following error:
Data migrated:
Migration rate:
Error:
MigrationTransientException: Failed to communicate with the mailbox database. --> Failed to communicate with the mailbox database. --> MapiExceptionNetworkError: Unable to make connection to the server. ‎(hr=0x80040115, ec=-2147221227)‎ Diagnostic
context:    ......    Lid: 9624    dwParam: 0x0 Msg: EEInfo: Detection location: 501    Lid: 13720   dwParam: 0x0 Msg: EEInfo: Flags: 0    Lid: 11672   dwParam:
0x0 Msg: EEInfo: NumberOfParameters: 4    Lid: 8856    dwParam: 0x0 Msg: EEInfo: prm[0]: Unicode string: ncacn_ip_tcp    Lid: 8856    dwParam: 0x0 Msg: EEInfo: prm[1]: Unicode string: <Server
FQDN>    Lid: 12952   dwParam: 0x0 Msg: EEInfo: prm[2]: Long val: 3749909585    Lid: 12952   dwParam: 0x0 Msg: EEInfo: prm[3]: Long val: 382312662    Lid: 45169   StoreEc: 0x824
Lid: 50544   ClientVersion: 15.0.847.32    Lid: 52080   StoreEc: 0x824         Lid: 44273      Lid: 49064   dwParam: 0x1    Lid: 37288
StoreEc: 0x6AB         Lid: 49064   dwParam: 0x2    Lid: 59431   EMSMDB.EcDoConnectEx called [length=203]    Lid: 51239   EMSMDB.EcDoConnectEx exception [rpc_status=0x6D9][latency=0]
Lid: 62184      Lid: 16280   dwParam: 0x0 Msg: EEInfo: ComputerName: n/a    Lid: 8600    dwParam: 0x0 Msg: EEInfo: ProcessID: 3460    Lid: 12696   dwParam: 0x0 Msg: EEInfo:
Generation Time: 0414-04-07T16:32:03.2100000Z    Lid: 10648   dwParam: 0x0 Msg: EEInfo: Generating component: 2    Lid: 14744   dwParam: 0x0 Msg: EEInfo: Status: 1753    Lid: 9624
dwParam: 0x0 Msg: EEInfo: Detection location: 501    Lid: 13720   dwParam: 0x0 Msg: EEInfo: Flags: 0    Lid: 11672   dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 4    Lid: 8856
dwParam: 0x0 Msg: EEInfo: prm[0]: Unicode string: ncacn_ip_tcp    Lid: 8856    dwParam: 0x0 Msg: EEInfo: prm[1]: Unicode string: <Server FQDN>    Lid: 12952   dwParam: 0x0 Msg: EEInfo:
prm[2]: Long val: 2767313664    Lid: 12952   dwParam: 0x0 Msg: EEInfo: prm[3]: Long val: 382312662    Lid: 59505   StoreEc: 0x824         Lid: 50544   ClientVersion:
15.0.847.32    Lid: 52080   StoreEc: 0x824         Lid: 36081      Lid: 51152      Lid: 52465   StoreEc: 0x80040115
Lid: 60065      Lid: 33777   StoreEc: 0x80040115    Lid: 59805      Lid: 52487   StoreEc: 0x80040115    Lid: 19778      Lid: 27970
StoreEc: 0x80040115    Lid: 17730      Lid: 25922   StoreEc: 0x80040115
All of the issues listed above have been corrected, and all of the databases are mounted. Users are able to send and receive mail, but I can not migrate mail using the Migration Batch utility.
The destination server is a Hyper-V Guest running Server 2012, SP1, and Exchange 2013
The Source Server is Running Exchange 2007.
I have tried doing a test move to another destination server that is also Server 2012, and Exchange 2013, and the migration also failed.
I would appreciate any help you can give me!
Thanks,
Jon

Any update if you have resolved the issue.
Not similar, but this thread can be helpful while you migrate the mailboxes from exchange 2007 to 2013. Please check :http://social.technet.microsoft.com/Forums/exchange/en-US/721f0ae4-623a-4b02-adaf-f561d86c0426/move-mailboxes-and-public-folders-from-exchange-2007-to-exchange-2013?forum=exchangesvrdeploy&prof=required

Removing mailbox databases

Hello!
I'm getting this warning when removing a mailbox database in Exchnage 2013 SP1:
I've never had it in Exchange 2013 (NOT SP1)... How can I now remove a "monitoring mailbox object of database ..." from my AD?
Thank you in advance,
Michael

Hi
Here you go
Failed to remove monitoring mailbox object of database “database_name”. Exception: Active directory operation failed on “server_name”. This error is not retrievable. Additional information: Access is
denied. Active directory response: 000000005: SecErr: DSID-031520B2, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0.
In this case, the database was removed an Active Directory [AD] error (with a not very useful description) complaining about insufficient permissions is thrown. If you run:
Get-Mailbox -Monitoring
You will most likely see a warning regarding a corrupted Health Mailbox:
WARNING: The object “domain_name”/Microsoft Exchange System Objects/Monitoring Mailboxes/”Health_Mailbox_GUID” has been corrupted, and it's in an inconsistent state. The following validation errors happened:
WARNING: Database is mandatory or UserMailbox.
Because Exchange 2013 did not have sufficient permissions to the domainname/Microsoft Exchange System Objects/Monitoring Mailboxes Organizational Unit [OU], it could not delete the AD objects related to the database’s health mailboxes. In
this case, the database attribute is null because the database the health mailbox references no longer exists.
To fix this issue, simply delete the health mailboxes referenced by the error(s) from that OU by using Active Directory Users and Computers. After removing these, the warning should be gone.
Deleting health mailboxes is a low risk procedure because they will be automatically re-created by the Microsoft Exchange Health Manager service on the Exchange 2013 server hosting the database when this service is restarted
Source of information - http://www.msexchange.org/kbase/ExchangeServerTips/ExchangeServer2013/ManagementAdministration/exchange-2013-error-deleting-database.html
Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com Thanks Sathish
(MVP)

Is it possible to activate lagged mailbox databases automatically

Similar Messages

Maybe you are looking for