Exchange 2013 DAG always failing over to passive node and back daily after the backup ?
Hi All,
My Exchange Server 2013 DAG spreads across 5x mailbox servers VM in three different Data Center locations.
So each mailbox servers hold mixed of 2 Active 3 Passive or 3 Active 2 Passive mailbox DB.
After the nightly successful backup, I can see that the some of the current Mailbox databases are mounted on the server that is activation preference 2.
So the database is kept on mounting from one server to another one (changed daily after the successful backup).
Is this the normal behavior of DAG ?
Would there be any impact if I let it automatically failover to one server nightly or keep running on the passive node forever ?
Note here are the settings applied for all the Mailbox Database:
And this is the Cluster Properties from one of the DAG member which should be replicated for all nodes:
My Exchange Server 2013 DAG spreads across 5x mailbox servers VM in three different Data Center locations.
So each mailbox servers hold mixed of 2 Active 3 Passive or 3 Active 2 Passive mailbox DB.
After the nightly successful backup, I can see that the some of the current Mailbox databases are mounted on the server that is activation preference 2.
So the database is kept on mounting from one server to another one (changed daily after the successful backup).
Is this the normal behavior of DAG ?
Would there be any impact if I let it automatically failover to one server nightly or keep running on the passive node forever ?
Note here are the settings applied for all the Mailbox Database:
AutoDagExcludeFromMonitoring : False
AutoDatabaseMountDial : GoodAvailability
DataMoveReplicationConstraint : SecondCopy
ReplicationType : RemoteAnd this is the Cluster Properties from one of the DAG member which should be replicated for all nodes:
cluster /prop SameSubnetThreshold=20:DWORD
cluster /prop SameSubnetDelay=2000:DWORD
cluster /prop CrossSubnetThreshold=20:DWORD
cluster /prop CrossSubnetDelay=4000:DWORD
cluster /prop RouteHistoryLength=40:DWORDSOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Just take backup for passive copies on every server. Exclude active copies.
ASKER
What about running the PowerShell script RedistributeActiveDatabase
So if all of the mailbox Database is on the Activation Preference 1, then the script is just skipped so no outage to execute this Script.
https://technet.microsoft.com/en-us/library/dd335158(v=exchg.150).aspx
So if all of the mailbox Database is on the Activation Preference 1, then the script is just skipped so no outage to execute this Script.
https://technet.microsoft.com/en-us/library/dd335158(v=exchg.150).aspx
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Amit,
The reason is because the Mailbox server VM was backed up with Veeam (using snapshot technology).
Since the mailbox servers contains mixed DB, there is no way I can provision dedicated server just to serve as Passive DB copy only.
If I just backup the active DB only using Veeam, then it is still using snapshot but on the different VM drive.
The reason is because the Mailbox server VM was backed up with Veeam (using snapshot technology).
Since the mailbox servers contains mixed DB, there is no way I can provision dedicated server just to serve as Passive DB copy only.
If I just backup the active DB only using Veeam, then it is still using snapshot but on the different VM drive.
I understand, that is why I said in long term. If you have option to build another server with only passive copies.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks, all.
According to Veeam, the best way to backup my DAG is using the NBD. In this mode, data is retrieved via the ESX(i) host over LAN using the Network Block Device protocol (NBD).
Therefore, no snapshot is taken.
According to Veeam, the best way to backup my DAG is using the NBD. In this mode, data is retrieved via the ESX(i) host over LAN using the Network Block Device protocol (NBD).
Therefore, no snapshot is taken.
ASKER
There are mixed if both Active and Passive database in each VM, so I cannot create dedicated passive node due to standard Edition limitation of 5 mounted DB.