An Azure service that runs native VMware workloads on Azure.
What could be done to reduce the cost in this scenario?
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
If an organisation has stretched cluster having approximately 2500 VM's hosted on AVS and its data is replicating in 2 AZ. How we can do a cost optimisation where data for 1000 VM's could be replicated in single availability zone.
An Azure service that runs native VMware workloads on Azure.
What could be done to reduce the cost in this scenario?
AI answer
Assign a vSAN policy with site disaster tolerance set to Preferred or Secondary to the VM namespace and every VMDK; only after all relevant objects are compliant will that VM’s data remain in one site instead of being synchronously mirrored across both availability zones.
For the 1,000 VMs that do not require cross-zone protection:
vSANSiteDisasterTolerance):
Preferred — no site redundancy; keep data on the preferred site, orSecondary — no site redundancy; keep data on the secondary site.vSANFailuresToTolerate): choose the required within-site protection, such as R1FTT1 for RAID-1 protection against one host failure.None/NoneStretch locality for this purpose. The documented stretched-cluster settings specifically provide Preferred and Secondary for retaining data on one site. Dual is the cross-site mirroring option.^1^Set-VMStoragePolicySet-VMStoragePolicy does not alter existing disk-level policies. Using this Run Command without step 2 can therefore leave the VMDKs dual-site mirrored.^1^Preferred or Secondary policy.Dual-Site Mirroring policy.This configuration intentionally removes availability-zone protection for those VMs. A stretched cluster normally uses synchronous vSAN replication so both zones confirm writes; with single-site locality, the affected data has no copy in the other site.^2^
The AVS stretched-cluster 99.99% infrastructure availability commitment requires Dual-Site Mirroring with local SFTT 1. VMs changed to Preferred or Secondary do not meet that dual-site policy requirement.^3^
Classify the 1,000 VMs by recovery objective before changing them:
Dual.Preferred or Secondary only where an AZ outage and recovery from backup or another DR mechanism is acceptable.Changing the storage policy does not directly reduce the AVS bill. AVS stretched clusters are charged by deployed nodes, not by how many VMs use dual-site mirroring; the witness and inter-AZ traffic are not separately charged.^3^
Savings occur only if reduced storage consumption permits host removal while preserving compute, memory, vSAN capacity, and operational headroom. Stretched clusters:
Therefore, model the reclaimable vSAN capacity after policy conversion and confirm that it enables at least one valid two-host scale-in unit; otherwise, the policy change reduces replicated capacity but not the node charge.
References