RDoc-2313 - clarify about retention policy when incremental backups are created

docs/backup/overview.mdx

@@ -226,9 +226,9 @@ A full [snapshot image](../backup/overview#snapshot-image) is a duplication of t
 An incremental backup contains only **the changes** made to the database since the last backup, to save storage space and reduce backup time.
 
 <Admonition type="info" title="">
-When an incremental-backup task is executed, it checks for the existence of a backup file.  
-- If a backup file is not found, the task will create a [full backup](../backup/overview#full-backup).  
-- Subsequent backups will be incremental.  
+When an incremental-backup task is executed:  
+- If no backup file is found, the task creates a [full backup](../backup/overview#full-backup) first. Subsequent backups will be incremental.  
+- If the database has not changed since the last backup, the task is skipped - no backup file is produced.  
 </Admonition>
 
 * **Location**  

versioned_docs/version-6.2/studio/database/tasks/backup-task.mdx

@@ -126,6 +126,7 @@ Select the content to back up. Note: Both incremental and full backups can be sc
     The Full Backup that is done the first time will be either a 'Backup' or a 'Snapshot', depending on the type selected.  
     * Data that is backed up in **Incremental Backup** is _always_ of type 'Backup' - even if the Backup Task Type is 'Snapshot'.  
     'Backup' types save index definitions, but not the fully built indexes.  
+    * If the database has not changed since the last backup, the incremental backup task is skipped - no backup file is produced.  
 
  Schedule the Backup Tasks to occur at regular intervals (daily, monthly, hourly, every minute) at specific times.  
 
@@ -151,6 +152,9 @@ Old backups are deleted after the defined time period during the next scheduled
     **We recommend enabling** it so that the deletion of obsolete backups can be scheduled.  
  2. Select the retention period.  
 
+* The retention policy treats a **full backup** and its **incremental backups** as one unit.  
+  The group is only deleted when the **newest incremental backup** in the group exceeds the retention period.  
+
 <Admonition type="info" title="">
 
 Some organizations require backups to be stored for as long as 7 years. If this is the case, consider the issue when scheduling and setting the retention policy. 

versioned_docs/version-7.0/studio/database/tasks/backup-task.mdx

@@ -126,6 +126,7 @@ Select the content to back up. Note: Both incremental and full backups can be sc
     The Full Backup that is done the first time will be either a 'Backup' or a 'Snapshot', depending on the type selected.  
     * Data that is backed up in **Incremental Backup** is _always_ of type 'Backup' - even if the Backup Task Type is 'Snapshot'.  
     'Backup' types save index definitions, but not the fully built indexes.  
+    * If the database has not changed since the last backup, the incremental backup task is skipped - no backup file is produced.  
 
  Schedule the Backup Tasks to occur at regular intervals (daily, monthly, hourly, every minute) at specific times.  
 
@@ -151,6 +152,9 @@ Old backups are deleted after the defined time period during the next scheduled
     **We recommend enabling** it so that the deletion of obsolete backups can be scheduled.  
  2. Select the retention period.  
 
+* The retention policy treats a **full backup** and its **incremental backups** as one unit.  
+  The group is only deleted when the **newest incremental backup** in the group exceeds the retention period.  
+
 <Admonition type="info" title="">
 
 Some organizations require backups to be stored for as long as 7 years. If this is the case, consider the issue when scheduling and setting the retention policy. 

versioned_docs/version-7.1/studio/database/tasks/backup-task.mdx

@@ -126,6 +126,7 @@ Select the content to back up. Note: Both incremental and full backups can be sc
     The Full Backup that is done the first time will be either a 'Backup' or a 'Snapshot', depending on the type selected.  
     * Data that is backed up in **Incremental Backup** is _always_ of type 'Backup' - even if the Backup Task Type is 'Snapshot'.  
     'Backup' types save index definitions, but not the fully built indexes.  
+    * If the database has not changed since the last backup, the incremental backup task is skipped - no backup file is produced.  
 
  Schedule the Backup Tasks to occur at regular intervals (daily, monthly, hourly, every minute) at specific times.  
 
@@ -151,6 +152,9 @@ Old backups are deleted after the defined time period during the next scheduled
     **We recommend enabling** it so that the deletion of obsolete backups can be scheduled.  
  2. Select the retention period.  
 
+* The retention policy treats a **full backup** and its **incremental backups** as one unit.  
+  The group is only deleted when the **newest incremental backup** in the group exceeds the retention period.  
+
 <Admonition type="info" title="">
 
 Some organizations require backups to be stored for as long as 7 years. If this is the case, consider the issue when scheduling and setting the retention policy.