vSAN -- ESXi Host vSAN Storage is down after moving vSAN Cluster to another vCenter
search cancel

vSAN -- ESXi Host vSAN Storage is down after moving vSAN Cluster to another vCenter

book

Article ID: 399504

calendar_today

Updated On:

Products

VMware vSAN VMware vSAN 7.x VMware vSAN 8.x

Issue/Introduction

After moving vSAN Cluster to a new vCenter one or more of the following issues are being observed:

 

  • New vCenter: vSAN Skyline Health is reporting: vSAN object health: red
Location: vSAN Cluster --> Monitor --> vSAN --> Skyline Health
The details of "vSAN object health" showing many Objects in state "Reduced Availability", while no Resync is going on 
 
 
  • New vCenter: When trying to power on a VM the following error is received:
Module MonitorLoop power on failed. Failed to start the virtual machine. Failed to power on VM. Could not power on virtual machine: Failure.
Failed to create swap file '/vmfs/volumes/vsan:###########/########/######.vswp' : Failure
 
Sample Output:

 

 

  • New vCenter: vSAN Skyline Health is reporting: vSAN Cluster Configuration Consistency: Issue: "Deduplication and Compression is enabled but should be disabled"

Sample Output:

 

Environment

vSAN 7.x
vSAN 8.x

 

Cause

In the new vCenter, the vSAN Configuration is not complete.

 

Resolution

1.) In the new vCenter: Enable "Deduplication and Compression" by hitting "Remediate Inconsistent Configuration" shown in the screenshot above
2.) In the new vCenter: Ensure that the Storage Policies assigned to VMs located on vSAN have the same settings as the Storage Policies used for these VMs in the old vCenter

 

Additional Information