Steps to decommission the vSAN datastore.
search cancel

Steps to decommission the vSAN datastore.

book

Article ID: 392097

calendar_today

Updated On:

Products

VMware vSAN

Issue/Introduction

This KB provides steps to decommission the vSAN datastore from the vSAN cluster.

Environment

vSAN 7.x 8.x

Resolution

Verify the vSAN datastore has nothing residing on it.

  • Make sure all VMs are migrated or deleted as required.
    • To perform Storage vMotion of a VM from vSAN to SAN storage, right-click the VM in the vSphere Client, select "Migrate," choose "Change storage only," select the SAN datastore as the destination, and follow the wizard to complete the migration.
  • Place the cluster into retreat mode to remove running vCLS VMs
  • Use the following CLI commands to see if any vmdks remain in the vSAN datastore and if any data components using space on the ESXI host.
    • List out the vmdks in the vSAN cluster  (run from any vSAN host in the cluster)
esxcli vsan debug vmdk list
    • Get the component details, total and used space information (run on each host in the cluster)
esxcli vsan debug limit get
    • The vSAN performance object data is expected to be present and can be ignored

Remove the vSAN disk groups

Note that vSAN Skyline Health service alarms, and other vSAN related alarms in vCenter will be present during the process. As all data residing on vSAN is confirmed to be removed these can be ignored.

If running workload remains in the cluster on other storage:

  • Put one host in maintenance mode using the "No data migration" option.
  • Delete the disk group(s) for the host in maintenance mode using the "Disk Management" section under the cluster -> Configure -> vSAN.
  • Take the host out of maintenance mode
  • Repeat the process with each host until all vSAN disk groups are removed

If no workload is running on the cluster:

Remove vSAN Networking

  • On each host select the vmkernel port with the vSAN service enabled under Hostname -> Configure -> Networking -> VMkernel adapters
  • Select the three dot menu to the left of the device name (vmk2, vmk3, etc)
  • Select the edit option
  • Uncheck the vSAN check box
  • Click OK
  • Ensure the process is performed on all hosts in the cluster

Disable vSAN Service on the cluster

  • Select the cluster intended to have vSAN disabled
  • Validate vSphere HA is disabled on the cluster via Configure > Services > vSphere Availability, if not then temporarily disable it (and re-enable it after disabling vSAN) via Configure > Services > vSphere Availability > Edit > slider to off > OK
  • Navigate to the cluster -> Configure -> vSAN -> Services
  • Click the "Turn off vSAN" button in the upper right corner
  • Click OK.

Validate vSAN disk groups have been removed

  • Using the UI:
    • Select vSAN host in the vCenter UI
    • Navigate to Configure -> Storage -> Storage Devices
    • Select a disk using the checkbox to the left of it
    • In the detail panel below select the "Partition Details" tab
    • Verify there are no vSAN partitions (labeled "vSAN metadata" or "vSAN File System"
    • Repeat for all disks on all hosts in the cluster
  • Using the CLI
    • Open ssh to a host in the cluster
    • run "ls /dev/disks/"
    • Verify no vSAN partitions remain (disks used for vSAN have two partitions and show similar to the following) Do not remove partitions without verifying the disk has vSAN partitions on it.

naa.#################
naa.#################:1
naa.#################:2

    • Repeat on all hosts in the cluster

If the cluster will remain in use with other storage enable vCLS

Additional Information

Powered by Wolken Software