gunschee
asked on
Exchange 2010 - DAG Issue
We have three servers with a DAG setup for the mailbox role. The server with activation preference #1 occasionally acts up, and by the design, another server steps up to the plate and asumes the mounted status. At this point the #1 server is marked as healthy. After a while, #1 goes back to mounted status, and all is well.
But about three weeks ago, this very scenario started again, but this time the #1 server is staying in healthy status, never going back to mounting the DB back again.
I know I could manually activate it back, but what are the reasons that would keep it in that condition?
Thanks.
But about three weeks ago, this very scenario started again, but this time the #1 server is staying in healthy status, never going back to mounting the DB back again.
I know I could manually activate it back, but what are the reasons that would keep it in that condition?
Thanks.
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
This will configure the failback of the cluster group but not the databases
furthermore you should never change any settings in the cluster manager when using DAGs it will render your setup unsupported by microsoft
furthermore you should never change any settings in the cluster manager when using DAGs it will render your setup unsupported by microsoft
Once the database or server is failover over for whatever reason, it doesn't automatically fail it back.
It has to be done manually or another failover has to happen.
It has to be done manually or another failover has to happen.
ASKER
"Once the database or server is failover over for whatever reason, it doesn't automatically fail it back.
It has to be done manually or another failover has to happen"
So what is the purpose of the activation preference then? And if it does go back to preference #1, that means that another server that has the role has also failed?
It has to be done manually or another failover has to happen"
So what is the purpose of the activation preference then? And if it does go back to preference #1, that means that another server that has the role has also failed?
Activation preference comes as a decision maker (one of many) while trying to select a copy to be activated (during a failure).
If you have only two copies, it is not going to do much.
If you have only two copies, it is not going to do much.
ASKER
We have 3 copies of our main DB across 3 servers.
SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
Again failback will never occur automatically in exchange and I strongly disrecommend to do any change using the failover cluster manager. Your setup will no longer be supported.
Once a database fails the active manager takes the activation preference into consideration to decide which on server will the db be activated
Once a database fails the active manager takes the activation preference into consideration to decide which on server will the db be activated
Hi...
If you want to check the Automatic failback for the exchange server, i request to check below setting and it will be useful to you..
Open --> Fail over cluster manager --> Right click on DAG properties --> Manage core cluster group and you can find the Failback and preferred owners all these options.
you have to check these settings had configured properly or not..
Thx