Browsing Posts tagged vCenter

Reading Time: 2 minutes The Reduced Downtime Upgrade (RDU) is a new mechanism introduced in vSphere 8.x for upgrade/update the self-managed vCenter Servers with a minimal downtime (lesser compared to normal upgrade/update procedure). What is the Self-managed vCenter Server? It’s a vCenter Server that manages its own ESXi host and its own virtual machine. More information are available in KB 92659 (vCenter Server upgrades with the reduced downtime).

Reading Time: < 1 minute According with Product Lifecycle Matrix and KB 89305, VMware has officially declared, vSphere 6.5.x and vSphere 6.7.x will be End of General Support by October 15th 2022. To maintain your full level of Support and Subscription Services, VMware recommends upgrading to vSphere 7.

Reading Time: 2 minutes The file-level backup feature introduced in vCSA 6.5 is very powerfull and schedulable (starting with vCSA 6.7) because sometimes the image-level backup may not provide the proper integrity if you have corrupted files inside the VM. Also with vSphere 7.0 is possible monitoring the status of the file-level backup directly from vSphere Client and this is quite usefull to have this information direct visible from the UI:

Reading Time: 2 minutes There is a big issue in vCenter Server, with sensitive information disclosure vulnerability in the VMware Directory Service (vmdir). Under certain conditions vmdir that ships with VMware vCenter Server, as part of an embedded or external Platform Services Controller (PSC), does not correctly implement access controls.

Reading Time: 2 minutes A usual 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 and cannot guarantee a restore in some cases, for example in the case of a database corruption.

Reading Time: < 1 minute This is an article realized for StarWind blog and focused on the design and architecture of VMware vCenter and PSC topologies. See the original post. You can “federate” multiple vCenter Server systems using vCenter Linked Mode (introduced in vSphere 4.0) to build a single pane of glass and share information between vCenter instances, like view and manage the inventories of all the vCenter Server systems that are linked.

Reading Time: 3 minutes If 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: 3 minutes One 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: 2 minutes VMware vSphere 6.5 it’s quite popolar now, considering the deadline for the version 5.5 in this year and the direct upgrade path from v5.5 to v6.5. But maybe not everybody want to update vSphere 6.5 to Update 2, considering that there will be no upgrade path (yet) to version 6.7 and maybe other minor issues due to the backport of some features.

Reading Time: 3 minutes VMware has released (on Feb, 15th) a new vCSA version: vCenter Server 6.5 U1f, with build number 7801515. This release patches the vCSA operating system (Photon OS) mainly against two vulnerabilities: bounds-check bypass (Spectre-1, CVE-2017-5753) and rogue data cache load issues (Meltdown, CVE-2017-5754). As of now, there is still no patch for branch target injection vulnerability (Spectre-2, CVE-2017-5715). VMware has also updated the security advisory dealing with all of its virtual appliances updates for Spectre and Meltdown vulnerabilities, VMSA-2018-0007. But note that VMSA-2018-0004.2 has not been updated yet, and it still report that the suggested version for […]

© 2024-2011 vInfrastructure Blog | Disclaimer & Copyright