Apparently the “Commserve_DR_Disk” and Primary/Secondary copies are created automatically during certain CommVault installation/setup steps….
We are attempting to retire an old disk library and there’s still some data on it that commvault will not age off (I may have to create a ticket for some of it). I could force/delete it but I’m also trying to have it clean up “nicely/cleanly”. One of the larger blocks of data appears to be some DR backups that are attached to the ‘Primary” copy. I did some digging by running the “Data Retention Forecast and Compliance Report” and it appears that this data (~10 TB) is hanging around due to “Managed Disk Space Option Enabled for Prunable Job on Disk Media”. I checked the Primary copy and yep, the “Enable managed Disk Space for Disk Library” has been checked. i assume tahts teh setting causing the extended retention.
- Is “Enable managed Disk Space for Disk Library” checked by default by commvault when it creates/builds the Commserve_DR_Disk Primary copy storage policy? If so, any idea why? I’m mostly just wondering if its not the default and someone checked it long ago.
- Is there any dangers for ‘unchecking” “Enable managed Disk Space for Disk Library” for this copy so it can delete the data off of storage now? I figure I could finagle the managed disk library settings by setting them to 0% to make the DR backups age off, but having “Enable managed Disk Space for Disk Library” seems like a lot of DR backup data to keep if we have a large disk library (and we have ~10 TB used up by these, per the report)
Best answer by NiallView original
The “Managed Disk Space” option is both a blessing and a curse.
Basically, it allows you to say, I know what the storage policy retention is but if there is enough disk library space available please keep the jobs for longer.
So, in terms of your questions -