Storage Replica: Unable to Sincronize replication group "cannot update state for replication group in the storage replica driver"

2019-05-27

Question

_{Monday, May 27, 2019 5:51 PM}

Hi all:

How are you? I have a problem to create a storage replica in a PoC (virtual testing environment) I tried to crete a Storage replica (Windows 2019 standard) using the following command (powershell with admin rights):

Set-SRPartnership -SourceComputerName APPLIANCEWK01 -SourceRGName rg01 -SourceVolumeName g: -SourceLogVolumeName r: -DestinationComputerName APPLIANCEWK02 -DestinationRGName rg02 -DestinationVolumeName g: -DestinationLogVolumeName r:

But the following error apperars:

New-SRPartnership : Unable to synchronize replication group rg02, detailed reason: Cannot update state for replication group rg02 in the Storage Replica driver.

The replica was created, but the destination partition is in RAW format, and i can’t obtain the “replica status”

PS C:\Users\administrator.DCFSAAS> Get-SRGroup

do{

$r=(Get-SRGroup -Name "rg01").replicas

[System.Console]::Write("Number of remaining bytes {0}`n", $r.NumOfBytesRemaining)

Start-Sleep 10

}until($r.ReplicationStatus -eq 'ContinuouslyReplicating')

Write-Output "Replica Status: "$r.replicationstatus

AllowVolumeResize : False

AsyncRPO :

ComputerName : APPLIANCEWK01

Description :

Id : 215a66cc-404e-4494-927e-62b297e5c03c

IsAutoFailover :

IsCluster : False

IsEncrypted : False

IsInPartnership : True

IsMounted : False

IsPrimary : True

IsSuspended : False

IsWriteConsistency : False

LastInSyncTime :

LogSizeInBytes : 8589934592

LogVolume : r:\

Name : rg01

NumOfReplicas : 1

Partitions : {14bd8a0b-bf8e-4fc1-9a6d-a2a7bb78bec0}

Replicas : {MSFT_WvrReplica (PartitionId = "14bd8a0b-bf8e-4fc1-9a6d-a2a7bb78bec0")}

ReplicationMode : Synchronous

ReplicationStatus : ContinuouslyReplicating

TemporaryPath :

PSComputerName :

Number of remaining bytes 0

Replica Status:

ContinuouslyReplicating

Have you some documentation to help me with this or any idea about this problem?

I tried recreating the virtual volumes again (using V-cloud) but the problem persist, the size of all partitions (replica and logs) is 15Gb.

All replies (3)

_{Wednesday, May 29, 2019 3:08 PM ✅Answered}

Hi!

Thanks for your answer, I ran Test-topology before New-PartnerShip, and everything was checked with "green check"

Now the replica is working well, I had to delete content from registry Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WVR\ConfigStore\ in SourceServer and DestinationServer

This entry have all ResourceGroup configuration, next, restart both servers, and then create again the New-PartnerShip using this command:

And now it's working.

Thanks for your information and rapid response,

_{Tuesday, May 28, 2019 4:16 AM | 1 vote}

Hi,

Thanks for your question.

We need to first check if configuration of the storage replica by Powershell commands "Test-SRTopology", We can refer to this blog,

https://robertsmit.wordpress.com/2018/10/30/step-by-step-server-to-server-storage-replication-with-windows-server-2019-storage-replica-windowsadmincenter-storagereplica-windowsserver2019-refs-sr-azure

Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.

Here's a thread which discussed a similar issue like yours, hope this helps.

https://social.technet.microsoft.com/Forums/en-US/7f5848e0-5f28-46a8-aec9-ad3b236661f0/creates-a-replication-but-this-error-occurs-storage-replica-windows-server-2019-standard?forum=winserverClustering

The most errors come from the basics. wrong disk layout or san access rights, firewalls. all simple things but often forgotten. We need to check that,

You must create two volumes on each enclosure: one for data and one for logs.
Log and data disks must be initialized as GPT, not MBR.
The two data volumes must be of identical size.
The two log volumes should be of identical size.
All replicated data disks must have the same sector sizes.
All log disks must have the same sector sizes.
The log volumes should use flash-based storage, such as SSD. Microsoft recommends that the log storage be faster than the data storage. Log volumes must never be used for other workloads.
The data disks can use HDD, SSD, or a tiered combination and can use either mirrored or parity spaces or RAID 1 or 10, or RAID 5 or RAID 50.
The log volume must be at least 9GB by default and may be larger or smaller based on log requirements.
The File Server role is only necessary for Test-SRTopology to operate, as it opens the necessary firewall ports for testing.

Other references for you,

/en-us/windows-server/storage/storage-replica/storage-replica-known-issues /en-us/windows-server/storage/storage-replica/server-to-server-storage-replication

Hope above information can help you. If you have any question or concern, please feel free to let me know.

Best regards,

Michael

Please remember to mark the replies as an answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected]

_{Thursday, May 30, 2019 1:42 AM}

Hi,

I'm glad that your issue was resolved successfully!

Thanks for your sharing and support.

Have a nice day!