What does Windows error code 5030 (ERROR_CLUSTERLOG_RECORD_EXCEEDS_MAXSIZE) mean?

ERROR_CLUSTERLOG_RECORD_EXCEEDS_MAXSIZE

ERROR_CLUSTERLOG_RECORD_EXCEEDS_MAXSIZE means a single cluster-log record was too large to be written. The condition can identify an unexpectedly large diagnostic payload or a component that is producing excessive log data.

Identify the component and record type that generated the oversized entry and preserve the original payload if possible. Fix excessive or malformed diagnostic data at its producer instead of reducing cluster logging broadly.

What to check

• Collect a fresh Cluster.log and identify the component that emits the oversized record.
• Check recent resource DLL, provider, backup, or management changes that might have introduced unusually large status data.
• Review the preceding resource and cluster service events; the record-size error is usually secondary to another operation.

Get-ClusterLog -UseLocalTime -Destination C:\Temp

Microsoft: Get-ClusterLog

Microsoft: Troubleshoot unexpected cluster failover

Microsoft: FailoverClusters PowerShell module