cb-analytics-admin
Use this skill when the user wants to inspect or manage the Analytics service's runtime — checking ingestion health, killing…
Plan and execute Couchbase backup and restore operations. Use whenever the user asks about backup, restore, cbbackupmgr, backup repository, backup archive, full backup, incremental backup, differential backup, backup schedule, retention policy, backup verification, Capella
Claude Code
$ npx -y skills add celticht32/Couchbase-Skills-for-Claude.ai --skill couchbase-backup-restore --agent claude-code
Codex
$ npx skills add celticht32/Couchbase-Skills-for-Claude.ai --skill couchbase-backup-restore -a codex -y
Cursor
$ npx skills add celticht32/Couchbase-Skills-for-Claude.ai --skill couchbase-backup-restore -a cursor -y
Gemini CLI
$ npx skills add celticht32/Couchbase-Skills-for-Claude.ai --skill couchbase-backup-restore -a gemini-cli -y
GitHub Copilot
$ npx skills add celticht32/Couchbase-Skills-for-Claude.ai --skill couchbase-backup-restore -a github-copilot -y
OpenCode
$ npx skills add celticht32/Couchbase-Skills-for-Claude.ai --skill couchbase-backup-restore -a opencode -y
Windsurf
$ npx skills add celticht32/Couchbase-Skills-for-Claude.ai --skill couchbase-backup-restore -a windsurf -y
name: couchbase-backup-restore description: "Plan and execute Couchbase backup and restore operations. Use whenever the user asks about backup, restore, cbbackupmgr, backup repository, backup archive, full backup, incremental backup, differential backup, backup schedule, retention policy, backup verification, Capella managed backup, backup to S3, backup to filesystem, restoring a bucket, restoring specific documents, admin_backup_* tools, or 'how do I back up / restore Couchbase.' Distinct from couchbase-migration-execution (one-time data migration to a new cluster) and couchbase-mcp (operating the tools). Use proactively for DR planning, RPO/RTO requirements, backup verification workflows, and pre-upgrade snapshots." license: MIT
A skill for *planning and executing* Couchbase backup and restore operations — both self-managed (cbbackupmgr) and Capella-managed.
Distinct from:
| Question | Read | |---|---| | "cbbackupmgr commands — config, backup, restore, list, merge, examine" | `references/cbbackupmgr.md` | | "Backup strategy — full vs incremental, schedules, retention, S3" | `references/strategy.md` | | "How to restore — full cluster, single bucket, single document, point-in-time" | `references/restore.md` | | "Capella managed backups — schedules, retention, restore" | `references/capella-backups.md` |
**Principle 1 — An untested backup is not a backup.** Run a restore drill regularly — quarterly at minimum, monthly for production data. `cbbackupmgr examine` lets you inspect backup contents without a full restore. A restore drill to a staging cluster is the only way to know your backups are complete and your restore procedure works.
**Principle 2 — Incremental backups depend on the full backup chain.** Couchbase incremental backups are differential (each increment contains only mutations since the prior backup). To restore to a point in time, you need the full backup plus every increment up to that point. A corrupted full backup invalidates the entire chain. Keep multiple full backup generations, not just increments.
**Principle 3 — Backup is not DR.** Backup protects against data corruption, accidental deletion, and ransomware. It does not protect against site loss with your RPO — that's what XDCR active-passive is for. Most deployments need both: XDCR for RTO (fast failover), backup for RPO (data recovery from logical errors that XDCR would have replicated).
| Task | Tool | |---|---| | List backup repositories | `admin_backup_list_repositories` | | Get repository info | `admin_backup_get_repository` | | Trigger a backup | `admin_backup_trigger_backup` | | Get backup history | `admin_backup_get_backup_info` | | Trigger a restore | `admin_backup_trigger_restore` | | Get restore status | `admin_backup_get_restore_status` |
These tools interact with the Couchbase Backup Service (available in Couchbase 7.0+ EE). For older clusters or more control, use `cbbackupmgr` CLI directly.
| Approach | RPO | RTO | Notes | |---|---|---|---| | Incremental backup hourly | ~1 hour | Hours (depends on data size) | Standard for most workloads | | Incremental backup every 15 min | ~15 min | Hours | Increases backup storage and I/O | | XDCR active-passive + backup | Near-zero (XDCR) / hours (backup) | Minutes (XDCR failover) | Best of both for production | | Capella managed (daily + auto) | Up to 24 hours | Hours | Acceptable for non-critical data |
Claude skill files for working with Couchbase — covering every major service and deployment pattern from application integration through AI applications, Kubernetes operations, mobile sync, security hardening, and analytics.
Use this skill when the user wants to inspect or manage the Analytics service's runtime — checking ingestion health, killing…
Use this skill when the user wants to manage Couchbase Capella resources through the Cloud Management API — listing organisations…
Use this skill when the user wants to inspect or configure the Couchbase cluster itself — node membership, memory quotas,…
Use this skill when the user is managing Analytics data-source links — S3, Azure Blob, GCS, or remote Couchbase links — including…
Use this skill when the user is setting up cb-analytics-mcp from scratch or troubleshooting an existing install — generating…
Use this skill when the user wants to write or improve SQL++ queries against Couchbase Analytics through cb-analytics-mcp.…
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
Ask which skill or flow fits your situation. A router over the skills in this repo.