VMware vSphere

 View Only

  • 1.  SME: vSphere Storage Expert, Re-Creating VMDK

    Posted Aug 25, 2019 09:46 PM

    Hi vSAN Gurus,

    I am posting it here since you will be more in-dpeth with vSphere Storage with vSAN!

    I managed to understand that for a VMDP descriptor file when it is a VMDK on a VMFS6 it uses SeSparse and the CID is same as Parent CID for the single VMDK descriptor file [Snapshots case]

    1-) I want someone to correct me and let me understand more

    2-) I want to know how can I recreate a vmdk descriptor if I am fixing a broken snapshot vmdks Chain?

    3-) Another question what does these values mean?

    ddb.longContentID = "5e74802d20df1083c065f15ffffffffe"

    ddb.grain = "8"

    ddb.longContentID = "7d84b45bb175061408e526edfffffffe"



  • 2.  RE: SME: vSphere Storage Expert, Re-Creating VMDK

    Posted Aug 26, 2019 10:27 AM

    Hello any Expert?



  • 3.  RE: SME: vSphere Storage Expert, Re-Creating VMDK



  • 4.  RE: SME: vSphere Storage Expert, Re-Creating VMDK

    Posted Aug 27, 2019 10:07 AM

    That actually wouldn't work the same on vSAN as we point descriptors to Objects not -flat files. You or a mod should consider moving this thread as it doesn't appear to be related to vSAN.

    Bob



  • 5.  RE: SME: vSphere Storage Expert, Re-Creating VMDK

    Posted Aug 27, 2019 09:00 PM

    I DID