The last component you may need to troubleshoot is the VMs. Typical issues are related to power-on, delete, misconfiguration, and resources.

To list the files belonging to a specific VM, use the ls -lah command:

[root@esxi-prod-1:/vmfs/volumes/5c601d26-2c3ab9f8-e0ab-005056a95cde/VCSA-lab.learnvmware.local] ls -lah
total 36349248
drwxr-xr-x 1 root root 88.0K Feb 16 15:50 .
drwxr-xr-t 1 root root 76.0K Feb 14 12:07 ..
-rw-r--r-- 1 root root 92 Feb 16 15:20 VCSA-lab.learnvmware.local-1af96f43.hlog
-rw------- 1 root root 10.0G Feb 11 20:35 VCSA-lab.learnvmware.local-1af96f43.vswp
-rw------- 1 root root 12.0G Feb 16 16:16 VCSA-lab.learnvmware.local-flat.vmdk
-rw------- 1 root root 8.5K Feb 14 15:22 VCSA-lab.learnvmware.local.nvram
-rw------- 1 root root 546 Feb 16 15:20 VCSA-lab.learnvmware.local.vmdk
-rw-r--r-- 1 root root 0 Feb 10 13:48 VCSA-lab.learnvmware.local.vmsd
-rwxr-xr-x 1 root root 4.1K Feb 16 15:20 VCSA-lab.learnvmware.local.vmx
-rw------- 1 root root 0 Feb 16 15:20 VCSA-lab.learnvmware.local.vmx.lck
-rwxr-xr-x 1 root root 4.1K Feb 16 15:20 VCSA-lab.learnvmware.local.vmx~
lab.learnvmware.local_8-flat.vmdk
-rw------- 1 root root 546 Feb 11 20:13 VCSA-lab.learnvmware.local_8.vmdk
-rw------- 1 root root 10.0G Feb 11 20:14 VCSA-lab.learnvmware.local_9-flat.vmdk
-rw------- 1 root root 548 Feb 11 20:13 VCSA-lab.learnvmware.local_9.vmdk
-rw-r--r-- 1 root root 222.3K Feb 16 07:20 vmware-185.log
-rw-r--r-- 1 root root 223.8K Feb 16 08:00 vmware-186.log
-rw-r--r-- 1 root root 222.3K Feb 16 08:50 vmware-187.log
-rw-r--r-- 1 root root 228.4K Feb 16 11:15 vmware-188.log
-rw-r--r-- 1 root root 228.2K Feb 16 13:50 vmware-189.log
-rw-r--r-- 1 root root 226.0K Feb 16 15:20 vmware-190.log
-rw-r--r-- 1 root root 183.7K Feb 16 16:09 vmware.log
-rw------- 1 root root 110.0M Feb 16 15:19 vmx-VCSA-lab.learnvmware.local-452554563-1.vswp

During the TRBL process, vmware.log is the virtual machine's log file, which helps you to understand the problem better. In this log, you will see all the details about the problem. The name of the log file, vmware.log, is the same for each VM.

Many problems are due to resources, resource pools, and vApp, thus you should be very careful. If it is not a requirement, don't use reservations or limits for VMs.

Although TRBL can fix most problems, there are situations where restoring a VM from the backup is the only possible solution. Backup is an essential part of vSphere management.