All posts by this author

Does low latency, high throughput & CPU offloading require RDMA? What? Blasphemy, how dare we even question this? In my defense, I’m not questioning anything. I am merely being curious. I’m the inquisitive kind. The need for RDMA is the premise that we have been working with ever since RDMA became available outside of HPC InfiniBand fabrics. For us working in the Windows ecosystem this was with SMB Direct. Windows Server 2012 was the OS version that introduced us to SMB Direct, which leverages RDMA.

Learn More

Appreciate how useful this article was to you?

5 out of 5, based on 1 review

Loading...

iWarp, RDMA, RoCE, SMB

The RDMA wars in regards to SMB Direct: RoCE versus iWarp.

Learn More

Appreciate how useful this article was to you?

5 out of 5, based on 1 review

Loading...

DMA, iWarp, RoCE RDMA Mellanox, SMB, SMB Direct

The Flavors of RDMA & what role DCB plays.

Learn More

Appreciate how useful this article was to you?

5 out of 5, based on 1 review

Loading...

Datacenter, DCB, RDMA, SMB Direct, Windows Server 2012 R2

What is RDMA and why do we like it.

Learn More

Appreciate how useful this article was to you?

1 out of 5, based on 1 review

Loading...

CPU, HCI, RDMA, SMB, SMB Direct

Imagine you have a server with data source volumes that are backed up to local (or a share) target backup volumes with Veeam Agent for Windows (VAW). You might or might not backup the OS as well. That server is old, has issues or has crashed beyond repair and needs to be replaced. You don’t really care all that much about the server OS potentially but you do care about your data backup history! You don’t want to lose all those restore points. Basically, we try to answer how do you replace the backup server when it’s a local Veeam Agent for Windows 2.1 deployment.

Learn More

Appreciate how useful this article was to you?

5 out of 5, based on 1 review

Loading...

backup, SQL, VAW, Veeam, Veeam Agent

Many years ago, I wrote a white paper on how to configure a VEEAM Off-host backup proxy server for backing up a Windows Server 2012 R2 Hyper-V cluster that uses a hardware VSS provider with VEEAM Backup & Replication 7.0.  It has aged well and you can still use it as a guide to set it all up. But in this article, I revisit the use of a hardware VSS provider dedicated specifically to some changes in Windows Server 2016 and its use by Veeam Backup & Replication v9.5 or later. The information here is valid for any good hardware VSS provider like the one StarWind Virtual SAN provides (see Do I need StarWind Hardware VSS provider?)

Learn More

Appreciate how useful this article was to you?

5 out of 5, based on 1 review

Loading...

backup proxy, Hyper-V backup, Hyper-V host, LSFS, Veeam backup proxy, VSS, VSS provider, VSS snapshots, windows server 2016, Windows Server 2016 Hyper-V

In Windows Server 2016 Microsoft introduced storage Quality of Service (QoS) policies.  Previously in Windows Server 2012 R2, we could set minimum and maximum IOPS individually virtual hard disk but this was limited even if you could automate it with PowerShell. The maximum was enforced but the minimum not. That only logged a warning if it could be delivered and it took automation that went beyond what was practical for many administrators when it needed to be done at scale. While it was helpful and I used it in certain scenarios it needed to mature to deliver real value and offer storage QoS in environments where cost-effective, highly available storage was used that often doesn’t include native QoS capabilities for use with Hyper-V.

Learn More

Appreciate how useful this article was to you?

No Ratings Yet

Loading...

bandwidth, CSV, Hyper-V cluster, IOPS, QoS policies, Scale-out File Server, SoFS, storage load, storage performance, VHDX, virtual hard disk, windows server 2016

Ever since Windows Server 2012 we have SMB Direct capabilities in the OS and Windows Server 2012 R2 added more use cases such as live migration for example. In Windows Server 2016, even more, workloads leverage SMB Direct, such as S2D and Storage Replication. SMB Direct leverages the RDMA capabilities of a NIC which delivers high throughput at low latency combined with CPU offloading to the NIC. The latter save CPU cycles for the other workloads on the hosts such as virtual machines.

Learn More

Appreciate how useful this article was to you?

No Ratings Yet

Loading...

CPU, Mellanox, networks, protocols, RDMA, SMB Direct, throughput, Virtual Network Adapter, vNIC, vSwitch, windows server 2016

If you read my blog on Switch Embedded Teaming with RDMA (for SMB Direct) you’ll notice that I set the -IeeePriorityTag to “On” on the vNICs that use DCB for QoS. This requires some explanation. When you configure a Switch Embedded Teaming (SET) vSwitch and define one or more management OS vNICs on which you enable RDMA you will see that the SMB Direct traffic gets it priority tag set correctly. This always happens no matter what you set the -IeeePriorityTag option to. On or Off, it doesn’t make a difference. It works out of the box.

Learn More

Appreciate how useful this article was to you?

5 out of 5, based on 1 review

Loading...

DCB, IeeePriorityTag, QoS priority, RDMA, RDMA vNIC, SET, SMB Direct, Switch Embedded Teaming, vNIC, vSwitch, windows server 2016

Window Server 2016 Hyper-V brought us Switch Embedded teaming (SET). That’s the way forward when it comes to converged networking and Software-Defined Networking with the network controller and network virtualization.  It also allows for the use of RDMA on a management OS virtual NIC (vNIC). One of the capabilities within SET is affinitizing a vNIC to a particular team member, that is a physical NIC (pNIC). This isn’t a hard requirement for SET to work properly but it helps in certain scenarios. With a vNIC we mean either a management OS vNIC or a virtual machine vNIC actually, affinitizing can be done for both. The main use case and focus here and in real life is in the management OS vNICs we use for SMB Direct traffic.

Learn More

Appreciate how useful this article was to you?

No Ratings Yet

Loading...

pNIC, PoweShell, RDMA, SDN, SET, SET vSwitch, smb3, Switch Embedded Teaming, vNIC, vSwitch