- Notes, cautions, and warnings
- Preface
- PowerProtect Data Manager for Kubernetes Overview
- About asset sources, assets, and storage
- Prerequisites
- Supported Internet Protocol versions
- Encryption in-flight
- Roadmap for Kubernetes cluster protection
- Roadmap for Tanzu Kubernetes guest cluster protection
- Updating PowerProtect Data Manager from version 19.13 or earlier to the latest version in a Kubernetes environment
- Security configuration
- Enabling the Kubernetes Cluster
- Adding a Kubernetes cluster asset source
- Prerequisites to Tanzu Kubernetes guest cluster protection
- Prerequisites to Kubernetes cluster discovery
- Enable an asset source
- Delete an asset source
- Add a VMware vCenter Server
- Add a Kubernetes cluster
- Controller Configurations
- Customizing the PowerProtect Data Manager pod configuration
- Add a VM Direct Engine
- Managing Storage, Assets, and Protection for Kubernetes Clusters
- Protection policies for Kubernetes namespace protection
- Supported protection policy purposes
- Supported protection policy objectives
- Replication triggers
- Roadmap for planning a protection policy
- Before you add a protection policy for Kubernetes namespace protection
- Add a protection policy for Kubernetes namespace protection
- Extended retention for protection policies created in PowerProtect Data Manager 19.11 or earlier
- Add a service-level agreement
- Protection rules
- Edit the retention period for backup copies
- Delete backup copies
- Using the PowerFlex volumegroup snapshot extension
- Protecting PVCs in PowerScale access zones
- Protection policies for Kubernetes namespace protection
- Restoring Kubernetes Namespaces and PVCs
- Kubernetes Cluster Best Practices and Troubleshooting
- PPDMK8SDIAG diagnostics tool
- 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
- Restore to original cannot be completed when datastore containing FCD is shared across vCenters
- Specify volumesnapshotclass for v1 CSI snapshots
- Enabling protection when the vSphere CSI driver is installed as a process
- Considerations when protecting nonsnapshot CSI volumes
- Pod configuration not updated in Velero deployment when field is omitted from patch string
- Backups fail or hang on OpenShift after a new PowerProtect Data Manager deployment
- Restore of imagestream and imagestreamtags cannot be completed on OpenShift
- 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
- vSphere CSI backups might fail when the File System agent is used as the data mover
- Pull images from Docker Hub as authenticated user if Docker pull limits reached
- Warning displays when temporary persistent volumes not deleted by CSI driver before timeout
- 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
- Glossary
PowerProtect Data Manager 19.15 Kubernetes User Guide
Using the PowerFlex volumegroup snapshot extension
The PowerFlex CSI driver volumegroup snapshot extension enables you to snapshot all of the Kubernetes PVCs that belong to the same volume group, instead of creating a snapshot of each PVC using the existing CSI volumesnapshot functionality.
PowerProtect Data Manager automatically uses the volumegroup snapshot extension when the following conditions are met:
- The Kubernetes clusters are using PVCs provisioned by the CSI driver for PowerFlex.
- The CSI driver for PowerFlex has the volumegroup snapshotter feature enabled, and the volumegroupsnapshot CRD is present on the Kubernetes cluster.
- The PVCs share the same volume-group label.
When the volumegroup snapshotter feature is in use for a group of PVCs in a protection policy, an entry for VolumeGroup appears in the Details pane of the PowerProtect Data Manager UI Jobs window for the protection policy backup.
NOTE:If one or more PVCs belonging to a
volumegroup is excluded from a protection policy,
PowerProtect Data Manager falls back to using the
volumesnapshot functionality for all of the PVCs in this
volumegroup, even if the other PVCs in the
volumegroup are included in the protection policy. When this occurs, the backup completes successfully but with a warning in the
PowerProtect Data Manager UI
Jobs window.
If you want PowerProtect Data Manager to use the volumesnapshot functionality instead of the PowerFlex volumegroup snapshot extension, you can disable the volumegroup snapshot extension by performing the following steps:
- From the PowerProtect Data Manager UI, go to .
- In the Kubernetes tab, select the Kubernetes cluster asset source that is used to protect the PVCs belonging to the volume group, and then click Edit.
- In the Edit Kubernetes dialog box, click the down arrow to expand Advanced Settings.
- Under Controller Configuration, set the value for the property k8s.ppdm.support.volumeGroup to false.
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: <>()\