diff --git a/docs/components/concepts/backups.md b/docs/components/concepts/backups.md index df854ec93d..2dd8a7d263 100644 --- a/docs/components/concepts/backups.md +++ b/docs/components/concepts/backups.md @@ -35,7 +35,7 @@ Manual backups refer to the user-initiated process of creating a consistent snap ### Retention and rate limits -To ensure system stability, backup operations are subject to rate limits. Specifically, you can perform a backup operation every five hours. +To ensure system stability, backup operations are subject to rate limits. Specifically, you can perform a backup operation every hour. However, users can delete an existing backup to create a new one before the rate limit period ends. The system retains the three most recent completed backups per cluster. Failed backup attempts do not count towards the retention count. When a new backup is successful and the retention count is reached, the oldest backup is automatically deleted. diff --git a/versioned_docs/version-8.2/components/concepts/backups.md b/versioned_docs/version-8.2/components/concepts/backups.md index 96aed17483..0aaf233545 100644 --- a/versioned_docs/version-8.2/components/concepts/backups.md +++ b/versioned_docs/version-8.2/components/concepts/backups.md @@ -35,7 +35,7 @@ Manual backups refer to the user-initiated process of creating a consistent snap ### Retention and rate limits -To ensure system stability, backup operations are subject to rate limits. Specifically, you can perform a backup operation every five hours. +To ensure system stability, backup operations are subject to rate limits. Specifically, you can perform a backup operation every hour. However, users can delete an existing backup to create a new one before the rate limit period ends. The system retains the three most recent completed backups per cluster. Failed backup attempts do not count towards the retention count. When a new backup is successful and the retention count is reached, the oldest backup is automatically deleted. diff --git a/versioned_docs/version-8.3/components/concepts/backups.md b/versioned_docs/version-8.3/components/concepts/backups.md index 96aed17483..0aaf233545 100644 --- a/versioned_docs/version-8.3/components/concepts/backups.md +++ b/versioned_docs/version-8.3/components/concepts/backups.md @@ -35,7 +35,7 @@ Manual backups refer to the user-initiated process of creating a consistent snap ### Retention and rate limits -To ensure system stability, backup operations are subject to rate limits. Specifically, you can perform a backup operation every five hours. +To ensure system stability, backup operations are subject to rate limits. Specifically, you can perform a backup operation every hour. However, users can delete an existing backup to create a new one before the rate limit period ends. The system retains the three most recent completed backups per cluster. Failed backup attempts do not count towards the retention count. When a new backup is successful and the retention count is reached, the oldest backup is automatically deleted. diff --git a/versioned_docs/version-8.4/components/concepts/backups.md b/versioned_docs/version-8.4/components/concepts/backups.md index 96aed17483..0aaf233545 100644 --- a/versioned_docs/version-8.4/components/concepts/backups.md +++ b/versioned_docs/version-8.4/components/concepts/backups.md @@ -35,7 +35,7 @@ Manual backups refer to the user-initiated process of creating a consistent snap ### Retention and rate limits -To ensure system stability, backup operations are subject to rate limits. Specifically, you can perform a backup operation every five hours. +To ensure system stability, backup operations are subject to rate limits. Specifically, you can perform a backup operation every hour. However, users can delete an existing backup to create a new one before the rate limit period ends. The system retains the three most recent completed backups per cluster. Failed backup attempts do not count towards the retention count. When a new backup is successful and the retention count is reached, the oldest backup is automatically deleted. diff --git a/versioned_docs/version-8.5/components/concepts/backups.md b/versioned_docs/version-8.5/components/concepts/backups.md index df854ec93d..2dd8a7d263 100644 --- a/versioned_docs/version-8.5/components/concepts/backups.md +++ b/versioned_docs/version-8.5/components/concepts/backups.md @@ -35,7 +35,7 @@ Manual backups refer to the user-initiated process of creating a consistent snap ### Retention and rate limits -To ensure system stability, backup operations are subject to rate limits. Specifically, you can perform a backup operation every five hours. +To ensure system stability, backup operations are subject to rate limits. Specifically, you can perform a backup operation every hour. However, users can delete an existing backup to create a new one before the rate limit period ends. The system retains the three most recent completed backups per cluster. Failed backup attempts do not count towards the retention count. When a new backup is successful and the retention count is reached, the oldest backup is automatically deleted.