Simply test Windows S2D (3) in a vsphere environment

W2016 includes a number of PowerShell tools to help users diagnose, view, and collect storage-related logs. In the next experiment, we look at the commands that are related to troubleshooting.

1. Use the Get-storagesubsystem command to view the name of the S2D subsystem in the test environment, such as the following is the author of the test s2d, because the name is longer, so the next step in the command in the wildcard "*" instead of the "cluster" in addition to the part:

650) this.width=650; "title=" Get-storagesubsystem.png "src=" https://s3.51cto.com/wyfs02/M00/98/CB/ Wkiol1laquedjcwpaadcskvdcbk945.png "alt=" Wkiol1laquedjcwpaadcskvdcbk945.png "/>

2. The Enable-storagediagnosticlog command can be configured to collect different levels of log information (including critical, Error, informational, verbose, and warning), where we enable the collection of verbose logs:

Enable-storagediagnosticlog-storagesubsystemfriendlyname *cluster*-level Verbose

650) this.width=650; "Width=" 751 "height=" 103 "title=" Enable-storagediagnosticlog.png "style=" width:750px;height : 84px; "src=" Https://s1.51cto.com/wyfs02/M02/98/CB/wKioL1lArMqTHZkfAABUOrHulJI900.png "alt=" Wkiol1larmqthzkfaabuorhulji900.png "/>

3. We then use the following command to collect the relevant logs and place the collected logs in the C:\tmp directory:

Get-storagediagnosticinfo-storagesubsystemfriendlyname *cluster*-destinationpath C:\tmp-Verbose

650) this.width=650; "width=" 814 "height=" 183 "title=" Get-storagediagnosticinfo.png "style=" width:728px;height : 144px; "src=" Https://s4.51cto.com/wyfs02/M01/98/CD/wKiom1lAyVuRoJMVAABGyuJPgbE102.png "alt=" Wkiom1layvurojmvaabgyujpgbe102.png "/>

After completion we can find the log of each node in the corresponding directory, as shown in the Event Viewer to open the corresponding. ETL and EVTX files:

650) this.width=650; "Width=" 523 "height=" "title=" Get-storagediagnosticinfo-folder1.png "style=" width:520px; Height:135px;float:none, "src=" Https://s2.51cto.com/wyfs02/M00/98/D1/wKioL1lA3lbRmZfbAAAsXGaHET0427.png "alt=" Wkiol1la3lbrmzfbaaasxgahet0427.png "/>

650) this.width=650; "Width=" 516 "height=" "title=" Get-storagediagnosticinfo-folder2.png "style=" WIDTH:511PX; Height:115px;float:none, "src=" Https://s2.51cto.com/wyfs02/M02/98/D1/wKiom1lA3laRX2xLAAAkEQAa5hE395.png "alt=" Wkiom1la3larx2xlaaakeqaa5he395.png "/>

4. We can also use the Get-storagehealthaction command to view running tasks in the background, with the Get-storagehealthreport command to view real-time storage pool read/write latency, CPU or memory consumption, read and write bandwidth consumption, and other performance-related data , which is especially important for diagnosing performance problems. The command and output results are as follows:

Get-storagesubsystem-friendlyname *cluster* | Get-storagehealthaction

650) this.width=650; "Width=" 620 "height=" "title=" Get-storagehealthaction.png "style=" width:615px;height:90px; " Src= "Https://s1.51cto.com/wyfs02/M01/98/D3/wKioL1lA5ZmQAcdtAAAvzripg5I538.png" alt= " Wkiol1la5zmqacdtaaavzripg5i538.png "/>

is a performance report that is caught when a volume is written to a storage pool for a large amount of data:

Get-storagesubsystem-friendlyname *cluster* | Get-storagehealthreport-verbose

650) this.width=650; "Width=" 1121 "height=" 359 "title=" Get-storagehealthreport.png "style=" width:1019px;height : 307px; "src=" Https://s1.51cto.com/wyfs02/M02/98/D3/wKioL1lA5cez7gt8AALAxW0Ns0M890.png "alt=" Wkiol1la5cez7gt8aalaxw0ns0m890.png "/>

5.get-storagereliabilitycounter is also a useful tool, such as using a combination of commands like the following to capture the maximum read/write delay, read/write errors, temperature, and frequency of each SSD disk in the storage pool. Write count consumption and so on important information (I suspect that because of the use of the virtual disk, causing some of the data in this case can not be caught properly).

Get-physicaldisk |? Mediatype-eq SSD | Get-storagereliabilitycounter-verbose |select *

650) this.width=650; "width=" 1111 "height=" 355 "title=" Get-storagereliabilitycounter.png "style=" WIDTH:1088PX; height:342px, "src=" Https://s1.51cto.com/wyfs02/M01/98/D3/wKiom1lA6RuwVVYFAAES0RbNgok986.png "alt=" Wkiom1la6ruwvvyfaaes0rbngok986.png "/>

6. With the help of Windows Performance Monitor, we can further monitor the performance indicators of a VD, as shown in:

650) this.width=650; "Width=" 572 "height=" 426 "title=" Perfmonitorcounters.png "style=" width:565px;height:394px; "src = "Https://s3.51cto.com/wyfs02/M02/98/D4/wKioL1lA64SgGhNTAABMYgmuX6Q110.png" alt= " Wkiol1la64sgghntaabmygmux6q110.png "/>

7. Similar to other major SDS products, the current s2d also has a strong data protection capabilities, the author has been in the test environment to simulate a single block of disk drop, multiple disk drop, or even more than one node unexpectedly downtime and other situations. In general, whether or not VD in the storage pool can continue to be accessed in the case of a failure depends on the fault-tolerant layout defined at the time of creation and the definition of the fault domain. It is also important to note that regardless of which fault-tolerant layout is used, backups cannot be replaced. Regular backups of business data remain critical. When there are multiple disk drop, or multiple node failure, resulting in data is not properly accessed, the first time to crawl the detailed log, contact the vendor after sale is the most important.

This article is from the "servers in the Cloud" blog, so be sure to keep this source http://yddfwq.blog.51cto.com/4016432/1936701

Simply test Windows S2D (3) in a vsphere environment