Do we have any option to perform Incremental restore.
we have tested the Namespace and Application level restore( in and out of place restore). while performing the out of place restore for already existing namespace , if overwrite option is not enabled restoration fails and it succeeds if overwrite option is enabled. In backend this overwrite deletes all the existing resources from the namespaces and recreates again. we are not able to achieve the incremental restore which is not suitable for the TB’s of data size.
Hello
This document may be useful for you
Restores for Kubernetes - https://documentation.commvault.com/2023e/essential/restores_for_kubernetes.html
For Kubernetes applications, you can restore full applications, application manifests or specifications, or application files (from a PersistentVolume). When you restore a specific application, you can choose the restore granularity: full application, application manifests, or application files.
You can restore an application out of place to any Kubernetes cluster that is added to Commvault, for application migration or disaster recovery. You can migrate Kubernetes applications between different Kubernetes distributions, clusters, and StorageClasses. Commvault requires the source and destination cluster to use the same major release of Kubernetes. For example, you can restore Kubernetes 1.23 to Kubernetes 1.23.
Thank you,
Collin
Hi PPC,
We do incremental restore for PVC data. I.e for PVC only restore we do restore only missing files without overwrite option. In case of namespace or app restore we do incremental restore for pods that do not exist. The only case where we do not do incremental restore is if we see POD exist on destination (Whether running or not running ) we skip that entire App from restore. is this the case that you are looking for .. Usually PVC restores are huge in size so that supports incremental restore
Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.