- 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
Prerequisites
Ensure that your environment meets the requirements for a new deployment or update of PowerProtect Data Manager.
Requirements:
NOTE:The most up-to-date software compatibility information for the
PowerProtect Data Manager software and the application agents is provided by the
E-Lab Navigator.
- A list of hosts that write backups to PowerProtect DD systems is available.
-
DDOS version 6.1 or later and the PowerProtect DD Management Center are required. All models of DD systems are supported.
NOTE:PowerProtect DD Management Center is required with a DDOS version earlier than 6.1.2. With DDOS version 6.1.2 or later, you can add and use a DDOS system directly without PowerProtect DD Management Center. - License: A trial license is provided with the PowerProtect Data Manager software. Contact your Customer Support representative for assistance with a permanent PowerProtect Data Manager license.
- Large environments require multiple PowerProtect Data Manager instances. Contact Champions.eCDM@dell.com for assistance with sizing requests.
- The
PowerProtect Data Manager 19.15 download file requires the following:
- ESXi version 6.5, 6.7, or 7.0.
- 8 vCPUs, 18 GB RAM, one 100 GB disk, and one 500 GB disk.
- The latest version of the Google Chrome browser to access the PowerProtect Data Manager UI.
- TCP port 7000 is open between PowerProtect Data Manager and the application agent hosts.
- VMware ESXi server that hosts
PowerProtect Data Manager meets the following minimum system requirements:
- 10 CPU cores
- 18 GB of RAM for PowerProtect Data Manager
- Five disks with the following capacities:
- Disk 1—100 GB
- Disk 2—500 GB
- Disk 3—10 GB
- Disk 4—10 GB
- Disk 5—5 GB
- One 1-GB NIC
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: <>()\