I’m working from home today, and while checking in on my Veeam backups and taking stock of the environment I noticed something I hadn’t seen before. Veeam has a new repository type named “Scale-out Repositories”. Having not heard of this before, and not having a lot of work to do on this work from home day I decided to investigate.
Now that Log Insight 3.3 has had its GA release lets take a look at it. The biggest thing to come out of this GA is the announcement that all licensed versions of vCenter will now come with a 25 OSI pack for Log Insight. Now at the very least vCenter customers will be able to take advantage of Log Insight to log and monitor at least the physical components of their infrastructure, such as the physical hosts that ESXi is installed, the switches, and even the storage arrays. With ever expanding content packs that means that just by purchasing a fully licensed version of vCenter you’ll be able to centrally manage your logs from your physical infrastructure and alert from these logs. This will be an excellent way for businesses to review the value of Log Insight and get their feet wet without having to plunge all the way in, and is also a good way to save money for smaller business by packaging a pretty robust monitoring solution into the product. Continue reading “Log Insight 3.3”
Note: This post was originally made on Sept. 18, 2015 on a separate blog. I am relocating the information here.
This is a quick guide on how to automate the deployment of a Log Insight instance using PowerCLI. It also reviews how to get information about various configuration options so you can work with other OVA deployments. Please note that this only gets you a VM that is configured and ready to power on. There is currently not a(n easy) way to script the configuration of the application with scripting. I have put in a feature request and it is being looked at.
Today the Virtual SAN team at VMware released a content pack for Log Insight. This expands on the fairly basic, single dashboard provided in the vSphere content pack, which is a combination of VSAN and VVOLs, which is really just a glorified “is it running” dashboard. The content pack contains useful information and a way to easily visualize common problems in a VSAN deployment. Since I made a feature request around this on the VMware Log Insight forum I figured I would do a quick run through of what is provided in the content pack and my opinions on it. Continue reading “Virtual SAN and Log Insight”
Previously I discussed default settings regarding Horizon View linked-clone machines and their Failures To Tolerate (FTT) setting on a Virtual SAN cluster. Today I want to talk about performing maintenance on a VSAN cluster hosting a Horizon View environment. This is mostly in regards to maintenance that requires a reboot of the host, e.g. BIOS/firmware updates. I recently had a memory module fail on a host that caused it to be unable to boot until the module was removed. This causes faults with Horizon View in several different ways. The primary one I want to discuss is an error regarding the Composer server being unable to connect with all the hosts in the cluster being used. Continue reading “Horizon View and Host Maintenance”
I had a host fail due to a bad stick of RAM over the weekend and it brought my attention to something I hadn’t noticed before. There are two VM Storage Policies for Horizon View Linked Clone desktop VMs, and one of them (OS_DISK_FLOATING_<hex UUID>) is set to tolerate 0 failures of the cluster. Now, at first I thought it was just a fluke but I confirmed this on another View on VSAN cluster. It appears to be the default policy setting. Continue reading “Horizon View on VSAN and Faults To Tolerate”
This probably isn’t the best way to introduce myself into the world of blogging, however it is something that I have had to deal with many times, and I really want to bring attention to it because I rarely hear anyone talking about it. In light of the most recent CBT bug reported in ESXi 6.0 I want to talk about VMware and snapshots in general. Continue reading “VMware and Snapshots”