Windows Server Storage Replica

Windows Server Storage Replica

The storage replica is a new feature in Windows Server 2016, which is a block-level storage replica mechanism independent of the traditional storage device kind (Nas/das/san). The storage replica supports synchronous replication and asynchronous replication of two different ways of replicating data, and storage replicas replicate and transmit data using the SMB communication protocol. It can use any fixed disk storage, as well as any storage structure. The storage replica does not require clustering technology, and it can be managed using Failover Cluster Manager, PowerShell, and WMI.

The differences between synchronous replication and asynchronous replication are the following:

Synchronous replication mechanism: when the "synchronous (synchronous)" Replication mechanism is used, the system will guarantee that the data will be written to at least two different locations before each data IO job is completed before replying to the upper-level application to complete the IO job. Therefore, when the source node host failure event, can be fault-tolerant redundancy switch action, and then let the application use the destination node host data quickly restore operation. Therefore, it is suitable for operational services that require high availability and disaster recovery, which is the "0 data loss (Loss)".

The following are the actions of data replication between two hosts when a synchronous replication mechanism is used:

1. The application issues write data requirements.

2. The source-side node host writes data to the local-side storage resource "log", and transmits it to the destination node host through the SMB 3 protocol.

3. The destination node host, writes the received data to the local storage resource "log".

4. After the destination node host write is completed, reply to the source-side host has completed IO action.

5. The source-side node host reply application confirms that the IO action has been completed.

650) this.width=650; "title=" clip_image002[5] "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px, "border=" 0 "alt=" clip_ IMAGE002[5] "src=" http://s3.51cto.com/wyfs02/M02/89/78/wKiom1gUS8LjG6YpAABYiU0Ez6M959.jpg "height="/>

Asynchronous replication mechanism: When the asynchronous (asynchronous) replication mechanism is used, the system responds to the upper-level application immediately after the IO job is completed on the local side, before the data is replicated to another location. Therefore, such a data replication mechanism still has the risk of data loss, can only achieve "near Zero data Loss" operating environment, so it is not suitable for use in high-availability operating environment (for example, failover clustering).

The following are the actions of data replication between two hosts when using asynchronous replication mechanisms:

1. The application issues write data requirements.

2. The source-side node host writes data to the local-side storage resource "log".

3. The source-side node host reply application confirms that the IO action has been completed.

4. Transfer data to the destination node host through the SMB 3 protocol.

5. The destination node host, writes the received data to the local storage resource "log".

6. After the destination node host write is completed, reply to the source-side host has completed IO action.

650) this.width=650; "title=" clip_image004[5] "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px, "border=" 0 "alt=" clip_ IMAGE004[5] "src=" http://s3.51cto.com/wyfs02/M00/89/79/wKiom1gUS8PQu9VwAABcw0oVy5E614.jpg "height=" 311 "/>

In this experiment, I will use two Windows Server Datacenter to test, two servers are in the same domain (Vcloud.lab). We assume that two servers are on different floors to be able to cope with failure damage. In Windows Server 2016, there is no GUI interface that can be configured, so we are using PowerShell to configure this lab environment uniformly.

650) this.width=650; "title=" clip_image006 "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px, "border=" 0 "alt=" clip_ image006 "src=" http://s3.51cto.com/wyfs02/M00/89/76/wKioL1gUS8SgYLTeAABINpPN8xU888.jpg "height=" 336 "/>

1 , create a replication partnership

In this experiment, I added two disks for two servers, namely data disk, size 50GB, log disk, size 15GB. As shown in the following:

SRNode1:

650) this.width=650; "title=" clip_image007 "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px, "border=" 0 "alt=" clip_ image007 "src=" http://s3.51cto.com/wyfs02/M01/89/79/wKiom1gUS8WBOT4hAAAhkVZwgVc240.png "height=" 297 "/>

650) this.width=650; "title=" clip_image008[5] "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px, "border=" 0 "alt=" clip_ IMAGE008[5] "src=" http://s3.51cto.com/wyfs02/M02/89/79/wKiom1gUS8azJBCuAAAYHLZ3rhg921.png "height=" 136 "/>

SRNode2:

650) this.width=650; "title=" clip_image009 "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px, "border=" 0 "alt=" clip_ image009 "src=" Http://s3.51cto.com/wyfs02/M02/89/79/wKiom1gUS8fB0mf-AAAhTlkjkGQ919.png "height=" 288 "/>

650) this.width=650; "title=" clip_image010[5] "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px, "border=" 0 "alt=" clip_ IMAGE010[5] "src=" Http://s3.51cto.com/wyfs02/M00/89/79/wKiom1gUS8fyMG0lAAAXKnBtYOc606.png "height=" 137 "/>

To install the storage replica role for two servers, use the following PS command:

Invoke-command-computername Srnode1,srnode2-command {install-windowsfeature-name Storage-Replica,FS-FileServer- Restart}

650) this.width=650; "title=" clip_image012[5] "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px, "border=" 0 "alt=" clip_ IMAGE012[5] "src=" http://s3.51cto.com/wyfs02/M00/89/76/wKioL1gUS8jzA8-WAAA6mB6auhQ570.jpg "height="/>

Use the test-srtopology command to test the storage copy and run the following PS command:

Test-srtopology-sourcecomputername srnode1-sourcevolumename D:-sourcelogvolumename e:-DestinationComputerName Srnode2-destinationvolumename d:-destinationlogvolumename e:-durationinminutes 5-resultpath c:\Log\

650) this.width=650; "title=" clip_image014 "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px, "border=" 0 "alt=" clip_ image014 "src=" http://s3.51cto.com/wyfs02/M01/89/76/wKioL1gUS8nB4UREAABJi8nQ5O0759.jpg "height=" 131 "/>

After the test is complete as shown:

650) this.width=650; "title=" clip_image016 "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px, "border=" 0 "alt=" clip_ image016 "src=" http://s3.51cto.com/wyfs02/M02/89/79/wKiom1gUS8uwek8NAABcj2dpmpY392.jpg "height=" 145 "/>

A test report is produced after the test is completed, as shown in:

650) this.width=650; "title=" clip_image018 "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px, "border=" 0 "alt=" clip_ image018 "src=" http://s3.51cto.com/wyfs02/M01/89/76/wKioL1gUS8yRTrDnAAEjuVGAYd0115.jpg "height=" 1125 "/>

Use the new-srpartnership command to create a storage copy, as shown in the following command:

New-srpartnership-sourcecomputername srnode1-sourcergname sr-srnode1-sourcevolumename D:-SourceLogVolumeName E:- Destinationcomputername srnode2-destinationrgname sr-srnode2-destinationvolumename D:-DestinationLogVolumeName E:- Logsizeinbytes 5gb-verbose

650) this.width=650; "title=" clip_image020 "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px, "border=" 0 "alt=" clip_ image020 "src=" http://s3.51cto.com/wyfs02/M00/89/79/wKiom1gUS8yw7-xsAAA_af9XMNY430.jpg "height=" 117 "/>

Create the completion as shown in:

650) this.width=650; "title=" clip_image022 "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px, "border=" 0 "alt=" clip_ image022 "src=" http://s3.51cto.com/wyfs02/M01/89/79/wKiom1gUS82zpe7jAABhUXnZFEA029.jpg "height=" 189 "/>

Switch to node after creation is complete SRNODE2 will find its data (D) disk is not available:

650) this.width=650; "title=" clip_image023 "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px, "border=" 0 "alt=" clip_ image023 "src=" Http://s3.51cto.com/wyfs02/M02/89/79/wKiom1gUS86RA_7OAAAkTaMGl60341.png "height=" 166 "/>

2 , monitoring replication performance:

Open Performance Monitor and click on the Green +:

650) this.width=650; "title=" clip_image025 "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px, "border=" 0 "alt=" clip_ image025 "src=" http://s3.51cto.com/wyfs02/M02/89/76/wKioL1gUS8_ToJENAABG3zbNAn8808.jpg "height=" 244 "/>

Click Storage Replica Statistics, then click Add, click OK:

650) this.width=650; "title=" clip_image027 "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px, "border=" 0 "alt=" clip_ image027 "src=" http://s3.51cto.com/wyfs02/M02/89/76/wKioL1gUS9DBa8xSAACsV5_Heic608.jpg "height=" 387 "/>

Run the following PS command to test Copy-item C:\Windows\System32\Drivers D:-recurse

650) this.width=650; "title=" clip_image029 "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px, "border=" 0 "alt=" clip_ image029 "src=" http://s3.51cto.com/wyfs02/M00/89/76/wKioL1gUS9GQomIHAAAgbsUAZvM395.jpg "height=" Notoginseng "/>

Observe the Performance Monitor when the data begins to replicate, as shown in:

650) this.width=650; "title=" clip_image031 "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px, "border=" 0 "alt=" clip_ image031 "src=" http://s3.51cto.com/wyfs02/M00/89/76/wKioL1gUS9KAd86OAACqMQbWfNo264.jpg "height=" 389 "/>

3 , configuring Reverse Replication

In this step I will configure SRNode2 as the source server, SRNode1 configured as the target server.

To open Windows PowerShell as an administrator, type the following PS command:

Set-srpartnership-newsourcecomputername srnode2-sourcergname Sr-srnode2-destinationcomputername SRNode1- Destinationrgname sr-srnode1-confirm: $False

650) this.width=650; "title=" clip_image033 "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px, "border=" 0 "alt=" clip_ image033 "src=" http://s3.51cto.com/wyfs02/M01/89/79/wKiom1gUS9PQ7Th2AAAnHjsnmxM118.jpg "height="/>

The command execution completes as shown in:

650) this.width=650; "title=" clip_image035 "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px, "border=" 0 "alt=" clip_ image035 "src=" Http://s3.51cto.com/wyfs02/M02/89/79/wKiom1gUS9SxdQu5AAA479JJa8E547.jpg "height=" 111 "/>

Log in to SRNode1 to see the D drive marked as unavailable:

650) this.width=650; "title=" clip_image037 "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px, "border=" 0 "alt=" clip_ image037 "src=" http://s3.51cto.com/wyfs02/M00/89/79/wKiom1gUS9STi4q5AAAbb0VIARw558.jpg "height="/>

4 , deleting replicas

In this step I will remove the Windows volume copy.

To open Windows PowerShell as an administrator:

Before I start the deletion, I will query the storage replica group and the stored partnership with the following two PS commands: Get-srgroup, get-srpartnership. As shown in:

650) this.width=650; "title=" clip_image039 "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px, "border=" 0 "alt=" clip_ image039 "src=" http://s3.51cto.com/wyfs02/M01/89/79/wKiom1gUS9Xz2CGYAACiC07dAG0220.jpg "height=" 297 "/>

650) this.width=650; "title=" clip_image040[5] "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px, "border=" 0 "alt=" clip_ IMAGE040[5] "src=" Http://s3.51cto.com/wyfs02/M02/89/79/wKiom1gUS9bCNY3BAAAdS_VP_8I757.png "height=" 185 "/>

Use the following command to delete replication:

Get-srpartnership | Remove-srpartnership-confirm: $False

650) this.width=650; "title=" clip_image042 "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px, "border=" 0 "alt=" clip_ image042 "src=" http://s3.51cto.com/wyfs02/M02/89/76/wKioL1gUS9fhLQpsAAAeIBuq61o261.jpg "height="/>

Remove-srgroup-name Sr-srnode2:

650) this.width=650; "title=" clip_image043 "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px, "border=" 0 "alt=" clip_ image043 "src=" http://s3.51cto.com/wyfs02/M02/89/76/wKioL1gUS9iSkUOhAAAJUdjl_GM503.png "height="/>

Successful deletion, as shown in:

650) this.width=650; "title=" clip_image045 "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px, "border=" 0 "alt=" clip_ image045 "src=" http://s3.51cto.com/wyfs02/M01/89/79/wKiom1gUS9nzDZFoAABQeOKIeY0079.jpg "height="/>

Switch to SRNode1 delete srgroup:

Remove-srgroup-name Sr-srnode1

650) this.width=650; "title=" clip_image046[5] "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px, "border=" 0 "alt=" clip_ IMAGE046[5] "src=" http://s3.51cto.com/wyfs02/M01/89/76/wKioL1gUS9nS6EsIAAAJXHO64Z8205.png "height="/>

viewing SRNode1 and SRNode2 disk drives are normal:

650) this.width=650; "title=" clip_image048 "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px, "border=" 0 "alt=" clip_ image048 "src=" Http://s3.51cto.com/wyfs02/M02/89/79/wKiom1gUS9riEiDQAAAd1hl6esY165.jpg "height=" 111 "/>650" this.width=650, "title=" clip_image050 "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px, "border=" 0 "alt=" clip_ image050 "src=" http://s3.51cto.com/wyfs02/M00/89/79/wKiom1gUS9uiogpeAAAgz7nY5ns593.jpg "height=" "/>"

Verify that the D disk for each server has a previously copied drivers folder:

650) this.width=650; "title=" clip_image051 "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px, "border=" 0 "alt=" clip_ image051 "src=" Http://s3.51cto.com/wyfs02/M00/89/76/wKioL1gUS9ywt0f2AAAVYGbZNa0883.png "height=" 94 "/>

650) this.width=650; "title=" clip_image052 "style=" border-top:0px;border-right:0px;background-image:none; border-bottom:0px;padding-top:0px;padding-left:0px;border-left:0px;padding-right:0px, "border=" 0 "alt=" clip_ image052 "src=" http://s3.51cto.com/wyfs02/M01/89/76/wKioL1gUS92T8SGmAAAWs-RYRHM460.png "height="/>

This article is from the "Wu Yuzhang Microsoft blog" blog, make sure to keep this source http://wuyvzhang.blog.51cto.com/9992636/1867094

Windows Server Storage Replica