Remove unsupported guidance from docs on incremental backups (#19571)

Author: katmayb

src/current/_includes/releases/v23.1/v23.1.0.md

@@ -293,12 +293,6 @@ With the move from Preview to GA, this feature brings many new capabilities, suc
    </tr>
   </thead>
   <tbody>
-  <tr>
-   <td><p>Support longer incremental backup chains</p>
-   </td>
-   <td><p>We now support up to 400 incremental backups, an 8x increase, enabling you to preserve your data even more effectively (reducing RPO) while being more cost-efficient. Incremental backups contain only the data that has changed since the last backup, so they are smaller and faster to produce.
-   </td>
-  </tr>
   <tr>
    <td><p>Restrict backups to a locality</p>
    </td>

src/current/v23.1/take-full-and-incremental-backups.md

@@ -153,15 +153,7 @@ If you are taking backups on a regular cadence, we recommend [creating a schedul
 
 ### Recommendations for incremental backup frequency
 
-Incremental backups form chains between full backups. Each incremental backup contains only the data that has changed since a base set of backups. This base set of backups must include one full backup and can include many incremental backups, which are smaller and faster to produce than full backups. You can take incremental backups either as of a given timestamp or with full [revision history]({% link {{ page.version.version }}/take-backups-with-revision-history-and-restore-from-a-point-in-time.md %}).
-
-Cockroach Labs recommends taking incremental backups every 10 minutes. CockroachDB supports up to 400 incremental backups between full backups. This may vary based on your specific use-case, so we recommend testing within your own environment and workloads. This can look like:
-
-- A full backup taken daily with incrementals taken every hour for a total of 24 incremental backups.
-- A full backup taken daily with incrementals taken every 10 minutes for a total of 144 incremental backups.
-- A full backup taken daily with incrementals taken every 5 minutes for a total of 288 incremental backups.
-- A full backup taken weekly with incrementals taken every hour for a total of 168 incremental backups.
-- A full backup taken weekly with incrementals taken every 30 minutes for a total of 336 incremental backups.
+Incremental backups form chains between full backups. Each incremental backup contains only the data that has changed since a base set of backups. This base set of backups must include one full backup and can include multiple incremental backups, which are typically smaller and faster to run than full backups. You can take incremental backups either as of a given timestamp or with full [revision history]({% link {{ page.version.version }}/take-backups-with-revision-history-and-restore-from-a-point-in-time.md %}). Cockroach Labs supports up to 48 incremental backups between full backups.
 
 ### Garbage collection and backups
 

src/current/v23.2/take-full-and-incremental-backups.md

@@ -153,15 +153,7 @@ If you are taking backups on a regular cadence, we recommend [creating a schedul
 
 ### Recommendations for incremental backup frequency
 
-Incremental backups form chains between full backups. Each incremental backup contains only the data that has changed since a base set of backups. This base set of backups must include one full backup and can include many incremental backups, which are smaller and faster to produce than full backups. You can take incremental backups either as of a given timestamp or with full [revision history]({% link {{ page.version.version }}/take-backups-with-revision-history-and-restore-from-a-point-in-time.md %}).
-
-Cockroach Labs recommends taking incremental backups every 10 minutes. CockroachDB supports up to 400 incremental backups between full backups. This may vary based on your specific use-case, so we recommend testing within your own environment and workloads. This can look like:
-
-- A full backup taken daily with incrementals taken every hour for a total of 24 incremental backups.
-- A full backup taken daily with incrementals taken every 10 minutes for a total of 144 incremental backups.
-- A full backup taken daily with incrementals taken every 5 minutes for a total of 288 incremental backups.
-- A full backup taken weekly with incrementals taken every hour for a total of 168 incremental backups.
-- A full backup taken weekly with incrementals taken every 30 minutes for a total of 336 incremental backups.
+Incremental backups form chains between full backups. Each incremental backup contains only the data that has changed since a base set of backups. This base set of backups must include one full backup and can include multiple incremental backups, which are typically smaller and faster to run than full backups. You can take incremental backups either as of a given timestamp or with full [revision history]({% link {{ page.version.version }}/take-backups-with-revision-history-and-restore-from-a-point-in-time.md %}). Cockroach Labs supports up to 48 incremental backups between full backups.
 
 ### Garbage collection and backups
 

src/current/v24.1/take-full-and-incremental-backups.md

@@ -153,15 +153,7 @@ If you are taking backups on a regular cadence, we recommend [creating a schedul
 
 ### Recommendations for incremental backup frequency
 
-Incremental backups form chains between full backups. Each incremental backup contains only the data that has changed since a base set of backups. This base set of backups must include one full backup and can include many incremental backups, which are smaller and faster to produce than full backups. You can take incremental backups either as of a given timestamp or with full [revision history]({% link {{ page.version.version }}/take-backups-with-revision-history-and-restore-from-a-point-in-time.md %}).
-
-Cockroach Labs recommends taking incremental backups every 10 minutes. CockroachDB supports up to 400 incremental backups between full backups. This may vary based on your specific use-case, so we recommend testing within your own environment and workloads. This can look like:
-
-- A full backup taken daily with incrementals taken every hour for a total of 24 incremental backups.
-- A full backup taken daily with incrementals taken every 10 minutes for a total of 144 incremental backups.
-- A full backup taken daily with incrementals taken every 5 minutes for a total of 288 incremental backups.
-- A full backup taken weekly with incrementals taken every hour for a total of 168 incremental backups.
-- A full backup taken weekly with incrementals taken every 30 minutes for a total of 336 incremental backups.
+Incremental backups form chains between full backups. Each incremental backup contains only the data that has changed since a base set of backups. This base set of backups must include one full backup and can include multiple incremental backups, which are typically smaller and faster to run than full backups. You can take incremental backups either as of a given timestamp or with full [revision history]({% link {{ page.version.version }}/take-backups-with-revision-history-and-restore-from-a-point-in-time.md %}). Cockroach Labs supports up to 48 incremental backups between full backups.
 
 ### Garbage collection and backups
 

src/current/v24.2/take-full-and-incremental-backups.md

@@ -153,15 +153,7 @@ If you are taking backups on a regular cadence, we recommend [creating a schedul
 
 ### Recommendations for incremental backup frequency
 
-Incremental backups form chains between full backups. Each incremental backup contains only the data that has changed since a base set of backups. This base set of backups must include one full backup and can include many incremental backups, which are smaller and faster to produce than full backups. You can take incremental backups either as of a given timestamp or with full [revision history]({% link {{ page.version.version }}/take-backups-with-revision-history-and-restore-from-a-point-in-time.md %}).
-
-Cockroach Labs recommends taking incremental backups every 10 minutes. CockroachDB supports up to 400 incremental backups between full backups. This may vary based on your specific use-case, so we recommend testing within your own environment and workloads. This can look like:
-
-- A full backup taken daily with incrementals taken every hour for a total of 24 incremental backups.
-- A full backup taken daily with incrementals taken every 10 minutes for a total of 144 incremental backups.
-- A full backup taken daily with incrementals taken every 5 minutes for a total of 288 incremental backups.
-- A full backup taken weekly with incrementals taken every hour for a total of 168 incremental backups.
-- A full backup taken weekly with incrementals taken every 30 minutes for a total of 336 incremental backups.
+Incremental backups form chains between full backups. Each incremental backup contains only the data that has changed since a base set of backups. This base set of backups must include one full backup and can include multiple incremental backups, which are typically smaller and faster to run than full backups. You can take incremental backups either as of a given timestamp or with full [revision history]({% link {{ page.version.version }}/take-backups-with-revision-history-and-restore-from-a-point-in-time.md %}). Cockroach Labs supports up to 48 incremental backups between full backups.
 
 ### Garbage collection and backups
 

src/current/v24.3/take-full-and-incremental-backups.md

@@ -153,15 +153,7 @@ If you are taking backups on a regular cadence, we recommend [creating a schedul
 
 ### Recommendations for incremental backup frequency
 
-Incremental backups form chains between full backups. Each incremental backup contains only the data that has changed since a base set of backups. This base set of backups must include one full backup and can include many incremental backups, which are smaller and faster to produce than full backups. You can take incremental backups either as of a given timestamp or with full [revision history]({% link {{ page.version.version }}/take-backups-with-revision-history-and-restore-from-a-point-in-time.md %}).
-
-Cockroach Labs recommends taking incremental backups every 10 minutes. CockroachDB supports up to 400 incremental backups between full backups. This may vary based on your specific use-case, so we recommend testing within your own environment and workloads. This can look like:
-
-- A full backup taken daily with incrementals taken every hour for a total of 24 incremental backups.
-- A full backup taken daily with incrementals taken every 10 minutes for a total of 144 incremental backups.
-- A full backup taken daily with incrementals taken every 5 minutes for a total of 288 incremental backups.
-- A full backup taken weekly with incrementals taken every hour for a total of 168 incremental backups.
-- A full backup taken weekly with incrementals taken every 30 minutes for a total of 336 incremental backups.
+Incremental backups form chains between full backups. Each incremental backup contains only the data that has changed since a base set of backups. This base set of backups must include one full backup and can include multiple incremental backups, which are typically smaller and faster to run than full backups. You can take incremental backups either as of a given timestamp or with full [revision history]({% link {{ page.version.version }}/take-backups-with-revision-history-and-restore-from-a-point-in-time.md %}). Cockroach Labs supports up to 48 incremental backups between full backups.
 
 ### Garbage collection and backups
 

src/current/v25.1/take-full-and-incremental-backups.md

@@ -153,15 +153,7 @@ If you are taking backups on a regular cadence, we recommend [creating a schedul
 
 ### Recommendations for incremental backup frequency
 
-Incremental backups form chains between full backups. Each incremental backup contains only the data that has changed since a base set of backups. This base set of backups must include one full backup and can include many incremental backups, which are smaller and faster to produce than full backups. You can take incremental backups either as of a given timestamp or with full [revision history]({% link {{ page.version.version }}/take-backups-with-revision-history-and-restore-from-a-point-in-time.md %}).
-
-Cockroach Labs recommends taking incremental backups every 10 minutes. CockroachDB supports up to 400 incremental backups between full backups. This may vary based on your specific use-case, so we recommend testing within your own environment and workloads. This can look like:
-
-- A full backup taken daily with incrementals taken every hour for a total of 24 incremental backups.
-- A full backup taken daily with incrementals taken every 10 minutes for a total of 144 incremental backups.
-- A full backup taken daily with incrementals taken every 5 minutes for a total of 288 incremental backups.
-- A full backup taken weekly with incrementals taken every hour for a total of 168 incremental backups.
-- A full backup taken weekly with incrementals taken every 30 minutes for a total of 336 incremental backups.
+Incremental backups form chains between full backups. Each incremental backup contains only the data that has changed since a base set of backups. This base set of backups must include one full backup and can include multiple incremental backups, which are typically smaller and faster to run than full backups. You can take incremental backups either as of a given timestamp or with full [revision history]({% link {{ page.version.version }}/take-backups-with-revision-history-and-restore-from-a-point-in-time.md %}). Cockroach Labs supports up to 48 incremental backups between full backups.
 
 ### Garbage collection and backups
 

src/current/v25.2/take-full-and-incremental-backups.md

@@ -153,15 +153,7 @@ If you are taking backups on a regular cadence, we recommend [creating a schedul
 
 ### Recommendations for incremental backup frequency
 
-Incremental backups form chains between full backups. Each incremental backup contains only the data that has changed since a base set of backups. This base set of backups must include one full backup and can include many incremental backups, which are smaller and faster to produce than full backups. You can take incremental backups either as of a given timestamp or with full [revision history]({% link {{ page.version.version }}/take-backups-with-revision-history-and-restore-from-a-point-in-time.md %}).
-
-Cockroach Labs recommends taking incremental backups every 10 minutes. CockroachDB supports up to 400 incremental backups between full backups. This may vary based on your specific use-case, so we recommend testing within your own environment and workloads. This can look like:
-
-- A full backup taken daily with incrementals taken every hour for a total of 24 incremental backups.
-- A full backup taken daily with incrementals taken every 10 minutes for a total of 144 incremental backups.
-- A full backup taken daily with incrementals taken every 5 minutes for a total of 288 incremental backups.
-- A full backup taken weekly with incrementals taken every hour for a total of 168 incremental backups.
-- A full backup taken weekly with incrementals taken every 30 minutes for a total of 336 incremental backups.
+Incremental backups form chains between full backups. Each incremental backup contains only the data that has changed since a base set of backups. This base set of backups must include one full backup and can include multiple incremental backups, which are typically smaller and faster to run than full backups. You can take incremental backups either as of a given timestamp or with full [revision history]({% link {{ page.version.version }}/take-backups-with-revision-history-and-restore-from-a-point-in-time.md %}). Cockroach Labs supports up to 48 incremental backups between full backups.
 
 ### Garbage collection and backups