The vCenter Server must configure the vSAN Datastore name to a unique name.

A vSAN Datastore name by default is "vsanDatastore". If more than one vSAN cluster is present in vCenter, both datastores will have the same name by default, potentially leading to confusion and manually misplaced workloads.

If no clusters are enabled for vSAN, this is not applicable.

From the vSphere Client, go to Host and Clusters.

Select a vSAN Enabled Cluster >> Datastores.

Review the datastores and identify any datastores with "vSAN" as the datastore type.

or

From a PowerCLI command prompt while connected to the vCenter server, run the following commands:

If($(Get-Cluster | where {$_.VsanEnabled} | Measure).Count -gt 0){ Write-Host "vSAN Enabled Cluster found" Get-Cluster | where {$_.VsanEnabled} | Get-Datastore | where {$_.type -match "vsan"} } else{ Write-Host "vSAN is not enabled, this finding is not applicable." }

If vSAN is enabled and a datastore is named "vsanDatastore", this is a finding.

From the vSphere Client, go to Host and Clusters.

Select a vSAN Enabled Cluster >> Datastores.

Right-click on the datastore named "vsanDatastore" and select "Rename".

Rename the datastore based on site-specific naming standards.

Click "OK".

or

From a PowerCLI command prompt while connected to the vCenter server, run the following commands:

If($(Get-Cluster | where {$_.VsanEnabled} | Measure).Count -gt 0){ Write-Host "vSAN Enabled Cluster found" $Clusters = Get-Cluster | where {$_.VsanEnabled} Foreach ($clus in $clusters){ $clus | Get-Datastore | where {$_.type -match "vsan"} | Set-Datastore -Name $(($clus.name) + "_vSAN_Datastore") } } else{ Write-Host "vSAN is not enabled, this finding is not applicable." }