-
Notifications
You must be signed in to change notification settings - Fork 709
cloud: update backup policies and execution rules #22227
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: release-8.5
Are you sure you want to change the base?
Changes from all commits
dbdb691
0e7e99e
ccf92e7
b4d0f9a
1862cca
a7e98f0
9dbf2af
8a78915
4abb72f
fd5fb3b
3adebbb
1248d02
97e95ab
c539192
34d8259
6ff8e53
56a8077
ba00105
9887ef0
2d2636d
4ac3a13
2734b54
abc7965
6a31fdc
82d7a9c
9fa36dd
9b49cab
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|
@@ -30,49 +30,39 @@ Backup files can originate from the following sources: | |||||||||||||||
|
|
||||||||||||||||
| ## Automatic backups | ||||||||||||||||
|
|
||||||||||||||||
| TiDB Cloud automatically backs up your instance data, letting you restore data from a backup snapshot to minimize data loss in the event of a disaster. | ||||||||||||||||
| {{{ .premium }}} offers enhanced automatic backup capabilities, combining high-frequency snapshots with log backups to maximize data reliability for production environments. | ||||||||||||||||
|
|
||||||||||||||||
| ### Learn about the backup setting | ||||||||||||||||
| ### Automatic backup policies | ||||||||||||||||
|
|
||||||||||||||||
| Compared with {{{ .starter }}} clusters and {{{ .essential }}} clusters, {{{ .premium }}} offers enhanced backup capabilities, including longer retention and hourly backup support. | ||||||||||||||||
| {{{ .premium }}} instances provide a comprehensive data protection strategy through a multi-layered backup architecture: | ||||||||||||||||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||||||||||||
|
|
||||||||||||||||
| | Backup setting | {{{ .starter }}} (free) | {{{ .starter }}} (with spending limit > 0) | {{{ .essential }}} | {{{ .premium }}} | | ||||||||||||||||
| |------------------|--------------------------|---------------------------------------------|--------------------|------------------| | ||||||||||||||||
| | Backup Cycle | Daily | Daily | Daily | Daily + Hourly | | ||||||||||||||||
| | Backup Retention | 1 day | 30 days | 30 days | Up to 33 days | | ||||||||||||||||
| | Backup Time | Fixed time | Configurable | Configurable | Configurable | | ||||||||||||||||
| - Point-in-Time Recovery (PITR) | ||||||||||||||||
| - Retention period: 7 days. | ||||||||||||||||
|
Comment on lines
+39
to
+40
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
Replcae L39-49 with a table with a table to make it easier to compare backup type. |
||||||||||||||||
| - Restore granularity: supports restoration to any specific moment within the 7-day retention window. | ||||||||||||||||
|
|
||||||||||||||||
| - **Backup Cycle** determines how frequently backups are created. | ||||||||||||||||
| - Hourly backup snapshot | ||||||||||||||||
| - Retention period: 7 days. | ||||||||||||||||
| - Restore granularity: supports restoration to any specific hourly snapshot generated within the 7-day retention window | ||||||||||||||||
|
|
||||||||||||||||
| - Premium instances support both **daily** and **hourly** backups. | ||||||||||||||||
| - The **default** is **hourly backups**. | ||||||||||||||||
| - Daily backup snapshot | ||||||||||||||||
| - Retention period: 33 days. | ||||||||||||||||
| - Restore granularity: supports restoration to any daily snapshot (captured at 0:00 UTC by default) within the 33-day retention window. | ||||||||||||||||
|
|
||||||||||||||||
| - **Backup Retention** is the duration for which backups are retained. Expired backups cannot be restored. | ||||||||||||||||
| ### Backup execution rules | ||||||||||||||||
|
|
||||||||||||||||
| - Premium instances can retain backups for up to **33 days**. | ||||||||||||||||
| - Backup cycle: {{{ .premium }}} instances support both daily and hourly automatic backups. | ||||||||||||||||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||||||||||||
|
|
||||||||||||||||
| - **Backup Time** is the scheduled start time for backups. | ||||||||||||||||
| - Backup schedule: | ||||||||||||||||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||||||||||||
| - Hourly backup: always runs at the start of every hour (on the hour). | ||||||||||||||||
| - Daily backup: executed daily at 0:00 UTC. | ||||||||||||||||
| - Currently, backup time management or customization is not supported. | ||||||||||||||||
|
Comment on lines
+56
to
+58
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||||||||||||
|
|
||||||||||||||||
| - For Premium instances, **daily backups** can be configured to start at a preferred time (in 30-minute intervals), while **hourly backups** always run on the hour. | ||||||||||||||||
| - **Retention mechanism**: backups that exceed their retention period (7 days or 33 days) automatically expire and cannot be restored. | ||||||||||||||||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||||||||||||
|
|
||||||||||||||||
| ### Configure the backup settings | ||||||||||||||||
|
|
||||||||||||||||
| To configure backups for a {{{ .premium }}} instance, perform the following steps: | ||||||||||||||||
|
|
||||||||||||||||
| 1. Navigate to the [**Backup**](#view-the-backup-page) page of your TiDB instance. | ||||||||||||||||
|
|
||||||||||||||||
| 2. Click **Backup Setting**. This will open the **Backup Setting** window, where you can configure automatic backup options. | ||||||||||||||||
|
|
||||||||||||||||
| 3. In **Backup Cycle**, choose between the **Hourly Backup** and **Daily Backup** tabs: | ||||||||||||||||
|
|
||||||||||||||||
| - **Hourly Backup** (default): | ||||||||||||||||
| - Runs **on the hour**. | ||||||||||||||||
| - You can configure **Backup Retention** (1–33 days). | ||||||||||||||||
| - **Daily Backup**: | ||||||||||||||||
| - Runs at a configurable time in **30-minute intervals**. | ||||||||||||||||
| - You can configure both **Backup Retention** (1–33 days) and **Backup Time**. | ||||||||||||||||
|
|
||||||||||||||||
| 4. Click **Save** to save your settings. | ||||||||||||||||
| > **Note:** | ||||||||||||||||
| > | ||||||||||||||||
| > - Storage costs for automatic backups are calculated based on your backup data volume and retention duration. | ||||||||||||||||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||||||||||||
| > - To extend a backup retention period beyond the default limits, contact [TiDB Cloud Support](https://docs.pingcap.com/tidbcloud/tidb-cloud-support). | ||||||||||||||||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||||||||||||
|
|
||||||||||||||||
| ### Delete backup files | ||||||||||||||||
|
|
||||||||||||||||
|
|
||||||||||||||||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.