My lecture about S2D at 3rd SysOps/DevOps meetup in Wrocław.

Recently I’ve bitten quite hard into Storage Space Direct (S2D) Hyper-V clusters. Surprisingly I was also asked to prepeare some lecture on the SysOps/DevOps 3rd meetup and as at that time I was preparing to upgrade my MCSA to 2016, lecture about S2D was quite a good idea as it was covering some materials.

Here is me showing how good piece of an idea it was ^^

CoolStoryBro

Here it is (might be harder for those who do not know Polish language ^^):

I added some pieces of information post factum, here they are:

  1. In Windows Server 1709 it is possible for data to migration from capacity tier back to the performance tier, operations that decide when this happen are writes – not reads – more about it >> here <<
  2. I told that there is no place showing associations of cache drives to the capacity drives – well I was wrong at that time, no longer than 2 days after the meetup I’ve found out this mavelous article by Jan-Tore Pedersen – thanks Jan! ^^

I am happy I had opportunity to hand over a copy of own book, this was my first time I was actually signing something to someone and this person was not a police officer and the paper was not a ticket, YAY!

Advertisements

Automated way to check Mellanox RDMA ping (nb_send_bw.exe) across nodes in a Hyper-V cluster.

So just recently we got need of checking RDMA ping between nodes, and as we got a few the task of running nb_send_bw.exe was getting a little fiddly. As we were waiting for repair storage jobs to finish between restarts I wrote a few lines to automating task.

GetReady

Continue reading “Automated way to check Mellanox RDMA ping (nb_send_bw.exe) across nodes in a Hyper-V cluster.”

Storage Space Direct – how to check storage jobs to not blow things up.

Just a small reminder for myself…

thisclose

Remember kids, storage jobs are only visible when running ISE or PowerShell console as an admin!

Safest is to always check the status of the jobs with invoke-command, as my dear colleague told me today, when using invoke you use the highest privileges:

Invoke-Command -ComputerName <CLUSTER_NODE_NAME> -ScriptBlock {Get-StorageJob}