RVTools Analyzer v2.0
RVTools Analyzer
System Architect — Infrastructure Analysis & Sizing Tool  |  RVTools Export Intelligence Platform
i
RVTools Export Requirements
✓
vInfo (Required)
VM inventory — name, cluster, power state, OS, tools status, folder
✓
vPartition (Required for storage)
Consumed MB per VM — used to calculate raw protection footprint (Step 3)
○
vDisk (Optional)
Disk types — enables detection of RDM, RAW, and independent disk modes
○
vHost / vCluster (Optional)
Enriches cluster-level summaries and host context
Without vPartition, storage calculations will show 0 TB. Without vDisk, RAW/RDM detection is limited to vInfo disk mode column only.
Customer / Prospect
for:
For SmartSizer Export
Annual Growth %:
01 — Data Ingestion
Drop RVTools Export Here
Upload your RVTools Excel export, CSV file, or ZIP of per-tab CSVs to begin analysis
.xlsx .xls .csv .zip
0%
Analysing Environment…
Initializing analysis engine...
0%
Loading sheets
Building storage map
Scanning disk types
Processing VMs
Classifying workloads
Aggregating clusters
Flagging disk issues
Footprint calc
Top 20 VMs
Complete
03 — Analysis Results
Workload Distribution
Storage by Workload (TB)
Workload Type Detection Signals VM Count Total Storage (TB) Avg / VM (GB) % of Total
⚠ Classification is pattern-based from VM name, OS type, folder, and cluster. All assignments must be verified with the customer and tuned accordingly.
Cluster Workload Type VM Count Storage (TB) % of Total
⚠
VMs Without VMware Tools — Snapshot Consistency Risk

These VMs cannot use application-aware protection. Storage for these VMs has been estimated using the assumed overhead % below and added to the total protected footprint.

% of their provisioned size
— or —
(overrides % if filled)
VM NameClusterWorkloadPower StateTools StatusConsumed (TB)Risk
RankVM NameClusterWorkloadPowerConsumed (TB)VMware ToolsDisk Flags
SmartSizer export assumptions — review before sending to SmartSizer:
• Every workload is sized as Workload Type IBA / Subtype VMware (image-based). RVTools tells us a VM runs SQL/Oracle/SAP etc., not how it will actually be protected — if any of these need native DB-agent ("Application Dump") sizing instead, change that row's Workload Type in SmartSizer directly.
• Cluster rows use the SmartSizer template's own example defaults (Resiliency Model 1d:1n - EC 2:1, Software Version <=7.3, Node Preference Auto, Duration 24, Buffer 20%) — Location is left blank since RVTools doesn't report it.
• Daily Change Rate per workload comes from the WST tab's per-type values (adjust there before exporting if needed). Full/Incr Data Reduction Rate are left blank, matching the template's own example, so SmartSizer applies its own defaults rather than us inventing a combined number.
• A workload with VMs on more than one Policy Assignment is split into one row per policy (plus one "unassigned" row if some VMs have none) — same cluster and workload type, different Policy Name / Custom Policy.
• The Replication sheet is left empty — RVTools has no replication/DR topology data to populate it from.
• Only clusters/workload rows 7–9 (first 3) are guaranteed to show the in-Excel Cluster Name dropdown on the Workloads sheet beyond row 10, per a hardcoded limit in the vendor template itself; every row's data value is still correct and valid regardless.