In my initial setup I opt’d to use use NFS as my CSI as the lab I was using to play around was still vSphere 6.7u2 which did not meet the minimum requirements for Cloud Native storage. So I decided to spend some time over the weekend and upgrade it to 7.0u2 which was recently been released.
As always I’m sure this blog series will contain some errors/issues as I am learning as I go so please feel free to reach out to me and lets chat, we are all learning together!
In the previous post we mentioned a Kubernetes cluster is made up of a CNI, CSI and a container runtime. We previously went through the process of deploying our container runtime(containerd) and our network interface(calico) and managed to bootstrap the whole setup together forming our functional cluster, Awesome!
Continuing with our learning here as always I’m sure this blog series will contain some errors/issues as I am learning as I go so please feel free to reach out to me and lets chat, we are all learning together!
Looking at how IT is changing it is undeniable that containers has become the latest hot topic and rightfully so, arguably becoming the next step in the virtualization lifecycle, Not that it should be viewed as a replacement for VMs, in fact i think we will be seeing containers and VMs living side by side for a long time as they both provide a function.
We all love storage and these days even in a home setting we store terabytes worth of data. The new cliché saying is “Data is the new oil” and when you think about it that is very true.
We generate an unreal amount of data each day which must be stored somewhere, what better way to store this data than on your own NAS. In this run through of the new Synology DS1621xs+ we will be taking a look at the NAS unit itself, The new Synology HAT5300-8T HDDs and the new Synology Active Backup for Business suite offered by Synology.
We talk a lot about cloud mobility and how it has affected the IT landscape of the past decade. It has disrupted business as we know it as it seems every company is going through a cloud journey of some sort most prominent being the public cloud.
We see customers moving workloads to public cloud in anger and in some cases require the ability to move that particular workload back due to unforeseen issues. This is more common than one would think so today I will being taking you on an adventure to Azure and back again using Veeam.
Setting up modern authentication in Veeam for Office 365 recently came up in a conversation so thought I’d write a quick blog post about it because honestly its amazingly easy and makes life a lot easier 🙂
I have been running a VMware HomeLab for quite some time now and considering I rebuild my lab often I decided its probably time to re-deploy my VMware home lab using vCenter 7. I’ve held off for a while due to hardware constraints but the time as finally come…
Veeam Office365 V5 dropped today which includes native support for Teams. This is a huge step in the right direction as MS Teams usage has exploded since COVID, I know I spend a lot of my day in Teams and have recently uploaded a significant amount of data to Teams so being able to protect it is very important.
This post will hopefully be the start of a series of small but useful tips for everyday Veeam users. We use Veeam almost everyday so we know our way around it but every now and then you stumble upon a feature that gets you all excited because its been there but you just haven’t used it or weren’t aware it was there. 🙂
Veeam version 10 released a heap of new features along with SAML 2.0 support for Veeam Enterprise Manager (VEM). What this means is that you can now use 3rd party identity providers to authenticate users into the Enterprise Manager, adding support for non-Active Directory users, multi-factor authentication etc.