Click here to browse files, or drag & drop
Load all RVTools CSV exports Β· All processing is local in your browser
Active VMs
β
load files to begin
ESXi Hosts
β
physical servers
Total vCPUs
β
β physical cores
Physical RAM
β
host total
vRAM Allocated
β
active VMs
Provisioned Storage
β
all VMs
vCPU : Core Ratio
β
vCPUs per physical core
vRAM : pRAM Ratio
β
memory overcommit
VM Density
β
VMs per ESXi host
VM Power State
OS Distribution
π₯Top 10 Heavy Hitters (vCPU)
| VM Name | vCPU | vRAM (GiB) | Prov. (GiB) | Cluster | Host | Power |
|---|---|---|---|---|---|---|
| Load files to see data | ||||||
π²Cluster Summary
| Cluster | VMs On | VMs Off | vCPUs | vRAM (GiB) | pCores | vCPU/Core | vRAM/pRAM |
|---|---|---|---|---|---|---|---|
| Load files to see data | |||||||
π₯ESXi Host Inventory
| Host | Datacenter | Cluster | Sockets | Cores | RAM (GiB) | vCPUs | vRAM (GiB) | VMs | ESXi Version |
|---|---|---|---|---|---|---|---|---|---|
| Load files to see data | |||||||||
| VM Name | Power | vCPU | vRAM (GiB) | Prov. (GiB) | Cluster | Host | OS | HW Ver |
|---|---|---|---|---|---|---|---|---|
| Load files to see data | ||||||||
Allocation-based recommendations (no live utilisation data). Rules: >8 vCPU = NUMA boundary risk Β· >16 vCPU = HIGH Β· Powered-off VMs waste resources Β· Cluster vCPU/Core >8:1 or vRAM/pRAM >1:1 = overcommit risk.
β
High vCPU VMs (>8)
β
Powered-Off VMs
β
Overcommit Clusters
β
vRAM in Off VMs
β οΈCluster Overcommit Risk
| Cluster | vCPU/Core | CPU Risk | vRAM/pRAM | Mem Risk | VMs On | Recommendation |
|---|---|---|---|---|---|---|
| Load files to see data | ||||||
π΄VMs with Excessive vCPUs (>8)
| VM Name | vCPU | vRAM (GiB) | Cluster | Power | Suggested | Priority | Reason |
|---|---|---|---|---|---|---|---|
| Load files to see data | |||||||
π€Powered-Off VMs β Wasted Resources
| VM Name | vCPU | vRAM (GiB) | Prov. (GiB) | Cluster | OS | Action |
|---|---|---|---|---|---|---|
| Load files to see data | ||||||
βοΈRight-Sizing Candidates
| VM Name | Current vCPU | Suggested | Current vRAM | Suggested | OS | Priority | Notes |
|---|---|---|---|---|---|---|---|
| Load files to see data | |||||||
Total Snapshots
β
all VMs
Critical (>30 days)
β
overdue deletion
Large (>50 GiB)
β
storage risk
Total Snap Storage
β
GiB consumed
πΈSnapshot Inventory
| VM Name | Snapshot Name | Date | Age (days) | Size (GiB) | Power | Status |
|---|---|---|---|---|---|---|
| Load tabvSnapshot.csv to see data | ||||||
πΎTop 50 VMs by Provisioned Storage
| VM Name | Prov. (GiB) | In Use (GiB) | Cluster | Host | Power |
|---|---|---|---|---|---|
| Load files to see data | |||||
π
OS End-of-Life Status
| OS Family | VM Count | EoS Date | Status | Action Required |
|---|---|---|---|---|
| Load files to see data | ||||
Total Datastores
β
all types
Critical (<15% Free)
β
immediate action needed
Warning (15β25%)
β
monitor closely
Total Capacity
β
free available
ποΈDatastore Capacity
| Name | Type | Capacity (GiB) | Free (GiB) | Free % | Used % | VMs | Status |
|---|---|---|---|---|---|---|---|
| Load tabvDatastore.csv to see data | |||||||
VM Network Adapter Check: E1000 / E1000e / PCNet32 adapters have significantly higher CPU overhead and lower throughput than VMXNET3. Migrating to VMXNET3 reduces vCPU cycles and improves network performance β requires VMware Tools installed.
Total vNICs
β
all VM adapters
VMXNET3
β
recommended
Legacy Adapters
β
E1000 / E1000e / PCNet32
VMs Affected
β
need migration
β οΈVMs with Legacy Network Adapters
| VM Name | NIC Label | Adapter Type | Network | Connected | Power | Action |
|---|---|---|---|---|---|---|
| Load tabvNetwork.csv to see data | ||||||
β
All VM Adapters Summary
| VM Name | NIC Label | Adapter | Network | Connected | Power |
|---|---|---|---|---|---|
| Load tabvNetwork.csv to see data | |||||
vHealth Alerts are automatically detected issues from your vCenter β zombie VMDK files, performance tips, misconfigured VMs, and more. These are directly actionable items found by RVTools analysis.
Total Alerts
β
all categories
Zombie VMDKs
β
orphaned disk files
Zombie VMX/Other
β
orphaned VM configs
Datastores Affected
β
contain zombie files
Perf Tips
β
optimisation hints
ποΈZombie Files β By Datastore
Zombie files are orphaned VMDKs and VM config files with no owning VM in vCenter inventory. RVTools detects them by path but cannot report individual file sizes because they are not attached to any VM. Sizes require manual inspection via the vCenter Datastore Browser or
du from an ESXi shell. The datastore free space shown below indicates the available headroom on each affected datastore.
| Datastore | Zombie Files | VMDKs | Other Files | DS Capacity (GiB) | DS Free (GiB) | DS Free % | DS Status | Urgency to Clean |
|---|---|---|---|---|---|---|---|---|
| Load tabvHealth.csv + tabvDatastore.csv | ||||||||
πZombie Files β Full List
| File Path | Type | Datastore | DS Free % | Message |
|---|---|---|---|---|
| Load tabvHealth.csv to see zombie files | ||||
π₯All Other vHealth Alerts
| Object / VM | Type | Severity | Message |
|---|---|---|---|
| Load tabvHealth.csv to see data | |||
CPU > 70%
β
hosts under CPU pressure
Memory > 80%
β
hosts under mem pressure
Ballooning Active
β
memory reclamation active
ESXi 6.x / 7.0
β
outdated ESXi version
πHost Performance Overview
| Host | Cluster | CPU % | Mem % | Ballooned MiB | Swapped MiB | VMs | ESXi Version | Status |
|---|---|---|---|---|---|---|---|---|
| Load tabvHost.csv to see data | ||||||||
π’ESXi Version Compliance
| ESXi Version | Host Count | Support Status | Recommendation |
|---|---|---|---|
| Load tabvHost.csv to see data | |||
Tools OK
β
up to date
Tools Outdated
β
needs upgrade
Not Running
β
service stopped
Not Installed
β
no tools at all
Why VMware Tools matter: Required for graceful shutdown, quiesced snapshots, VMXNET3 drivers, guest heartbeat monitoring, and accurate OS/IP reporting. VMs without Tools running are effectively unmanaged from vCenter's perspective.
β οΈVMs Needing Tools Attention
| VM Name | Power | Tools Status | Tools Version | HW Version | OS | Action |
|---|---|---|---|---|---|---|
| Load tabvTools.csv to see data | ||||||
πCBT (Changed Block Tracking) Status
CBT is critical for backup efficiency. Without CBT enabled, backup jobs must scan the entire virtual disk on every run β dramatically increasing backup windows and storage I/O load.
| VM Name | Power | CBT | Cluster | Host | Action |
|---|---|---|---|---|---|
| Load tabvInfo.csv to see data | |||||
Load RVTools CSV files to generate Executive Summary
Good (80β100)
β
well protected
Fair (60β79)
β
needs attention
Poor (40β59)
β
high backup risk
Critical (<40)
β
no backup safety net
Backup Readiness Score (0β100) per powered-on VM. Deductions: CBT disabled β30 Β· Tools not installed β25 Β· Tools not running β20 Β· Snapshot >90 days β20 Β· Snapshot >30 days β10 Β· Legacy NIC β5 Β· Tools outdated β5.
π‘οΈVM Backup Readiness
| VM Name | Score | Rating | CBT | Tools | Snapshot | NIC | Issues |
|---|---|---|---|---|---|---|---|
| Load files to see data | |||||||
Good (80β100)
β
well protected
Fair (60β79)
β
needs attention
Poor (40β59)
β
high backup risk
Critical (<40)
β
no backup safety net
Backup Readiness Score (0β100) per powered-on VM. Deductions: CBT disabled β30 Β· Tools not installed β25 Β· Tools not running β20 Β· Snapshot >90 days β20 Β· Snapshot >30 days β10 Β· Legacy NIC β5 Β· Tools outdated β5.
π‘οΈVM Backup Readiness
| VM Name | Score | Rating | CBT | Tools | Snapshot | NIC | Issues |
|---|---|---|---|---|---|---|---|
| Load files to see data | |||||||
VMs on Critical DS
β
immediate migration risk
VMs on Warning DS
β
monitor closely
Multi-DS VMs
β
disks span datastores
Total Mapped
β
VMs with disk data
VM β Datastore Mapping β Shows exactly which VMs are on which datastores. VMs on critical datastores (<15% free) are flagged β these are at risk if the datastore fills. Load tabvDisk.csv + tabvDatastore.csv for full mapping.
π΄VMs on Critical Datastores (<15% Free)
| VM Name | Datastore | DS Free % | DS Free (GiB) | DS Capacity (GiB) | VM Power | VM vCPU | VM vRAM | Action |
|---|---|---|---|---|---|---|---|---|
| Load tabvDisk.csv + tabvDatastore.csv | ||||||||
πΊοΈFull Datastore Inventory with VM List
| Datastore | Free % | Free (GiB) | Capacity (GiB) | VM Count | Status | VMs (top 5) |
|---|---|---|---|---|---|---|
| Load tabvDisk.csv + tabvDatastore.csv | ||||||
Paravirtual SCSI
β
recommended controller
LSI Logic (Legacy)
β
lower I/O performance
Thick Provisioned
β
disks wasting space
Thick Storage
β
GiB over-reserved
Disk Controller: VMware Paravirtual SCSI delivers significantly higher throughput and lower CPU overhead than LSI Logic. Migrating requires a VM reboot and VMware Tools installed. Thin provisioning allows datastores to be better utilised β thick disks reserve full capacity immediately regardless of actual use.
Controller Type Distribution
Thin vs Thick by Storage (GiB)
β οΈVMs with Legacy LSI Logic Controllers
| VM Name | Disk | Controller | Capacity (GiB) | Thin | Power | Cluster | Action |
|---|---|---|---|---|---|---|---|
| Load tabvDisk.csv to see data | |||||||
πΎThick Provisioned Disks
| VM Name | Disk | Capacity (GiB) | Controller | Datastore | Power | Action |
|---|---|---|---|---|---|---|
| Load tabvDisk.csv to see data | ||||||
Avg VM Growth/Month
β
last 12 months
RAM Runway (Cluster 1)
β
months until full
RAM Runway (Standalone)
β
months until full
Critical Datastores
β
fill in <6 months
Capacity projections are based on current allocation trends. VM growth rate uses your actual creation dates from tabvInfo.csv. Datastore fill rate assumes 2% consumed per month. Cluster limits use 8:1 vCPU/core and 1:1 vRAM/pRAM safe thresholds.
VM Growth Timeline (Monthly Creations)
Cluster Headroom β VMs Remaining
πCluster Capacity Runway
| Cluster | Current VMs | vCPU Used | CPU Headroom (VMs) | CPU Runway | RAM Used (GiB) | RAM Headroom (VMs) | RAM Runway | Bottleneck |
|---|---|---|---|---|---|---|---|---|
| Load tabvInfo.csv + tabvHost.csv | ||||||||
ποΈDatastore Fill Rate Projections
| Datastore | Capacity (GiB) | Free (GiB) | Free % | Growth Rate | Est. Full | VMs | Risk |
|---|---|---|---|---|---|---|---|
| Load tabvDatastore.csv | |||||||
What-If Scenario Simulator β Drag the sliders to model adding new VMs and instantly see how each cluster responds. The dashboard updates in real time so you can answer "can we take on this new project?" before committing resources.
Add VMs to Standalone Hosts
0
VMs
Avg profile per new VM:
vCPU per VM
RAM GiB per VM
Storage GiB per VM
Add VMs to Cluster 1
0
VMs
Avg profile per new VM:
vCPU per VM
RAM GiB per VM
Storage GiB per VM
Host Failure Impact Analysis β Shows what happens to each cluster if one (N-1) or two (N-2) hosts fail simultaneously. vSphere HA will try to restart VMs on surviving hosts β this analysis shows if surviving hosts have enough headroom to absorb the load.
Load tabvHost.csv + tabvInfo.csv to see HA analysis
Reclamation Opportunity Calculator β Quantifies the exact CPU, RAM and Storage you can recover by acting on existing findings. Use these numbers to justify remediation work to management.
Load RVTools files to calculate reclamation opportunities
Thin Provisioning Overcommit Risk β Thin provisioning lets VMs reserve more space than physically exists, assuming not all VMs use their full allocation simultaneously. When actual writes exceed physical capacity, the datastore fills instantly causing VM crashes. The global overcommit ratio across your environment is β.
Total Capacity
β
physical datastore space
Total Provisioned
β
committed to VMs
Actual In Use
β
real bytes written
Phantom Space
β
promised but not physical
Datastores by Overcommit Ratio (top 15)
Capacity vs Provisioned vs In-Use (TiB)
πDatastore Overcommit Detail
| Datastore | Capacity (GiB) | Provisioned (GiB) | In Use (GiB) | Free (GiB) | Overcommit Ratio | Write Buffer | Risk |
|---|---|---|---|---|---|---|---|
| Load tabvDatastore.csv to see data | |||||||
VM Placement Advisor β Enter your new VM specs below. The advisor scores every ESXi host in your environment and recommends the best placement based on available RAM headroom, CPU ratio, current load, VM density, and ESXi version. Hosts that cannot accommodate the VM are automatically filtered out.
βοΈNew VM Specifications
VM Name
vCPU Count
RAM (GiB)
Storage (GiB)
Workload Type
Cluster Preference
ESXi Version & Compliance Tracker β Tracks ESXi version, uptime, certificate expiry, NTP status, and patch currency across all 34 hosts. Hosts on ESXi 6.x are end-of-life and no longer receive security patches.
ESXi 8.x Hosts
β
current generation
ESXi 7.x Hosts
β
approaching EOL
ESXi 6.x Hosts
β
end-of-life now
Long Uptime (>365d)
β
needs maintenance reboot
ESXi Version Distribution
Host Uptime (days)
π₯οΈAll Hosts β Compliance Detail
| Host | ESXi Version | Build | Generation | Uptime | Cert Expiry | Cert Status | NTP | Model | Cluster | VMs |
|---|---|---|---|---|---|---|---|---|---|---|
| Load tabvHost.csv to see data | ||||||||||
VM Configuration Compliance Audit β Checks every powered-on VM against 6 configuration rules. Each VM receives a compliance score. Filter by rule to see exactly which VMs are failing and why.
β
Overall Compliance
β
VM Compliance Detail
| VM Name | Score | Tools | CBT | NIC | Snapshot | HW Version | Disk | Cluster | Issues |
|---|---|---|---|---|---|---|---|---|---|
| Load RVTools files to see compliance data | |||||||||
Datastore Balance Advisor β Analyses free space across all datastores and recommends specific VM storage vMotion operations to bring critical datastores above safe thresholds. Target fill level is 62% (current average across your estate).
Critical (<15% free)
β
immediate action needed
Warning (15β25%)
β
monitor closely
Healthy (>25%)
β
sufficient headroom
Moves Recommended
β
vMotion operations
Datastore Fill Levels (%)
Free Space Distribution (GiB)
πRecommended Storage vMotion Operations
| Priority | VM to Move | Source DS | Source Free% | VM Size (GiB) | Target DS | Target Free% | Target Free After | Action |
|---|---|---|---|---|---|---|---|---|
| Load tabvDisk.csv + tabvDatastore.csv | ||||||||
ποΈDatastore Inventory
| Datastore | Capacity (GiB) | Used (GiB) | Free (GiB) | Free % | VMs | Status |
|---|---|---|---|---|---|---|
| Load tabvDatastore.csv | ||||||
VM Performance Advisor β Every powered-on VM is analysed across 6 performance rules. Click any category card to filter the VM list instantly. Fix these issues to reduce CPU overhead, improve I/O throughput, and free up host resources.
β‘VM Performance Analysis
| VM Name | Issues | vCPU | RAM (GiB) | High vCPU | Legacy NIC | HW Version | Tools | Disk | Snapshot | Cluster | Top Fix |
|---|---|---|---|---|---|---|---|---|---|---|---|
| Load tabvInfo.csv to see data | |||||||||||