No, thats expected.
that command shows the OwnerNode and the cluster generic windows name. There are only a few windows clustering components in an Exchange cluster.
you get the name of the DAG with
get-cluster
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
We have two Exchange 2019 Servers in a DAG group that is viewed by the Exchange Admin Console as DAG01. There is no Cluster Name Object (CNO) in AD. Cluster services are running.
On both servers the PowerShell command Get-ClusterGroup returns:
Name OwnerNode State
------
Available Storage Mail03 Offline
Cluster Group Mail03 Online
Mail03 is the name of one of the DAG members. It holds a healthy copy of the 2 mail DBs and is the Primary Active Manager.
Should the Cluster Group be the name of the DAG? If so, what are methods to fix?
Thanks.
No, thats expected.
that command shows the OwnerNode and the cluster generic windows name. There are only a few windows clustering components in an Exchange cluster.
you get the name of the DAG with
get-cluster
Hi @Oren Iwanaga ,
The Cluster Group do not need to be the name of the DAG.
You could refer to the documentation:
https://learn.microsoft.com/zh-cn/Exchange/high-availability/database-availability-groups/database-availability-groups?view=exchserver-2019
If an Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Thanks to both experts for the clarification.
What started this is that I was concerned that the Primary Active Manager is on Mail03 and wanted to migrate the function to Mail01. Should the Move-Clustergroup -Cluster Mail03 -Node Mail01 -Name "ClusterGroup", work in this case as it does not see the DAG name as a cluster but rather sees the node Mail03 as the cluster group?