-
Notifications
You must be signed in to change notification settings - Fork 182
DOC-12561 Continuous backup PITR #4138
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.1
Are you sure you want to change the base?
Changes from all commits
c5c08f5
1c47291
d743b51
44e4906
0e8a305
31efbb9
5eec3ce
a99d781
987febd
ffde6f3
e811a87
19bfd14
f76f3fd
b489b9b
0a6c053
f038fb0
5bda019
c052a8a
b25f4ea
d23144a
fe8d8f4
f00b611
c62fb79
45e4300
fcd8aff
ea725c3
b631d1b
05cb3a9
74b692a
b7fdecd
fc91254
59bed0c
b8bb407
694d668
5e96c8d
fb26e63
0ecb4f7
33be269
f08ff0e
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 | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|
@@ -39,6 +39,10 @@ Note that this restriction also protects the cluster in situations where multipl | |||||||||||||
| [#performing-an-unsafe-failover] | ||||||||||||||
| === Performing an Unsafe Failover | ||||||||||||||
|
|
||||||||||||||
| CAUTION: If you have 1 or more buckets using continuous backup, you must stop the Couchbase Server process on the node before performing an unsafe failover on it. | ||||||||||||||
| Not stopping the Couchbase Server process could result in data inconsistencies that can cause issues with the continuous backup. | ||||||||||||||
| See xref:learn:services-and-indexes/services/continuous-backup.adoc[] for more information. | ||||||||||||||
|
Comment on lines
+42
to
+44
Contributor
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
|
||||||||||||||
|
|
||||||||||||||
| In Couchbase Server 7.0 or a later version, metadata is managed by a _consensus protocol_; which achieves strong consistency by _synchronously_ replicating metadata to a majority of the nodes before considering it committed. | ||||||||||||||
| (This is described in xref:learn:clusters-and-availability/metadata-management.adoc[Metadata Management].) | ||||||||||||||
| The metadata so managed includes _topology information_. | ||||||||||||||
|
|
||||||||||||||
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -49,6 +49,11 @@ See xref:rest-api:rest-bucket-create.adoc[Creating and Editing Buckets]. | |||||
| * The CLI, using `couchbase-cli bucket-create` (to create a bucket) or `couchbase-cli bucket-edit` (to edit a bucket); specifying one or both of the parameters `history-retention-bytes` and `history-retention-seconds`. | ||||||
| See xref:cli:cbcli/couchbase-cli-bucket-create.adoc[bucket-create] and xref:cli:cbcli/couchbase-cli-bucket-edit.adoc[bucket-edit]. | ||||||
|
|
||||||
| IMPORTANT: You must enable change history on any bucket you want to back up using continuous backup. | ||||||
| Once you enable continuous backup, you cannot turn off change history for the bucket unless you turn off continuous backup first. | ||||||
| Using collection-level overrides of change history in a bucket where you have enabled continuous backup is unsupported. | ||||||
| See xref:learn:services-and-indexes/services/continuous-backup.adoc[] for more information. | ||||||
|
Contributor
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
|
||||||
|
|
||||||
| [#default-collection-setting] | ||||||
| === Default Collection-Setting | ||||||
|
|
||||||
|
|
||||||
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -36,6 +36,14 @@ To use it on a regular schedule, you must rely on an external scheduling system | |||||
| See xref:backup-restore:enterprise-backup-restore.adoc[cbbackupmgr] for more information about using the command-line tool. | ||||||
|
|
||||||
| == The Backup Service and Continuous Backup | ||||||
|
|
||||||
| In addition to the periodic backups provided by the Backup Service, you can also use the continuous backup agent to frequently back up changes to Magma buckets. | ||||||
| This backup can limit the loss of data updates that occur between full and incremental backups. | ||||||
| It also records the timestamps of when data was mutated. | ||||||
|
Contributor
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
|
||||||
| These timestamps let you perform Point-In-Time Recovery (PITR) to restore the Magma bucket's data to the state it was in at a specific moment. | ||||||
| See xref:learn:services-and-indexes/services/continuous-backup.adoc[] for more information about using continuous backup. | ||||||
|
Contributor
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-service-architecture] | ||||||
| == Backup Service Architecture | ||||||
|
|
||||||
|
|
||||||
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.