Backup retention

Backup retention

Organizations use Active Directory (AD) backups to recover business-critical data in the event of site-wide data loss. But they don’t want to waste valuable storage space on backups that were taken ages ago. Ideally, organizations should hold backups until they reach their retention period as defined by organizational standards. However, manually tracking down and deleting backup data that has exceeded the backup retention period is a hassle that no one wants to deal with.

To ease this backup management problem, RecoveryManager Plus has a backup retention feature that allows you to define the number of full backups to be retained in your repository at any given time. When the number of full backups in your repository exceeds the specified number, the oldest full backup and its associated incremental backups will be deleted.

How it works

RecoveryManager Plus allows you to take a periodic full backup of your AD every week or month, depending on your need. When you configure backup settings for a domain, you can specify the number of full backups to retain. Multiple incremental backups, either scheduled or manual, can happen in the same day, but don't count toward the number of full backups retained in your repository.

Assume you have the following backup settings configured: a backup retention count of four backups, incremental backups scheduled to run daily, and full backups set to run on the first day of each week.

In the above case, after the full backup on day one, RecoveryManager Plus will incrementally back up your AD for the next six days. RecoveryManager Plus will then take a full backup of your AD after six days of incremental backups, and the cycle will continue until the 28th day.


When RecoveryManager Plus performs a full backup for the fifth time on 29th, the backup retention count will have exceeded the limit you set, and the retention policy will take effect. The oldest full backup and all incremental backups corresponding to that full backup will be removed from your repository. While the retention policy is only based on the number of full backups to be retained, the incremental backups are also deleted, because they cannot be used in the absence of the associated full backup.


This is how RecoveryManager Plus ensures you don't have older backups wasting your storage space.

Couldn't find the feature you wanted? Raise a feature request 
Need a full-fledged demonstration of the product? Request a personalized demo

A single pane of glass for Active Directory and Exchange Backup