In regards to the way CommVault is associated to a Disk/Cloud Library there is two ways:
- Un-Deduped Data
- Deduped Data
Once Backup data is written to a Disk/Cloud Library, an association is tied to the Disk/Cloud Library. CommVault will not remove the Disk/Library unless all the underlying blocks are first removed from the CommServe DB then a Aging Process is triggered (referred to as Data Aging).
Data Aging is the logical dis-association from the CommServe Level (after doing manual remove of backup jobs) , on a default basis we will then send a reuqest to physically prune the data from the Disk/Library.
So following the logic of removing data from Disk/LIbrary, as the references are removed from the CommServe DB, their will be no way to recover or re-reference. However here are some possible options:
- If the Backup jobs is still retained in the CommServe, you can try to "un-age" (assuming that it is not physically removed from the Disk/Cloud Library)
- CommServe Restore to a point in time before the Data Aging was issued (this will also be a last resort, as you might be able to go back in time, but will lost the delta backup between the time of the CommServe DR Backup and the time when you plan to do so).
The following are example scenario, and every environment is different and unique.
Hopefully that helps