Storage Replication is a new feature in Windows Server 2016. It uses the block storage replication technology that comes with Windows Server.
First, let's briefly explain the deployment requirements:
1. This function currently only exists in Windows Server 2016 Datacenter version
2. Two functions, Storage-Replica and FS-FileServer, need to be installed.
3. Kerberos is used for verification during the replication process, so it needs to enter the domain
. 4. The replication node requires at least two disks. One data disk, one log disk, and must be in GPT format
5. The upper limit of the data disk is 10TB, and the lower limit of the log disk is 8GB
. 6. Ports used in the replication process: 445, 5445
, 5895 Good 10Gbps (synchronous replication)
Let's talk about the characteristics of this technology:
1. Use SMB3.1.1 technology
2. Support synchronous replication and asynchronous replication (default)
3. Log disk and data disk are required for replication. Data is first written to log disk, and then Commit data disk
4. There is no requirement for the underlying storage layer,
It can be any technology
For the synchronous replication and asynchronous replication mentioned above, we will make a brief introduction
synchronous replication
Asynchronous replication
Finally, let's start our functional testing
server information
server01
server02
To enable replication
of any machine, execute the following command
Invoke-Command -Computername SRV01,SRV02 -ScriptBlock{Install-WindowsFeature -Name Storage-Replica,FS-FileServer -IncludeManagementTools -restart}
New-SRPartnership -SourceComputerName SRV01 -SourceRGName RG01 -SourceVolumeName D: -SourceLogVolumeName E: -DestinationComputerName SRV02 -DestinationRGName RG02 -DestinationVolumeName D: -DestinationLogVolumeName E: -LogSizeInBytes 12GB -Verbose
View replication status through powershell
Get-SRPartnership
In Get-SRgroup 
, we should pay attention to the value of ReplicationStatus. The attribute is Relicating, indicating that the copying is in progress, and InitialBlockCopy indicates that the initial copying is still in progress.
We can see storage replication through Windows performance counters (block replication, related to disk space, status changed from InitialBlockCopy to ContinuouslyReplicating)
We can also analyze the status of storage replication through the windows log 
Note: The warning reminder of 1241 in the log can be ignored. Before establishing a replication group relationship, a block replication must be completed. After completion, the RPO will become available.
One thing to note is that after the replication relationship is created , the data disk follows the technology 
that the primary node can read and write, but the secondary node cannot , the original master node SRV01 suddenly goes down, the command will be invalid, the general practice is to remove the replication group relationship: Get-SRPartnership | Remove-SRPartnership -Force (this command can be executed on any node)
Interested students can experiment