DOC-12561 Continuous backup PITR by ggray-cb · Pull Request #4138 · couchbase/docs-server

ggray-cb · 2026-07-02T13:14:25Z

Adds documentation for Continuous backup and point-in-time recovery,

The links in the following changes led to the preview site. You will need the Docs Team credentials on Confluence.

Also addresses DOC-14623 which asked for addinitional information about PITR performance.

New pages added:

Continuous Backup — Concepts page for Continuous Backup.
Manage Continuous Backup — How to configure and manage continuous backup
Manage Point-in-Time Recovery — How to use PITR to restore data to a specific point in time
Monitor Continuous Backup — How to monitor continuous backup status

Existing pages updated:

Backup Service — Notes added referencing the new continuous backup capability
Install Ports and Server Processes — Port/process entry added for cbcontbk
What's New — Continuous Backup and PITR announced as new features

NOTE: Known issue with these documents is that there are places where it should link to the credential store documentation. However, those documents have not been written yet. I've added DOC-14531 to track this needed update.

…e service page.

* Added minitor continuous backup. * Updated metrics. * Finished draft of manage continuous backup.

…he install section.

Copilot

Pull request overview

Adds Couchbase Server 8.1 documentation and reference updates for the new Continuous Backup + Point-in-Time Recovery (PITR) capabilities, including new Learn/Manage pages, navigation entries, and supporting operational reference updates (ports/processes/metrics metadata).

Changes:

Introduces new Learn + Manage documentation for continuous backup and PITR, plus example command/log snippets.
Updates site navigation and related “new features”/cross-reference pages to surface continuous backup.
Extends metrics metadata and operational reference docs (install ports + server processes) to reflect new/updated functionality.

Reviewed changes

Copilot reviewed 19 out of 20 changed files in this pull request and generated 23 comments.

Show a summary per file

File	Description
preview/DOC-12561_Continuous_backup_PITR.yml	Adds a preview build config enabling the `backup` content source for the DOC-12561 preview.
modules/ROOT/nav.adoc	Adds nav entries for the new continuous backup/PITR learn + manage pages.
modules/metrics-reference/attachments/n1ql_metrics_metadata.json	Adds/adjusts SQL++ (N1QL) metrics metadata entries.
modules/metrics-reference/attachments/kv_metrics_metadata.json	Adds/adjusts KV metrics metadata (including continuous backup/magma/fusion-related metrics).
modules/metrics-reference/attachments/index_metrics_metadata.json	Adds new index metrics metadata for vector-related index counts.
modules/metrics-reference/attachments/goxdcr_metrics_metadata.json	Updates XDCR metrics help/notes and adjusts a metric type/version entry.
modules/metrics-reference/attachments/fts_metrics_metadata.json	Adds new FTS metrics metadata for vector indexes in CPU/GPU memory.
modules/metrics-reference/attachments/cm_metrics_metadata.json	Adds a new CM telemetry metric metadata entry.
modules/manage/pages/manage-backup-and-restore/monitor-continuous-backup.adoc	New “monitor continuous backup” operational doc page.
modules/manage/pages/manage-backup-and-restore/manage-pitr.adoc	New PITR management doc page.
modules/manage/pages/manage-backup-and-restore/manage-continuous-backup.adoc	New “configure/manage continuous backup” doc page.
modules/manage/examples/continuous-backup.sh	Adds example `cbcontbk` CLI snippets referenced by the Manage docs.
modules/manage/examples/continuous-backup.log	Adds example output referenced by the Manage docs.
modules/learn/pages/services-and-indexes/services/continuous-backup.adoc	New Learn overview page describing continuous backup + PITR concepts.
modules/learn/pages/services-and-indexes/services/backup-service.adoc	Adds a section linking Backup Service to continuous backup/PITR.
modules/learn/pages/data/change-history.adoc	Adds guidance tying change history requirements to continuous backup usage.
modules/learn/pages/clusters-and-availability/hard-failover.adoc	Adds a caution about unsafe failover behavior when continuous backup is enabled.
modules/introduction/partials/new-features-81.adoc	Adds 8.1 release notes bullets for continuous backup + PITR.
modules/install/pages/server-processes.adoc	Documents the `cbcontbk` process and normalizes path formatting in the process table.
modules/install/pages/install-ports.adoc	Adds port 9125 and documents the `cbcontbk` port usage.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

matthallcb

LGTM

Copilot

Pull request overview

Copilot reviewed 19 out of 20 changed files in this pull request and generated 14 comments.

Comments suppressed due to low confidence (1)

modules/metrics-reference/attachments/kv_metrics_metadata.json:993

Spelling: "emphemeral" should be "ephemeral".

    "help": "When true, DCP backfills will be checked for progress. Any backfill which makes no progress for dcp_backfill_idle_limit_seconds will be subject to further checks. If the directory referenced by dbname is over dcp_backfill_idle_disk_threshold percent used and cancelling the backfill will free disk space, the scan cancels and the associated DCP stream will end with reason slow. This is ignored for emphemeral buckets",

…ous backup settings.

Copilot

Pull request overview

Copilot reviewed 21 out of 22 changed files in this pull request and generated no new comments.

Comments suppressed due to low confidence (18)

modules/manage/pages/manage-backup-and-restore/manage-continuous-backup.adoc:170

Step 1 under "Configure Continuous Backup Using the Web Console" has a typo ("Ic") and the second sentence is not formatted as part of the numbered list. This will likely render as a stray paragraph instead of an instruction step.

. Ic creating a new bucket, click  menu:Buckets[Add Bucket].  
If editing an existing bucket, click *Buckets*, expand an existing bucket, and click *Edit*.

modules/manage/pages/manage-backup-and-restore/manage-continuous-backup.adoc:208

KMS prefix list contains a typo: azurekeyvalue should be azurekeyvault (consistent with the Web Console section and other backup docs).

    This URI must start with `awskms`, `azurekeyvalue`, or `gcpkms`.

modules/manage/pages/manage-backup-and-restore/manage-continuous-backup.adoc:234

Grammar: "then Backup Service" should be "the Backup Service", and adding commas improves readability.

* `--continuous-backup-interval`: How frequently in minutes then Backup Service copies data to the continuous backup location.

modules/manage/pages/manage-backup-and-restore/manage-continuous-backup.adoc:240

KMS prefix list contains a typo: azurekeyvalue should be azurekeyvault.

    This URI must start with `awskms`, `azurekeyvalue`, or `gcpkms`.

modules/rest-api/pages/rest-bucket-create.adoc:102

Trailing whitespace after the parameter value placeholder is inconsistent with surrounding lines and can cause noisy diffs.

  -d continuousBackupKmKeyUrl=<string>

modules/learn/pages/services-and-indexes/services/continuous-backup.adoc:121

Grammar: "a higher volume mutations" is missing "of".

You can choose to have a shorter continuous backup interval on vital buckets that have a higher volume mutations.

modules/learn/pages/services-and-indexes/services/continuous-backup.adoc:202

Typo: "to a point it time" should be "to a point in time".

For continuous backup to be able to reliably restore a bucket to a point it time, it must have a consistent history of the changes made to a bucket.

modules/metrics-reference/attachments/kv_metrics_metadata.json:993

Spelling: "emphemeral" should be "ephemeral".

    "help": "When true, DCP backfills will be checked for progress. Any backfill which makes no progress for dcp_backfill_idle_limit_seconds will be subject to further checks. If the directory referenced by dbname is over dcp_backfill_idle_disk_threshold percent used and cancelling the backfill will free disk space, the scan cancels and the associated DCP stream will end with reason slow. This is ignored for emphemeral buckets",

modules/manage/pages/manage-backup-and-restore/manage-pitr.adoc:91

These bullet points are missing "is", which makes the list read ungrammatically.

* `--tmp-dir` a temporary directory the `cbcontbk` can use when restoring data.
* `-l` the continuous backup storage location.

modules/manage/pages/manage-backup-and-restore/manage-continuous-backup.adoc:206

The REST API section says you must supply "1 of the following" encryption/KMS settings, but two items are listed and the CLI section below explicitly says "both of the following". This is internally inconsistent and unclear for readers.

* `continuousBackupRetentionPeriod`: the number of hours the Backup Service keeps the continuous backup data before purging it. 
This value sets how far back in time you can use point-in-time recovery (PITR).
* If you have enabled encryption at rest for the bucket, you must supply 1 of the following:

modules/manage/pages/manage-backup-and-restore/manage-continuous-backup.adoc:209

Parameter description should start with a capital letter ("the name" -> "The name") for consistency with other entries in the list.

** `continuousBackupKmCredId`: the name of a credential in the Couchbase Server credential store that grants the Backup Service access to a KMS to manage its encryption keys.

modules/manage/pages/manage-backup-and-restore/manage-continuous-backup.adoc:230

Grammar: "This value must a string" is missing "be".

This value must a string containing either an absolute path to an NFS mount point mounted on every node or a cloud storage URI.

modules/rest-api/pages/rest-bucket-create.adoc:97

Parameter syntax is missing a space before the closing bracket (consistent style elsewhere is [ true | false ]).

This issue also appears on line 102 of the same file.

  -d continuousBackupEnabled=[ true | false]

modules/rest-api/pages/rest-bucket-create.adoc:1668

Sentence should start with a capital letter ("the number" -> "The number").

the number of hours the Backup Service keeps the continuous backup data before purging it.

modules/rest-api/pages/rest-bucket-create.adoc:1676

KMS prefix list contains a typo: azurekeyvalue should be azurekeyvault (consistent with other docs).

This URI must start with `awskms`, `azurekeyvalue`, or `gcpkms`.

modules/learn/pages/services-and-indexes/services/continuous-backup.adoc:88

Typo: "verses" should be "versus".

This issue also appears in the following locations of the same file:

line 121
line 202

When setting the interval, you must consider potential data loss verses the potential increased storage cost.

modules/install/pages/server-processes.adoc:32

Path formatting is inconsistent: other Linux process entries use a trailing / for directories, but cbcontbk does not. Keeping this consistent avoids confusion about whether the value is a directory vs file path.

| `/opt/couchbase/bin`

modules/manage/pages/manage-backup-and-restore/manage-pitr.adoc:84

Grammar: missing article in "to point in time".

This issue also appears on line 90 of the same file.

You use the `cbcontbk` command line tool to restore a bucket backed up using continuous backup to point in time.

Copilot

Pull request overview

Copilot reviewed 21 out of 22 changed files in this pull request and generated no new comments.

Comments suppressed due to low confidence (18)

modules/manage/pages/manage-backup-and-restore/manage-continuous-backup.adoc:234

Typo: “then Backup Service” should be “the Backup Service”.

* `--continuous-backup-interval`: How frequently in minutes then Backup Service copies data to the continuous backup location.

modules/manage/pages/manage-backup-and-restore/manage-continuous-backup.adoc:240

The KMS scheme list contains azurekeyvalue, which appears to be a typo (elsewhere it’s azurekeyvault).

    This URI must start with `awskms`, `azurekeyvalue`, or `gcpkms`.

modules/metrics-reference/attachments/kv_metrics_metadata.json:993

Spelling: “emphemeral” should be “ephemeral”.

    "help": "When true, DCP backfills will be checked for progress. Any backfill which makes no progress for dcp_backfill_idle_limit_seconds will be subject to further checks. If the directory referenced by dbname is over dcp_backfill_idle_disk_threshold percent used and cancelling the backfill will free disk space, the scan cancels and the associated DCP stream will end with reason slow. This is ignored for emphemeral buckets",

modules/rest-api/pages/rest-bucket-create.adoc:103

In the curl syntax block, the new continuous backup lines have inconsistent bracket spacing compared to other parameters and include trailing whitespace. Aligning the formatting improves readability and consistency.

  -d continuousBackupEnabled=[ true | false] 
  -d continuousBackupLocation=<string>
  -d continuousBackupCloudStorageCredId=<string>
  -d continuousBackupInterval=<integer>
  -d continuousBackupRetentionPeriod=<integer>
  -d continuousBackupKmKeyUrl=<string> 
  -d continuousBackupKmCredId=<string>

modules/rest-api/pages/rest-bucket-create.adoc:1669

The continuousBackupRetentionPeriod definition starts with a lowercase “the”. Capitalize it to match the surrounding parameter descriptions.

`continuousBackupRetentionPeriod`:: 
the number of hours the Backup Service keeps the continuous backup data before purging it. 
This value sets how far back in time you can use point-in-time recovery (PITR).

modules/rest-api/pages/rest-bucket-create.adoc:1676

The KMS scheme list contains azurekeyvalue, which appears to be a typo (elsewhere in the same PR it’s written as azurekeyvault). This should be consistent and accurate because users will copy/paste it.

The URI for the KMS key the Backup Service uses to manage the encryption key it uses to encrypt data encryption keys. 
This URI must start with `awskms`, `azurekeyvalue`, or `gcpkms`.

modules/manage/pages/manage-backup-and-restore/manage-continuous-backup.adoc:170

Step text has typos (“Ic”), extra spaces, and a missing space after “click”. This reads like an instruction users will follow verbatim, so it should be corrected.

. Ic creating a new bucket, click  menu:Buckets[Add Bucket].  
If editing an existing bucket, click *Buckets*, expand an existing bucket, and click *Edit*.

modules/manage/pages/manage-backup-and-restore/manage-continuous-backup.adoc:209

This section says “you must supply 1 of the following” but then lists a KMS key URL and a credential ID, which are not alternatives (and the CLI section below says “both”). Please make the requirement consistent and fix the azurekeyvalue typo.

* If you have enabled encryption at rest for the bucket, you must supply 1 of the following:
** `continuousBackupKmKeyUrl`: The URI for the KMS key the Backup Service uses to manage the encryption key it uses to encrypt data encryption keys. 
    This URI must start with `awskms`, `azurekeyvalue`, or `gcpkms`.
** `continuousBackupKmCredId`: the name of a credential in the Couchbase Server credential store that grants the Backup Service access to a KMS to manage its encryption keys.

modules/manage/pages/manage-backup-and-restore/manage-continuous-backup.adoc:230

Grammar: “This value must a string …” is missing “be”.

This value must a string containing either an absolute path to an NFS mount point mounted on every node or a cloud storage URI.

modules/learn/pages/services-and-indexes/services/continuous-backup.adoc:88

“verses” should be “versus” in this context.

When setting the interval, you must consider potential data loss verses the potential increased storage cost.

modules/learn/pages/services-and-indexes/services/continuous-backup.adoc:202

Typo: “point it time” should be “point in time”.

For continuous backup to be able to reliably restore a bucket to a point it time, it must have a consistent history of the changes made to a bucket.

modules/learn/pages/services-and-indexes/services/continuous-backup.adoc:213

Grammar: “decrypt older the data” should be “decrypt older data”.

Therefore, the current DEKs are usually not the same ones continuous backup needs to decrypt older the data in its backups.

modules/manage/pages/manage-backup-and-restore/manage-pitr.adoc:73

Extra punctuation: the sentence ends with “information..”.

See <<#pitr_force_updates>> for more information..

modules/install/pages/install-ports.adoc:356

Trailing whitespace in the port description (“Continuous backup ”).

| Continuous backup

modules/install/pages/server-processes.adoc:32

The path formatting is inconsistent: most entries use /opt/couchbase/bin/ but cbcontbk is /opt/couchbase/bin. Standardizing avoids implying different paths.

| `/opt/couchbase/bin`

modules/manage/examples/continuous-backup.sh:7

Trailing whitespace at the end of the curl line can cause copy/paste issues in some shells and fails some linters.

     -d continuousBackupInterval=10

modules/manage/pages/manage-backup-and-restore/monitor-continuous-backup.adoc:32

This xref targets continuous-backup:cbcontbk.adoc, but there’s no cbcontbk.adoc page in this repository and no other existing references to a continuous-backup component. Unless that component/page is provided elsewhere at build time, this will render as a broken link.

See the xref:continuous-backup:cbcontbk.adoc[`cbcontbk`] documentation for details.

modules/manage/pages/manage-backup-and-restore/manage-pitr.adoc:105

This xref targets continuous-backup:cbcontbk.adoc, but there’s no cbcontbk.adoc page in this repository and no other existing references to a continuous-backup component. Unless that component/page is provided elsewhere at build time, this will render as a broken link.

See the documentation for xref:continuous-backup:cbcontbk.adoc[`cbcontbk`] for details.

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

sarahlwelton

I'm leaving a lot of repetitive comments around some style nits... I haven't gotten to the last few files because this is already a lot of comments, but maybe call this good for a first pass, clean up some of the repetitive issues, and then I can take a look at the remaining few files? There's just some missing sections, word order, etc. that I keep bringing up that I think you can make a judgment call on your own about fixing :)

Just reach out if you want to discuss.

sarahlwelton · 2026-07-30T14:28:34Z

+This backup can limit the loss of data updates that occur between full and incremental backups.
+In addition to backing up data, it also backs up the timestamps of mutations.
+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.


Suggested change

See xref:learn:services-and-indexes/services/continuous-backup.adoc[] for more information.

For more information, see xref:learn:services-and-indexes/services/continuous-backup.adoc[].

sarahlwelton · 2026-07-30T14:29:43Z

+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.


Suggested change

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.

CAUTION: If you have 1 or more buckets using continuous backup, you must stop the Couchbase Server process on the node before you can perform an unsafe failover on that node.

Not stopping the Couchbase Server process could result in data inconsistencies that can cause issues with the continuous backup.

For more information, see xref:learn:services-and-indexes/services/continuous-backup.adoc[].

sarahlwelton · 2026-07-30T14:30:21Z

+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.


Suggested change

See xref:learn:services-and-indexes/services/continuous-backup.adoc[] for more information.

For more information, see xref:learn:services-and-indexes/services/continuous-backup.adoc[].

sarahlwelton · 2026-07-30T14:30:50Z

+
+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.


Suggested change

It also records the timestamps of when data was mutated.

Continuous backup also records the timestamps of when data was mutated.

sarahlwelton · 2026-07-30T14:31:13Z

+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.
+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.


Suggested change

See xref:learn:services-and-indexes/services/continuous-backup.adoc[] for more information about using continuous backup.

For more information about using continuous backup, see xref:learn:services-and-indexes/services/continuous-backup.adoc[].

sarahlwelton · 2026-07-30T14:57:14Z

+You can enable continuous backup when creating a bucket or editing it via the REST-API.
+
+Whether you're creating a new bucket or editing an existing bucket, make a POST call to the `/pools/default/buckets/<bucket-name>` REST API endpoint.
+Set the following:


I'm wondering if this part should be a table with "Setting", "Description", "Example" instead of a list?

sarahlwelton · 2026-07-30T14:58:03Z

+
+Use the `couchbase-cli` tool's `bucket create` or `bucket-edit` command to change the continuous backup settings for the bucket.
+
+Use the following arguments to configure continuous backup:


Same thing, change this to a table instead of a bullet list?

sarahlwelton · 2026-07-30T14:58:42Z

+              --continuous-backup-retention-period 270
+```
+
+See the documentation for the `couchbase-cli` tool's xref:cli:cbcli/couchbase-cli-bucket-create.adoc[] and xref:cli:cbcli/couchbase-cli-bucket-edit.adoc[] commands for more information about creating and editing buckets using the command line.


Suggested change

See the documentation for the `couchbase-cli` tool's xref:cli:cbcli/couchbase-cli-bucket-create.adoc[] and xref:cli:cbcli/couchbase-cli-bucket-edit.adoc[] commands for more information about creating and editing buckets using the command line.

For more information about how to create and edit buckets using the command line, see `couchbase-cli` tool's xref:cli:cbcli/couchbase-cli-bucket-create.adoc[] and xref:cli:cbcli/couchbase-cli-bucket-edit.adoc[] commands.

sarahlwelton · 2026-07-30T14:59:25Z

+
+You can turn off continuous backup using the Couchbase Server Web Console, REST API, or command line:
+
+Using the Couchbase Server Web Console::


I would personally set this to a tabbed block if you're going to go this route, and not just use headings like previously.

sarahlwelton · 2026-07-30T14:59:41Z

+              --username $USERNAME --password $PASSWORD \
+              --bucket travel-sample \
+              --continuous-backup-enabled 0
+```


No Next Steps?

sarahlwelton

I'm leaving a lot of repetitive comments around some style nits... I haven't gotten to the last few files because this is already a lot of comments, but maybe call this good for a first pass, clean up some of the repetitive issues, and then I can take a look at the remaining few files? There's just some missing sections, word order, etc. that I keep bringing up that I think you can make a judgment call on your own about fixing :)

Just reach out if you want to discuss.

…on of KMS to Key Management System.

ggray-cb added 7 commits June 24, 2026 13:26

Initial in-progress commit.

c5c08f5

Initial draft pf continuoud backup concepts page. Added note on chang…

1c47291

…e service page.

Draft of the manage continuous backup page.

d743b51

* In progress on managing PITR.

44e4906

* Added minitor continuous backup. * Updated metrics. * Finished draft of manage continuous backup.

Wrapped up draft of PITR page.

0e8a305

Added the port # for cbcontbk to the list of ports and processes in t…

31efbb9

…he install section.

Added link to introduction.

5eec3ce

ggray-cb requested a review from Copilot July 2, 2026 13:14

Copilot started reviewing on behalf of ggray-cb July 2, 2026 13:15 View session

Copilot AI reviewed Jul 2, 2026

View reviewed changes

ggray-cb and others added 20 commits July 2, 2026 09:40

Potential fix for pull request finding

a99d781

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

Fixing anchor link

987febd

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

Fixing link

ffde6f3

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

Typo fix and fixing broken link

e811a87

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

Fixing incorrect anchor

19bfd14

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

Typo fix

f76f3fd

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

Removing stray step

b489b9b

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

Typo fix

0a6c053

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

Fixing accidental Markdown

f038fb0

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

Remove accidental Markdown

5bda019

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

Remove duplicate word

c052a8a

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

Fixing typo

b25f4ea

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

Fixing command name

d23144a

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

Fixing typo

fe8d8f4

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

Yet more Markdown

f00b611

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

Fixing anchor

c62fb79

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

Fixing typo

45e4300

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

Add missing word

fcd8aff

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

Fixing typo

ea725c3

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

Yet more markdown

b631d1b

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

ggray-cb requested a review from TimLFletcher July 2, 2026 15:23

matthallcb reviewed Jul 3, 2026

View reviewed changes

Updates based on Matt's feedback.

74b692a

matthallcb reviewed Jul 22, 2026

View reviewed changes

Comment thread modules/manage/pages/manage-backup-and-restore/manage-continuous-backup.adoc

More changes based on Matt's feedback, plus some general edits.

b7fdecd

ggray-cb requested a review from matthallcb July 24, 2026 14:50

matthallcb approved these changes Jul 24, 2026

View reviewed changes

Minor consistency changes

fc91254

ggray-cb requested a review from Copilot July 27, 2026 14:20

Copilot started reviewing on behalf of ggray-cb July 27, 2026 14:21 View session

Copilot AI reviewed Jul 27, 2026

View reviewed changes

ggray-cb added 3 commits July 27, 2026 12:03

Fixes based on CoPilot review. Also some additional cleanup and tweaks.

59bed0c

Just realized I forgot to update the REST API section for the continu…

b8bb407

…ous backup settings.

More minor fixes

694d668

ggray-cb requested a review from Copilot July 28, 2026 15:06

Copilot started reviewing on behalf of ggray-cb July 28, 2026 15:07 View session

Copilot AI reviewed Jul 28, 2026

View reviewed changes

Changes to address DOC-14523

5e96c8d

ggray-cb requested a review from Copilot July 29, 2026 13:32

Copilot started reviewing on behalf of ggray-cb July 29, 2026 13:32 View session

Copilot AI reviewed Jul 29, 2026

View reviewed changes

ggray-cb and others added 4 commits July 29, 2026 14:04

Misc issues found by CoPilot.

fb26e63

Apply suggestions from code review

0ecb4f7

Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>

Updating concept doc with the CAS check information from DOC-14523.

33be269

Weird formatting issue with text between monospace text.

f08ff0e

ggray-cb requested a review from a team July 30, 2026 12:49

sarahlwelton requested changes Jul 30, 2026

View reviewed changes

ggray-cb added 2 commits July 30, 2026 15:25

Updates based on Sarah's feedback: header fixes and xref wording.

00eccc5

Addressed more feedback. Added See Also. Also fixed incorrect expansi…

37cff6e

…on of KMS to Key Management System.

	See xref:learn:services-and-indexes/services/continuous-backup.adoc[] for more information.
	For more information, see xref:learn:services-and-indexes/services/continuous-backup.adoc[].

	It also records the timestamps of when data was mutated.
	Continuous backup also records the timestamps of when data was mutated.

	See xref:learn:services-and-indexes/services/continuous-backup.adoc[] for more information about using continuous backup.
	For more information about using continuous backup, see xref:learn:services-and-indexes/services/continuous-backup.adoc[].


		Use the `couchbase-cli` tool's `bucket create` or `bucket-edit` command to change the continuous backup settings for the bucket.

		Use the following arguments to configure continuous backup:

	See the documentation for the `couchbase-cli` tool's xref:cli:cbcli/couchbase-cli-bucket-create.adoc[] and xref:cli:cbcli/couchbase-cli-bucket-edit.adoc[] commands for more information about creating and editing buckets using the command line.
	For more information about how to create and edit buckets using the command line, see `couchbase-cli` tool's xref:cli:cbcli/couchbase-cli-bucket-create.adoc[] and xref:cli:cbcli/couchbase-cli-bucket-edit.adoc[] commands.


		You can turn off continuous backup using the Couchbase Server Web Console, REST API, or command line:

		Using the Couchbase Server Web Console::

Uh oh!

Conversation

ggray-cb commented Jul 2, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

matthallcb left a comment

Choose a reason for hiding this comment

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Uh oh!

sarahlwelton left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

sarahlwelton left a comment

Choose a reason for hiding this comment

ggray-cb commented Jul 2, 2026 •

edited

Loading