OCVS External Storage Pricing

Assumptions

Sizing

Datastore size TiB = 20,480 GB/GiB (1 TiB = 1,024) Hours per month hrs Keep 730 to match Google and Azure calculators

View options

Performance levelsChoose tier per platformOn: a tier picker on each platform card; prices and figures follow your pick (off = default tier). Performance figuresShow IOPS and throughputOn: a Performance section in the table (rate, max per volume) and expected IOPS/throughput on each card. Additional informationLevel details, ownership, size limitsOn: extra table rows: what the tier means, who operates the storage, min/max datastore size. DiscountsApply % off list priceOn: a % box per platform; table and slide show list, discount and net monthly price.

Comparison

Service notes and links

How the figures work

One datastore = one volume. The tool assumes each datastore is a single volume (or file system) of the size you enter, grown in whole TiB — the normal way OCVS datastores are built. Only if the size is larger than one volume can be (32 TiB for OCI Block Volume) does it use more.
Expected IOPS and throughput come from the provider's published rate for that performance level, up to the maximum per volume. Example: OCI Balanced gives 60 IOPS per GB with a maximum of 25,000 IOPS per volume, so a 20 TiB datastore gets 25,000 IOPS and 480 MB/s — the same figures the OCI cost estimator shows.
Block storage, except on GCVE. The comparison is about block (iSCSI/VMFS) datastores. Google Cloud VMware Engine supports no block datastore at all, so GCVE is compared on what it does offer: storage-only nodes (extra vSAN capacity, priced per node with 1- or 3-year commitments) or NFSv3 from Filestore or Google Cloud NetApp Volumes. Flagged on the card and in the table.
Storage-only nodes are priced per node. The tool works out how many nodes give your usable capacity: raw TB per node, converted to TiB, times the vSAN protection (RAID-1 = 50% usable, RAID-5 = 75%). Check: 3 × ve2-small-so, 3-year, Frankfurt = 3 × $5.180792 × 730 h = $11,345.93/month, as in the Google Cloud calculator.
Regions. Each region list shows only the regions where that VMware service runs. A storage option is offered only where it is supported as a datastore for that service (for AVS + Azure NetApp Files, Microsoft's published list of supported regions). Frankfurt is the default everywhere.
Prices are monthly list prices. 1 TiB = 1,024 GB/GiB, as in each provider's calculator. Hours per month (default 730) only affects the services billed per hour — Filestore, NetApp Volumes and Azure NetApp Files. The Google and Azure calculators always use 730 hours, so leave it at 730 to match them. Check: Filestore Zonal, Iowa, 100 TiB = 102,400 GiB × $0.25 = $25,600/month, the same as the Google Cloud calculator.

For a deeper look at OCI storage performance with OCVS, see Oracle's articles: Performance of OCI Block Volume with OCVS standard shapes · How OCI set new storage performance standards

Before quoting these figures

Indicative only. Public list prices. Tick Apply discounts to enter a negotiated discount per provider; it is taken off that provider's list price, and the savings, callouts and PPT use the discounted prices. Confirm on the provider's own calculator before sharing with a customer.
FSx for ONTAP (EVS) includes its throughput-capacity charge (default 128 MBps). The AWS calculator pre-fills 65% compression and deduplication savings and bills only the remaining 35% of capacity; the tool defaults to 0% so every service is compared on the capacity you provision. Enter 65% and the throughput AWS uses to reproduce its figure — e.g. 900 TiB, 65%, 256 MBps, Single-AZ, Frankfurt = $48,061.44 + $210.43 = $48,271.87.
Not in the price: Filestore custom performance and OCI High Performance Mount Targets are charged separately.
Storage only: no VMware nodes, networking, egress, backup, support or taxes.