Historically, the adoption rate on major server releases is slow. With Windows Server 2016 about to hit one year in the release cycle, more organizations are gearing up to deploy the operating system in their environments. That being the case, it seemed appropriate to walk through an install of Microsoft Windows Server 2016 as the guest OS in a vSphere 6.5 environment.
NOTE – Server 2016 is fully supported from ESXi 5.5 and up, as per the VMware Compatibility Guide.
VMware vRealize Orchestrator is an automation tool that utilizes workflows to simplify complex IT tasks. vRealize Orchestrator is natively integrated into vRealize Automation or it can be deployed stand-alone as a Linux appliance. At first glance, the lines between vRealize Orchestrator (vRO) and vRealize Automation (vRA) may seem blurred. To clear up any confusion, vRO is a general-purpose run book tool to automate IT tasks. vRA, on the other hand, is cloud management tool that relies on policy based governance to deliver IT service. As its central automation tool, Automation leverages Orchestrator workflows.
NOTE – Version releases prior to 7.0.1 also allowed for a Windows-based installer. If you are still using a Windows version, you can migrate from Windows to the appliance.
For the purpose of this post, we will be deploying the Linux-based appliance and configuring vRealize Orchestrator 7.3 as a Standalone Server using vSphere Authentication.
Here is an issue more on the obscure side; nevertheless, it may prove beneficial to someone, somewhere, at some point. The issue pertains to a SQL database going Suspect after a Zerto Failover. To adequately explain the cause, we will first look at Microsoft SQL Server best practices for both VMware and Zerto.
Let’s start with VMware best practices. Assuming the back-end storage is spinning disks and the virtual disks reside on VMFS volumes, VMware recommends separating SQL files. Meaning, SQL Server binaries, SQL data (mdf), SQL transaction logs (ldf), and tempdb files are placed on separate VMDKs. Since SQL Server accesses all that data in different I/O patterns, separating their files helps minimize disk head movements and limits I/O contention; thus optimizing storage performance. The disk configuration in the affected environment looked like this:
A few months back, we discussed how to upgrade ESXi hosts using VMware Update Manager. However, if you do not employ VUM, hosts can also be upgraded via ESXCLi commands using an online repository.
In this tutorial, we will upgrade an ESXi host from 6.0 to 6.5 using VMware Online Depot. In addition, I will discuss how to differentiate image profiles within the depot. If you are unfamiliar with the VMware Online Depot, it’s an online repository that provides access to a set of VIBs and image profiles.
Let’s start with that overview on image profiles and how to distinguish them in the online depot. This information could have easily been a post in itself, but if you are new to image profiles and the online depot, it may prove beneficial to be all in one place. If you already know the deal, feel free to skip ahead.