Skip to content

Commit 17e6214

Browse files
committed
Added Ad hoc backup retention
1 parent 96f1546 commit 17e6214

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

articles/backup/backup-configure-vault.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -253,8 +253,8 @@ After the initial backup is completed, the **Job completed** status appears in t
253253

254254
| Backup Policy for Scheduled Backup | Ad hoc Backup Retention
255255
| -- | --
256-
| Daily | **Default Retention**: Equivalent to the “retention in days for daily backups.” <br/><br/> **Exception**: If a daily scheduled backup is set for long-term retentions (Weeks, Months, Years) fails, then an ad hoc backup triggered right after this failed scheduled backup is considered for long-term retention. Otherwise, the next successful scheduled backup is considered for long-term retention.<br/><br/> **Example**: If all (Weekly/Monthly/Yearly) retention backups are in failed state and you triggers a ad hoc backup then it will follow the yearly retention period.
257-
| Weekly | **Default Retention** : 1 day. <br/> Ad hoc Backups taken for a data source with weekly Backup policy are deleted the very next day, even if they are the most recent Backups for the data source. <br/><br/> **Exception**: If a weekly scheduled backup is set for long-term retentions (Weeks, Months, Years) fails, then an ad hoc backup triggered right after this failed scheduled backup will be considered for long-term retention. Otherwise, the next successful scheduled backup is considered for long-term retention. <br/><br/> **Example**: If both (Weekly/monthly) retention backups are in failed state and you triggers a ad hoc backup then it will follow the Monthly retention period.
256+
| Daily | **Default Retention**: Equivalent to the “retention in days for daily backups.” <br/><br/> **Exception**: If a daily scheduled backup is set for long-term retentions (Weeks, Months, Years) fails, then an ad hoc backup triggered right after this failed scheduled backup is considered for long-term retention. Otherwise, the next successful scheduled backup is considered for long-term retention.<br/><br/> **Example**: If all the (Weekly/Monthly/Yearly) retention backups are in failed state and you triggers a ad hoc backup then it will follow the Yearly retention period.
257+
| Weekly | **Default Retention** : 1 day. <br/> Ad hoc Backups taken for a data source with weekly Backup policy are deleted the very next day, even if they are the most recent Backups for the data source. <br/><br/> **Exception**: If a weekly scheduled backup is set for long-term retentions (Weeks, Months, Years) fails, then an ad hoc backup triggered right after this failed scheduled backup will be considered for long-term retention. Otherwise, the next successful scheduled backup is considered for long-term retention. <br/><br/> **Example**: If both the (Weekly/Monthly) retention backups are in failed state and you triggers a ad hoc backup then it will follow the Monthly retention period.
258258

259259

260260
## Next steps
-5.36 KB
Loading

0 commit comments

Comments
 (0)