Exchange 2010, Databases Failed & Suspended frequently.
My Exchange 2010 SP1 (this same problem happened pre SP1) environment consists of a 2 server DAG with dedicated SAN storage. I have 21 databases.
However almost any action causes the DB's to lose sync with each other. If i don't touch anything they fairly rarely corrupt however if I failover one server to the other, the odds are 3-4 of the 21 dbs are going to have to be reseeded. When I have an update that requires me to reboot both servers I reboot #2 (all db's active on 1), it comes up, i fail over to 1 and reboot 2. At the end of this I have 6 DBs that need reseeding.
This is driving me crazy .. the sync between these can't be this fragile. What is wrong with my environment ?
However almost any action causes the DB's to lose sync with each other. If i don't touch anything they fairly rarely corrupt however if I failover one server to the other, the odds are 3-4 of the 21 dbs are going to have to be reseeded. When I have an update that requires me to reboot both servers I reboot #2 (all db's active on 1), it comes up, i fail over to 1 and reboot 2. At the end of this I have 6 DBs that need reseeding.
This is driving me crazy .. the sync between these can't be this fragile. What is wrong with my environment ?
ASKER
Yep servers are in the same rack. AV is not even installed on these.
They are Dell R710's
They are Dell R710's
do you have a second network adapter configured for replication traffic only?
ASKER
I do, I have 2 seperate networks, and the primary network is unchcked for replication only the adapter on the SAN network is configured for replication. Although maybe i should try replicating over my primary IP network instead of the san network ?
how are your drives presented to the servers, iscsi, fiber, etc?
you typically want the primary network dedicated for standard traffic
you typically want the primary network dedicated for standard traffic
ASKER
they are iscsi on an equalogic array. Both servers have 2 LUN's with half the mailboxes on each.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
ok i'll give that a troy, and yes it was the one set for replication
Can you also check under network connections -> advanced -> and check that your nic for mapi connections is on top
Whats the status regarding this ?
cheers
cheers
ASKER
Sorry I wanted to wait a bit and be sure but this has fixed it, note to anyone finding this article, don't do replication over the network you are doing iSCSI on even if that has less traffic then your LAN interface.
ASKER
solved
I take it there is a mailbox on each database?