How to fix Error 3210 on Windows Server 2025 / Windows 11

by

Troubleshooting Guide: SQL Server Error 3210 — Mirror Member Inconsistency

Why This Error Happens

Error 3210 occurs when SQL Server 2025 detects that the backup or restore header information on one mirrored media set member does not match the others, typically because the drives were written in different backup sessions, one drive contains stale or corrupted media, or the physical media/device letters were swapped or reordered between backup operations. This commonly happens after manual file substitution on a mirrored backup set, a failed or interrupted mirrored backup, or when using incompatible tape/disk devices with mismatched family GUIDs. Since SQL Server validates the Media Family GUID and sequence number across all mirror members before allowing the operation to proceed, any mismatch triggers a hard failure rather than a silent continuation.

Step-by-Step Resolution Guide

Step 1: Identify the Mismatched Mirror Members

  • Check the full error message for the exact drive paths referenced (the two %ls placeholders).
  • Run RESTORE HEADERONLY FROM DISK = 'drive_path' against each mirror member individually to compare MediaFamilyGUID, FamilySequenceNumber, and MediaSequenceNumber values.
  • Confirm whether any backup files were manually copied, renamed, or replaced after the original backup job completed.

Step 2: Recreate the Mirrored Backup Set from a Clean State

  • Delete or archive the inconsistent backup files from all mirror drives (e.g., D:\SQLBackups\Mirror1\, E:\SQLBackups\Mirror2\).
  • Re-run the full BACKUP DATABASE ... TO DISK = 'drive1', MIRROR TO DISK = 'drive2' command in a single, uninterrupted session so all mirror members share the same Media Family GUID.
  • Ensure no external process (antivirus, backup agent, or scheduled task) is locking or modifying files in these directories mid-backup.

Step 3: Validate Storage and Connectivity Stability

  • Check Windows Server 2025 Event Viewer under Windows Logs > System for disk or NTFS corruption warnings (Event ID 7, 51, or 153) on the volumes hosting the mirror drives.
  • Run chkdsk D: /f and chkdsk E: /f (replace with actual mirror drive letters) during a maintenance window to rule out underlying disk corruption.
  • If using network shares or SAN-attached storage, verify no intermittent disconnects occurred during the backup window via Storage Spaces or SAN logs.

Step 4: Rebuild the Backup Device Configuration

  • Drop and recreate any named backup devices via sp_dropdevice and sp_addumpdevice if the mirror paths were defined as persistent SQL Server backup devices.
  • Confirm both mirror paths point to distinct, healthy physical or logical drives — SQL Server does not support mirroring to the same underlying disk.

Alternative or Verification Steps

  • After re-running the backup, verify consistency by executing RESTORE VERIFYONLY FROM DISK = 'drive1', DISK = 'drive2' — it should complete without raising Error 3210.
  • If the issue persists, bypass mirroring entirely by performing a standard single-device backup (BACKUP DATABASE ... TO DISK = 'single_path') to confirm the database itself isn’t corrupted, then re-introduce mirroring once the root storage issue is resolved.