my personal blog about systemcenter

Storage Replica Windows Server 2016 TP5 Server to Server Replication

Microsoft added Storage Replica in Windows Server 2016 , and this post will cover the smallest deployment that is server to server replication

https://technet.microsoft.com/en-us/library/mt126183.aspx

image

First off is the licensing part , Storage Replica require Windows Datacenter edition

But if this is to protect a small branch office with a bunch of VM the host is most likely licensend with datacente either way

PS C:\Users\administrator.COFFEE> $Servers = ‘SR01′,’SR02’
PS C:\Users\administrator.COFFEE>
PS C:\Users\administrator.COFFEE> $Servers | ForEach { Install-WindowsFeature –ComputerName $_ –Name Storage-Replica,FS-
FileServer –IncludeManagementTools -restart }

Success Restart Needed Exit Code      Feature Result
——- ————– ———      ————–
True    Yes            SuccessRest… {File and iSCSI Services, File Server, Rem…
WARNING: You must restart this server to finish the installation process.
True    Yes            SuccessRest… {File and iSCSI Services, File Server, Rem…
WARNING: You must restart this server to finish the installation process.

Adding the WindowsFeature required to use storage replica Smile

image

Then we need to ensure we have the drives adding a data and a log drive to use with replication

After drives have been created we can then run the Test-SRTopology powershell that checks all the bits to see if everyone is configured correctly

Test-SRTopology -SourceComputerName SR01 -SourceVolumeName E: -SourceLogVolumeName F: -DestinationComputerName SR02 -DestinationVolumeName E: -DestinationLogVolumeName F: -DurationInMinutes 30 -ResultPath c:\temp

image

image

This will stress the networking but lays the foundation of how this will perform in production after being enabled

So let it sit for the default 30 mins Smile

image

20 Test Run , 1 warning

image

and lack of ICMP in firewall rule ended up with a warning for latency test not completed

Time to enable replication

New-SRPartnership -SourceComputerName SR01 -SourceRGName rg01 -SourceVolumeName e: -SourceLogVolumeName f: -DestinationComputerName SR02 -DestinationRGName rg02 -DestinationVolumeName e: -DestinationLogVolumeName f:

image

On my little test setup with 2 cores we can push 6gb/s with resonable cpu usage (not with RDMA adapters)

After initial sync is done we are now in sync

E: is available for use on server SR01 , F: is the log drive where the default 8gb is reserved

And we can reverse replication from SR02 to SR01 instead

Set-SRPartnership -NewSourceComputerName SR02 -SourceRGName rg02 -DestinationComputerName SR01 -DestinationRGName rg0

image

And we are now mounted on SR with with the active E: