Question: “Why” is it not recommended to use this setting if retention is above 90 days or ‘extended retention” set? Would it not work if it was 120 days, or “extended retention” as set to 120 days and you just set it to 365? What is the danger if retention is higher than 90 days?
Background:
In this document: Deduplication FAQ (commvault.com) there is a statement made for a setting in [DDB] → properties → Settings called “Do not Deduplicate against objects older than n day(s)”
Statement: “Do not Deduplicate against objects older than n day(s) option to 4 times of the retention days when the retention is below 90 days on the storage policy copy. If the retention is above 90 days or the extended retention is set on the storage policy copy, then do not use this option”
Also: It appears this setting can probably go up to 365 days (its “365” in the greyed out settings if its not checked to set this setting).
Also: I have some old (read only) mount points that have “referenced data” on them that’s not cleaning up (after about a year of waiting), and I saw this setting and wondered what would happen if I turned this setting on and set it to 365 days. I was hoping the referenced data on the old mount points would be deleted for good and I wouldn’t have to seal the DDB’s.