Educational Episodes: Hyperconverged Infrastructure (HCI)

Why do I need to use complicated ways to access my files that are located on company’s server or in my homelab, for example? I want to ask the same question in order to make remote files available for my local applications without any extra actions. The answer, as well as the solution to the problems listed above, lies in the next four words – Network File System protocol. I’d like to start with the general description of the NFS technology and some background about its purpose, and how it was created. The story goes back to middle 80’s when, alongside with the Van Halen’s new “1984” album, the company named Sun Microsystems created a Network File System protocol. It allowed users to access some files from the servers over a network, just like if these files were located on users’ machines.

Here is the second article of 2 for the Azure Site Recovery implementation with ARM:

1. Preparation of the environment (Part 1)
2. Start the replication and Failover/Failback

Today we will see how to implement a DRP solution, with Azure Site Recovery. I’ll deploy this solution, based on the ARM. ASR can be used to migrate your VMs to Azure, from VMWare to Azure, etc. In my DRP plan, the service that I defined as critical for my business is a website. I’ll replicate this VM on Azure, with ASR. You can do the same work with a multi-tier application. In my architecture, I have a VPN S2S to Azure. Attached to this network who is connected to the VPN, I have a second domain controller, who is acting as DNS.

In the previous blog post, I’ve walked you thru the process of creating the Windows Server 2016 Failover Cluster  (WSFC) that is not joined to an Active Directory Domain. It is very important that you get the underlying WSFC properly configured and stabilized before you even attempt to create the SQL Server 2016 Always On Basic Availability Group. The availability and reliability of your SQL Server 2016 Always On Basic Availability Group depends so much on the WSFC.

Managing user mailboxes in Microsoft Exchange Server 2016 is a day-to-day task of system engineers. This article focuses on managing user mailboxes in Microsoft Exchange Server 2016 including very common features like creating, removing and disabling the mailboxes with the help of PowerShell.

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.

We have been talking on this blog before about the importance Microsoft and the rest of cloud providers are giving to security features and products in the last couple of years. The well-known security incidents present in the industry just in 2017 generated to companies billions in a loss, hence a large number of releases from Microsoft to face these incidents and, above all, provide calm to their customers around the cloud. Microsoft Advanced Threat Analytics (ATA) combines several of the latest security enhancements. In this article, we will review how to connect the ATA platform to Azure, guaranteeing a reliable monitoring.

In the modern IT world, almost every tech guy, no matter a systems administrator or an engineer, wants his environment to show the best results that can be squeezed out of the hardware. In this article, I want you to take a look at the StarWind support of an iSER technology which stands for the iSCSI Extensions for RDMA. There’s not much of a change in the overall system configuration. iSER is utilizing the common iSCSI protocol by using the RDMA transport service that can be used on some network adapters with hardware offload capability. This means that iSER can supply higher bandwidth, intended for large transfers of block storage data.

Microsoft SQL Server 2016 has a pretty decent feature set to achieve cost-effective high availability for your environment and build a reliable disaster recovery solution. Basic Availability Groups (BAGs) and Failover Cluster Instances (FCI) are included in SQL Server 2016 Standard Edition and serve to implement high redundancy level for business-critical databases. In this article, I would like to discuss some differences between these solutions and open the curtain on how it can be done with Software-Defined Storage like Storage Spaces Direct (S2D) and VSAN from StarWind (StarWind VSAN).