- Notes, cautions, and warnings
- Preface
- Getting started
- About asset sources, assets, and storage in PowerProtect Data Manager
- About Kubernetes cluster asset sources and namespace assets
- About Tanzu Kubernetes guest clusters and Supervisor clusters
- Prerequisites
- Roadmap for Kubernetes cluster protection
- Roadmap for Tanzu Kubernetes guest cluster protection
- Updating PowerProtect Data Manager from version 19.13 to the latest version in a Kubernetes environment
- Supported Internet Protocol versions
- 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 for virtual machine, Kubernetes cluster, or NAS protection
- 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
- Add a service-level agreement
- Protection rules
- Edit the retention period for asset copies
- Delete asset backup copies
- Export data for deleted backup copies
- Remove asset copy records from the PowerProtect Data Manager database
- Using the PowerFlex volumegroup snapshot extension
- Protecting PVCs in PowerScale access zones
- Protection policies for Kubernetes namespace protection
- Restoring Kubernetes namespaces and PVCs
- 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 Kubernetes cluster issues
- Troubleshooting network setup issues
- powerprotect-controller pod not created due to security policy configuration
- Restore to original cannot be completed when datastore containing FCD is shared across vCenter servers
- 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.17 Kubernetes User Guide
Restore to original cannot be completed when datastore containing FCD is shared across vCenter servers
A Kubernetes Restore to Original fails with the following error when the datastore containing the PVC/FCD is mounted across multiple vCenter servers:
Failed to open 'folder/fcd/_006c/_00c8/_004c/05f679e4ab8f47009ae1dac71e8f9242-000003.vmdk': DiskLib error 16392: Failed to lock the file 2023-02-06T23:29:44.195Z NOTICE: VDDK INFO Fail to open file [Vol1].
This operation is not supported by the VMware vSphere CSI driver. If this failure occurs, contact VMware support to:
- Unshare the datastores across vCenter servers, and wait for the cache to update.
- Run reconcile on the shared datastore, as described in the following article.
After performing these steps, wait for the scheduled synchronization to refresh the cache, and then retry the Restore to Original.
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: <>()\