Exchange 2010 offline FSW failover occurs ?

Hello
We have two Exchange 2010 servers in DAG.
FSW is located on separate first DC and alternative FSW in located on second DC.
I know that Alternative FSW is not providing redundancy,...
We had a situation, that DC1 is been offline for few minutes because of windows updates
and when he was offline failover occurs from one Exchange node1 to node2 !
So my question is why failover occurs if the FWS is not online for some minutes and exchange 2 nodes are normaly online and working ?
Can we use Round Robin dns for FSW and create CNAME for fsw and add 2 hosts in it ? :)
Thanks for help,
BR
Marjan R.

Hello,
Sorry for delayed response.
You're right. The Alternate Witness Server itself does not provide any redundancy for the Witness Server, and DAGs do not dynamically switch witness servers, nor do they automatically start using the Alternate Witness Server in the event of a problem with
the Witness Server.
You can try to use Round Robin dns for FSW.
Cara Chen
TechNet Community Support

Similar Messages

Exchange 2010 - Offline Address Book and Global Address List Issue!

I don't think I'm going crazy but cant find out why this is happening?
When I search the Address book in cached mode (OAB) in outlook for "Jackie W"
I get a number of users which include "Jackie W***"
but some are "Jackie K***" or "Jackie B***"
but their Office is set to "Westminster"
But this is the strange part when I search on the address book with Cached mode disabled (GAL) I only get users with Surnames begging with
"W" so only "Jackie W***" show up and if I just type in "Westminster" I get users form that location! but not a mix like on the OAB! Also when using the OAB if I type
"Jackie West" it brings up the Jackie from Westminster but this dose not happen when using the GAL because there is no
"Jackie West" in the Address book?
To my knowledge the OAB is just a Copy of the GAL that updates every 24 hours, and should be the same (give or take a few starters and leavers in the last 24 hours) and should pull up the same information when searching is this correct or am I going crazy!
:D
Technical Beta Tester || Matthew John Earley BSc (hons) || www.o0MattE0o.myby.co.uk

Hi MattE,
Does it happen for each Outlook profile you have, from every user account which is on Cached Mode.
A.If not then I believe OAB copy is either corrupted or Out of date.
Checking it on OWA would confirm the actual GAL data.(Similar to Online Exchange)
Client side update runs by default at Startup and every 24hrs , if skipped it will wait for next day or manual update.
1.In Outlook 2010, select the File tab in the upper left corner, then Download Address Book from the Account Settings drop down menu.
Outlook 2007 users should select Tools from Outlooks uppermost menu, then Send/Receive and Download Address Book from the Tools drop down menus.
2.The Offline Address Book window will appear. Make sure the following options are selected:
##De-check the Download changes since last Send/Receive option
##Make sure Full Details is selected
##Make sure the \Global Address List is selected from the Choose address book drop down menu
Q: How frequently is the offline address book updated on the Outlook client?
A: If left constantly running, Outlook in cached mode automatically updates the offline address book on the client every 24 hours. The 24-hour time period is measured from the time that the offline address book was last downloaded successfully. For example, if you complete an offline address book download at 09:00 today, Outlook will start the offline address book download the next day at approximately 09:00. Therefore, different people will receive updates at different, random times.
Note The default setting on the Exchange computer is to generate an offline address book differential file every morning at 04:00. For a change that is made in Active Directory to reach the client computer, the following events must occur:•The change must be picked up by the Exchange computer that generates the offline address book files. This can take several hours. At worst, it can take 24 hours. This variable will be referred to as "x."
•The Outlook clients must download the offline address book updates every 24 hours. This update can take several hours. At worst, it can take 24 hours. This variable will be referred to as "y."
The update reaches the client machines x+y hours later. It would be rare for a client to ever experience a 48-hour delay or more unless there were some Active Directory or public folder replication issues.
B.If yes, then there is a issue with OAB generation, that needs further troubleshooting depending on the distribution structure used Public Folder based or EWS.
• Try following:
EMC > Organization configuration > Mailbox > Offline address book.
Then right click on "Default offline addressbook" and select properies.
Click on "Distribution" tab, and untick "Enable public folder distribution". Click "Apply" and "OK"
Update the Address Book. Let replication finish.
Now go back to same location and tick "Enable public folder distribution" back again. Click "Apply" and "OK".
Here is a old times article I like:
Offline Address List Generation Overview
http://blogs.msdn.com/b/dgoldman/archive/2005/03/31/overview-of-the-oabgen-process.aspx
One More Old but relevant:
Administering the offline address book in Outlook
http://support.microsoft.com/kb/841273
Regards,
Satyajit
Please “Vote As Helpful”
if you find my contribution useful or “Mark As Answer” if it does answer your question. That will encourage me - and others - to take time out to help you.

Multi site Exchange 2010 deployment. Failover and Autodiscover

I have made some significant changes to my Exchange environment that have me a little confused as to how to proceed.
A few months ago I upgraded from SP1 to SP3 UR5 and my previous strategy for DR stopped working.
Just to give a little background:
I have two sites connected with a 100Mb ethernet link that each have a dag member with a hub transport and two CAS servers. These servers at each site are load balanced with a Kemp Technologies LM-2200 cluster.
Previous to the upgrade we were working in warm standby where a passive copy of the mailbox databases were being held in the second site but not being used until needed. When needed we would change the load balancer to connect users to the second site
or in the case of a site failure we would change DNS to point to the second site. After the upgrade things changed and I could no longer do cross site RPC out of the box and when I enabled cross site RPC it still did not work like previous so I figured
this would be a good opportunity to strengthen my setup and try to go for a more automatic failover design were each site gets its own namespace and the CAS servers can redirect users to the correct site based on the current state of the DAG.
This works great aside from the folks who are not connected to the domain to get SCP. For instance I have activesync devices and OWA users on the outside. If the primary site goes down before these devices make an attempt to connect they will
not know that the site is down and their mailbox is now active in the secondary site. The device will just fail to connect.
Is there any way to make autodiscover site resilient? The only thing I can think of is using round robin DNS for autodiscover but that would likely cause some connection troubles if the site that is randomly resolved happens to be down.
Thoughts on this would be appreciated.
Thank you,
Nick

I realize that DAC mode does nothing but prevent the databases from mounting without open communication between the DAG members. I was not insinuating that it would help with my DR strategy other than that I know I could run into trouble if I do not
enable it and the DAG members come online but cannot talk to each other.
I realize that the alternate witness does not activate without intervention. If you read my reply you would see that I am not interested in full DR being automatic.
"I do not expect to have zero intervention when doing a datacenter switchover but I would prefer to have it as automated as possible when there is a simple failure of the primary dag member and the witness is still available. We have had this happen
a few times when the information store service has failed due to bugs in old code and the second site came online without difficulty."
I realize that everyone says HA should be provided by DAG nodes in the same site but I do not have that luxury right now. In most of the cases were this would even apply a second DAG member in the same site would do me no good because typically the
issues that have caused failover in the past have been related to the underlying systems of our VM environment (storage, network, blade chassis). There is no reason that an automatic failover DAG cannot be maintained across a strong Ethernet link between
sites as long as the limitations are well documented and followed.
In the case that I have to run Exchange out of the DR site alone I would bring up the alternate witness server and remove the primary DAG member from service giving the DR site majority and users would connect to Exchange via the DR namespace.
Regardless of all that the original question I had has not been answered. How does autodiscover get handled in a scenario like this? If my autodiscover addresses are pointed at a site that is not operational devices will not know where to go
for services. Is my only option to repoint DNS and wait hours for the record changes to propagate?

Exchange 2010 "This message could not be sent. Try sending the message again later, or contact your network administrator. Error is [0x80004005-00000000-00000000].

Exchange 2010 "This message could not be sent. Try sending the message again later, or contact your network administrator. Error is [0x80004005-00000000-00000000].
In a mixed client environment, mostly Outlook 2010 & 2013 clients. Only Outlook 2013 clients (about only 4 mailboxes) are receiving this error immediately after sending an email. My temp band-aid at the
moment is to: from the client, go into the "address book" & select a different address book like "Contacts" & then select the address again & select the Global Address List, which is the default. (it will have the users email
+ at the beginning of the field, it reads, Global Address List - (email of the user), then I close Outlook & open it back up, & the problem is solved. But on some mailboxes, not all, the issue comes back. From my research, I know that our individual
mailboxes do not send out over 500 emails in one day. Most users will send out maybe 20 or 30 in one day, so I don't think it's that.
But I'm not sure if this is related, but I have noticed that the log files for the Exchange 2010 seems to only hold logs with date stamps of only a couple of days. It used to hold log files indefinitely until they were archived, deleted, etc. So, this is
a new, unusual issue I have seen as well.
We have 2 .edb's, one active: 78 GB's and one disabled at 7 GB's. Exchange 2010 is running on Windows Server 2008 r2, Enterprise Ed. We have had Exchange 2010 running now for about almost 2 years now and this is the first time this particular issue has come
up.
Thanks.

Hi,
You can refer to the following steps to rebuild an Offline Address Book.
1. Open EMS. Update OAB using the Update-OfflineAddressbook "offline address book" cmdlet. Restart Background Intelligent Transfer Service on the Mailbox server.
2. Initiate OAB replication from mail box server to CAS server. Execute for each CAS server using the Update-FileDistributionService "CASServerName" cmdlet.
3. Start Outlook and download OAB.
What's more, here is an article for your reference.
How to Quickly Rebuild an Exchange 2010 Offline Address Book
http://social.technet.microsoft.com/wiki/contents/articles/7725.how-to-quickly-rebuild-an-exchange-2010-offline-address-book.aspx
Hope this can be helpful to you.
Best regards,
Amy Wang
TechNet Community Support

Force email download in HTML or text format on iPhone/iPad with ActiveSync (Exchange 2010 SP3)

Hi,
When an HTML email with attachment is received on iPhone/iPad (iOS 8.2),
it can be downloaded in three cases of
intermittents ways :
- The full message is downloaded in HTML format
- The message is download in text format and a
"Download full message" link is displayed
at the bottom of the message
- The message is displayed in text format,
but continues to download the rest of the message.
When the download is complete, the message is displayed
in HTML format.
This behavior is intermittent. The Apple's support
says it is a particular configuration on Exchange server
that causes this behavior.
I want to know if there is a way to fix
this problem and force download email
either in text or HTML format ?
This problem occurs on iPhones/iPad
(iOS8.2) with ActiveSync account (Exchange 2010
SP3). It occurs also with Outlook.com account.
On the Exchange 2010 SP3 server, The MaxEmailBodyTruncationSize
and MaxEmailHTMLBodyTruncationSize settings are
unlimited in ActiveSync policies.
Thank you for your help.

Hi,
We can configure Exchange ActiveSync Mailbox Policy Properties to force device download HTML or text format email.
Use the EMC to view or configure Exchange ActiveSync Mailbox Policy by the following steps:
In the console tree, navigate to Organization Configuration >
Client Access.
In the result pane, click the Exchange ActiveSync Mailbox Policies tab, and then select the policy you want to view or configure.
In the action pane, click Properties.
Under the Sync Settings tab, check or uncheck the box
Allow HTML-formatted e-mail. Select this check box to enable e-mail messages that are formatted in HTML to be synchronized to the mobile phone. If this check box isn't selected, all e-mail messages will be converted to plain text before synchronization.
And use this command to configure whether allow text messaging on the mobile phone. The Exchange Enterprise Client Access License is required to change the values of this setting.
Set-ActiveSyncMailboxPolicy -Identity PolicyName –AllowTextMessaging $True
For more information, please refer to this document.
https://technet.microsoft.com/en-us/library/bb123484(v=exchg.141).aspx
Best Regards.
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Lynn-Li
TechNet Community Support

Exchange 2010 DAG Failover does not works

Hi Experts,
I have a Exchange 2010 setup in a DAG environment. We have 2 MBX servers in the main site and 1 MBX server in the DR site , all part of one DAG. We have 2 HUB/CAS servers in the main site and 1 HUB/CAS server in the DR site.
Recently we had to do our BCP test for audit purpose. We had issues in doing failover to the DR site and below is the error faced.
Please advise urgently on the possible causes and resolution steps for it as we need to do this test again on the coming weekend.
"EvictDagClusterNode got exception Microsoft.Exchange.Cluster.Replay.AmClusterEvictWithoutCleanupException: An Active Manager operation failed. Error An error
occurred while attempting a cluster operation. Error: Evict node 'sme-ho-mbx01' returned without the node being fully cleaned up. Please run cluster.exe node <NodeName> /forcecleanup to complete clean up for this node.. ---> System.ComponentModel.Win32Exception:
The wait operation timed out"
So, basically one of the MBX server was not evicting from the Cluster due to which failover did not work.
Would appreciate some urgent thoughts for the possible resolution.
regards
abubakar
Md.Abubakar Noorani IT Systems Engineer Serco Ltd.

Hi,
Yes, you can run the Stop-DatabaseAvailabilityGroup without shutting down the Mailbox server. During the process of DAG failover to DR site, the Stop-DatabaseAvailabilityGroup cmdlet should be run against all servers in the primary datacenter. If the Mailbox
server is unavailable but Active Directory is operating in the primary datacenter, the Stop-DatabaseAvailabilityGroup command with the ConfigurationOnly parameter must be run against all servers in this state in the primary datacenter.
And please note that the Stop-DatabaseAvailabilityGroup cmdlet can be run against a DAG only when the DAG is configured with a DatacenterActivationMode value of DagOnly.
Based on the error message, it seems that you should run the cluster node nodename /forcecleanup cmdlet against the specified node in the main site. Have you tried this to check the result?
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Exchange 2010 SP3 Move Mailbox fails on every mailbox with Fatal error MapiExceptionJetErrorIndexNotFound has occurred

We are currently running Small Business Server 2003 with Exchange 2003 SP2 and are migrating to Server 2008 R2 with Exchange 2010 SP3 as an interim before moving to Server 2012 R2 with Exchange 2013 SP1. The mailbox move reaches 95% before failing with the
message "Fatal error MapiExceptionJetErrorIndexNotFound has occurred.
Error details: MapiExceptionJetErrorIndexNotFound: Unable to copy to target. (hr=0x80004005, ec=-1404)
Diagnostic context:
    Lid: 45095   EMSMDB.EcDoRpcExt2 called [length=78]
    Lid: 61479   EMSMDB.EcDoRpcExt2 returned [ec=0x0][length=75][latency=0]
    Lid: 23226   --- ROP Parse Start ---
    Lid: 27962   ROP: ropGetPropsSpecific [7]
    Lid: 21921   StoreEc: 0x40380
    Lid: 31418   --- ROP Parse Done ---
    Lid: 45095   EMSMDB.EcDoRpcExt2 called [length=45]
    Lid: 61479   EMSMDB.EcDoRpcExt2 returned [ec=0x0][length=140][latency=0]
    Lid: 23226   --- ROP Parse Start ---
    Lid: 27962   ROP: ropGetReceiveFolderTable [104]
    Lid: 31418   --- ROP Parse Done ---
    Lid: 45095   EMSMDB.EcDoRpcExt2 called [length=69]
    Lid: 61479   EMSMDB.EcDoRpcExt2 returned [ec=0x0][length=48][latency=0]
    Lid: 23226   --- ROP Parse Start ---
    Lid: 27962   ROP: ropGetAllPerUserLtids [125]
    Lid: 17082   ROP Error: 0xFFFFFA84
    Lid: 29793
    Lid: 21921   StoreEc: 0xFFFFFA84
    Lid: 31418   --- ROP Parse Done ---
    Lid: 22753
    Lid: 21817   ROP Failure: 0xFFFFFA84
    Lid: 25738
    Lid: 18570   StoreEc: 0xFFFFFA84
    Lid: 23370   StoreEc: 0xFFFFFA84
    Lid: 24302
    Lid: 32494   StoreEc: 0xFFFFFA84
   at Microsoft.Mapi.MapiExceptionHelper.ThrowIfErrorOrWarning(String message, Int32 hresult, Boolean allowWarnings, SafeExInterfaceHandle iUnknown, Exception innerException)
   at Microsoft.Mapi.MapiUnk.ThrowIfErrorOrWarning(String message, Int32 hr)
   at Microsoft.Mapi.MapiProp.CopyTo(MapiProp destProp, Boolean reportProgress, CopyPropertiesFlags copyPropertiesFlags, Boolean copySubObjects, ICollection`1 excludeTags)
   at Microsoft.Mapi.MapiProp.ExportObjectHelper(IMapiFxProxy dest, PropTag[] tags, CopyPropertiesFlags copyPropertiesFlags, Boolean useCopyProps)
   at Microsoft.Mapi.MapiProp.ExportObject(IMapiFxProxy fxProxy, CopyPropertiesFlags copyPropertiesFlags, PropTag[] excludeTags)
   at Microsoft.Exchange.MailboxReplicationService.LocalSourceMailbox.Microsoft.Exchange.MailboxReplicationService.ISourceMailbox.CopyTo(IFxProxy fxProxy, PropTag[] excludeTags)
   at Microsoft.Exchange.MailboxReplicationService.SourceMailboxWrapper.<>c__DisplayClass7.<Microsoft.Exchange.MailboxReplicationService.ISourceMailbox.CopyTo>b__6()
   at Microsoft.Exchange.MailboxReplicationService.ExecutionContext.Execute(GenericCallDelegate operation)
   at Microsoft.Exchange.MailboxReplicationService.SourceMailboxWrapper.Microsoft.Exchange.MailboxReplicationService.ISourceMailbox.CopyTo(IFxProxy destMailbox, PropTag[] excludeProps)
   at Microsoft.Exchange.MailboxReplicationService.MailboxMover.FinalSyncCopyMailboxData()
   at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.ForeachMailboxContext(MailboxMoverDelegate del)
   at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.FinalSync(Object[] wiParams)
   at Microsoft.Exchange.MailboxReplicationService.CommonUtils.CatchKnownExceptions(GenericCallDelegate del, FailureDelegate failureDelegate)
Error context: --------
Operation: ISourceMailbox.CopyTo
OperationSide: Source"
This is happening on every mailbox we attempt to move. Any help would be appreciated

Thanks for responding
I'm already using BadItemLimit of 50. The largest corrupt message that was skipped is 10.
We're on Small Business Server Standard Edition which only permits one mailbox store. I should mention that the interim machine (where Exchange 2010 is installed) is a Hyper V virtual machine
Here is the entire message from the log:
11/28/2014 7:18:07 PM [VRTL-SVR2008] 'PeacePresbyterianChurch.local/MyBusiness/Users/SBSUsers/Dev Mathura' created move request.
11/28/2014 7:18:27 PM [VRTL-SVR2008] The Microsoft Exchange Mailbox Replication service 'VRTL-SVR2008.PeacePresbyterianChurch.local' (14.3.123.2 caps:07) is examining the request.
11/28/2014 7:18:27 PM [VRTL-SVR2008] Connected to target mailbox 'Primary (d3391cdd-bc37-41ad-9e44-9f8880c47270)', database 'Mailbox Database 0224662151', Mailbox server 'VRTL-SVR2008.PeacePresbyterianChurch.local' Version 14.3 (Build 123.0).
11/28/2014 7:18:27 PM [VRTL-SVR2008] Connected to source mailbox 'Primary (d3391cdd-bc37-41ad-9e44-9f8880c47270)', database 'PEACE-SERVER\First Storage Group\Mailbox Store (PEACE-SERVER)', Mailbox server 'peace-server.PeacePresbyterianChurch.local' Version
6.0 (Build 7654.0).
11/28/2014 7:18:38 PM [VRTL-SVR2008] Request processing started.
11/28/2014 7:18:38 PM [VRTL-SVR2008] Mailbox signature will not be preserved for mailbox 'Primary (d3391cdd-bc37-41ad-9e44-9f8880c47270)'. Outlook clients will need to restart to access the moved mailbox.
11/28/2014 7:18:38 PM [VRTL-SVR2008] Source mailbox information before the move:
Regular Items: 20, 1.906 MB (1,998,818 bytes)
Regular Deleted Items: 3, 7.803 KB (7,990 bytes)
FAI Items: 20, 0 B (0 bytes)
FAI Deleted Items: 0, 0 B (0 bytes)
11/28/2014 7:18:39 PM [VRTL-SVR2008] Initializing folder hierarchy in mailbox 'Primary (d3391cdd-bc37-41ad-9e44-9f8880c47270)': 31 folders total.
11/28/2014 7:18:40 PM [VRTL-SVR2008] Folder hierarchy initialized for mailbox 'Primary (d3391cdd-bc37-41ad-9e44-9f8880c47270)': 31 folders total.
11/28/2014 7:18:40 PM [VRTL-SVR2008] Stage: CreatingInitialSyncCheckpoint. Percent complete: 15.
11/28/2014 7:18:40 PM [VRTL-SVR2008] Stage: LoadingMessages. Percent complete: 20.
11/28/2014 7:18:40 PM [VRTL-SVR2008] Mailbox 'Primary (d3391cdd-bc37-41ad-9e44-9f8880c47270)' contains 3 soft-deleted items (7.803 KB (7,990 bytes)). They won't be migrated.
11/28/2014 7:18:40 PM [VRTL-SVR2008] Stage: CopyingMessages. Percent complete: 25.
11/28/2014 7:18:40 PM [VRTL-SVR2008] Copy progress: 0/38 messages, 0 B (0 bytes)/1.906 MB (1,998,550 bytes).
11/28/2014 7:18:41 PM [VRTL-SVR2008] Messages have been enumerated successfully. 38 items loaded. Total size: 1.906 MB (1,998,550 bytes).
11/28/2014 7:18:43 PM [VRTL-SVR2008] Initial seeding completed, 38 items copied, total size 1.906 MB (1,998,550 bytes).
11/28/2014 7:18:44 PM [VRTL-SVR2008] Final sync has started.
11/28/2014 7:18:45 PM [VRTL-SVR2008] Stage: FinalIncrementalSync. Percent complete: 95.
11/28/2014 7:18:46 PM [VRTL-SVR2008] Fatal error MapiExceptionJetErrorIndexNotFound has occurred.
Error details: MapiExceptionJetErrorIndexNotFound: Unable to copy to target. (hr=0x80004005, ec=-1404)
Diagnostic context:
    Lid: 45095   EMSMDB.EcDoRpcExt2 called [length=78]
    Lid: 61479   EMSMDB.EcDoRpcExt2 returned [ec=0x0][length=75][latency=0]
    Lid: 23226   --- ROP Parse Start ---
    Lid: 27962   ROP: ropGetPropsSpecific [7]
    Lid: 21921   StoreEc: 0x40380
    Lid: 31418   --- ROP Parse Done ---
    Lid: 45095   EMSMDB.EcDoRpcExt2 called [length=45]
    Lid: 61479   EMSMDB.EcDoRpcExt2 returned [ec=0x0][length=140][latency=0]
    Lid: 23226   --- ROP Parse Start ---
    Lid: 27962   ROP: ropGetReceiveFolderTable [104]
    Lid: 31418   --- ROP Parse Done ---
    Lid: 45095   EMSMDB.EcDoRpcExt2 called [length=69]
    Lid: 61479   EMSMDB.EcDoRpcExt2 returned [ec=0x0][length=48][latency=0]
    Lid: 23226   --- ROP Parse Start ---
    Lid: 27962   ROP: ropGetAllPerUserLtids [125]
    Lid: 17082   ROP Error: 0xFFFFFA84
    Lid: 29793
    Lid: 21921   StoreEc: 0xFFFFFA84
    Lid: 31418   --- ROP Parse Done ---
    Lid: 22753
    Lid: 21817   ROP Failure: 0xFFFFFA84
    Lid: 25738
    Lid: 18570   StoreEc: 0xFFFFFA84
    Lid: 23370   StoreEc: 0xFFFFFA84
    Lid: 24302
    Lid: 32494   StoreEc: 0xFFFFFA84
   at Microsoft.Mapi.MapiExceptionHelper.ThrowIfErrorOrWarning(String message, Int32 hresult, Boolean allowWarnings, SafeExInterfaceHandle iUnknown, Exception innerException)
   at Microsoft.Mapi.MapiUnk.ThrowIfErrorOrWarning(String message, Int32 hr)
   at Microsoft.Mapi.MapiProp.CopyTo(MapiProp destProp, Boolean reportProgress, CopyPropertiesFlags copyPropertiesFlags, Boolean copySubObjects, ICollection`1 excludeTags)
   at Microsoft.Mapi.MapiProp.ExportObjectHelper(IMapiFxProxy dest, PropTag[] tags, CopyPropertiesFlags copyPropertiesFlags, Boolean useCopyProps)
   at Microsoft.Mapi.MapiProp.ExportObject(IMapiFxProxy fxProxy, CopyPropertiesFlags copyPropertiesFlags, PropTag[] excludeTags)
   at Microsoft.Exchange.MailboxReplicationService.LocalSourceMailbox.Microsoft.Exchange.MailboxReplicationService.ISourceMailbox.CopyTo(IFxProxy fxProxy, PropTag[] excludeTags)
   at Microsoft.Exchange.MailboxReplicationService.SourceMailboxWrapper.<>c__DisplayClass7.<Microsoft.Exchange.MailboxReplicationService.ISourceMailbox.CopyTo>b__6()
   at Microsoft.Exchange.MailboxReplicationService.ExecutionContext.Execute(GenericCallDelegate operation)
   at Microsoft.Exchange.MailboxReplicationService.SourceMailboxWrapper.Microsoft.Exchange.MailboxReplicationService.ISourceMailbox.CopyTo(IFxProxy destMailbox, PropTag[] excludeProps)
   at Microsoft.Exchange.MailboxReplicationService.MailboxMover.FinalSyncCopyMailboxData()
   at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.ForeachMailboxContext(MailboxMoverDelegate del)
   at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.FinalSync(Object[] wiParams)
   at Microsoft.Exchange.MailboxReplicationService.CommonUtils.CatchKnownExceptions(GenericCallDelegate del, FailureDelegate failureDelegate)
Error context: --------
Operation: ISourceMailbox.CopyTo
OperationSide: Source
Primary (d3391cdd-bc37-41ad-9e44-9f8880c47270)
PropTags: [ContainerHierarchy; ContainerContents]
11/28/2014 7:18:46 PM [VRTL-SVR2008] Relinquishing job.

Unable to remove orpahned Exchange 2010 mailbox databse server permantely offline

Greetings,
I am having great problems removing and Exchange 2010 mailbox Database, the server that the database resided upon is permanently offline and gone,
Under Organization Configuration / mailbox
The orphaned database is listed there however I cannot delete it under Database Copies a copy of the orphaned database is listed as offline.
How can I remove this database if the server is offline?

run ADSIEDIT.msc
Select Configuration well-known naming configuration -> CN=Configuration -> CN=Services -> CN=Microsoft Exchange -> CN=<YourExchOrgName> -> CN=Administrative Group -> CN=Exchange Administrative
Group (FYDIBOHF23SPDLT) -> CN=Servers > CN=Databases -> Select Exchange 2010 database name and delete
MCP, MCSE 2000 , MCSA 2000 ,MCSA 2003 , MCITP , MCTS , MCT

Exchange 2010 and Outlook 2010 Offline Address Book Download

Hi All,
Strange problem that I can't seem to get to the bottom of.
On a couple of users, about 10/100, can't seem to download the Offline Address Book. When they do a manual Download Address Book through Send/Receive Group, the progress window will remain at about 5% and the status will show "Copying Offline Address Book
Template File". If I leave the window, it will be the same for a couple of hours without erroring out.
We have a casarray set up, forced the ports to 59595 and 59596 for the address book as mentioned the guide. We are not doing SSL redirect on the Virtual Directory. Test-AutoConfiguration from Outlook returns the correct entries. Works for most users but
not all.
On the users that do not work, I've tried deleting the users profile, deleting the Outlook Directory under AppData. Sometimes, magically (for a lack of a better word), if I check the Offline Address Book Directory a few days later, there are files there.
If I then do a manual Download, same thing, the progress bar will be stuck.
Puzzling as I'm not quite sure what else to check.
All clients are on Windows 7 and Outlook 2010.
Any ideas?
Thanks,
Dave K

I also used your recipe --disconnect the wireless mouse-- and the OAB update worked right away.
     (It is not a Microsoft mouse.   )
Thanks for the information.
I have been trying to find information on non-HID.
If you have any quick tips or a pointer to info about this, I wanted to get a better understanding of this topic.
Does this "wireless" for the mouse use the same "wireless" for the laptop regular network access via WiFi ?
(We had some evidence that when the laptop did not use the wireless mouse the OAB worked OK and/or when the laptop was running only on WiFi the OAB worked OK.    Not sure if this is all the same root cause.)
Also, does anyone know if this is something that Microsoft will fix at some point ?
We are trying to determine if "few or many" people here might be having OAB failures and have not reported it.
Thanks again.
keywords ---- Outlook 2010 Offline Addrress Book update OAB Exchange 2007 cache mode wireless mouse Windows 7 W7 hung manual OAB update scheduled / automatic OAB update
==

Move mailbox from exchange 2010 2003 , Transient error MapiExceptionLogonFailed has occurred.

We are currently migrating from Exchange 2003 to Exchange 2010, same domain.
We have successfully moved some mailboxes from exchange 2003 to exchange 2010 without any problems.
Now we need to move 1 mailbox back from exchange 2010 to exchange 2003.
After creating the moverequest it stucks on 0% and the log shows the error below.
After using Bing I found this post -> http://social.technet.microsoft.com/Forums/exchange/en-US/ef41ae05-8816-4c0c-968a-c48f0e3d50b5/move-mailbox-back-from-exchange-2010-to-exchange-2003-failure?forum=exchangesvrdeploylegacy
This suggest ->
After I give FULL permissions to each Mailbox Stores on Exchange 2003 server, I was able to move my mailbox back onto the Exchange 2003 server. In details:
Simply right click Storage Group\Mailbox Store and go to Security, in there you may see Exchange Servers group already there, if no add it in, then give it FULL permissions! and thats it!
Create a new move request but still stuck on 0% and error as below
20-3-2014 16:32:10 [ex2010p11] 'contoso.com/Users/exadmin' created move request.
20-3-2014 16:32:11 [ex2010p21] The Microsoft Exchange Mailbox Replication service 'exchangep21.contoso.com' (14.3.151.0 caps:07) is examining the request.
20-3-2014 16:32:11 [ex2010p21] Connected to target mailbox 'Primary (82b54f9e-27ff-44d2-9142-f949d567e1e7)', database 'ex2003\Basic\Basic', Mailbox server 'ex2003.contoso.com' Version 0.0 (Build 7638.0).
20-3-2014 16:32:11 [ex2010p21] Connected to source mailbox 'Primary (82b54f9e-27ff-44d2-9142-f949d567e1e7)', database 'EX2010DB', Mailbox server 'ex2010p20.contoso.com' Version 14.3 (Build 174.0).
20-3-2014 16:32:11 [ex2010p21] Request processing started.
20-3-2014 16:32:11 [ex2010p21] Transient error MapiExceptionLogonFailed has occurred. The system will retry (1/60).
Error details: MapiExceptionLogonFailed: Unable to make connection to the server. (hr=0x80040111, ec=1010)
Diagnostic context:
Lid: 13720 dwParam: 0x6D9 Msg: EEInfo: Flags: 0
Lid: 11672 dwParam: 0x6D9 Msg: EEInfo: NumberOfParameters: 4
Lid: 8856 dwParam: 0x6D9 Msg: EEInfo: prm[0]: Unicode string: ncacn_ip_tcp
Lid: 8856 dwParam: 0x6D9 Msg: EEInfo: prm[1]: Unicode string: ex2003
Lid: 12952 dwParam: 0x6D9 Msg: EEInfo: prm[2]: Long val: -545057711
Lid: 12952 dwParam: 0x6D9 Msg: EEInfo: prm[3]: Long val: 382312662
Lid: 45169 StoreEc: 0x824
Lid: 44273
Lid: 59431 EMSMDB.EcDoConnectEx called [length=163]
Lid: 34855 EMSMDB.EcDoConnectEx returned [ec=0x3F2][length=56][latency=0]
Lid: 56945
Lid: 59431 EMSMDB.EcDoConnectEx called [length=163]
Lid: 34855 EMSMDB.EcDoConnectEx returned [ec=0x3F2][length=56][latency=0]
Lid: 59505 StoreEc: 0x3F2
Lid: 52465 StoreEc: 0x3F2
Lid: 60065
Lid: 33777 StoreEc: 0x3F2
Lid: 59805
Lid: 52209 StoreEc: 0x3F2
Lid: 56583
Lid: 52487 StoreEc: 0x3F2
Lid: 19778
Lid: 27970 StoreEc: 0x3F2
Lid: 17730
Lid: 25922 StoreEc: 0x3F2
at Microsoft.Mapi.MapiExceptionHelper.ThrowIfError(String message, Int32 hresult, SafeExInterfaceHandle iUnknown, Exception innerException)
at Microsoft.Mapi.ExRpcConnection.Create(ConnectionCache connectionCache, ExRpcConnectionCreateFlag createFlags, ConnectFlag connectFlags, String serverDn, String userDn, String user, String domain, String password, String httpProxyServerName,
Int32 ulConMod, Int32 lcidString, Int32 lcidSort, Int32 cpid, Int32 cReconnectIntervalInMins, Int32 cbRpcBufferSize, Int32 cbAuxBufferSize, Client xropClient, Byte[] clientSessionInfo, TimeSpan connectionTimeout)
at Microsoft.Mapi.MapiStore.OpenMapiStore(String serverDn, String userDn, String mailboxDn, Guid guidMailbox, Guid guidMdb, String userName, String domainName, String password, String httpProxyServerName, ConnectFlag connectFlags, OpenStoreFlag
storeFlags, CultureInfo cultureInfo, Boolean wantRedirect, String& correctServerDN, ClientIdentityInfo clientIdentity, String applicationId, Client xropClient, Boolean wantWebServices, Byte[] clientSessionInfo, TimeSpan connectionTimeout)
at Microsoft.Mapi.MapiStore.OpenMailbox(String serverDn, String userDn, String mailboxDn, String userName, String domainName, String password, String httpProxyServerName, ConnectFlag connectFlags, OpenStoreFlag storeFlags, CultureInfo cultureInfo,
WindowsIdentity windowsIdentity, String applicationId)
at Microsoft.Exchange.MailboxReplicationService.MapiUtils.OpenSystemMailbox(Guid mdbGuid, String serverDN, String dcName, NetworkCredential cred, String& systemMailboxDn)
at Microsoft.Exchange.MailboxReplicationService.LocalMailbox.OpenSystemMailbox()
at Microsoft.Exchange.MailboxReplicationService.LocalMailbox.Microsoft.Exchange.MailboxReplicationService.IMailbox.SaveSyncState(Byte[] key, String syncStateStr)
at Microsoft.Exchange.MailboxReplicationService.MailboxWrapper.<>c__DisplayClass57.<Microsoft.Exchange.MailboxReplicationService.IMailbox.SaveSyncState>b__56()
at Microsoft.Exchange.MailboxReplicationService.ExecutionContext.Execute(GenericCallDelegate operation)
at Microsoft.Exchange.MailboxReplicationService.MailboxWrapper.Microsoft.Exchange.MailboxReplicationService.IMailbox.SaveSyncState(Byte[] key, String syncState)
at Microsoft.Exchange.MailboxReplicationService.MailboxCopierBase.ClearSyncState()
at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.<>c__DisplayClass23.<CleanupOrphanedDestinationMailbox>b__22(MailboxMover mbxCtx)
at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.ForeachMailboxContext(MailboxMoverDelegate del)
at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.CleanupOrphanedDestinationMailbox(Object[] wiParams)
at Microsoft.Exchange.MailboxReplicationService.CommonUtils.CatchKnownExceptions(GenericCallDelegate del, FailureDelegate failureDelegate)
Error context: --------
Operation: IMailbox.SaveSyncState
OperationSide: Target
Primary (82b54f9e-27ff-44d2-9142-f949d567e1e7)
Key: F2FA63B0116C564EA4C598D69786443D9E4FB582FF27D2449142F949D567E1E7E0CA914F6695624C98892FA527AAA91E
SyncStateLength: 0
20-3-2014 16:32:41 [ex2010p21] The Microsoft Exchange Mailbox Replication service 'ex2010p21.contoso.com' (14.3.151.0 caps:07) is examining the request.
20-3-2014 16:32:41 [ex2010p21] Connected to target mailbox 'Primary (82b54f9e-27ff-44d2-9142-f949d567e1e7)', database 'ex2003\Basic\Basic', Mailbox server 'ex2003.contoso.com' Version 0.0 (Build 7638.0).
20-3-2014 16:32:41 [ex2010p21] Connected to source mailbox 'Primary (82b54f9e-27ff-44d2-9142-f949d567e1e7)', database 'EX2010DB', Mailbox server 'ex2010p20.contoso.com' Version 14.3 (Build 174.0).
20-3-2014 16:32:41 [ex2010p21] Request processing started.
20-3-2014 16:32:41 [ex2010p21] Transient error MapiExceptionLogonFailed has occurred. The system will retry (2/60).

Hello，
When you move mailbox from exchange 2010 to exchange 2003, please check if the following situations exist:
http://technet.microsoft.com/en-us/library/dd638157(v=exchg.141).aspx
Before you move mailbox again, please clear the previous move request.
I recommend you use EXBPA to check your exchange server 2003 and exchange 2010.
Please check if inheritable permission is missing on the mailbox store on Exchange Server 2003.
Cara Chen
TechNet Community Support

Exchange 2010 SP3 DAG Flip Flop File Share Witness Issue

Hi All,
We are facing one strange issue with Exchange 2010 SP3.
Our environment is as below
a single DAG spanned accross 2 AD sites with 6 MBX server.
Each site have 3 MBx server.
File Share Witness is on Hub server in primary site.
Note: The DAG IP is from Primary DC VLAN and which cant be streched accross DC due to network restrictions/limitations.
It was working fine till date.
But, yesterday onwards we are facing issue.
All DB dismounted and DAG name disappear from EMC and while doing refresh its giving error as below
Exception type: Microsoft.Exchange.Data.DataValidationException
Exception message: Could not convert property WitnessServer to type UncFileSharePath. Error while converting string 'vesthub700.mydomain.com\DAG1.mydomain.com' to result type Microsoft.Exchange.Data.UncFileSharePath: "vesthub700.mydomain.com\DAG1.mydomain.com"
is not an acceptable path. You must use an absolute, local, long file path, that doesn't contain '~', or a UNC path. Parameter name: path
We are not able to execute any cmdlets related to databaseavailabilitygroup from EMS and its giving same error.
Failover Cluster DAG resource is Flip/Flip continuously.
Its only become stable after reboot of the hub server holding FSW and the 1st mailbox server.(Cluster Owner)
We are even not able to move cluster group to different server.
Performed ExBPA no such issues found which related to DAG.
Performed clsuter validation.
Only generic cluster events in Mailbox servers.
Observation:
Its only become stabe if we remove the msExchFileShareWitness Value for DAG1 using ADSIEdit.
And the problem recurs if we set it back again.
Any help or suggestion is appreciated.
Thanks,
soumen
Soumen Ghosh

Hi Belinda,
Thanks! I have checked the Mailbox Server Application Log and found few 2155 Event Id generated at the time of the issue occured.
Process Microsoft.Exchange.ServiceHost.exe () (PID=9312). Configuration object CN=DAG1,CN=Database Availability Groups,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=xxxxxx,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=mydomain,DC=com
read from DCTDK35.mydomain.com failed validation. DataValidationException will be thrown. Set event logging level for Validation category to Expert to get additional events about each failure.
One update is that the DAG is stable now after we set an alternate FSW last night.
Regarding the 2nd IP assignment for DAG for the 2nd subnet, we have gone through technet and other sites which refering to add the same from EMC or EMS.
Is it sufficinet to simply adding the 2nd IP to DAG from EMC or EMS? Or do we need to take any other special consideration.
Also, adding another IP it will create one more IP address resource to Failover Cluster, but I belive at a time both the IP wont be online. Do we need to keep it offline manually or its automatically taken care by Exchange.
Please suggest.
Also, regarding executing the CollectOverMetrics.ps1 we are following
http://www.msexchange.org/articles-tutorials/exchange-server-2010/monitoring-operations/monitor-dag-database-failover.html
but failed to execute. Can you suggest the correct parameter.
Thanks,
Soumen
Soumen Ghosh

Exchange 2010 DAG's - 4 Mailbox Servers in 2 Datacenters with per site redundancy

I recently came into a company with an Exchange 2010 sp1 environment where there are two data centers in two different subnets (10.70.62.0 and 10.80.56.0)
Each datacenter has 2 mailbox servers (4 servers total) but their plan was to have only enough storage space to host 1/2 of the databases on each server. So instead of server 1, 2, and 3 being copies of each other, ServerA is a copy of ServerA and ServerB
is a copy of ServerB
Server     -    Databases
Site1mbA - Primary Database copy 1-10
Site1mbB - Primary Database copy 11-20
Site2mbA - Secondary Database copy 1-10
Site2mbB - Secondary Database copy 11-20
Normally if there were enough storage space I would keep a copy on each server and replicate within 1 DAG.
However since not all the databases are on each member server do I need to use 2 DAGS? 1st for Site1mbA & Site2mbA and 2nd for Site1mbB & Site2mbB
I feel I would need the 2 DAG's because with 1 DAG if Site1mbA server went offline the DAG couldn't switch to the Failover Cluster IP for Site2 because there are still active mailboxes in Site1 on Site1mbB.
Does that make any sense or am I over complicating it?
Thanks!

There is no rule that every server in a DAG must have a copy of every Database. You could do this with one DAG, but if the WAN goes down then the DAG will be active in only a single site not both.
http://technet.microsoft.com/en-us/library/dd979781(v=exchg.141).aspx#FourTwo
As illustrated in the previous example, using a single four-member DAG extended across two datacenters can provide high availability and site resilience for the mailbox services and data. However, if a WAN outage occurs, only the primary datacenter retains
service because it contains the majority of the voters. The datacenter with the minority of voters loses majority, and the DAG members in that datacenter lose quorum and go offline.
To deploy highly available Mailbox servers in a multiple datacenter environment, where each datacenter is actively serving a local user population, we recommend that you deploy multiple DAGs, where each DAG has a majority of voters in a different datacenter,
as illustrated in the following figure.
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:
http://blogs.technet.com/rmilne
Twitter:   LinkedIn:
  Facebook:
  XING:
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.

[SOLVED] Can't add a node to the cluster with error (Exchange 2010 SP3 DAG Windows Server 2012)

Hi there!
I have a problem which makes me very angry already :)
I have two servers Exchange 2010 SP3 with MB role started on Windows Server 2012. I decided to create a DAG.
I have created the prestaged AD object for the cluster called msc-co-exc-01c, assigned necessary permissions and disabled it. Allowed through the Windows Firewall traffic between nodes and prepared the File Share Witness server.
Then I have tried to add nodes. The first node has been added successfully, but the second node doesn't want to be added :). Now I can add only one node to the DAG. I tried to add different servers first, but only the first one was added.
LOGS on the second nodes:
Application Log
"Failed to initialize cluster with error 0x80004005." (MSExchangeIS)
Failover Clustering Diagnostic Log
"[VER] Could not read version data from database for node msc-co-exc-04v (id 1)."
CMDLET Error:
Summary: 1 item(s). 0 succeeded, 1 failed.
Elapsed time: 00:06:21
MSC-CO-EXC-02V
Failed
Error:
A database availability group administrative operation failed. Error: The operation failed. CreateCluster errors may result from incorrectly configured static addresses. Error: An error occurred while attempting a cluster operation. Error: Cluster API '"AddClusterNode()
(MaxPercentage=100) failed with 0x5b4. Error: This operation returned because the timeout period expired"' failed. [Server: msc-co-exc-04v.int.krls.ru]
An Active Manager operation failed. Error An error occurred while attempting a cluster operation. Error: Cluster API '"AddClusterNode() (MaxPercentage=100) failed with 0x5b4. Error: This operation returned because the timeout period expired"' failed..
This operation returned because the timeout period expired
Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.3.174.1&t=exchgf1&e=ms.exch.err.ExC9C315
Warning:
Network name 'msc-co-exc-01c' is not online. Please check that the IP address configuration for the database availability group is correct.
Warning:
The operation wasn't successful because an error was encountered. You may find more details in log file "C:\ExchangeSetupLogs\DagTasks\dagtask_2014-11-17_13-54-56.543_add-databaseavailabiltygroupserver.log".
Exchange Management Shell command attempted:
Add-DatabaseAvailabilityGroupServer -MailboxServer 'MSC-CO-EXC-02V' -Identity 'msc-co-exc-01c'
Elapsed Time: 00:06:21
UPD:
when Exchange servers ran on the same Hyper-V node, the DAG is working well, but if I move one of VM to another node, It stops working.
I have installed Wireshark and captured trafic of cluster interface. When DAG members on the same HV-node, there is inbound and outbound traffic on the cluster interface, but if I move one of DAG member to another node, in Wireshark I see only outbound traffic
on both nodes.
It's confused me, because there is normal connectivity between these DAG members through the main interface.
Please, help me if you can.

Hi, Jared! Thank you for the reply.
Of course I did it already :) I have new info:
when Exchange servers ran on the same Hyper-V node, the DAG is working well, but if I move one of VM to another node, It stops working.
I have installed Wireshark and captured trafic of cluster interface. When DAG members on the same HV-node, there is inbound and outbound traffic on the cluster interface, but if I move one of DAG member to another node, in Wireshark I see only outbound traffic
on both nodes.
It's confused me, because there is normal connectivity between these DAG members through the main interface.

Replay only particular logs (before a certain date) to restored Exchange 2010 database?

Hello,
I'm doing Exchange 2010 database full backup using windows server backup (windows 2008 R2) every weekend. I have a Mac user which Mac Outlook 2011 which somehow managed to corrupt his mailbox. I.e. on Wednesday many messages and contacts disappeared (all
contact gone) after his Outlook told his something about "corrupted database". I'm not sure what Mac Outlook did, but fact is that his mailbox has zero contacts and many inbox message are gone. Hard deleted items don't contain lost messages.
So I have DB backup from weekend before and weekend after. No circular logging, so all logs in place.
Is there a way how I can restore his mailbox back to the point in time? I want to restore his mailbox how it was on Wednesday morning. For it looks obvious that since I have log files from Monday to Friday, it should be possible to replay logs until certain
time.
I tried to did thick trick by removing Friday and Thursday logs and doing soft recovery, but got Operation terminated with error -543 (JET_errRequiredLogFilesMissing, The required log files for recovery is missing.) They indeed missing:
dbtime: 2221857861 (0x846edc45)
State: Dirty Shutdown
Log Required: 2895446-2895464 (0x2c2e56-0x2c2e68)
Log Committed: 0-2895465 (0x0-0x2c2e69)
Log Recovering: 2838005 (0x2b4df5)
Log required are logs from they day of backup, so they are really missed in that case, but that's what I want - restore DB with less/older logs to get back in time, when mailbox was not corrupted.
Is that possible?
Thanks

ok so the problem is you have the dreaded -1018 error and this is a very serious issue. -1018 is not a good deal at all, in short your DB has corruption within it
and it is usually caused by a hardware or firmware related issue. Most of the time these occur somewhere within the storage subsystem, i.e. firmware upgrade or lack of firmware upgrade, Controller issue, cabling, disk, disk arrays, etc, however they can
also be caused by memory upgrades or failures, Motherboard issues etc.   The -1018 tells you the DB is already damaged and if you see these its very bad and needs to be addressed ASAP else the DB's are sure to fail and the more stress you put on
them the faster the chance of failure, i.e. database backups, defrag;s and repairs etc are not recommended at all until you solve the hardware issue. So here is what I would recommend:
A: Lets try to ensure the box is stable and whatever caused the DB to get the -1018's is solved before we do anything else.
General Review: Whats changed recently? i.e. any hardware, memory, motherboard, any firmware updates on anything at all?
Event Log Review: Look at your Application Log, how long have these 1018's been occurring?   Look at your System event log for errors and pay close attention to any errors regarding disk, memory or MB and report back
Protect: I would dismount the database & copy it and any others off to a secure, safe drive that is NOT connected to this system
Action: Depending on what you find in your review there are really two options
     i: If you had a recent change that is easily identifiable you may be able to correct it and then we can look at finding a clean copy of the EDB and rolling up the logs OR we opt to repair the DB you have
     ii: if you cannot find the issue in short order then I would suggest that you build a new Exchange Server on new hardware and migrate your mailboxes immediately.
B: Once you have addressed the -1018 issue then;
1. We need to find a database from your backups that does NOT have the -1018 result code when attempting a rollup.
2. Once you have a non -1018 result you can then grab a fresh copy of the EDB along with all logs from that point forward and make a consistent DB via rollup up to the 18th as desired.
3. If you cannot find a good copy of the EDB then you are stuck with the latest data you have and should either move all mailboxes to a new EDB on that server but ONLY IF the source of the -1018 is found and resolved, else you will just be making thing s
worse. IF you CANNOT resolve the issue that causes the -1018 then build a brand new server and move all users over to it ASAP, else you are headed for a major failure on all users.
Search, Recover, & Extract Mailboxes, Folders, & Email Items from Offline Exchange Mailbox and Public Folder EDB's and Live Exchange Servers or Import/Migrate direct from Offline EDB to Any Production Exchange Server, even cross version i.e. 2003 -->
2007 --> 2010 --> 2013 with Lucid8's
DigiScope

Exchange 2010 DAG netowrk replications issues - Causing database copies to be disconnected and resynchronizing.

My
environment is as follows.<o:p></o:p>
We have 3 exchange 2010 servers.<o:p></o:p>
EX1, EX2, DREX1. All servers are exchange 2010 14.2 build 247.5<o:p></o:p>
EX1 and EX2 have two nics, one LAN and one for BACKUP <o:p></o:p>
The dag is configured to to communicate to all three.<o:p></o:p>
The IP for EX1 is 192.168.100.51 - LAN, switch A; 160.100.3.51 - BACKUP, switch B<o:p></o:p>
The IP for EX2 is 192.168.100.52 - LAN, switch A; 160.100.3.52 - BACKUP, switch B<o:p></o:p>
DREX1 is located in another network. It is in another building connected via vpn. The ip
for DREX1 is 192.170.100.51. There is no BACKUP network for this server<o:p></o:p>
(These are not the actual address, but the concept is similar)<o:p></o:p>
The dag network configuration is as follows.<o:p></o:p>
DAGNetworkDR has a subnet of 192.170.100.0/24; Network Interface of 192.170.100.51<o:p></o:p>
DAGNetwork01 (LAN) has a subnet of 192.168.100.0/24; Network Interfaces of 192.168.100.51
and 192.168.100.52<o:p></o:p>
DAGNetwork02 (BACKUP) has a subnet of 160.100.3.0/24; Network Interfaces of
160.100.3.51 and 160.100.3.52<o:p></o:p>
Last Friday, 3/7/14 something happened.<o:p></o:p>
To lead up to that, I noticed the issue because we have DPM 2010 making 15minute express
full backups of our exchange databases when I reviewed the backup jobs, the
exchange database backups using dpm2010 failed all weekend long starting at
11:00pm that Friday.<o:p></o:p>
The issue that occurred was that the database copies went to a status of Disconnected and
Resynchronizing, and after about 30 seconds, the status would show
Resynchronizing.<o:p></o:p>
All attempts to resolve this with the research methods failed. Deleting the
logs and reseeding failed, suspending, then rebuilding failed.<o:p></o:p>
Creating a new database worked, creating a database copy worked, but seeding the copy
failed. All with the same pattern, a status of Disconnected and
Resynchronizing, and after about 30 seconds, and the status would show
Resynchronizing.<o:p></o:p>
The database was mounted on EX2, and seeding to EX1
DREX1 has no issues.<o:p></o:p>
All the DAG networks were in a good status, all Green and all up. I could ping from
EX1 to EX2 and from EX2 to EX1 on both networks fine.<o:p></o:p>
In the middle of the week, about 3/12/14, we resolved the issue. We rebooted EX1, no
fix, but after rebooting EX2, it all resolved. It did a fail over to DREX1. I think it failed to do the failover to EX1. However, when it came back up, it was happy, it was reseeding slowly. After about an hour and a half, it
was all healthy.<o:p></o:p>
We thought it was all good EXCEPT, on Friday night at 11:00pmish on 3/14/14, the same
issue occurred; a status of Disconnected and Resynchronizing, and after about
30 seconds, the status would show Resynchronizing.<o:p></o:p>
The database was mounted on EX2 and seeding to EX1 again. I did not notice the
issue until I performed my review of the backup jobs again on Monday.<o:p></o:p>
Late Monday morning, my boss and I were looking at more articles, but all the same results,
delete the database copy and reseed. Which we knew would not work.<o:p></o:p>
I mentioned that it was strange because the networks were all up. What made us try the next
scenarios was just "luck" I guess. I made a statement about not remembering
which networks DAG replication took place over. Again, we have a LAN and
a BACKUP network. Bother were listed to use replication, so we decided to
disable replication over the BACKUP network in the EMC. Immediately, the
database copies switch to healthy and started seeding.<o:p></o:p>
Later that evening I enabled replication over the BACKUP network and it failed again with
a status of Disconnected and Resynchronizing, and after about 30 seconds, the
status would show Resynchronizing. I disabled the replication over the
BACKUP network and the database copy went back to healthy<o:p></o:p>
The last round of windows updates were pushed to these boxes the Friday before the
issues began, 2/28/14. I don't believe the updates to be the issue. <o:p></o:p>
Can anyone make any suggestions as to where to look? It worked with the BACKUP
network enabled to so long that is eluding me as to why the issues would start
all of a sudden. I am also confident that the switch configuration for the
BACKUP network has not been changed at all in at least 2-3 months. I am
still open to look at the config. Please help if you can.<o:p></o:p>
<o:p></o:p>
Lastly, this is more of a monitoring thing, if anyone can suggest a good way to monitor
the database copies so that I can be alerted when the status changes. We
use WhatsUpGold 16.2 to monitor the devices. <o:p></o:p>
Thanks for any future assistance.<o:p></o:p>
Ian
Ian

You don't have to enable the Replication on Backup Network.
You should collapse your DAG network.
http://blogs.technet.com/b/timmcmic/archive/2011/09/26/exchange-2010-collapsing-dag-networks.aspx
http://blogs.technet.com/b/samdrey/archive/2012/12/04/exchange-2010-dag-collapse-the-mapi-networks-in-a-dag.aspx
Post the result of Below command:
Get-DatabaseAvailabilityGroupNetwork
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.

Exchange 2010 offline FSW failover occurs ?

Similar Messages

Maybe you are looking for