Comments on: Can Exchange 2013 and Exchange 2016 Servers Be Added to the Same Database Availability Group?

By: Teninet

Teninet — Mon, 19 Sep 2022 10:55:37 +0000

Can Exchange 2016 and Exchange 2019 Servers Be Added to the Same Database Availability Group?

By: Ahmad Amin

Ahmad Amin — Mon, 04 Feb 2019 06:43:21 +0000

Hello,
I have new Exchange server 2016 CU11 as the old ones, but Windows Server 2016.
The old Exchange 2016 CU11 is Windows Server 2012 R2.
When Join the new server to dag, it pop up error “Server ‘DHAMOPMP-EXCH1’ has an incompatible OS Version (10.0) with Server ‘RIYMOPMP-EXCH1’ that’s running OS Version (6.3).”

By: mike

mike — Fri, 24 Mar 2017 15:16:25 +0000

Paul,

I think it also does not support mixed OS also, even though exchange versions and builds are same. In my situation, I have 2 Member DAG with Exchange 2016 CU5, I wanted to move exchange 2016 to Windows 2016, so I installed Exchange 2016 on Windows 2016, then added the Windows Clustering and joined the cluster., everything worked great, until when I tried to add DAG, it gives me error Incompatible OS Version(10.) with other server running OS version (6.3). My other servers are running Windows 2012 R2 latest build and updates.

Is there a workaround or it just does not work? remember Exchange build and version are all same. Only one member of cluster is 2016 OS.

By: Paul Cunningham

Paul Cunningham — Sat, 23 Apr 2016 08:55:01 +0000

In reply to Ozgur. No.

By: Ozgur

Ozgur — Fri, 22 Apr 2016 08:19:57 +0000

Could we make mixed DAG for Exhange 2010 SP3 CU13 and Exchange 2013 ?

By: Paul Cunningham

Paul Cunningham — Mon, 21 Dec 2015 04:52:00 +0000

In reply to Xahaar. Exchange hasn't supported in-place upgrades since 2000->2003, and it is not supported to have mixed versions in a DAG (as the article says). So if you want any kind of Exchange 2016 deployment in your environment it will involve installing new servers.

By: Xahaar

Xahaar — Sun, 20 Dec 2015 03:50:06 +0000

So just making sure I understand – at this time there is no supported way of upgrading a 2013 DAG? My situation being that my production environment has a single 2013 DAG stretched across three sites and one of those sites is scheduled to close in short time. We want to maintain a 3-site topology so we’re standing up servers at another of our sites. My hope was to take this opportunity as a first step towards 2016 but that’s not an option unless I stand up a whole new DAG and move all the mailboxes over?

By: Paul Cunningham

Paul Cunningham — Mon, 02 Nov 2015 04:11:32 +0000

In reply to Eric Wright. I've moved archive mailboxes from 2013 -> 2016 with no problems. These are non-DAG servers though. If you've got a problem getting your moves to work I suggest opening a support ticket with Microsoft. Absolutely do not add both 2013 and 2016 servers to the same DAG.

By: Eric Wright

Eric Wright — Tue, 20 Oct 2015 13:53:44 +0000

In reply to F21. Same here. Only problem is my current archive database is in a different DAG. Trying to think of how to move these archive mailboxes without joining it to the DAG.

By: F21

F21 — Mon, 12 Oct 2015 13:27:19 +0000

Of course, i was able to create DB copy from 2013 to 2016 with a second time…

The seeding operation failed. Error: An error occurred while performing the seed operation. Error: Failed to open a log truncation context to source server ‘E2013.domain.com’. Hresult: 0xc7ff1004. Error: Error returned from an ESE function call (-1305).
[Database: DB1, Server: E2016.elkogroup.com]

After Resume-MailboxDatabaseCopy DB copy from E2013 created successfuly on E2016 side.