This video demonstrates how to revert an ESXi host to a previous version using the Direct User Console Interface (DCUI).
VMware recommends that you back up the configuration data before proceeding with any changes.
Reverting an ESXi host is only available if the host was updated using one of the following methods:
- VIB installation or removal
- Profile installation or removal
- ESXi host updated using VMware Update Manager
- ESXi host updated from a ISO
This video demonstrates how to purge old data from the SQL Server database used by vCenter Server. You would need to perform task if your vCenter database is full.
When the vCenter Server database if full:
- You cannot log in to vCenter Server
- VMware VirtualCenter Server service may start and stop immediately.
To resolve this issue, we need to manually purge or truncate the vCenter Server database. Details of how to do this and the script to truncate the database is documented in KB article: Purging old data from the database used by vCenter Server (1025914)
This video demonstrates how to update patches on an ESXi 5.x/6.x host using “esxcli software vib” commands. Patches can either be installed or updated on an ESXi host using esxcli vib commands.
Caution: The install method has the possibility of overwriting existing drivers. If you are using third-party ESXi images, VMware recommends using the update method to prevent an unbootable state.
Patches for VMware products can be downloaded from the following location
This video demonstrates how to backup and restore an embedded vCenter Server 6.0 vPostgres database. Backing up your database protects the data stored in your database. Of course, restoring a backup is an essential part of that function.
This follows up on our recent blog & video: How to backup and restore the embedded vCenter Server Appliance 6.0 vPostgres database
Note: This video is only supported for backup and restore of the vPostgres database to the same vCenter Server. Use of image-based backup and restore is the only solution supported for performing a full, secondary appliance restore.
This video demonstrates how to backup and restore an embedded vCenter Server Appliance 6.0 vPostgres database. Backing up your database protects the data stored in your database. Of course, Restoring a backup is an essential part of that function.
Note: This video is only supported for backup and restore of the vPostgres database to the same vCenter Server Appliance. Use of image-based backup and restore is the only solution supported for performing a full, secondary appliance restore.
This video demonstrates how to troubleshoot “SSO log directory full” warnings in vCenter Server Appliance 6.0. This is a known issue affecting vCenter Server Appliance 6.0, and currently, there is no resolution. You see that the /storage/log directory is highly utilized in an Embedded vCenter Server Appliance or Platform Controller Server Appliance 6.0.
To work around this issue, reduce the maximum backup size and the maximum backup index in the log4j.properties file.
Note: In external Platform Service Controller (PSC) environments, log in to the Platform Service Controller instead to make the suggested changes.
This video tells you how to recreate a missing virtual machine disk descriptor, also know as the vmdk file.
Note: VMware recommends to attempt to restore the missing descriptor file from backups if possible. If this is not possible, proceed with recreating the virtual machine disk descriptor file.
Watch the video to see the steps taken to create a virtual machine disk descriptor file:
- Identify the size of the flat file in bytes.
- Create a new blank virtual disk that is the same size as the original. This serves as a baseline example that is modified in later steps.
- Rename the descriptor file (also referred to as a header file) of the newly-created disk to match the name of the original virtual disk.
- Modify the contents of the renamed descriptor file to reference the flat file.
- Remove the leftover temporary flat file of the newly-created disk, as it is not required.
This procedure will not work on virtual disks configured with a Para-virtualized SCSI controller in the virtual machine
This video demonstrates how to install Windows guest operating system using the Easy Install feature in VMware Fusion.
Before creating a virtual machine, you must obtain the operating system and any necessary product keys for installation in that virtual machine. VMware Fusion does not come with any operating systems to install in virtual machines you create.
This method assumes that you are using a physical CD or a disk image (.iso / .cdr /.dmg file). You cannot create a Windows virtual machine by using .exe files downloaded from Microsoft, as those files need to be run on a Windows PC.
This video demonstrates how to troubleshoot Virtual SAN Providers which display the status as disconnected in the vSphere Web Client. This issue occurs if the SMS certificate for vCenter server is expired.
To resolve this issue, expired certificate will be removed and a new certificate will be generated.
This video demonstrates how to troubleshoot Virtual SAN on-disk format upgrade to 3.0, which may fail in small Virtual SAN clusters or ROBO/stretched clusters.
Attempting an on-disk upgrade in certain VSAN configurations may result in failure. Configurations that can cause these errors include:
- The stretched VSAN Cluster consists of two ESXi Hosts and the Witness Node (ROBO configuration)
- Each Host in the Stretched Cluster contains a single VSAN Disk Group
- A Virtual SAN cluster consists of three normal nodes, with one disk group per node
- A Virtual SAN cluster is very full, preventing the “full data migration” disk-group decommission mode
To allow an upgrade to proceed in these configurations, a compromise as to availability must be made. Data accessibility will be maintained, but the redundant copy of the data will be lost and rebuilt during the upgrade process. As a result, data will be exposed to faults and failures such as the loss of a disk on another node may result in data loss. This exposure to additional failure risk is referred to as “reduced redundancy,” and must be manually specified in the Ruby vSphere Console (RVC) to allow the upgrade to proceed. It is not possible to specify reduced redundancy when using the vSphere Web Client to start the upgrade.
Caution: During upgrade, a single point of failure is exposed. Follow all VMware best practices, and your business practices, regarding the backup of important data and virtual machines.