bikerhong
asked on
Error trying to add Database Copy
Hi All
Exchange 2010 SP3 x2 on Server 2012.
Set up new DAG - when adding first database copy i get the error:
A source-side operation failed. Error An error occurred while performing the seed operation. Error: A timeout occurred while communicating with server 'BERLIN'. Error: "A connection could not be completed within 15 seconds.".
The database shows up after a refresh anyway as Suspended, and doesnt seem to be doing anything. Copy Queue Length is sitting at 27k.
Google suggests this is a networking issue however there ping times are nice and low between all IP's.
Exchange Replication is enabled on all networks at the moment.
What should I do??
Exchange 2010 SP3 x2 on Server 2012.
Set up new DAG - when adding first database copy i get the error:
A source-side operation failed. Error An error occurred while performing the seed operation. Error: A timeout occurred while communicating with server 'BERLIN'. Error: "A connection could not be completed within 15 seconds.".
The database shows up after a refresh anyway as Suspended, and doesnt seem to be doing anything. Copy Queue Length is sitting at 27k.
Google suggests this is a networking issue however there ping times are nice and low between all IP's.
Exchange Replication is enabled on all networks at the moment.
What should I do??
What is the distance between these servers? Are they in separate AD sites?
ASKER
Iv gone through those links and they do not seem to apply here.
Test-ReplicationHealth comes back as all passed.
Yes, these are on physical separate sites and also different AD Sites.
Test-ReplicationHealth comes back as all passed.
Yes, these are on physical separate sites and also different AD Sites.
My first suspicion is IPv6 - try disabling that on the servers and see if they have better luck talking to each other.
Under AD Sites & Services, do you have an EdgeSyncService container for each AD Site?
Under AD Sites & Services, do you have an EdgeSyncService container for each AD Site?
ASKER
Hmm. OK.
I destroyed the DAG, and forced replication.
Disabled IPv6 on both NICs.
Recreated the DAG and this time, the odd thing I noticed was when it did automatically created the DAG networks, it only did the LAN ones.
Cluster Manager shows no errors and everything is online. Windows Event Logs do now reveal anything obvious either.
I added a network in manually, specifying the IP's of the 2 Replication NICS - however it sits as status "Unknown", with no adapters showing as the LAN ones do.
Still, I added a database copy, and it worked, showing as Healthy.
However I'm still convinced something is not right and I dont this to come back to haunt me in the future.
Can someone just sanity check this IP layout.
HQ Server VLAN - 192.168.61.0/24
HQ Management VLAN - 192.168.60.0/24
DR Server VLAN - 192.168.32.0/24
DR Management VLAN - 192.168.100.0/24
For other reasons we chose not to enable a whole subnet for Exchange Replication, instead tying it down directly to /32 IP's.
DAG IP - 192.168.61.45
HQ Replication NIC IP - 192.168.60.140
DR Replication NIC IP - 192.168.100.140
So, on the DAG Properties, the IP is set to DAG IP above.
It automatically created the DAG Networks which show:
HQ Server Network
Subnet - 192.168.61.0/24 UP
Network Interfaces - 192.168.61.40 UP
DR Server Network
Subnet - 192.168.32.0/24 UP
Network Interfaces - 192.168.32.40 UP
As I said, I had to manually create the Replication Network, with the 2 Replication NIC IP's in the Properties:
Subnet - 192.168.60.140 UNKNOWN
- 192.168.100.140 UNKNOWN
Network Interfaces - empty
Where do I go from here?
Like I say - Cluster Manager shows no errors or warnings. Again the odd thing is it only shows 2 Cluster Networks, the LAN's, and no Network for the Replication.
I destroyed the DAG, and forced replication.
Disabled IPv6 on both NICs.
Recreated the DAG and this time, the odd thing I noticed was when it did automatically created the DAG networks, it only did the LAN ones.
Cluster Manager shows no errors and everything is online. Windows Event Logs do now reveal anything obvious either.
I added a network in manually, specifying the IP's of the 2 Replication NICS - however it sits as status "Unknown", with no adapters showing as the LAN ones do.
Still, I added a database copy, and it worked, showing as Healthy.
However I'm still convinced something is not right and I dont this to come back to haunt me in the future.
Can someone just sanity check this IP layout.
HQ Server VLAN - 192.168.61.0/24
HQ Management VLAN - 192.168.60.0/24
DR Server VLAN - 192.168.32.0/24
DR Management VLAN - 192.168.100.0/24
For other reasons we chose not to enable a whole subnet for Exchange Replication, instead tying it down directly to /32 IP's.
DAG IP - 192.168.61.45
HQ Replication NIC IP - 192.168.60.140
DR Replication NIC IP - 192.168.100.140
So, on the DAG Properties, the IP is set to DAG IP above.
It automatically created the DAG Networks which show:
HQ Server Network
Subnet - 192.168.61.0/24 UP
Network Interfaces - 192.168.61.40 UP
DR Server Network
Subnet - 192.168.32.0/24 UP
Network Interfaces - 192.168.32.40 UP
As I said, I had to manually create the Replication Network, with the 2 Replication NIC IP's in the Properties:
Subnet - 192.168.60.140 UNKNOWN
- 192.168.100.140 UNKNOWN
Network Interfaces - empty
Where do I go from here?
Like I say - Cluster Manager shows no errors or warnings. Again the odd thing is it only shows 2 Cluster Networks, the LAN's, and no Network for the Replication.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Subnet error
https://www.experts-exchange.com/questions/27866408/DAG-DB-Copy-will-not-seed.html
Also go through this article as well
http://exchangeserverpro.com/forums/exchange-server-2010/442-delete-failed-suspended-database-copy.html