This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(92.8, 64%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ELZ%3C/text%3E%3C/svg%3E)
Hi
I have an Existing Exchange 2016 DAG with user mailboxes.
I would like to deploy on premise Archive mailboxes on different mailbox servers.
Since the backup process is configured per DAG and we do have backup issues from time to time
I was considering creating the new mailbox servers in a second DAG in the same AD site so the backups could run in parallel and not impact the other backup process.
I have a few questions hopefully someone can provide answers:
Thanks
Liran Zamir
P.S. There is typically little reason to put the archive mailboxes on separate databases or servers. I would just include them in the existing DAG if possible. Or increase the allowed primary mailbox size
Hi Andy
thank you for your answer.
As stated the main reason for splitting DAGs is the backup issue.
Since we try to keep our databases at a maximum size of 2TB for DAG replication and recovery times, and we do have many users and large mailboxes
the idea of mixing primary mailboxes and archive mailboxes on the same databases is a recipe for disaster.
We use a load balancer to point clients to the Exchange address space URL.
I do have two mailbox servers in the current DAG dedicated for Archive mailboxes (currently for pilot).
Those mailbox servers are not configured in the load balancer as target for client connections, however users with archive mailboxes gain access to the archive
via the mailbox server who do act as client facing servers so the access to the archive mailbox is proxied.
You stated that if I create a new DAG - clients will need to contact it directly, but how does this new address space should be configured for the clients to be load balanced ?
It should work as you have it configured now. When I said the clients will need to contact the new DAG members directly, I was really referring to ensuring you weren't attempting to block any connections.
Clients know nothing about the DAG - all they care about is the CAS role. If you have the existing CAS on the current DAG in the load balancer, that will work just fine.
You can build a new DAG and put the archive databases there.
What you will want to do is set the Autodiscover and client virtual directories on the new DAG mailbox servers to the existing Load Balanced Exchange name space ( just like you probably did for the pilot servers I assume). This will ensure the client connections all go through the load balancer
That will work and you can have two diff DAGs.... :)
Indeed.
Thank you again.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(12.8, 39%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMS%3C/text%3E%3C/svg%3E)
Hi
I have an Existing Exchange 2016 DAG
in the process of upgrading to Exchange 2019, for having a safety environment I tried to run a new DAG on new exchange server 2019 (In the same organization) but it was not successful.
first I thought it's a misconfiguration after many troubleshooting progress and run a LAB scenario I found that is because of Exchange 2016 DAG.
Now my question is, is it possible to add a new DAG for Exchange 2019 in the same organization that already had a Exchange 2016 DAG
Please open a new question for this. Thank you
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(92.8, 41%, 18%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMI%3C/text%3E%3C/svg%3E)
I think that s not problem if you have at least CU12 for 2016 Servers .
You can check this by the following url.