badabing1
asked on
Exchange 2010 DAG
hi ,
I have changed the subnet on one of the exchange server from 255.255.0.0 to 255.255.252.0 and not changed the IP address. as soon as I hit apply on the nic card it lost connectivity and then came back up after a minute and failed the Databases to the other exchange server in DAG.
we have two exchange servers in a DAG. I am now seeing "copy queue length" going higher on the failed over exchange server, I don't want to move the databases back to the original server until the queues are back to "0". (but they keep going up slowly)
what has gone wrong, I had to rekey ip setting for the server I changed subnet on in failover cluster manager, and I can now see that is ok, do I also need to change subnet for DAGNetwork although the old subnet /16 is still falls within the new range /22? (see attached)
(changing subnet on exchange server in a Dag what can it break or what needs updating for it to work properly)?
Thanks
dag1.PNG
I have changed the subnet on one of the exchange server from 255.255.0.0 to 255.255.252.0 and not changed the IP address. as soon as I hit apply on the nic card it lost connectivity and then came back up after a minute and failed the Databases to the other exchange server in DAG.
we have two exchange servers in a DAG. I am now seeing "copy queue length" going higher on the failed over exchange server, I don't want to move the databases back to the original server until the queues are back to "0". (but they keep going up slowly)
what has gone wrong, I had to rekey ip setting for the server I changed subnet on in failover cluster manager, and I can now see that is ok, do I also need to change subnet for DAGNetwork although the old subnet /16 is still falls within the new range /22? (see attached)
(changing subnet on exchange server in a Dag what can it break or what needs updating for it to work properly)?
Thanks
dag1.PNG
Did you changed the subnet of 10.11.0.0 or 10.4.0.0?
ASKER
10.11.0.0
thanks
thanks
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
so I do it on network card and not the subnet?
ASKER
I need clarification please is it the DAGNetwork02 I select and remove as suggested by you or the subnet or the network interfaces for 10.11. ?
cheers
cheers
ASKER
ok I've done what you suggested, it created new Dag network, but queues are still not going down fast enough, very slow up/down?
is it safe to activate the database back to its original server even though its showing nearly 4000 logs in copy queue length? the database is healthy but its just not catching up with queues. (see attached)
Thanks
data.PNG
is it safe to activate the database back to its original server even though its showing nearly 4000 logs in copy queue length? the database is healthy but its just not catching up with queues. (see attached)
Thanks
data.PNG
Did you changed network card subnet in both the DAG members?
ASKER
no just 10.11X
I've noticed the queue overnight has come down to 350 but I fear this will go up as users login this morning?
so per my last message is it safe to failback the database even though it has logs in copy queue length?
Thanks
I've noticed the queue overnight has come down to 350 but I fear this will go up as users login this morning?
so per my last message is it safe to failback the database even though it has logs in copy queue length?
Thanks
From your first screenshot I can see only single network interface, check the other DAG members for their IP subnet and change the 10.11 subnet to the same as in 10.11.0.7.
ASKER
we only have one nic in server, see attached after the update? this is how its always been except subnet change yesterday which is now up to date (se attached)
Thanks
dag2.PNG
Thanks
dag2.PNG
How many mailbox servers you've?
If you've only one MBX server their is no point of having DAG.
If you've only one MBX server their is no point of having DAG.
ASKER
2 servers, one local and one remote in a DAG?
Are these 2 servers are members of the DAG?
Share the DAG screenshot.
Get-DatabaseAvailabilityGr oup -id "Your DAG Name"
Share the DAG screenshot.
Get-DatabaseAvailabilityGr
ASKER
here you go, just to be clear from one server I removed the passive copy, so that the other DB can catch up with logs. you didn't answer my question on, is it safe to activate the DB that is healthy back to its original server but has logs in copy queue length..?
Thanks
dag.PNG
Thanks
dag.PNG
Yes try switch over and monitor the copy que length for sometime
ASKER
Great help from Sunil for the DAG network re-creation, however it turned out that the major issue was with our WAN which caused the exchange logs delay, once that was fixed all is working normal. Thanks
Thank you badabing1.
I'm glad that your issue has been resolved :)
I'm glad that your issue has been resolved :)