Wednesday, 18 September 2013 00:00

Restore-DatabaseAvailabilityGroup Command Failed to Evict the Stopped DAG Member, Error 0x46

Written by

Restore-DatabaseAvailabilityGroup is one of the cmdlets used when we do a datacenter switchover of Exchange DAG, especially during a disaster recovery situation. We might end up unsuccessful in executing the Restore-DatabaseAvailabilityGroup and will fail with below error.

WARNING: Server 'EX2010-02' was marked as stopped in database availability group 'DAG-01' but couldn't be removed from
the cluster. Error: A server-side database availability group administrative operation failed. Error: The operation
failed. CreateCluster errors may result from incorrectly configured static addresses. Error: An error occurred while
attempting a cluster operation. Error: Cluster API '"EvictClusterNodeEx('EX2010.fabrikam.com') failed with 0x46.
Error: The remote server has been paused or is in the process of being started"' failed. [Server:
Ex2010-DR.fabrikam.com]
WARNING: The operation wasn't successful because an error was encountered. You may find more details in log file
"C:\ExchangeSetupLogs\DagTasks\dagtask_2013-09-18_07-23-26.439_restore-databaseavailabilitygroup.log".
Server 'EX2010' in database availability group 'DAG-01' is marked to be stopped, but couldn't be removed from the cl
uster. Error: A server-side database availability group administrative operation failed. Error: The operation failed. C
reateCluster errors may result from incorrectly configured static addresses. Error: An error occurred while attempting
a cluster operation. Error: Cluster API '"EvictClusterNodeEx('EX2010-02.fabrikam.com') failed with 0x46. Error: The rem
ote server has been paused or is in the process of being started"' failed. [Server: Ex2010-DR.fabrikam.com]
    + CategoryInfo          : InvalidArgument: (:) [Restore-DatabaseAvailabilityGroup], FailedToEvictNodeException
    + FullyQualifiedErrorId : EF6ADD3F,Microsoft.Exchange.Management.SystemConfigurationTasks.RestoreDatabaseAvailabil
   ityGroup

Before we jump into the solution, let’s understand what the command actually does,

  1. It forms the cluster with started DAG members using /forcequorum
  2. It evicts the stopped DAG member from the cluster nodes list.

You might observe that few stopped DAG members are evicted and failed on one of the stopped servers. What I observed is, it can be due to the delay in information replication or a communication failure.

Solution:

The issue can be workaround in couple of ways as stated below,

  1. Do run the Restore-DatabaseAvailabilityGroup cmdlets after some time and see if the activity succeed. (Note – you may re-run it when the cluster services are up and running if you are running Exchange 2010 SP1 or later. Earlier version administrators, please excuse me !!
  2. If you are unsuccessful when using Exchange Powershell, try evicting the server from Failover Cluster Manager mmc.

As mentioned, you may run the Restore-DatabaseAvailabilityGroup cmdlet couple of time to see if it succeeds without being stopping the cluster service on Exchange 2010 SP1 and above.

-Praveen

theme by reviewshub