Good understanding of storage is vital to every IT admin, freshman or not. vSphere continues to innovate how it uses storage, so it’s better to brush up on existing ways before getting into novelties. So before checking out vSphere 7 and Tanzu with their Paravirtual Container Storage Interface (pvCSI), let’s repeat the core material.
The issue with, for example, employees leaving your company is that they can take the Kube file with them. With that file, they can access your Azure Kubernetes Service (AKS). One way to avoid that is to remove the opportunity of access entirely by renewing certificate authority for the designated AKS cluster.
In large infrastructures, there may be clusters of hosts that require patching. A full reboot would take quite a long time. Now, vSphere Lifecycle Manager (vLCM) has a quick boot option (a kind of a warm boot), which allows for a much smoother boot. Additionally, the “desired state” image of the cluster feature will ensure that new hosts that differ for some reason from the “image” will be remediated to the desired state.
Normally, the pods within your Azure Kubernetes Service (AKS) communicate freely. Such a situation can compromise your security if met with a certain threat. To avoid that, you can use Azure or Calico Network Policies to restrict communication and allow only a set configuration for communication between your pods to avoid unnecessary cyber threats.
More transparency, fewer hardware restrictions, freedom of choice, clarity of control, and immutability — that’s where backups are headed. Microsoft has been taking too long to adapt its ReFS to those consumer demands. Veeam and Linux, on the other hand, leverage those trends and offer immutability with reasonable freedom of object and cloud storage choice.
More transparency, fewer hardware restrictions, freedom of choice, clarity of control, and immutability — that’s where backups are headed. Microsoft has been taking too long to adapt its ReFS to those consumer demands. Veeam and Linux, on the other hand, leverage those trends and offer immutability with reasonable freedom of object and cloud storage choice.
VMware VEBA is a tool that allows you to create event-driven automation with the ability to trigger custom or pre-built actions depending on your vSphere event. It’s currently distributed as a Fling and available as a virtual appliance, deployed via an OVA file. It’s easily deployable on-premises to your vSphere or in a public cloud if you’re using that scenario.
Learning how to configure Veeam Backup for Office 365 is great but restoring an O365 tenant is a whole other story. To follow this article and complete the necessary actions, you’ll need to install the explorer console provided with Veeam Backup for O365 on your server. Then, a user-friendly interface will take you through the restoration procedure.
Learn More
With new vSphere versions, it’s not just about one-click upgrades. There are various things an admin has to account for in good time. You need to consider the interoperability of other VMware products and other existing infrastructure components, which upgrade path to take, back-in-time upgrade threats, developing the upgrade plan, and necessary post-upgrade procedures.
Part 2 discussed adding the Linux server to Veeam managed servers and adding immutable repositories, along with incompatible configs that Veeam’ll block if you try using them. Today, you will learn about the entire configuration deeper: how immutability works, scenarios with bad actors, how they can succeed, and how to test if all is working fine.
