Just before Christmas (2017) Veeam released Update 3 for Veeam Availability Suite 9.5 in addition to updates for Veeam Agent for Windows and Veeam Agent for Linux. The links to the KB release notes are at the bottom of the post but below is a quick summary of some of the features announced.
So far I’ve covered the various methods vSAN uses to protect data within a cluster and even across sites. In this post I will look at how vSAN handles failures and the processes involved to recover data to ensure the virtual machines redundancy requirements are met.
Now I’ve covered the high-level architecture of vSAN it’s time to look at how the data is structured within the vSAN datastore and how vSAN uses multiple hosts within a cluster to provide data redundancy. Not forgetting one of the biggest benefits with vSAN - this is all configured using policies that are configured at the software layer.
This post will cover vSAN architecture at a high level along with network recommendations and requirements to support vSAN. Finally, I’ll cover some of the hardware recommendations to ensure a vSAN deployment is successful.
Whilst many of our customers have a good high-level understanding of vSAN this series of blog posts will cover some of the concepts in further detail and hopefully help answer some of the typical questions I get asked.
It’s hard to believe the popular SC4020 has been around for over 3 years now and recently Dell EMC have announced its successor, the SC5020. This post will look at some of the key differences and improvements to the mid-range SC storage array.
I am currently using Ivanti Patch for Windows Servers to patch our virtual demonstration and test environment and thought I would share a short blog post around some of the common misconfigurations that can be made when setting up the automated patching