Skip to main content

VSAN VM Storage Policy failed to retrieve data from the server

 

Last week I got into an issue in my lab environment where some of my VM's under the vSAN 7.0 cluster were unable to migrate from one ESXi host to another ESXi host.

During vMotion the VM from one host to another host,  I was getting an error that the storage profile missing.

Credit: yellow-bricks.com


On validating the VM storage profile from vCenter which is on 7.0 it's identified that none of the VM storage policies was visible there and flashing error " Failed to retrieve data from the server".

vCenter Storage providers were also showing blank as it looks not in sync.

Fig-1
Further, investigating through with the vCenter logs, I identified the below error:



As per the logs, it's showing Failed to register vSAN VP services.

vSAN health services are up and running on the vCenter Server, but found the service log file had a significant size.

--rw-r--r-- l.   1 vsan-health users 8.3G Oct 13 10:14 vmware-vsa-health-service.log

As the vSAN-health logs were occupying a significant amount of space of 8.3 GB on the partition and due to unavailability of space health services were unable to write new logging into /var/log/vmware/vsan-health partition.

To troubleshoot this issue, the below steps were taken into action.

1) Stopped vSAN health services on the vCenter Server.

2) Moved the vSAN health services logs file to other partitions for later reference or you can delete if you don't feel it's not useful for you.

3) Start vSAN health services.  >> Validated the service.log file has been recreated successfully.

4) Restarted SPS services on the vCenter Server.


After applying the above steps, all Storage providers were available again in vCenter Server.

After this, all VM storage profiles were visible as vSAN and VM level also able to successfully managed to vMotion VM from one host to another host.



Thanks for reading.. and keep sharing ...








Comments

Popular posts from this blog

Changing the FQDN of the vCenter appliance (VCSA)

This article states how to change the system name or the FQDN of the vCenter appliance 6.x You may not find any way to change the FQDN from the vCenter GUI either from VAMI page of from webclient as the option to change the hostname always be greyed out. Now the option left is from the command line of VCSA appliance. Below steps will make it possible to change the FQDN of the VCSA from the command line. Access the VCSA from console or from Putty session. Login with root permission Use above command in the command prompt of VCSA : /opt/vmware/share/vami/vami_config_net Opt for option 3 (Hostname) Change the hostname to new name Reboot the VCSA appliance.   After reboot you will be successfully manage to change the FQDN of the VCSA . Note: Above step is unsupported by VMware and may impact your SSL certificate and face problem while logging to vSphere Web Client. If you are using self-signed certificate, you can regenerate the certificate with the

VM Creation Date & Time from Powercli

Most of the times we have several requirement when we talk about IT environment like designing , deployment , compliance check or for Security auditing the environment. Somewhere during security auditing we require to provide several information to security team to get successful audit. One of them is the compliance of Virtual machine auditing of creation date and time. Here into this post we will explore how to get the creation date and time of virtual machine hosted into the vCenter or ESXi. To get the details we will use VMware Powercli to extract the details. By default there is no function added into Powercli to get such details, so here we will add a function of vm creation date. Below is the function which needed to be copy and paste into the Powercli. ======================================================================= function  Get-VMCreationTime  {     $vms  =  get-vm     $vmevts  = @()     $vmevt  =  new-object  PSObject     for

Unable to poweron the VM. (Failed to lock the file)

I have encountered may issues like where after some upgrade or migration we were unable to power on the VM. Figure 1 An error was received from the ESX host while powering on VM HSSVSQL01. Failed to start the virtual machine. Cannot open the disk '/vmfs/volumes/578d835c-18b2c97a-9b0d-0025b5f13920/SAMPLE1_cloud/000000.vmdk' or one of the snapshot disks it depends on. Failed to lock the file In above Figure:1, where while powering on the VM, its prompt for an error. Well, there are several reason for where the VM unable to poweron and you can find many article on this. Here in this article we will discuss to resolve this issue. Please use below step to resolve the disk lock issue  C hecked that VM is running on snapshot if its getting error " VM Consolidation required". Checked the snapshot manager if its showing any snapshot. If yes, try to delete the  snapshot. Verified the same from Esxi cl