Use Backup Manager when you want to ingest Couchbase data from existing backup archives. This method is useful for point-in-time recovery scenarios.

Before you begin

  • Couchbase backup exists in staging or is accessible via NFS

  • Backup structure is compatible with cbbackupmgr

  • Backup location and repository name are known (verify with: /opt/couchbase/bin/cbbackupmgr info -a <archive> -r <repo>)

  • The staging host meets the 2026.1.0 Couchbase connector requirements, including Python 3.11 and vSDK 5.0.1.

Procedure

  1. Navigate to Data > Data Management > dSources

  2. Select + dSource

  3. Select Couchbase source config

  4. Configure ingestion settings

    1. dSource type: Couchbase Backup Manager

    2. Staging host and port

    3. Mount path

  5. Configure backup parameters

    1. Backup location – Parent directory containing backups. Example: If backups are in /u01/backups/repo/, enter /u01/backups

    2. Archive name – Directory name containing the backup repository. Example: repo (for backups in /u01/backups/repo/). Leave empty to auto-discover latest backups in timestamp format (YYYYMMDDHHMMSS)

    3. Repository name – Internal repository identifier used by cbbackupmgr when the backup was created. Example: delphix (used with: cbbackupmgr backup -a <location> -r delphix)

  6. Configure cluster settings (same as XDCR):

    1. RAM sizes (Cluster, Index, FTS)

    2. Cluster name

    3. Admin credentials

  7. Configure bucket settings

    1. Bucket size:

      • 0 – Inherit bucket size from backup (recommended)

      • Any positive integer (MB) – Override all buckets to use this size

  8. Select Submit

During Backup Manager linking

  • Validates backup structure and accessibility

  • Mounts storage for backup access

  • Restores Couchbase cluster on staging using backup data

  • Builds snapshot baseline for VDB provisioning

Result

A dSource is created from backup data and is ready for snapshots and VDB provisioning.

If linking fails

If dSource linking encounters errors, check the following:

  • Backup Manager specific:

    • Verify backup path exists and backup files are accessible

    • Confirm backup structure is valid with: cbbackupmgr info -a <location> -r <repo>

  • Common issues:

    • Mount path inaccessible or not empty

    • SSH access issues to staging host

    • Couchbase binaries missing or wrong version on staging

    • Port conflicts or firewall blocking connections

Review Continuous Data Engine logs and Couchbase instance logs at /opt/couchbase/var/lib/couchbase/logs on staging host for detailed error messages.

Last updated
Oct 9, 2026