Windows Server 2022 — Storage Replica partnership stuck in initial sync state — Fix & Prevention

📖 ~1 min read

Table of contents

1. Symptom & Impact
2. Environment & Reproduction
3. Root Cause Analysis
4. Quick Triage
5. Step-by-Step Diagnosis
6. Solution — Primary Fix
7. Solution — Alternative Approaches
8. Verification & Acceptance Criteria
9. Rollback Plan
10. Prevention & Hardening
11. Related Errors & Cross-Refs
12. References & Further Reading

Symptom & Impact

Storage Replica partnership stuck in initial sync state on Windows Server 2022 disrupts operations and prevents the affected service from meeting its SLA until remediated.

Environment & Reproduction

The issue reproduces on Windows Server 2022 hosts where the storage subsystem is in use, typically following configuration drift or recent updates.

Test-SRTopology -SourceComputerName SRV01 -SourceVolumeName 'D:' -SourceLogVolumeName 'L:' -DestinationComputerName SRV02 -DestinationVolumeName 'D:' -DestinationLogVolumeName 'L:' -DurationInMinutes 30 -ResultPath C:Temp
Get-WinEvent -LogName 'Microsoft-Windows-StorageReplica/Admin' -MaxEvents 30

Root Cause Analysis

The defect stems from misaligned storage replica settings, missing prerequisites, or a corrupted state that blocks normal operation.

Quick Triage

Confirm the service is running and capture current configuration state before applying any change.

Get-SRGroup -ComputerName SRV01 | Select Name,ReplicationStatus
Get-Counter -ComputerName SRV01 -Counter 'Storage Replica Statistics(*)*'

Step-by-Step Diagnosis

Walk the storage stack from configuration to runtime, collecting logs and counters that point at the failing component.

Get-SRPartnership | Format-List
Get-WinEvent -LogName 'Microsoft-Windows-StorageReplica/Operational' | Where LevelDisplayName -eq 'Error'

Solution — Primary Fix

Apply the corrected configuration and restart dependent services so the storage replica component re-initialises cleanly.

Remove-SRPartnership -SourceComputerName SRV01 -SourceRGName 'rg01' -DestinationComputerName SRV02 -DestinationRGName 'rg02' -Confirm:$false
Remove-SRGroup -ComputerName SRV01 -Name 'rg01'
New-SRPartnership -SourceComputerName SRV01 -SourceRGName 'rg01' -SourceVolumeName 'D:' -SourceLogVolumeName 'L:' -DestinationComputerName SRV02 -DestinationRGName 'rg02' -DestinationVolumeName 'D:' -DestinationLogVolumeName 'L:' -ReplicationMode Synchronous

Solution — Alternative Approaches

Where the primary fix is blocked by policy or downtime windows, use the alternative configuration path or staged rollout below.

Set-SRPartnership -SourceComputerName SRV01 -SourceRGName 'rg01' -DestinationComputerName SRV02 -DestinationRGName 'rg02' -ReplicationMode Asynchronous
Set-SRGroup -ComputerName SRV01 -Name 'rg01' -LogSizeInBytes 8GB

Verification & Acceptance Criteria

Confirm the service reports healthy state and end-to-end functionality succeeds against a representative workload.

Get-SRGroup | Select Name,ReplicationStatus,NumOfReplicatedBytes
Get-SRPartnership | Select SourceComputerName,DestinationComputerName,ReplicationMode

Rollback Plan

If the fix introduces regressions, revert configuration to the pre-change baseline and restart the service to restore prior behaviour.

Remove-SRPartnership -SourceComputerName SRV01 -SourceRGName 'rg01' -DestinationComputerName SRV02 -DestinationRGName 'rg02' -Confirm:$false
Remove-SRGroup -ComputerName SRV01 -Name 'rg01'

Prevention & Hardening

Bake the validated storage replica configuration into baseline GPOs or DSC and add a monitoring check for early detection.

Set-SRGroup -ComputerName SRV01 -Name 'rg01' -AsyncRPO 30
Get-Counter -Counter 'Storage Replica Statistics(*)Bytes per Sec' -Continuous

Related Errors & Cross-Refs

Related: other storage failures, dependent service errors, and downstream client-side symptoms.

Related tutorial: View the step-by-step tutorial for Windows Server 2022.

View all Windows Server 2022 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Microsoft Learn documentation for Windows Server 2022 and the relevant component, plus internal runbooks.