Does cbbackupmgr use DCP

Couchbase Server
,
1

Does cbbackupmgr use DCP to fetch data ? Since DCP is not aware of scopes or collections, will requesting for a single scope stream data of bucket and we do read-discard in cbbackupmgr ?

Also any plans to support editing backup repo to add or remove objects ?

2

Hi @zxcvmnb,

Does cbbackupmgr use DCP to fetch data ?

Yes, that’s correct.

Since DCP is not aware of scopes or collections, will requesting for a single scope stream data of bucket and we do read-discard in cbbackupmgr ?

cbbackupmgr uses collection-level stream filters (as described here) meaning we don’t “read-discard”.

Also any plans to support editing backup repo to add or remove objects ?

Please could you clarify what you mean by “objects” in this case?

Thanks,
James

3

Just as an FYI – with the cbbackupmgr CLI, you can remove backups from a backup repository using the “cbbackupmgr remove” sub-command. Documentation link below:

https://docs.couchbase.com/server/current/backup-restore/cbbackupmgr-remove.html

For example, if the “cbbackupmgr info -a /mypath/cb_backups -r test_repo1” command shows the listing below, you could remove any of the backups listed using “cbbackupmgr remove” sub-command options. (One thing to be aware of is that it will also let you remove a full backup even if there are dependent incremental backups.)

% cbbackupmgr info -a /mypath/cb_backups  -r test_repo1
Name       | Size      | # Backups | Encrypted |
test_repo1 | 115.64MiB | 3         | false     |

+  Backup                           | Size     | Type | Source    | Cluster UUID                     | Range | Events | Aliases | Complete |
+  2022-07-19T09_11_42.55471-07_00  | 51.69MiB | FULL | localhost | 0544ec3c9cf241d8cf9c63a38847bbe4 | N/A   | 0      | 0       | true     |
+  2022-07-19T09_11_57.474436-07_00 | 51.69MiB | FULL | localhost | 0544ec3c9cf241d8cf9c63a38847bbe4 | N/A   | 0      | 0       | true     |
+  2022-07-19T09_12_51.255166-07_00 | 12.27MiB | INCR | localhost | 0544ec3c9cf241d8cf9c63a38847bbe4 | N/A   | 0      | 0       | true     |

For example, to remove the first full backup, I could run:

% cbbackupmgr remove -a /mypath/cb_backups  -r test_repo1 --start 2022-07-19T09_11_42.55471-07_00 --end 2022-07-19T09_11_42.55471-07_00
Backup `2022-07-19T09_11_42.55471-07_00` deleted successfully from archive `/mypath/cb_backups` repository `test_repo1`

% cbbackupmgr info -a /mypath/cb_backups  -r test_repo1
Name       | Size     | # Backups | Encrypted |
test_repo1 | 63.96MiB | 2         | false     |

+  Backup                           | Size     | Type | Source    | Cluster UUID                     | Range | Events | Aliases | Complete |
+  2022-07-19T09_11_57.474436-07_00 | 51.69MiB | FULL | localhost | 0544ec3c9cf241d8cf9c63a38847bbe4 | N/A   | 0      | 0       | true     |
+  2022-07-19T09_12_51.255166-07_00 | 12.27MiB | INCR | localhost | 0544ec3c9cf241d8cf9c63a38847bbe4 | N/A   | 0      | 0       | true     |