PowerMax: Enable Maintenance Mode for NDM Cutover, Commit and Cancel in Cluster Failover

Summary: Non‑Disruptive Migrations (NDM) remove disk paths from the server during Cutover, Commit or Cancel commands. In Microsoft Cluster Failover (MCF) host or node environments, the periodic disk health check can target a path being removed, causing MCF to trigger a cluster failover. ...

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Symptoms

Observed behavior during NDM operations

The following issues may occur when performing Non‑Disruptive Migration (NDM) commands in a Microsoft Cluster Failover environment:

  • Microsoft Cluster fails over during the NDM Cutover command (NDM Passthrough mode).
  • Microsoft Cluster fails over during the NDM Cancel command.
  • Microsoft Cluster fails over during the NDM Commit command (NDM Metro IA mode).

Cause

Root Cause of Cluster Failover During NDM Operations

The Microsoft Failover Cluster periodically executes a disk health check. During Non‑Disruptive Migration (NDM) Cutover, Cancel, or Commit commands, the storage system removes disk paths from the host. If the health‑check process attempts I/O to a path that is in the middle of being removed, the check fails, triggering an automatic cluster failover.

  • Cluster health‑check runs every few seconds and expects all configured paths to be available.
  • NDM Cutover, Cancel, and Commit commands delete disk paths on the server as part of the migration.
  • Concurrent I/O from the health‑check to a path being removed results in a failed health‑check.
  • The failed health‑check is interpreted by Microsoft Cluster Failover as a disk fault, causing the active node to fail over.

Resolution

Prevent Cluster Failover During NDM Operations

Step‑by‑Step Procedure

1. Identify all cluster resources (volumes) that reside on the node that will run the NDM Cutover, Commit, or Cancel command.

2. Place each identified resource into maintenance mode (suspend the resource) before starting the NDM operation.

# Example PowerShell command to suspend a cluster resource
Suspend-ClusterResource -Name "Cluster Disk 1"

3. Verify that the resources are in the Suspended state.

Get-ClusterResource -Name "Cluster Disk 1" | Format-Table Name, State

4. Execute the required NDM command (Cutover, Commit, or Cancel) on the PowerMax/VMAX array.

5. Once the NDM command completes successfully, return each resource to normal operation.

# Example PowerShell command to resume a cluster resource
Resume-ClusterResource -Name "Cluster Disk 1"

6. Confirm that the resources have returned to the Online state.

Get-ClusterResource -Name "Cluster Disk 1" | Format-Table Name, State

Verification

  • Check the cluster resource status in the Failover Cluster Manager or via PowerShell; all resources should show Online and not Failed .
  • Review the Windows Event Log for any Cluster Failover events during the NDM operation; none should be present.
  • Confirm that the NDM migration reports success in the Dell EMC management console.
Critical: Failure to suspend **all** cluster volumes on the migrating node can cause the Microsoft Cluster Failover service to detect a missing path and trigger an unintended failover.
Caution: Removing a resource from maintenance mode before the NDM command finishes may interrupt the migration and corrupt data.
Note: For detailed PowerShell syntax, refer to the Microsoft documentation: Suspend‑ClusterResource .
Warning: If you are unfamiliar with cluster resource management, contact Dell Support before proceeding.

Additional Information

Microsoft Cluster uses SCSI-3 Persistent Group Reservation (PGR) to maintain desk segregation and security on SCSI storage arrays. Microsoft Cluster Failover sends PGR reserve queries every few seconds to each cluster volume as a disk health check.  The storage array must respond to the health check IO on the path selected.

Affected Products

Microsoft Windows Server 2016, Microsoft Windows Server 2019, Microsoft Windows 2008 Server R2, Microsoft Windows 2008 Server Service Pack 2, Microsoft Windows 2012 Server, Microsoft Windows 2012 Server R2, PowerMax, PowerMax 2000, PowerMax 8000 , VMAX 100K ...

Products

VMAX 200K, VMAX 250F, VMAX 400K, VMAX 450F, VMAX 850F, VMAX 950F, VMAX All Flash, VMAX3 Series
Article Properties
Article Number: 000179895
Article Type: Solution
Last Modified: 16 Feb 2026
Version:  4
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.