- Notes, cautions, and warnings
- Preface
- PowerProtect Data Manager for Kubernetes Overview
- Enabling the Kubernetes Cluster
- Managing Storage, Assets, and Protection for Kubernetes Clusters
- Restoring Kubernetes Namespaces and PVCs
- Kubernetes Cluster Best Practices and Troubleshooting
- Configuration changes required for use of optimized data path and first class disks
- Recommendations and considerations when using a Kubernetes cluster
- Support Network File System (NFS) root squashing
- Update the Velero or OADP version used by PowerProtect Data Manager
- VM Direct protection engine overview
- Troubleshooting network setup issues
- Troubleshooting Kubernetes cluster issues
- Specify volumesnapshotclass for v1 CSI snapshots
- Enabling protection when the vSphere CSI driver is installed as a process
- Customizing PowerProtect Data Manager pod configuration
- Backups fail or hang on OpenShift after a new PowerProtect Data Manager installation or update from a 19.9 or earlier release
- Data protection operations for high availability Kubernetes cluster might fail when API server not configured to send ROOT certificate
- Kubernetes cluster on Amazon Elastic Kubernetes Service certificate considerations
- Removing PowerProtect Data Manager components from a Kubernetes cluster
- Increase the number of worker threads in Supervisor cluster backup-driver if Velero timeout occurs
- Velero pod backup and restore might fail if namespace being protected contains a large number of resources
- Pull images from Docker Hub as authenticated user if Docker pull limits reached
- Application-Consistent Database Backups in Kubernetes
- About application-consistent database backups in Kubernetes
- Obtain and deploy the CLI package
- About application templates
- Deploy application templates
- Perform application-consistent backups
- Verify application-consistent backups
- Disaster recovery considerations
- Granular-level restore considerations
- Log truncation considerations
PowerProtect Data Manager 19.10 Kubernetes User Guide
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 the VMware CSI driver secret vsphere-config-secret in the Kubernetes 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.
To provide the vCenter information and credentials to PowerProtect Data Manager, 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.
Also, to protect the Kubernetes environment on which CSI is installed as process, the following minimum vCenter user privileges are required when adding the vCenter that is associated to the Kubernetes cluster:
- Datastore.Low level file operations
- Tasks.Create task
- Tasks.Update task
NOTE The namespace location of the CSI driver secret
vsphere-config-secret depends on the VMware CSI version in use:
- For CSI versions earlier than 2.3, the secret is in the kube-system namespace.
- For CSI versions 2.3 and later, the secret is in the vmware-system-csi namespace.
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: <>()\