# Tracking usage of commvault to backup and restore k8s cluster and applications Updates as of 09/09/2022: - Installed public release v11.28 commvault. - with the operator pattern of dbs, struggling because there is no separate option to just restore the CR, so right now the option is there to backup whole namespace or the application (which does not have cr) - problem with them is they will install the statefuleset, and other resources that are meant to be created by the operator. Ideally we would need to restore just the pv and the CR. - hard to understand the segregation between whats present in the application level restore and namespace level restore - there is an option to restore just the yaml files, but it would much better if we can do that in the cluster node itself, instead of putting it in the commvault machine - retore of pvc not working, the job shows successful, but we cant see the data. TRACK: - Installaton is done on k8s v1.20.0 - [BUG1] non-namespaced resources are not backed up like crds, clusterrolebinfings, webhooks - [BUG2] [RESOLVED] For a component like knative it didn't even backup the configmaps. (the configmaps are not mounted with deployments, but they do exist in the namespace, and are _CRUCIAL_ for the component to work) - [BUG3] while doing restore, the following error comes up: ![](https://i.imgur.com/mcNEkGg.png) - [BUG4] in the logs and in the manifest it says thats its backing up clusterrolebindings, but they are not found after restore: ![](https://i.imgur.com/WZQXgrp.png) ![](https://i.imgur.com/00LwncK.png) - [BUG5] CRDs are not backed up, even though the documentation says so: https://documentation.commvault.com/11.24/essential/123634_kubernetes.html - [Technical Question 1] is there an option backup full cluster? [v11.28 beta] - [Technical Question 2] through the UI if we select an application, how does commvault know what all are the resources that have to be backed up? (missing from documenation) - [Technical Question 3] Since we are testing commvault with v1.20 k8s version, I hope that this is being considered while providing us with v11.28 pre-release commvault? - monitoring yet to be evaluated