Extended retention or not?

Hi @Bloopa 
 

If I’m understanding correctly, you have a incremental backup run daily and synthetic full run weekly.

• I would recommend setting basic retention to 14 days
  • With 1 cycle retention chosen, after the next synthetic full runs the previous cycle would meet retention when the latest incremental of the previous cycle has met its basic day retention
  • All jobs within the cycle must meet retention before any job in the cycle will become prunable
  • If you set 2 cycle basic retention then you would retain 2 cycles of backups and the first cycle would become prunable after a third has run and basic days is met for the latest backup of that first cycle.
  • A higher cycle count will allow you to retain additional cycles of the backups but may cause the backups to exceed your desired basic retention days as it will need to ensure all backups in the cycle have met basic days retention in addition to meeting the cycle retention
• It is true that adding additional extended retention to the primary storage policy copy can lead to an increase in size
• When you are intending to achieve an extended retention it is advised to create additional selective copies for this
• https://documentation.commvault.com/commvault/v11/article?p=11919.htm

  • For deduplication storage policy copy, a message appears that tells you that enabling extended retention rules on a deduplicated copy might increase the DDB size.

    Click No and create a selective copy with deduplication for each selective criteria (for example, weekly, monthly, and so on) and set the higher basic retention period on each selective copy. For instructions, see Creating a Selective Copy.

• https://documentation.commvault.com/commvault/v11/article?p=13907.htm