• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 630
  • Last Modified:

Error adding second DAG member with Exchange 2010

Hi I am receiving the error below adding a second member of the DAG. The error said that the mailbox server is a member of clusters "Clusxxx". That cluster does not exist it is old information . I initally created it and assigned the virtual IP but I never were able to add the members the firts time due a error with the IP so I decided deleted all. Created a new DAG name , new IP and added the members but now I trying to add the second member I am receiving the message below but that cluster does not exist . Is there any way that I can delete the old information?

THanks,

XX-MBX-01
Failed

Error:
Mailbox server XX-MBX-01 is a member of cluster 'ClusXXX'. The server must be evicted from the cluster prior to adding it to database availability group 'DAGMBX'.
Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.2.328.9&t=exchgf1&e=ms.exch.err.Ex08F45E

Warning:
The operation wasn't successful because an error was encountered. You may find more details in log file "C:\ExchangeSetupLogs\DagTasks\dagtask_2013-01-23_22-17-08.106_add-databaseavailabiltygroupserver.log".


Exchange Management Shell command attempted:
Add-DatabaseAvailabilityGroupServer -MailboxServer XX-MBX-01-Identity 'DAGMBX'

Elapsed Time: 00:00:00
0
CGNET-TE
Asked:
CGNET-TE
  • 2
  • 2
1 Solution
 
Simon Butler (Sembee)ConsultantCommented:
The error means what it says, so you will have to cluster manager to connect to the cluster, evict the node and then remove the old DAG cluster.

Simon.
0
 
CGNET-TEAuthor Commented:
I just notice that old information is on the CLuster manager program on that server. The other member has the correct cluste information at the cluster manager but no this. Can I evit the node and remove it from the cluster manager console?
0
 
Simon Butler (Sembee)ConsultantCommented:
That is what you need to do. The old DAG configuration needs to be cleaned up.
Hopefully you are using a different name for the DAG, otherwise you will have a huge mess on your hands.

Simon.
0
 
CGNET-TEAuthor Commented:
thanks
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now