Issue viewing cluster status from 1 CCR node in EMC


When you click on server -> Cluster name -> in EMC you receive the error

value cannot be null
Parameter name: nodeName

image

Issue can be caused be a server that is no longer part of the exchange cluster.

You can verify by doing running the following from a elevated EMS prompt
get-clusteredmailboxserverstatus and see if the server with the issue is listed, if not then the solutions is to un-install exchange and re-install as a passive node…. you don’t need to evict from the cluster

Exchange 2007\2010 Database Replication issues – Re-seed


Database replication problems can be caused by many things

  • Hardware Failure
  • Network Outage
  • Administrative Change
  • Log Corruption

If you have replication issues this WILL cause problems in moving the over the active node of your cluster, that is one reason it is very important you do not use cluster administrator to perform the move but rather use either EMC or EMS.

EMS Process = Move-ClusteredMailboxServer -id ClusterName -TargetMachine Node2 (2007)
                      Move-ActiveMailboxDatabaseMailbox Database-ActivateOnServer Node2 (2010)
EMC Process =
Server Configuration -> Mailbox -> Right Click ServerName -> Manage Clustered Mail Box Server -> browse for server -> next -> move (2007)
Organization Configuration -> Mailbox -> Database management -> Rt Click Database -> Move Active mailbox Database -> browse for server -> ok -> move (2010)

If you suspect you have a replication issue or you did but have now resolve the problem and are ready to “Re-Seed” your databases here is the process

EMS Process = Open Exchange management Shell ON the PASSIVE NODE

  1. First verify that the database is not replicating correctly
    get-storagegroupcopystatus or (Get-MailboxDatabaseCopyStatus for 2010)”
    If the state is other than healthy or the numbers for the queues are increasing then you have a replication issue.
    CopyQueue length (Logs queuing up to be sent to the passive node)
    ReplayQueue length (Logs queuing up to be replayed to the passive node database)
     
  2. To re-seed a database (remove all the passive contents and re-copy)
    • On the PASIVE node first suspend the Storage group in question
      Suspend-StorageGroupCopy -id clustername\storagegroup” (2007)
      Suspend-MailboxDatabaseCopy -id mailboxname\servername” (2010)
      then force an update removing the old data on the passive.
      Update-storagegroucopy -id clustername\storagegroup -DeleteExistingFiles” (2007)
      Update-MailboxDatabasecopy -id mailboxname\servername -DeleteExistingFiles” (2010)
      Or if you just want to reseed the entire Server (2007)
      • Get-StorageGroup -Server clustername | suspend-StorageGroupCopy
      • Get-StorageGroup -Server clustername| Update-StorageGroupCopy -DeleteExistingFiles

EMC Process = Open Exchange Management Console on the PASSIVE NODE

  1. Server Configuration -> Mailbox -> Select Cluster– > rt click Storage Group -> Suspend Storage group Copy (2007)
    Organization Configuration -> Mailbox -> Database management -> Rt Click Database copy -> suspend database copy (2010)
  2. Server Configuration -> Mailbox -> Select Cluster– > rt click Storage Group -> update storage group copy -> -> check “Delete Existing”->  Next -> Update (2007)

                                      image

Organization Configuration -> Mailbox -> Database management -> Rt Click Database copy -> update Database copy -> update (2010)

                                                   image

Glossary
EMS = Exchange Management Shell
EMC = Exchange Management Console
Variable
Powershell command