Understanding Retention Period

When configuring a backup scheduler, you must specify the maximum time for which a backup can be held in your repository. If you have set a retention period of ‘x’ months, it ensures that the backup held in your repository only holds information of all changes made in the preceding ‘x’ months.

When you configure a new backup scheduler, and you set a backup retention of ‘x’ months, the process that happens is as follows:

For example, assume a backup scheduler is created on July 5, 2018 to perform a backup every Sunday at 12:00 AM. The retention period is set to 1 year. The first time that the scheduler will run is on July 8th, 2018 at 12:00 AM. July 8th, 2018 will be set as the starting point of the retention period. All mailbox items that have their last modified entry from July 8, 2017 to July 8, 2018 will be backed up as the age of the modified item will be less than the maximum retention period. Any item that has the last modified date earlier than July 8, 2017 will not be backed up.

This retention policy is then applied to the backed up data on the repository.

Considering the same example from the scenario above, the next instalment of the backup will occur on July 15th, 2018 at 12:00 AM. With July 15th, 2018 set as the starting point of the retention period, RecoveryManager Plus will scan the backed up data to find all items whose last modified time are earlier than July 15th, 2017. All items that fit the criteria are then removed from the repository.