These days, businesses do not stick to one location anymore. Such trend pushes companies to build stretched clusters, IT infrastructures spanned across several locations. Such approach enables them to implement better disaster recovery strategies and achieve higher performance. To build such environments, you need fast connection and the solution to use resources of all your remote sites just as they were located in one place. Here, VSAN from StarWind comes into play – the solution for building high performing active-active replicated shared storage.

Many words were said about NFS (Network File System), but what exactly NFS can give us? In general, NFS used as the ISO library or just simple network file share with easy access from any Windows or Linux based machine. However, starts from NFS 3.0 protocol can give us the good performance and can be as the shared storage for ESXi or any Linux based Hypervisors. In this article, I will create the NFS share on the Windows Server 2016 and then mount NFS share on the ESXi 6.5 and will create the VM on it.

An under-reported trend in storage these days is the mounting dissatisfaction with server-centric storage infrastructure as conceived by proprietary server hypervisor vendors and implemented as exclusive software-defined storage stacks.  A few years ago, the hypervisor vendors seized on consumer anger around overpriced “value-add” storage arrays to insert a “new” modality of storage, so-called software-defined storage, into the IT lexicon.  Touted as a solution for everything that ailed storage – and as a way to improve virtual machine performance in the process – SDS and hyper-converged infrastructure did rather well in the market.  However, the downside of creating silo’ed storage behind server hosts was that storage efficiency declined by 10 percent or more on an enterprise-wide basis; companies were realizing less bang for the buck with software-defined storage than with the enterprise storage platforms they were replacing.

This series of articles will guide you through the basic deployment of Microsoft Windows Server 2016 Core version, covering all the steps from an initial installation to the deployment of Hyper-V role and Failover Cluster configuration. The first and the main thing you need to double-check before installing the Windows Server 2016 Core is whether your hardware meets the system requirements of WS 2016. This also is very important in the process of planning your environment, in order to be sure that you have enough amount of compute resources for running your production workload.

As written in the previous post, for ROBO scenario the most interesting HCI (Hyper-Converged Infrastructure) configuration is a two nodes configuration, considering that two nodes could be enough to run dozen VMs (or also more). For this reason, not all hyperconverged solutions could be suitable for this case (for example Nutanix or Simplivity need at least 3 nodes). And is not simple scale down an enterprise solution to a small size, due to the architecture constraints.

Design a ROBO scenario must match finally the reality of the customers’ needs, its constraints but also the type of workload and the possible availability solutions of them.