Transitioning a vSAN OSA cluster to a vSAN ESA cluster
search cancel

Transitioning a vSAN OSA cluster to a vSAN ESA cluster

book

Article ID: 432894

calendar_today

Updated On:

Products

VMware vSAN VMware vSphere ESXi

Issue/Introduction

This article describes the process for transitioning a VMware vSAN cluster running Original Storage Architecture (OSA) to Express Storage Architecture (ESA).

Direct or in-place upgrade/migration from vSAN OSA to vSAN ESA is not supported because OSA and ESA utilize fundamentally different data paths, storage mechanisms, and on-disk formats. OSA uses disk groups composed of dedicated cache and capacity devices, whereas ESA utilizes a unified storage pool architecture with high-performance NVMe devices.

Environment

  • VMware vSAN 8.0 (all builds)
  • VMware vSAN 9.0, 9.1

Cause

Direct conversion or in-place upgrade from vSAN OSA to vSAN ESA is not natively supported. Transitioning to ESA requires constructing a new ESA-enabled cluster or performing a destructive re-initialization of host storage devices.

Resolution

Since an in-place migration is not possible, choose one of the following two supported transition methods based on available hardware resources.


Method 1:  Side-by-Side Migration (New Hardware Available)

This method is recommended when new ESA-compatible hardware is available to build a parallel cluster.

  1. Deploy New Cluster: Build and configure a new vSAN ESA cluster using certified Express Storage Architecture hardware.

  2. Cross-Cluster Migration: Perform a Storage vMotion to migrate virtual machines from the source vSAN OSA cluster to the target vSAN ESA cluster.

  3. Validation & Decommission: Verify workload functionality on the new vSAN ESA cluster, then decommission the legacy OSA cluster.


Method 2:  Host Reuse & Destructive Re-initialization (Re-using Existing Hosts)

If existing hosts are being repurposed for the vSAN ESA cluster, all storage devices must be cleared of previous partition metadata and placed into a Clean or Unmounted state before ESA can claim them into the Storage Pool.


Note:  Re-using hosts requires wiping all existing disk groups and partitions. Ensure all Virtual Machines are evacuated off the host prior to deleting disk groups. Any remaining data on the host's storage devices will be permanently lost.

  1. Evacuate Host Virtual Machines: Migrate all Virtual Machines off the host to another cluster or datastore via vMotion/Storage vMotion.

  2. Enter Maintenance Mode: Place the target host into Maintenance Mode selecting the No Data Migration option (since all workloads have already been evacuated).

  3. Delete OSA Disk Groups: Navigate to the host's storage configuration and delete all existing vSAN OSA Disk Groups.

  4. Clean Disks: Ensure all local storage devices are cleared of partitions and reflect a "Clean" state.

  5. Reassign Host: Move the host out of the OSA cluster inventory to the vCenter Data Center level, then move it into the ESA-enabled cluster.

  6. Claim Storage Pool Disks: Claim the clean storage devices into the vSAN ESA Storage Pool format.

  7. Exit Maintenance Mode: Verify the storage pool status and exit Maintenance Mode.

Additional Information

For more information refer,

vSAN Migration Guide

Migration scenarios

vSAN OSA (Original Storage Architecture) クラスタを vSAN ESA (Express Storage Architecture) クラスタに変換する方法