From 57d89ea9e34cb9b3e7d756e5eab2e49c43582fe4 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Felix=20M=C3=BCller?= Date: Fri, 26 Jul 2024 11:54:57 +0200 Subject: [PATCH 1/4] Update backups.md --- docs/components/concepts/backups.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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. From 5ca51f57560b4788b71cefe0c2b9bef709eb6175 Mon Sep 17 00:00:00 2001 From: Amara Date: Fri, 26 Jul 2024 09:36:35 -0500 Subject: [PATCH 2/4] backport >8.2.4 --- versioned_docs/version-8.3/components/concepts/backups.md | 2 +- versioned_docs/version-8.4/components/concepts/backups.md | 2 +- versioned_docs/version-8.5/components/concepts/backups.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/versioned_docs/version-8.3/components/concepts/backups.md b/versioned_docs/version-8.3/components/concepts/backups.md index 96aed17483..74f9c3a245 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 one 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..74f9c3a245 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 one 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..1b2bc7f747 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 one 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. From 517ec2803ab04e84968109f6553026b0fa9d7b01 Mon Sep 17 00:00:00 2001 From: Amara Date: Fri, 26 Jul 2024 09:43:28 -0500 Subject: [PATCH 3/4] add 8.2 --- versioned_docs/version-8.2/components/concepts/backups.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/versioned_docs/version-8.2/components/concepts/backups.md b/versioned_docs/version-8.2/components/concepts/backups.md index 96aed17483..74f9c3a245 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 one 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. From b2eac501138396284dc00b7731fcb5f2d2f923eb Mon Sep 17 00:00:00 2001 From: Amara Date: Fri, 26 Jul 2024 09:50:59 -0500 Subject: [PATCH 4/4] oops --- versioned_docs/version-8.2/components/concepts/backups.md | 2 +- versioned_docs/version-8.3/components/concepts/backups.md | 2 +- versioned_docs/version-8.4/components/concepts/backups.md | 2 +- versioned_docs/version-8.5/components/concepts/backups.md | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/versioned_docs/version-8.2/components/concepts/backups.md b/versioned_docs/version-8.2/components/concepts/backups.md index 74f9c3a245..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 one hour. +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 74f9c3a245..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 one hour. +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 74f9c3a245..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 one hour. +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 1b2bc7f747..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 one hour. +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.