Shulou(Shulou.com)06/03 Report--

Storage Replication is a new feature in Windows Server 2016, which uses the block storage replication technology that comes with windows server.

First of all, let's briefly explain the deployment requirements:

1. Currently, only Windows Server 2016 Datacenter version of this feature is available.

2. Two functions of Storage-Replica,FS-FileServer need to be installed

3. Kerberos is used for verification during replication, so you need to enter the domain.

4. The replication node needs at least two disks, one data disk and one log disk, and must be in GPT format.

5. Upper limit of data disk 10TB, lower limit of log disk 8GB

6. Ports used in the replication process: 445, 5445, 5895

7. Network requirements: higher than 1Gbps as far as possible, preferably 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. The data is first written to the log disk, and then Commit data disk.

4. there is no requirement for the bottom layer of storage, and it can be any technology.

5. There is an active / standby relationship in the process of replication. The master can read and write, and the standby can not read or write by default.

Let's make a brief introduction to the synchronous replication and asynchronous replication mentioned above.

Synchronous replication

Asynchronous replication

Finally, let's start our functional testing.

Server information

Server01

Server02

Enable replication

On 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

Get-SRgroup

Among them, we should pay attention to the value of ReplicationStatus. The attribute "Relicating" indicates that the copy is being made, and the InitialBlockCopy description is still in the initial replication. If the word "error" appears, the copy cannot be performed.

We can view storage replication through Windows performance counters (block replication, related to disk space, status from InitialBlockCopy to ContinuouslyReplicating)

We can also use windows logs to analyze the status of storage replication

Note: a warning reminder of 1241 in the log can be ignored. Before establishing a replication group relationship, you need to complete a block copy, and the RPO will become available after completion.

It should be noted that after the replication relationship is created, the data disk follows the characteristic that the primary node is readable and the secondary node is not readable and writable.

We need to implement:

By switching the replication direction, you can see that the file has been copied normally.

If the original master node SRV01 suddenly goes down during production, the command will become invalid. The general practice is to undo the replication group relationship:

Get-SRPartnership | Remove-SRPartnership-Force (you can execute this command at any node)

Interested students can start the experiment.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.