Solved

EXCH 2010 DAG having 4 memebers

Posted on 2014-03-24
5
151 Views
Last Modified: 2014-03-31
I currently have 2 servers in the DAG A and B, and will be adding 2 more Mailbox servers to the DAG, C and D
My question is right now the dbs that are on the 2 servers in the DAG (A and B) have copies of each of their DBS on each. Now I will be adding 2 more MB servers to the DAG,(C and D) but these 2 will have different dbs than are on the other 2. Is it ok to have copies of dbs on the original 2 MB servers A and B between them and then have the copies of the DBS from the 2 new MB servers C and D between them?
So basically A and B share copies and C and D share copies...
0
Comment
Question by:vmich
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
5 Comments
 
LVL 8

Assisted Solution

by:EEhotline
EEhotline earned 250 total points
ID: 39951211
That is totally OK, though if you have enough space, you can make 2-3 copies of a db instead of 1.
0
 
LVL 1

Author Comment

by:vmich
ID: 39951229
Yes well I figured down the road once there is more space purchased for the san, then we could add more copies...
0
 
LVL 43

Expert Comment

by:Amit
ID: 39951494
It depends what is your business requirement. Practically one copy is enough, if you have regular backup running. Focus on

Redundancy: DB Copy, Server, Power Supply, SAN
Resiliency: Server and Site
Recovery: Backup strategy.
0
 
LVL 41

Accepted Solution

by:
Adam Brown earned 250 total points
ID: 39951505
Honestly, you may want to have a separate DAG for each pair, since the failover scenarios with what you have described could cause some problems. With two database copies on half your nodes in a single DAG, you could end up with some really messy failover situations. For instance, if you lose two servers in the DAG and the FSW setup to have the odd numbered vote, you could potentially cause a cluster shutdown for all databases, even if only one server in each pair shuts down. By way of explanation, let's say you have Copy a and b on servers 1 and 2, and copy c and d on 3 and 4, with FSW on 5. If you have two dags, you can have an additional FSW (6), but with a single DAG, you could lose server 1, 3, and 5 and even if server 2 and 3 are capable of running, the cluster will fail and you would have to perform a cluster recovery. If the same happened with two separate dags, one dag would be unaffected while the other would fail (because it lost over half its nodes).

If you have a DAG, it's always best to make sure there are as many database copies as there are nodes in the DAG.
0
 
LVL 1

Author Closing Comment

by:vmich
ID: 39966444
db
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article aims to explain the working of CircularLogArchiver. This tool was designed to solve the buildup of log file in cases where systems do not support circular logging or where circular logging is not enabled
After hours on line I found a solution which pointed to the inherited Active Directory permissions . You have to give/allow permissions to the "Exchange trusted subsystem" for the user in the Active Directory...
To show how to generate a certificate request in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Servers >> Certificates…
This video discusses moving either the default database or any database to a new volume.
Suggested Courses

617 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question