WilliamLam.com

Exploring the new vSAN Data Protection API in vSphere 8.0 Update 3

by // Leave a Comment

I have been spending some time with the new vSAN Data Protection (DP) capability that was just introduced with the latest vSphere 8.0 Update 3 release and if you are interested in what you can do with this new functionality, Duncan Epping has recently published a blog post on this exact topic that you should check out!

While the new vSAN DP capability can easily be consumed using the new vSphere UI plugin, it can be even more powerful with automation and I was interested in learning more about the vSAN DP API and how administrators can consume it.

Today, the vSAN DP (REST) API endpoint is part of the vSAN DP Virtual Appliance, which must be deployed access both the vSAN DP vSphere UI plugin and vSAN DP API. Since the vSAN DP API is available as a separate API endpoint, to authenticate you will need to request a SAML token from the vCenter Single Sign-On (SSO) service. There are currently some issues with the vSAN DP API documentation and once that is available, which I will linked, you will find more information about requesting a token along with all the available methods.

[Read more...]

Automating deployment of vSAN Data Protection OVA with PowerCLI

by // 2 Comments

vSphere 8.0 Update 3 introduces a new vSAN Data Protection capability for the vSAN Express Storage Architecture (ESA) and it is currently delivered as a standalone VMware OVA (see Duncan's post in case you are wondering where to download) which, once deployed and configures, enables a new vSphere UI plugin as shown in screenshot below.


After going through the manual (vSphere UI) deployment workflow, which also included some non-traditional input like requiring the raw vCenter Server TLS certificate, I was interested in automating the deployment using PowerCLI.

[Read more...]

Quick Tip - Retrieving NSX segment information from vCenter Server

by // Leave a Comment

Since vSphere 7.0, it has been much simpler to correlate between an NSX network segment defined in NSX Manager and its representation as a vSphere Distributed Virtual Portgroup (DVG) in vCenter Server as demonstrated in screenshot below using the vSphere UI.


With the additional NSX information such as NSX Transport Zone ID, Transport Zone ID Name, Logical Switch ID, Segment Name and VNI (Virtual Network Identifier), users can streamline debugging and troubleshooting issues with their network team by quickly providing this relevant information.

I recently had a user ask about retrieving the VNI information for a given NSX segment in vCenter Server using PowerCLI, so here is a quick snippet including other NSX information for those interested.

[Read more...]