DAG replication nic
HI
I have one exchange 2013 SP1 server holding both Mailbox and CAS roles,
I want to come up with DAG, so i am going to setup a witness server.
SRV1- Exchange 2013 SP1(MB,CAS)
SRV2 -Witness Server
Do i need replication NICS (As i have only one member i.e one server holding both MB,CAS).
I dont have any issue configuring replication NICS but is it recommended in my scenario?
I am aware it is recommended when you want to add two members to DAG.
If you are only going to have one server then you definitely don't need any replication NICs.
I typically only use dedicated replication NICs when the following are true:
I have dedicated NICs on the physical Server that are connected to a completely separate switch (not just vLAN)
I have a dedicated WAN for replication traffic to other sites. (if DAG stretches multiple sites)
In order to get the benefits of a replication network, these need to be met (atleast in my opinion)
Are you planning on setting up a second DAG member in the future? If not, I would hold off on even setting up and configuring the DAG, since you're not going to get any of the replication benefits from the DAG. You can always configure it again later
if you ever add the second server. Just my 2 cents.
Similar Messages
-
DAG Replication Network Isolation from MAPI
Hi,
Recently We have implemented Exchange 2010 SP2 DR setup.
We have two sites Prod and DR. We are facing some issue in DAG replication Network (Replication Adapter).
We are using 10.10.10.x for Mapi Networks and 192.168.1.x for Replication Network for Prod and 10.11.10.x for MAPI and 192.168.2.x for Replications.
As per Microsoft recommended, We configured replication adapters and added static routes for Replication Network.
We understand, Replicarion adapter is used for DAG Replication (Log Shipping and Seeding) and configured forewall to allow tonly DAG port 64327 for replication Vlans between sites.
Now, When we check the replication network hit in firewall. Its still using MAPI Network (MAPI Nic) to communication with DR sites. Replication Nics is not working properly.
Please let me know, How to isolate the MAPI and Replication Networks. Do we need configure Replication Port in DAG properties.
How to check whether Replication Network is working between the sites.
Regards
M
My Problem is, While seeding is happening between Primary Site to DR Site. Connections are going only via MAPI Networks. It is not using Replication Netowork. I have added the static route in all the prod and DR Mailbox Servers. But I have not
configured Replication Port in DAG properties. And also, I allowed only Port 64327 for Replication Vlan in both Primary and DR. Please let me know if you have any solutions. Regards M
That's expected if you are just using the EMC, or using standard options via EMS
What happens if you use
http://technet.microsoft.com/en-us/library/dd335201(v=exchg.141).aspx
Update-MailboxDatabaseCopy -Network
and
http://technet.microsoft.com/en-us/library/dd335158.aspx
Managing Mailbox Database Copies
To specify the networks you want to use for seeding, use the Network parameter when running the
Update-MailboxDatabaseCopy cmdlet and specify the DAG networks that you want to use. If you don't use the
Network parameter, the system uses the following default behavior for selecting a network to use for the seeding operation:
If the source server and target server are on the same subnet and a replication network has been configured that includes the subnet, the replication network will be used.
If the source server and target server are on different subnets, even if a replication network that contains those subnets has been configured, the client (MAPI) network will be used for seeding.
If the source server and target server are in different datacenters, the client (MAPI) network will be used for seeding.
Cheers,
Rhoderick
Microsoft Premier Field Engineer, Exchange
Blog:
http://blogs.technet.com/rmilne Twitter:
LinkedIn:
Facebook:
Note: My 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. -
Hi All,
Please have a look in to the below mentioned environment.
primary site :SITE 1
server 1
server 2
secondary site :SITE 2
server 3
Note : All the above three servers are in single DAG .All the database are mounted on the server (server 1) which is located in the primary site (I.E SITE 1).
On that 5 databases we are having 3500 users .Based on the user designation we have allocated the mailbox size.
Query : Each and every day we are having the large no copy queue length for all the five databases to the server located in SITE 2.
Please help me out on this and also tell me is there any tool available to exactly get the required bandwidth for the exchange servers located between the active directory sites.
Thanks & Regards S.NithyanandhamI don't know of any tool that can calculate things for you but latency is the biggest thing you have to worry about. The other issues is looking at the network gear between the 2 sites. I have seen many times were switches get maxed out if they are set to
1 GB or even ports getting maxed out and need to bonded for more throughput. Test your latency from the edge of each site then test it within to see if there is a difference.
Regardless of their geographic location relative to other DAG members, each member of the DAG must have round trip network latency no greater than 500 milliseconds between each other member.
As the round trip latency between two Mailbox servers hosting copies of a database increases, the potential for replication not being up to date also increases. Regardless of the latency of the solution, customers should validate that the networks between
all DAG members is capable of satisfying the data protection and availability goals of the deployment. Configurations with higher latency values may require special tuning of DAG, replication, and network parameters, such as increasing the number of databases
or decreasing the number of mailboxes per database, to achieve the desired goals.
Round trip latency requirements may not be the most stringent network bandwidth and latency requirement for a multi-datacenter configuration. You must evaluate the total network load, which
includes client access, Active Directory, transport, continuous replication, and other application traffic, to determine the necessary network requirements for your environment.
http://technet.microsoft.com/en-us/library/dd638104(v=exchg.150).aspx
DJ Grijalva | MCITP: EMA 2007/2010 SPA 2010 | www.persistentcerebro.com -
Exchange DAG Replication Data Rate
i need some information regarding DAG replication issue. In my environment there is two mailbox server. One DC and another in DR site. The connectivity between DC and DR site is VPN. Bandwidth is one MB. But in VPN connection have ping loss. The ping loss rate
1-2%. In my environment twodatabase.
one is single and another is under the dag member. when i move mailbox from single to dag database the move rate is so slow and sometimes database going to dismount. I think its happened as because connectivity issue.
Can you please suggest the details about dag replication. I need to know that: what is dag replication
data rate? also the acceptable rate of ping loss and How much rate connectivity between DAG Heartbeat connection.
Please suggest as soon as possible.
Thanks,
ParvezHi Parvez,
From your description, I would like to clarify the following things:
1. It is not recommended to install Exchange server on DC.
2. The witness server is needed when there's an even number of members in the DAG. Based on your case, you need a file share witness server.
3. The DAG replication rate depends on the replication traffic.
4. By default, heartbeat frequency (subnet delay) is 1000ms for both local and remote subnets. When a node misses 5 heartbeats (subnet threshold) another nod within your DAG cluster will initiate a failover.
What's more, here are some helpful threads for your reference.
Planning for High Availability and Site Resilience
http://technet.microsoft.com/en-us/library/dd638104(v=exchg.150).aspx
Exchange 2010: Collapsing DAG Networks
http://blogs.technet.com/b/timmcmic/archive/2011/09/26/exchange-2010-collapsing-dag-networks.aspx
Hope my clarification is helpful.
Best regards,
Amy
Amy Wang
TechNet Community Support -
Site Link Flooded By DAG Replication Traffic
Hi everyone,
I have a quick question regarding DAG replication. We have a DAG that stretches two sites (one site is the primary site and the other site is strictly DR). The WAN link is 150 Mbps, and we have
encoutered some issues with the network being over-saturated by bursts from the Exchange servers on the replication networks.
The manager of the Engineering team informed me of this today. Apparently this has been going on for a while, but they just discovered the cause recently. He asked about policing/rate-limiting
on traffic destined to the IP at the DR site to 100 Mbps. My understanding is that this would cause packets to drop if they go over 100 Mbps.
Now, I understand how TCP fundamentally works, and that the DAG utilizes TCP (default port 64327), so I would
like to think this wouldn't be an issue, but I wanted to open a dialog here anyway to see if anyone else has encountered anything like this, and if so, if problems arose.
As an aside, I am running Exchange 2010 SP2 (yeah, I know...hopefully going to SP3 next month). There are four total mailbox servers (three at the main site and one at the DR site). And yes,
I have collapsed my DAG networks (MAPI, Replication, Backup).
Any insight is welcome.
Thanks in advance!Thank you, Jared and Jim.
Yes, I figured that at worst my databases at my DR site may simply fall behind a bit, but I don't think it will be by too much, as it doesn't run that high all the time.
The manager of the engineering team is scheduling up a change for Tuesday morning to effectively limit the traffic on Tuesday morning. I'll monitor it for a few days and let you guys know how it is behaving.
Thanks again and have a great weekend! -
question on DAG replication
basic scenario DB will replicate on MAPI port and log will replicate on Replication port.
if replication port get disconnected than then replication will start on MAPI network that is by default senerio.
My Question
1) Some network outage happened but after some time network is restored and found that indexing get failed and both MAPI and REPlication are up then how the replication will work ?
2) And in the same senerio if database get unhealthy or corrupted then how it will work and which port it will use.Hi,
During the seeding process, the use of network depends on situations. If you want to specify the network that you want to use for seeding, you can use the Network parameter when running the
Update-MailboxDatabaseCopy cmdlet. If you don't use the
Network parameter, the system uses the following default behavior for selecting a network to use for the seeding operation:
If the source server and target server are on the same subnet and a replication network has been configured that includes the subnet, the replication network will be used.
If the source server and target server are on different subnets, even if a replication network that contains those subnets has been configured, the client (MAPI) network will be used for seeding.
If the source server and target server are in different datacenters, the client (MAPI) network will be used for seeding.
Best regards,
Belinda Ma
TechNet Community Support -
Changing a Network Interface in DAG Replication Network after going P2V
I have a DAG member suffering severe hardware failure so I have gone P2V with it. It's functioning fine, except that the DAG Network Interfaces have changed - The MAPI Interface was on "Local Area Network" on the physical server, and is now
on Local Area Connection 7 on the VM. However, the DAG settings still point to "Local Area Network" and will not let me change it. Same thing for the replication network.
I have lost redundancy due to this, so I need to get it repaired pretty promptly.
Removing and re-adding the subnet in the DAG network has no effect - it still references the old physical NIC instead of the new virtual NIC, despite the new virtual NIC having the same IP as the old physical NIC.Try to change the network binding on the server
http://technet.microsoft.com/en-us/library/cc732472(WS.10).aspx
Try to delete the hidden network adapters as well.
Open Device Manager, from the File menu, expand the View and select the Show Hidden Devices option. This will enable and show any old un-used devices in the window
http://www.gfi.com/blog/how-to-remove-hidden-network-adapters-from-virtual-machines/
Thanks,
MAS
Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. -
We have a current HA cluster at center1 which is mirrored to another HA cluster in center2. We have several instances already installed and working which are using one NIC for data and replication. We want to prevent mirror failovers by
configuring a NIC on a replication network which has no DNS server. What are the steps to configure the current SQL instances to use this dedicated NIC for mirror replication?Hi dskim111,
You can refer the following step by step article to create the dedicated mirroring NIC,
Step by Step Guide to Setup a Dedicated SQL Database Mirroring(DBM on dedicated Nic card)
http://blogs.msdn.com/b/sqlserverfaq/archive/2010/03/31/step-by-step-guide-to-setup-a-dedicated-sql-database-mirroring-dbm-on-dedicated-nic-card.aspx?Redirected=true
I’m glad to be of help to you!
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place. -
Exchange 2010 DAG Replication - too much data crossing the wire
I’m replicating 3 Exchange databases from our production active Exchange 2010 server across the WAN to another passive Exchange 2010 server at our DR site.
The Exchange server at the DR site does not have any active databases, i.e. no users are hitting that server.
We are running Update Rollup 8 for Exchange Server 2010 SP1 on both these servers.
The two sites are connected via a 10Mb/s MPLS connection and all the databases are in sync and the replication is working fine.
I have setup a network sniffer at the primary site and see a sizable amount of data crossing the wire from the production Exchange server to the DR Exchange server.
When I query the production Exchange server using the Tracking Log explorer and only choose the EventID ‘RECEIVED’ that should show me the amount of data that has been committed to the database.
If I choose a date range that is the same exact range that I have used to capture the raw data with my sniffer the amount of data the sniffer shows crossing the wire is 10 fold compared to what the Tracking Log Explorer shows.
If I actually count up the data in the LOG files it is about 20% more than what is crossing the wire but that seems to be because the DAG is compressing the data.
If in a one hour timeframe there is 500MB of data crossing the wire to the DR Exchange server the tracking log explorer will show only 50MB.
I would like to know why the data crossing the wire far exceeds the amount of data that is truly being sent/received from the primary exchange server.
Perhaps I’m simply not getting a true view of the amount of data being committed to the exchange server using the Tracking Log Explorer.
Maybe there is a better way to report how much data is being committed to the exchange databases.
Any assistance would be appreciated…Two things.
1 - you must update Exchange to SP3 and a recent RU. Willard has already provided the links, which point back to my blog if you want to see the lifecycle map for Exchange 2010. SP1 has been out of support since January 2013. Time to move
on pllease
2 - Looking at the tracking log is not sufficient. I would not expect that to show everything.
I want to know what traffic you see as excessive. What ports are you seeing used here?
My money is on content indexing. CI will use additional traffic over and above log repl traffic. Expect CI traffic to be roughly the same again. You can test this by disabling CI on the database or stopping the services on the DR server.
To disable the CI for the database:
Set-MailboxDatabase DBName -indexEnabled $False
Or stop the Exchange search services on the DR box to leave production unaffected.
Again - you need to update Exchange. You would be better to do that now rather than when something breaks and Microsoft support cannot fully assist you since you are not uptodate. I'll leave discussion of the security issues resolved
in recent Exchange RUs aside.
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. -
Exchange 2010 DAG and NIC Teaming | Team broke and now cluster doesn't see the box
Hello everyone,
Question for the group. We are running an Exchange 2010 DAG cluster with four boxes with active/passive DB's on each of the four boxes. We run HP boxes for Exchange and the NIC's are teamed. Now mind you, I arrived at this company well after this environment
was set up so I have inherited everything here.
What has happened is one of the four boxes had an issue after an otherwise normal reboot. We could no longer ping it. Logged into the ILO and was able to log into the server, only to discover its team NIC was messed up and our only option was to rebuild
the team NIC. So I rebuilt the team and gave it the original IP/subnet/gateway it had. The server reboots and we can ping it.
However, when I look in the EMC at Database Management, all the passive copies that were on that DB are showing Failed. Ok, so I suspend the copy and attempt to reseed. No luck. I get the error "The NetworkManager has not yet been initialized"
and it references my machine which had the bad team NIC. Curious, I go look at my Failover Cluster Manager.
Looking at the fail over cluster manager, I notice a X on the cluster and I am showing my server which had the bad team NIC being listed as down. I attempted to start the cluster service for the machine, but it did not work.
Is there something I a missing? What are my exact steps to take to get my cluster configuration working correctly again and see my box? Do I need to remove the box from the DAG, evict it from the cluster, and rejoin it again? If so, can I do this without
affecting the other three machines so users don't notice any outage?
Thanks for any help you can give!Hi Kyle,
I am Chetan Savade from Symantec Technical Support Team & sorry to know the problem you faced because of SEP.
Symantec recommends that the Exchange server's OS always be protected by the latest available release of SEP. The Exchange server's message flow and Information Store must be protected by a dedicated mail security product, such as Symantec
Mail Security for Microsoft Exchange.
For cluster environment I would recommend to follow this article:
Installing the Symantec Endpoint Protection client to a Windows cluster server
http://www.symantec.com/docs/TECH91154
Installation best practices for Endpoint Protection on Windows servers
http://www.symantec.com/docs/TECH91154
Best Regards,
Chetan -
Planning for Exchange 2013 DR. I have some queries on configuring DAG in my DR site.
Current setup:-
Primary site:- (2MB,2 CAS)
DR Planning:-
One Mailbox,One CAS Server
In primary mailbox server, two nic card is there. One is for MAPI and other one is for DAG replication. In DAG replication NIC card there is no gateway. Primary site DAG working without
any issues. In DR mailbox server two nic is there(One for Mapi and other for DAG replication). Problem iam facing is Primary site DAG NIC card not able to communicate with DR MBX server, since there is no gateway in replication NIC card. If I add the gateway
in replication NIC, then it is communicating with DR MBX. But iam getting mutiple gateways warning message.
MY Query is:-
1) Is there any problem having multiple gateways in MBX server.
2) If there is no problem with multiple gateway, how to restrict the users traffic hitting DAG replication NIC card.
3) Is there any configuration required in failover cluster manger menu for DR.
4) Is there any way to check DAG(replication) traffic hitting which NIC card..
Thanks for your support...Hi vino,
Thank you for your question.
Replication networks typically do not have default gateways, and if the MAPI network has a default gateway, then no other networks should have default gateways. Routing of network traffic on a Replication network can be configured by using persistent, static
routes to the corresponding network on other DAG members using gateway addresses that have the ability to route between the Replication networks. All other traffic not matching this route will be handled by the default gateway that's configured on the adapter
for the MAPI network.
So we should check configuration which is DAG cross site, we could refer to the following link:
https://social.technet.microsoft.com/Forums/exchange/en-US/bc260c97-a5aa-484d-bc8a-e7660ef4554f/setup-exchange-2010-dag-across-sites?forum=exchange2010
Issue 1: NO
Issue 2: In a general, user network was separated with replication network.
Issue 3:NO
Issue 4:it is pre-defined by yourselves, we could defined which NIC is charged for replication.
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim
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]
Jim Xu
TechNet Community Support -
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
IanYou 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 2013 SP1 on Windows Server 2008 R2 Enterprise - BSOD after DAG creation
Hi,
We are running Exchange 2007 SP3 RU13 on Windows 2003 R2 with SP2 in a 2003 native AD environment and recently decided to upgrade to Exchange 2013. We installed a pair of new DELL R420 servers running Windows 2008 R2 Enterprise then threw Exchange 2013 SP1
onto them. This all went fine and the servers are running stable.
We connected the second NIC of each server to the other via a separate switch, the second NIC has Client for MS Networks and File/Printer Sharing disabled plus a totally separate subnet with no DNS or GW address assigned. DAG setup was run and completed
OK. I created the DAG network in Exchange and enabled replication, I also left replication enabled across the production LAN. Finally, I went into the advanced network settings and made sure the replication network was below the production network in the binding
order.
After an hour or two the BSOD's started.. both servers would crash within a few minutes of each other and reboot with a Kernel Panic. I have attached the contents of the dump file below. This seems to happen every few hours and it always seems to be the
server hosting the passive DB copies crashes first, followed by the server hosting the active copies. Note that if we disable the replication NIC on both servers they do not crash.
I got the impression from somewhere that perhaps the servers had mixed up the binding order and were trying to use the replication network as primary, losing access to AD and rebooting (which I have read is the behaviour for Exchange now). It appears the
Exchange Health service has killed WININIT which causes the crash.
Thanks!!!
The crash dump text is below:
CRITICAL_OBJECT_TERMINATION (f4)
A process or thread crucial to system operation has unexpectedly exited or been
terminated.
Several processes and threads are necessary for the operation of the
system; when they are terminated (for any reason), the system can no
longer function.
Arguments:
Arg1: 0000000000000003, Process
Arg2: fffffa80192ebb30, Terminating object
Arg3: fffffa80192ebe10, Process image file name
Arg4: fffff80001dc37b0, Explanatory message (ascii)
Debugging Details:
PROCESS_OBJECT: fffffa80192ebb30
DEBUG_FLR_IMAGE_TIMESTAMP: 0
MODULE_NAME: wininit
FAULTING_MODULE: 0000000000000000
PROCESS_NAME: MSExchangeHMWo
BUGCHECK_STR: 0xF4_MSExchangeHMWo
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80001e4cab2 to fffff80001abebc0
STACK_TEXT:
fffff880`0d7f39c8 fffff800`01e4cab2 : 00000000`000000f4 00000000`00000003 fffffa80`192ebb30 fffffa80`192ebe10 : nt!KeBugCheckEx
fffff880`0d7f39d0 fffff800`01df7abb : ffffffff`ffffffff fffffa80`1bcf3060 fffffa80`192ebb30 fffffa80`383ea060 : nt!PspCatchCriticalBreak+0x92
fffff880`0d7f3a10 fffff800`01d77674 : ffffffff`ffffffff 00000000`00000001 fffffa80`192ebb30 00000000`00000008 : nt! ?? ::NNGAKEGL::`string'+0x17486
fffff880`0d7f3a60 fffff800`01abde53 : fffffa80`192ebb30 fffff880`ffffffff fffffa80`1bcf3060 00000000`00000000 : nt!NtTerminateProcess+0xf4
fffff880`0d7f3ae0 00000000`7772157a : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : nt!KiSystemServiceCopyEnd+0x13
00000000`34eed638 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : 0x7772157a
STACK_COMMAND: kb
FOLLOWUP_NAME: MachineOwner
IMAGE_NAME: wininit.exe
FAILURE_BUCKET_ID: X64_0xF4_MSExchangeHMWo_IMAGE_wininit.exe
BUCKET_ID: X64_0xF4_MSExchangeHMWo_IMAGE_wininit.exe
Followup: MachineOwnerHi Darrkon,
I suggest checking the status of the HealthMailbox on each of servers.
Also try to re-create the mailbox. You can safely delete and recreate health mailboxes.
Be aware that any local Managed Availability probes that are using the these mailboxes will fail until the Microsoft Exchange Health Manager is restarted. Once that service is restarted, it will recreate any mailboxes that it needs.
More details in the following similar thread, just for your reference:
BSOD after creating DAG
http://social.technet.microsoft.com/Forums/exchange/en-US/44d1cd98-cba1-4ed0-b0e7-8aa76ee3eabc/bsod-after-creating-dag
Thanks
Mavis
Mavis Huang
TechNet Community Support -
Hyper-V cluster validation report "Found duplicate physical address" on nic team interfaces.
I recently built a Windows 2012 Hyper-V cluster with 5 nodes. The validation report shows “duplicate physical address” error (error text pasted below).
The hardware: HP BladeSystem – servers are BL460c blades, in a c7000 enclosure, connected to HP Virtual Connect switches.
Each server has 2 physcal nics, teamed in Windows. In the NIC Teaming console, I created the following Team Interfaces and assigned each a VLAN ID:
“Team1” (the default team)
“Team1 - VLAN 204 – Management”
“Team1 - VLAN 212 - 2012HB”
“Team1 - VLAN 211 -Exchange DAG Replication”
I also created 2 HV Virtual Switches. Neither one allows management interface to share. They are assigned to “Team1” and “Team1 - VLAN 211 -Exchange DAG Replication” respectively.
Therefore, in Network Connection, I see the 2 physical Ethernet nics, and 4 “virtual” nics. Only 2 of them have IP addresses assigned: Management and HB. These are the two that the validation wizard complains
about.
The MAC address is not configurable in the NIC Teaming console, so I don’t see a way to resolve this error, except to use separate physical nics. I don’t want to do that because a) I would lose the benefits of
the bandwidth aggregation that Virtual Connect provides, and b) When creating an Interface on a Team in Windows, it looks like it ALWAYS gives it the same MAC address, so that should be a supported configuration.
Everything works just fine, and there are no other errors or IP conflicts or anything else. But I really want to fix it because I don’t know what unknown problems this may be causing.
From the Cluster Validation report:
Found duplicate physical address 10-60-4B-A9-4A-30 on node Cluster201.OurDomain.local adapter
Team1 - VLAN 212 - 2012HB and node Cluster201.OurDomain.local adapter
Team1 - VLAN 204 - Management.
Found duplicate physical address F0-92-1C-13-3C-2C on node Cluster202.OurDomain.local adapter
Team1 - VLAN 212 - 2012HB and node Cluster202.OurDomain.local adapter
Team1 - VLAN 204 - Management.
Found duplicate physical address 68-B5-99-C1-7E-9C on node Cluster210.OurDomain.local adapter
Team1 - VLAN 212 - 2012HB and node Cluster210.OurDomain.local adapter
Team1 - VLAN 204 - Management.
Found duplicate physical address 3C-4A-92-DE-1E-74 on node Cluster211.OurDomain.local adapter VC-Team - VLAN 212 - 2012HB and node Cluster211.OurDomain.local adapter
VC-Team - VLAN 204 - Management.
Found duplicate physical address 68-B5-99-C0-3D-50 on node Cluster212.OurDomain.local adapter
Team1 - VLAN 212 - 2012HB and node Cluster212.OurDomain.local adapter
Team1 - VLAN 204 - Management.
Thanks!
DanHi Dan,
"It turns out that both hosts had the same default MAC address ranges for their virtual switches. Since the host vNICs were attached to the virtual switch on each host they received the first couple of MAC addresses from the switches.
For details please refer to following link:
http://www.jefflafr.com/blog/4/19/2013/conflicting-mac-addresses-when-building-a-hyper-v-cluster-with-converged-networking
Hope this helps
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place. -
hi
Unable to add member to DAG
A server side database availability group administrative operation operation failed with a transient error.
Please try the operation again. Error: An error occured
while attempting a cluster operation. Error: Cluster API failed "CreateCluster() failed with 0x5b4.
Operation returned because timeout period expired
I am using Exchange 2013 SP1 on win2012 R2
Server1(MB CAS)
MAPI- 192.168.1.10 Replication NIC : 10.0.0.1
Server2(witness Server)
MAPI -192.168.1.11 Replication NIC : 10.0.0.2
i just assigned the ips to replication NIC thats it.Do i need to team the adapters on exchange and witness server?
I hav created DAG with below settings
New DAG name :MYDAG(disabled CNO in dsa.msc)
Witness server : ws.mydomain.com
witness directory : c:\dag01
ip : is this right ip(i have assigned mapi ip of witness server i.e 192.168.1.11)
please guide meadd-databaseavailabiltygroupserver started on machine MAIL1.
[2015-01-08T01:27:26] add-dagserver started
[2015-01-08T01:27:26] commandline: $scriptCmd = {& $wrappedCmd @PSBoundParameters }
[2015-01-08T01:27:26] Option 'Identity' = 'EX2K13DAG01'.
[2015-01-08T01:27:26] Option 'MailboxServer' = 'MAIL1'.
[2015-01-08T01:27:26] Option 'DatabaseAvailabilityGroupIpAddresses' = ''.
[2015-01-08T01:27:26] Option 'WhatIf' = ''.
[2015-01-08T01:27:26] Process: w3wp w3wp.exe:9120.
[2015-01-08T01:27:26] User context = 'NT AUTHORITY\SYSTEM'.
[2015-01-08T01:27:26] Member of group 'Everyone'.
[2015-01-08T01:27:26] Member of group 'BUILTIN\Pre-Windows 2000 Compatible Access'.
[2015-01-08T01:27:26] Member of group 'BUILTIN\Users'.
[2015-01-08T01:27:26] Member of group 'NT AUTHORITY\SERVICE'.
[2015-01-08T01:27:26] Member of group 'CONSOLE LOGON'.
[2015-01-08T01:27:26] Member of group 'NT AUTHORITY\Authenticated Users'.
[2015-01-08T01:27:26] Member of group 'NT AUTHORITY\This Organization'.
[2015-01-08T01:27:26] Member of group 'BUILTIN\IIS_IUSRS'.
[2015-01-08T01:27:26] Member of group 'LOCAL'.
[2015-01-08T01:27:26] Member of group 'IIS APPPOOL\MSExchangeECPAppPool'.
[2015-01-08T01:27:26] Member of group 'BUILTIN\Administrators'.
[2015-01-08T01:27:26] Updated Progress 'Validating the parameters.' 2%.
[2015-01-08T01:27:26] Working
[2015-01-08T01:27:26] Mailbox server: value passed in = MAIL1, mailboxServer.Name = MAIL1, mailboxServer.Fqdn = mail1.mydomain.com
[2015-01-08T01:27:26] LogClussvcState: clussvc is Stopped on mail1.mydomain.com. Exception (if any) = none
[2015-01-08T01:27:26] The IP addresses for the DAG are (blank means DHCP): 192.168.1.50
[2015-01-08T01:27:26] Looking up IP addresses for EX2K13DAG01.
[2015-01-08T01:27:26] EX2K13DAG01 = [ 192.168.1.50 ].
[2015-01-08T01:27:26] Looking up IP addresses for mail1.
[2015-01-08T01:27:26] mail1 = [ fe80::5de4:72e2:a34a:59a8%12, 192.168.1.25, 169.254.43.31 ].
[2015-01-08T01:27:26] Looking up IP addresses for mail1.mydomain.com.
[2015-01-08T01:27:26] mail1.mydomain.com = [ fe80::5de4:72e2:a34a:59a8%12, 192.168.1.25, 169.254.43.31 ].
[2015-01-08T01:27:26] DAG EX2K13DAG01 has 0 servers:
[2015-01-08T01:27:26] According to GetNodeClusterState(), the server MAIL1 is NotConfigured.
[2015-01-08T01:27:26] Updated Progress 'Checking if Mailbox server 'MAIL1' is in a database availability group.' 4%.
[2015-01-08T01:27:26] Working
[2015-01-08T01:27:26] GetRemoteCluster() for the mailbox server failed with exception = An error occurred while attempting a cluster operation.
Error: Cluster API failed: "OpenCluster(mail1.mydomain.com) failed with 0x6d9. Error: There are no more endpoints available from the endpoint mapper". This is OK.
[2015-01-08T01:27:26] Ignoring previous error, as it is acceptable if the cluster does not exist yet.
[2015-01-08T01:27:26] DumpClusterTopology: Opening remote cluster EX2K13DAG01.
[2015-01-08T01:27:26] DumpClusterTopology: Failed opening with Microsoft.Exchange.Cluster.Shared.AmGetFqdnFailedNotFoundException:
The fully qualified domain name for node 'EX2K13DAG01' could not be found.
at Microsoft.Exchange.Cluster.Shared.AmServerNameCache.<>c__DisplayClass1.<ResolveFqdn>b__0(Object param0, EventArgs param1)
at Microsoft.Exchange.Cluster.Shared.SharedHelper.RunADOperationEx(EventHandler ev)
at Microsoft.Exchange.Cluster.Shared.AmServerNameCache.ResolveFqdn(String shortNodeName, Boolean throwException)
at Microsoft.Exchange.Cluster.Shared.AmServerNameCache.GetFqdn(String shortNodeName, Boolean throwException)
at Microsoft.Exchange.Cluster.Shared.AmServerName..ctor(String serverName, Boolean throwOnFqdnError)
at Microsoft.Exchange.Management.SystemConfigurationTasks.DumpClusterTopology..ctor(String nameCluster, ITaskOutputHelper output)
[2015-01-08T01:27:26] Dumping the cluster by connecting to: EX2K13DAG01.
[2015-01-08T01:27:26] DumpClusterTopology: Not dumping, since the cluster could not be contacted.
[2015-01-08T01:27:26] The new server (MAIL1) is not a member of a cluster, nor are the other servers (if there are any other servers).
[2015-01-08T01:27:26] The computer account EX2K13DAG01 does not exist.
[2015-01-08T01:27:26] InternalValidate() done.
[2015-01-08T01:27:26] Updated Progress 'Adding server 'MAIL1' to database availability group 'EX2K13DAG01'.' 6%.
[2015-01-08T01:27:26] Working
[2015-01-08T01:27:26] Connecting to server 'mail1.mydomain.com' via WMI...
[2015-01-08T01:27:26] Fetching the network adapters and including the ones without default gateways.
[2015-01-08T01:27:26] mail1.mydomain.com has an address: 192.168.1.25/24 default gateway(s)=192.168.1.2 [valid]
[2015-01-08T01:27:26] IP address derived that's suitable for clustering DHCP/IPv6: 192.168.1.0/24.
[2015-01-08T01:27:26] mail1.mydomain.com has an address: fe80::5de4:72e2:a34a:59a8/64 default gateway(s)=192.168.1.2 [invalid]
[2015-01-08T01:27:26] The address 192.168.1.50 falls under the network (192.168.1.0/24).
[2015-01-08T01:27:26] Updated Progress 'Forming cluster named 'EX2K13DAG01' on server 'MAIL1'.' 8%.
[2015-01-08T01:27:26] Working
[2015-01-08T01:27:26] Forming cluster named 'EX2K13DAG01' on server 'MAIL1'. The cluster address is/are [192.168.1.50], and the cluster network prefix
length is/are [24].
[2015-01-08T01:30:29] The following log entry comes from a different process that's running on machine 'MAIL1'. BEGIN
[2015-01-08T01:30:29] [2015-01-08T01:27:26] Updated Progress 'Forming cluster named 'EX2K13DAG01' on server 'mail1'.' 2%.
[2015-01-08T01:27:26] Working
[2015-01-08T01:27:26] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseInitialize, ePhaseType = ClusterSetupPhaseStart, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 5, szObjectName = EX2K13DAG01, dwStatus = 0x0 )
[2015-01-08T01:27:26] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseInitialize, ePhaseType = ClusterSetupPhaseEnd, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 5, szObjectName = , dwStatus = 0x0 )
[2015-01-08T01:27:26] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseValidateNodeState, ePhaseType = ClusterSetupPhaseStart, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 10, szObjectName = mail1.mydomain.com, dwStatus =
0x0 )
[2015-01-08T01:27:26] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseValidateNodeState, ePhaseType = ClusterSetupPhaseEnd, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 10, szObjectName = , dwStatus = 0x0 )
[2015-01-08T01:27:26] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseValidateNodeState, ePhaseType = 4, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 10, szObjectName = Find a suitable domain controller for node mail1.mydomain.com.,
dwStatus = 0x0 )
[2015-01-08T01:27:26] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseQueryClusterNameAccount, ePhaseType = ClusterSetupPhaseStart, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 15, szObjectName = EX2K13DAG01, dwStatus =
0x0 )
[2015-01-08T01:27:26] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseQueryClusterNameAccount, ePhaseType = 4, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 15, szObjectName = Bind to domain controller \\mail1.mydomain.com.,
dwStatus = 0x0 )
[2015-01-08T01:27:26] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseQueryClusterNameAccount, ePhaseType = 4, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 15, szObjectName = Check whether the computer object EX2K13DAG01
for node mail1.mydomain.com exists in the domain. Domain controller \\mail1.mydomain.com., dwStatus = 0x0 )
[2015-01-08T01:27:26] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseQueryClusterNameAccount, ePhaseType = ClusterSetupPhaseEnd, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 15, szObjectName = , dwStatus = 0x0 )
[2015-01-08T01:27:26] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseQueryClusterNameAccount, ePhaseType = 4, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 15, szObjectName = Computer object for node mail1.mydomain.com exists
in the domain., dwStatus = 0x0 )
[2015-01-08T01:27:26] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseValidateClusterNameAccount, ePhaseType = ClusterSetupPhaseStart, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 21, szObjectName = EX2K13DAG01, dwStatus
= 0x0 )
[2015-01-08T01:27:26] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseValidateClusterNameAccount, ePhaseType = 4, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 21, szObjectName = Checking for account information for the computer
object in the 'UserAccountControl' flag for CN=EX2K13DAG01,OU=ExchangeDAGGroup,DC=mydomain,DC=com., dwStatus = 0x0 )
[2015-01-08T01:27:26] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseValidateClusterNameAccount, ePhaseType = 4, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 21, szObjectName = Enable computer object EX2K13DAG01 on domain
controller \\mail1.mydomain.com., dwStatus = 0x0 )
[2015-01-08T01:27:26] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseValidateClusterNameAccount, ePhaseType = ClusterSetupPhaseEnd, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 21, szObjectName = , dwStatus = 0x0 )
[2015-01-08T01:27:26] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseConfigureClusterAccount, ePhaseType = ClusterSetupPhaseStart, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 26, szObjectName = EX2K13DAG01 in organizational
unit OU=ExchangeDAGGroup,DC=mydomain,DC=com dwStatus = 0x0 )
[2015-01-08T01:27:26] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseConfigureClusterAccount, ePhaseType = 4, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 26, szObjectName = Get GUID of computer object with FQDN: CN=EX2K13DAG01,OU=ExchangeDAGGroup,DC=mydomain,DC=com,
dwStatus = 0x0 )
[2015-01-08T01:27:26] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseConfigureClusterAccount, ePhaseType = ClusterSetupPhaseEnd, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 26, szObjectName = , dwStatus = 0x0 )
[2015-01-08T01:27:26] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseValidateNetft, ePhaseType = ClusterSetupPhaseStart, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 31, szObjectName = mail1.mydomain.com, dwStatus = 0x0
[2015-01-08T01:27:26] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseValidateNetft, ePhaseType = ClusterSetupPhaseEnd, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 31, szObjectName = , dwStatus = 0x0 )
[2015-01-08T01:27:26] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseValidateClusDisk, ePhaseType = ClusterSetupPhaseStart, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 36, szObjectName = mail1.mydomain.com, dwStatus =
0x0 )
[2015-01-08T01:27:26] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseValidateClusDisk, ePhaseType = ClusterSetupPhaseEnd, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 36, szObjectName = , dwStatus = 0x0 )
[2015-01-08T01:27:26] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseConfigureClusSvc, ePhaseType = ClusterSetupPhaseStart, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 42, szObjectName = mail1.mydomain.com, dwStatus =
0x0 )
[2015-01-08T01:27:26] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseConfigureClusSvc, ePhaseType = ClusterSetupPhaseEnd, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 42, szObjectName = , dwStatus = 0x0 )
[2015-01-08T01:27:26] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseStartingClusSvc, ePhaseType = ClusterSetupPhaseStart, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 47, szObjectName = mail1.mydomain.com, dwStatus = 0x0
[2015-01-08T01:27:26] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseStartingClusSvc, ePhaseType = ClusterSetupPhaseEnd, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 47, szObjectName = , dwStatus = 0x0 )
[2015-01-08T01:27:26] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseFormingCluster, ePhaseType = ClusterSetupPhaseStart, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 52, szObjectName = EX2K13DAG01, dwStatus = 0x0 )
[2015-01-08T01:30:26] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseFormingCluster, ePhaseType = ClusterSetupPhaseEnd, ePhaseSeverity = ClusterSetupPhaseFatal, dwPercentComplete = 52, szObjectName = EX2K13DAG01, dwStatus = 0x5b4 )
[2015-01-08T01:30:26] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseFailureCleanup, ePhaseType = ClusterSetupPhaseStart, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 52, szObjectName = mail1.mydomain.com, dwStatus = 0x0
[2015-01-08T01:30:29] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseFailureCleanup, ePhaseType = ClusterSetupPhaseContinue, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 52, szObjectName = EX2K13DAG01, dwStatus = 0x0 )
[2015-01-08T01:30:29] ClusterSetupProgressCallback( eSetupPhase = ClusterSetupPhaseFailureCleanup, ePhaseType = ClusterSetupPhaseEnd, ePhaseSeverity = ClusterSetupPhaseInformational, dwPercentComplete = 52, szObjectName = , dwStatus = 0x0 )
[2015-01-08T01:30:29] The operation wasn't successful because an error was encountered. You may find more details in log file
"C:\ExchangeSetupLogs\DagTasks\dagtask_2015-01-08_01-27-26.627_add-databaseavailabiltygroupserver.log".
[2015-01-08T01:30:29] WriteError! Exception = Microsoft.Exchange.Cluster.Replay.DagTaskServerTransientException:
A server-side database availability group administrative operation failed with a transient error. Please try the operation again. Error: An error occurred while attempting a cluster operation. Error: Cluster API failed: "CreateCluster() failed with
0x5b4. Error: This operation returned because the timeout period expired" ---> Microsoft.Exchange.Cluster.Shared.ClusterApiException: An error occurred while attempting a cluster operation. Error: Cluster API failed: "CreateCluster() failed with
0x5b4. Error: This operation returned because the timeout period expired" ---> System.ComponentModel.Win32Exception: This operation returned because the timeout period expired
--- End of inner exception stack trace ---
at Microsoft.Exchange.Cluster.ClusApi.AmCluster.CreateExchangeCluster(String clusterName, AmServerName firstNodeName,
String[] ipAddress, UInt32[] ipPrefixLength, IClusterSetupProgress setupProgress, IntPtr context, Exception& failureException, Boolean throwExceptionOnFailure)
at Microsoft.Exchange.Cluster.ActiveManagerServer.ClusterFactory.CreateExchangeCluster(String clusterName, AmServerName firstNodeName, String[] ipAddress, UInt32[] ipPrefixLength, IClusterSetupProgress setupProgress, IntPtr context, Exception&
failureException, Boolean throwExceptionOnFailure)
at Microsoft.Exchange.Cluster.Replay.DagHelper.CreateDagCluster(String clusterName, AmServerName firstNodeName, String[] ipAddresses, UInt32[]
netmasks, String& verboseLog)
--- End of inner exception stack trace (Microsoft.Exchange.Cluster.Shared.ClusterApiException) ---
at Microsoft.Exchange.Cluster.Replay.DagHelper.ThrowDagTaskOperationWrapper(Exception exception)
at Microsoft.Exchange.Cluster.Replay.DagHelper.CreateDagCluster(String clusterName, AmServerName firstNodeName, String[] ipAddresses, UInt32[] netmasks, String& verboseLog)
at Microsoft.Exchange.Cluster.ReplayService.ReplayRpcServer.<>c__DisplayClass40.<RpcsCreateCluster>b__3f()
at Microsoft.Exchange.Data.Storage.Cluster.HaRpcExceptionWrapperBase`2.RunRpcServerOperation(String databaseName, RpcServerOperation rpcOperation)
--- End of stack trace on server (mail1.mydomain.com) ---
at Microsoft.Exchange.Data.Storage.Cluster.HaRpcExceptionWrapperBase`2.ClientRethrowIfFailed(String databaseName, String serverName, RpcErrorExceptionInfo errorInfo)
at Microsoft.Exchange.Cluster.Replay.ReplayRpcClientWrapper.RunCreateCluster(AmServerName rpcServerName, String clusterName, AmServerName firstNode, String[] ipaddrs, UInt32[] netmasks, String& verboseLog)
at Microsoft.Exchange.Management.SystemConfigurationTasks.AddDatabaseAvailabilityGroupServer.FormCluster()
[2015-01-08T01:30:29] Updated Progress 'Done!' 100%.
[2015-01-08T01:30:29] COMPLETED
add-databaseavailabiltygroupserver explicitly called CloseTempLogFile().
Maybe you are looking for
-
Export Sales Order Cycle for Country-IN
Hai, Can anyone give me complete sales cycle of "Export sales order" - What extra config settings need to be maintained. It would be more helpful, if anyone gives detailed info including transactions ( eg:LC BOND, Bill of Lading, Creation/Utilization
-
Hi All, Can i debug the standard sap script? And how can i get the test print with data?
-
Specific segment in idoc ORDERS05
Hi, In purchase order, we have idocs in type ORDERS05. Someone has added specific segment under standard segment E1EDPA1. In scheduling agreement release we have also idocs in type ORDERS05 but not the specific segment added. Do you know in which use
-
Listing client name on Cisco WLC 5508
Hi all, Anybody know how to do a listing wifi clients connected to all the WAPs on the wireless controller. I tried show client summary and then show client detail [mac-address] but that requires lots of work for all clients, anyone know how to do th
-
My airport express is 10 years old and I get the message that this version of airport utility (6.2) doesn't support my base station? What to do?