1 Reply Latest reply on Jul 12, 2019 5:05 AM by TheBobkin

    vSan Disk Polices

    seamusobr1 Novice

      I wonder if somebody can help

       

      I have recently been going through a list of our disk polices in vSan

      I have noticed a lot of objects listed under other with guid names

      Can anyone explain what these are and if there is an effective way to remove them

      I have listed below an example of what I mean

       

      Name                                                                                                                                                                   vsan object health                                                                       Compliance status   

          

      8ac2065d-5a1e-cdd5-0f72-246e96d7d06eHealthyOut of Date
      2e3e285d-8451-43cb-091b-246e96d7baeaHealthyOut of Date
      17baac5b-d870-84ca-e428-246e96d7d48cHealthyOut of Date
      43c4065d-147c-3385-e2df-246e96d7d48cHealthyOut of Date
      c502d85b-a033-c892-dc88-246e96d7d008HealthyOut of Date
        • 1. Re: vSan Disk Polices
          TheBobkin Virtuoso
          vExpertVMware Employees

          Hello Seamus,

           

          Before considering removing data objects, one should always identify them and confirm they are not needed.

          This can be achieved a number of ways:

          SSH to host:

          # esxcli vsan debug object list -u <objectUUID>

          # /usr/lib/vmware/osfs/bin/objtool getAttr -u <objectUUID>

          RVC:

          > vsan.object_info <objectUUID> <pathToCluster>

           

          If the namespace and/or descriptors are present normally in Datastore Browser via the clients then removal of Objects from here should be possible.

           

          Bob