- 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
Selectors
Selectors are an array of criteria that match resources which belong to the database application. For example, if the action is associated with a StatefulSet, then the selectors describe how to match the pods within the StatefulSet.
Selectors can have multiple logical terms, which are logically combined with AND statements to match resources. Logical terms can match on the Labels, Annotations, or Name fields, and provide filter expressions.
Labels and annotations support key-value pair matching. Names support regular-expression matching.
The selector order serializes the actions on each resource. For pods, the selector order controls the order in which each pod is backed up.
Before deploying the application template, verify that your key-value pairs and regular expressions correctly match all pods and select the pods in the correct order.
Example
An application template applies to a MySQL cluster with one StatefulSet. The application label is a key-value pair that is named app with the value mysql. The following selectors match:
- A primary pod with a name that contains the suffix "-0".
- Secondary pods with names that contain suffixes that start at "-1" and increment.
Remember that secondary pods are backed up before the primary pod.
StatefulSet:
selectors:
- selectorTerms:
- field: "Labels"
selectorExpression: "app=mysql"
- field: "Name"
selectorExpression: ".*-[1-9][0-9]*$"
- selectorTerms:
- field: "Labels"
selectorExpression: "app=mysql"
- field: "Name"
selectorExpression: ".*-0$"
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: <>()\