• State Verified Answer
  • +3 person also asked this people also asked this
  • Locked Locked
  • Replies 16 replies
  • Answers 2 answers
  • Subscribers 21 subscribers
  • Views 20217 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

ESXi 6.7 Compatibility for vRanger

leclaipa
over 6 years ago

Hey Quest!

 

How soon (or not) should we expect ESXi 6.7 compatibility with vRanger?   Do you guys have an ETA on when to expect a formal announcement? 

 

Thanks!

Parents
  • 0 over 5 years ago

    Any update on the time line for 6.7 support?

  • Anonymous
    +1 Anonymous over 5 years ago in reply to adrian.alba

    Hello Adrian,

    We are expecting to release a new vRanger version by the end of July that will support ESXi 7.6.

  • Anonymous
    0 Anonymous over 5 years ago in reply to Anonymous

    Well, no matter it will not meet Your 90 day SLA for support of new ESXi versions, but will support Even ESXi 7.6?

  • 0 over 5 years ago in reply to Anonymous

    Hello, we will support ESXi 6.7. The VMware 6.7 release came late April. As Rob mentioned above, the release is set to be by the end of July. Please remember that the developer version of the VDDK 6.7 is not the same as the general availability version, so additional testing and fixing is required. 

  • Anonymous
    0 Anonymous over 5 years ago in reply to Anonymous

    July 31st and old version is still out there.  90 day SLA is blown.  We are at 105 days now without a supported version.  6.7 was released April 17th.

  • 0 over 5 years ago in reply to Anonymous

    The Initial 6.7 vddk (basically what we use to access the disks of the VMs) release was on April 17th 2018. The initial release had some issues that were not addressed until VMware released 6.7.0 EP1 on May 24th 2018.

     https://code.vmware.com/web/sdk/67/vddk

    Once our 7.6.6 release went to QA for testing we ran into another issue we considered to be a blocker. We have an open support case with VMware and are awaiting a fix. 

    If you have already upgraded to ESXi 6.7 or have any other questions in regards to this topic I suggest opening a support ticket and referencing this post, we may be able to provide a solution or work around for issues you may be facing.

Reply
  • 0 over 5 years ago in reply to Anonymous

    The Initial 6.7 vddk (basically what we use to access the disks of the VMs) release was on April 17th 2018. The initial release had some issues that were not addressed until VMware released 6.7.0 EP1 on May 24th 2018.

     https://code.vmware.com/web/sdk/67/vddk

    Once our 7.6.6 release went to QA for testing we ran into another issue we considered to be a blocker. We have an open support case with VMware and are awaiting a fix. 

    If you have already upgraded to ESXi 6.7 or have any other questions in regards to this topic I suggest opening a support ticket and referencing this post, we may be able to provide a solution or work around for issues you may be facing.

Children
  • 0 over 5 years ago in reply to rpowell

    RPowell - Could you please give us an update since it's been 3 weeks since your last update.

    Thank You.

  • 0 over 5 years ago in reply to gmchale

    Hi gmchale,

    vRanger 7.6.6 went RTM today which means it was released to support for some additional testing. As long as we do not uncover any issues it will go GA and be available for download on September 10th.  

  • 0 over 5 years ago in reply to rpowell

    Hi rpowell,

    Thanks for the update, I'm glad to hear the updated release date is only a couple of weeks out.

    If you'd be interested in a early adopter\customer tester let me know - I upgraded my vranger to new hardware a couple of months ago, but still have my old hw with  vranger 7.6.4 around and could upgrade that old instance (which had data) and backup my 6.7 test lab and some 6.0 if needed, and could even upgrade my dr vsphere env to 6.7 and load a bunch of test vms on it to test backup and restore. If you're interested reach out to me at my username at williams.edu

    Thanks