exTechnology
asked on
DAG replication issues Exchange 2010
Hi Team,
I finished setting up a DAG in exchange 2010 last week with a mapi and replicaiton network. Aside from this, 2 of my active servers also have a SAN network. The 3rd and Passive server in the Dag has the storage locally in the server so no SAN network. I begined creating database copies last week and it worked for some and other just said resyncronizing or failed. I noticed that resyncronizing left a Copy Queue Length number next to the mailbox and it did not decrement at all so it didn't seem to be doing anything. After suspending and reseeding multiple times I decided to copy the database to the other server in DAG which left a re-syncronizing as well, but when this was done I copied that database to the 3rd server and suddenly all the copy queue length numbers begined decrementing leading to a healthy copy. In conclusing, the databases needs to be copied to all 3 servers in the Dag in order for it to work, i know this is not the way it should be but is the only work around I found up to now. I would like to find a solution to this.
Thank you.
I finished setting up a DAG in exchange 2010 last week with a mapi and replicaiton network. Aside from this, 2 of my active servers also have a SAN network. The 3rd and Passive server in the Dag has the storage locally in the server so no SAN network. I begined creating database copies last week and it worked for some and other just said resyncronizing or failed. I noticed that resyncronizing left a Copy Queue Length number next to the mailbox and it did not decrement at all so it didn't seem to be doing anything. After suspending and reseeding multiple times I decided to copy the database to the other server in DAG which left a re-syncronizing as well, but when this was done I copied that database to the 3rd server and suddenly all the copy queue length numbers begined decrementing leading to a healthy copy. In conclusing, the databases needs to be copied to all 3 servers in the Dag in order for it to work, i know this is not the way it should be but is the only work around I found up to now. I would like to find a solution to this.
Thank you.
ASKER
Hi Rancy,
I try doing it without selecting a network as well as selecting the internal network and the replication network. Both give the same result. I don't understand why when I seed it between all 3 servers it works.
I try doing it without selecting a network as well as selecting the internal network and the replication network. Both give the same result. I don't understand why when I seed it between all 3 servers it works.
How do you seed between all Servers at the same time ? and what do you mean by "I don't understand why when I seed it between all 3 servers it works".
- Rancy
- Rancy
ASKER
Server 1 seeds to server 2, the database copy fails, then I seed from server 1 to server 3 and the database copy on server 2 and 3 become healthy.
Thats Strange !! Ideally it should show each Copy status humm
- Rancy
- Rancy
ASKER
No solution yet found
What is the Exchange version of all three nodes ?
- Rancy
- Rancy
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Solution after contacting Microsoft
One Question when you do a reseed do you select any Network to reseed as it should be used ??
- Rancy