Browsing Posts in vSphere

Reading Time: 3 minutesVMware vSphere 5.5 is really close to its End of Support, that will mean no more updates and possible limited support from VMware. The End of General Support for vSphere 5.5 is September 19, 2018. To maintain your full level of support and subscription services, VMware recommends upgrading to vSphere 6.5, or to a newer version.

Reading Time: 3 minutesThree years ago, VMware has decided to make VMware Tools an independent package, with a separate lifecycle and available in the MyVMware download page as a separated package. Separated and independent from VMware Fusion, Workstation and ESXi virtualization solutions! Seems good, but on vSphere environment, this can make some confusion considering that you have the VMware Tools bundled with ESXi and the standalone VMware Tools usually with a bigger version and independent also by the version of vSphere!

Reading Time: 2 minutesThere are a lot of different possible reasons why a VM does not power on a VMware vSphere infrastructure, but usually, the error message can really help to found the reason or the root cause. Maybe not available resources, maybe some files that are missing, maybe some incompatibility… But normally you can put the error message and found the proper VMware KB that can help you.

Reading Time: 4 minutesAs usual, VMworld has several announcements, and for the second year in a row, there are some important announcements about the core virtualization platform: VMware vSphere. First news is a not surprising new vSphere 6.7 Update 1… At the begin of the year, my bet was that vSphere 6.7 was announced during VMworld US and maybe vSphere 6.7 Update 1 at VMworld EU, but seems that the releasing of the product has been accelerated (in my opinion to accelerate vSAN growing).

Reading Time: 6 minutesThe new vSphere Client in HTML5 introduced with vSphere 6.5 was originally a Flings project called: vSphere HTML5 Web Client. The name is inconsistent now, but the Flings project mantain the original name to avoid something like ‘vSphere Client Fling’ and also to keep its independed devel path. And on August 22, 2018 a new release of the Fling version has been released: v3.41 – Build 9687895.

Reading Time: 2 minutesIf you still are using the Windows based vCenter Server with a SQL Server database you may have some login issues, due to a recent Windows update (released on July 10, 2018). You will have some errors in the SQL Server part with SQL startup issues due to “TCP port is already in use” errors. This is caused by a regression in the TCP/IP functions that manages the TCP port pool introduced in the July 10, 2018 Windows updates for Windows 7/Server 2008 R2 and Windows 8.1/Server 2012 R2.

Reading Time: 7 minutesThe L1 Terminal Fault (aka Foreshadow) bug is another speculative execution side channel attack that affects Intel Core processors and Intel Xeon processors only. For VMware vSphere, there are some patches available as described in this document: VMSA-2018-0020. All patches have been released on August, 14th 2018.

Reading Time: 3 minutesDell EMC OpenManage Server Administrator (OMSA) is a complementary tool that provides a comprehensive, one-to-one systems management solution in two ways: from an integrated, web browser-based graphical user interface (GUI) and from a command line interface (CLI) through the operating system. Usually, you should add it to each bare metal system, unless you are using other management tools. But also if you are using Open Manage Essential (OME) or similar, OMSA provide some unique and powerful features, like the access to the BIOS settings.

Reading Time: 3 minutesOne common way to backup the VMware vCenter Server Appliance (VCSA) is to manage as a common VM and use a backup solution to backup (and restore) the entire VM. But it’s approach does not always work, for example in the case of a database corruption the VM restore could be not working. Starting with vSphere 6.5 and the new VCSA 6.5 was possible to use also a native backup solution integrated with the vCenter Server Appliance Management Interface (VAMI). But it was a manual operation (some scripts are available to automate and schedule it).

Reading Time: 7 minutesSome months ago I’ve written a post (Is the HTML5-based vSphere Client ready to replace the vSphere Web Client?) on the limitation of the new vSphere Client, but this was before the vSphere 6.7 and vSphere 6.5U2 releases. VMware vSphere, during its history and the different versions, has got several types of Graphical User Interface (GUI) client. One of the most used (not the first, but the standard one since Virtual Infrastructure 3.0) was the vSphere Client for Windows. But on May 2016 VMware has announced that the Legacy C# Client (aka thick client, desktop […]

Reading Time: 2 minutesVM Explorer is another backup (and replication) tool with native support for virtualized platforms (vSphere and Hyper-V) with a good success in the SMB segment. Initially was build by a Swiss company (Trilead), acquired later by HP(E) and recently acquired by Microfocus. Lot of changes in the name, but not in the substance and with a good development and release cycles. Now Microfocus has released a new VM Explorer release (v7.1) compatible with the latest version of VMware vSphere 6.7.

Reading Time: 3 minutesVMware vSphere provides a different way to copy the VM data during a backup operation: those modes are called transport modes. There are at least three major transport mode: network mode (or NBD), hot-add mode (or VM proxy mode), SAN mode (of storage offload mode). Most of the backup products can use those different transport modes depending on the configured infrastructure and the requirements.

© 2018-2011 vInfrastructure Blog | Disclaimer & Copyright