Retention period
Learn here about the retention periods that are defined by the server plan for your backup data.
For each server plan, the retention periods of the backup data are already preconfigured.
Therefore, as a user, you do not need to specify these time windows yourself after you have assigned your client to a server plan. You can see which retention periods apply to the data of your client (or the server plan to which your client is assigned) in the Command Center under https://console1.dasi.rwth-aachen.de/.
To do this, navigate to Manage > Plans > Backup destination and click Primary.
The "Retention Period" is the minimum number of days that all backup jobs must be retained. The number of days must be exceeded before the data is eligible for aging.
There is a distinction between the "Basic Retention Period" and the "Extended Retention Rules".
- In the example shown above, the Basic Retention Period is set to one week. This means that for each backup job assigned to this plan, a retention period of one week applies.
- Extended Retention Rules are also defined. Here, based on fullbackups, retention periods are extended for specific Full-backups.
- The example shows that weekly Full-backups have a retention period of one month and monthly Full-backups have a retention period of six months.
For example, if we define a backup cycle that runs from Monday to Sunday with a Full-Backup on Sunday, then all backups from Monday to Saturday will be retained for one week. Only the Full-Backups that run on Sundays are automatically retained for six months. Such a backup cycle eliminates the need to manually trigger weekly and monthly backups, as this is automatically defined via the retention rules.
Note: In the currently available server plans ServerplanB, ServerplanC, and ServerplanD (as of 03.05.23) a "Retention period 1 Month" is set with a retention period of six months. The adjustments to the server plans regarding the frequency of the synthetic backups are made to reduce the load on the clients and to reduce read operations on the underlying storage.
Details can be found at doku.dasi.nrw
Related content:
