Enabling protection when the vSphere CSI driver is installed as a process
PowerProtect Data Manager leverages the vSphere Velero plug-in to protect VMware Cloud Native Storage volumes that use VADP snapshots. To take these snapshots,
PowerProtect Data Manager and the Velero plug-in require the location and credentials of the vCenter Server. This information is provided in a VMware CSI driver secret with the name
vsphere-config-secret or
csi-vsphere-config. This secret must be present in the
kube-system or
vmware-system-csi namespace.
Some distributions, such as TKGI 1.11 and later, automatically install the CSI driver as a process rather than the method specified in the
VMware vSphere Container Storage Plug-in Documentation. If the CSI driver is installed automatically as a process,
PowerProtect Data Manager and the Velero plug-in are unable to obtain the CSI secret in the Kubernetes cluster. Without this information,
PowerProtect Data Manager is unable to protect these environments.
When you add or edit the Kubernetes cluster asset source in the
PowerProtect Data Manager UI, if a VMware CSI driver secret with the name
vsphere-config-secret or
csi-vsphere-config is not present, move the
VMware CSI Driver as process slider to the right under
Advanced Settings, and then select the vCenter Server asset source.
Add a Kubernetes cluster provides the details for specifying Kubernetes cluster advanced settings.
When adding the vCenter Server that is associated to this Kubernetes cluster, the following minimum vCenter user privileges are required :
Datastore.Low level file operations
Tasks.Create task
Tasks.Update task
NOTE:You can also provide the vCenter information and credentials to
PowerProtect Data Manager optionally using the API. Follow the instructions in the section "Enabling protection when the vSphere CSI driver is installed as a process" under
Back up and restore Kubernetes in the
PowerProtect Data Manager Public REST API documentation.
Data is not available for the Topic
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\