Menú
Use when the user wants to create, list, describe, delete, export, or restore backups, or manage backup policies on Zilliz Cloud.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Use when the user reports that a Zilliz Cloud cluster or Milvus collection is unhealthy, slow, stuck, returning errors, hitting quotas, or otherwise misbehaving — or when they ask "what's wrong with...", "why is ... slow", "diagnose ...", "troubleshoot ...".
Zilliz Cloud onboarding and usage assistant. Helps users understand Zilliz Cloud, choose the right plan, estimate costs, write code, debug issues, and adopt new features like Functions, Volumes, and Global Clusters. Use this skill whenever the user asks about Zilliz Cloud — including plan selection, pricing, cost estimation, capacity planning, cluster configuration, SDK usage, schema design, search patterns, migration, troubleshooting, MCP server setup, Terraform, auto-scaling, metrics/alerts, backup/restore, or any "how do I do X with Zilliz Cloud" question. Also trigger when the user mentions keywords like: "Zilliz", "zilliz cloud", "vector database", "which plan", "serverless vs dedicated", "CU", "vCU", "Milvus cloud", "pymilvus", "collection", "embedding function", "hybrid search", "rerank", "BM25", "global cluster", "BYOC", "tiered storage", "volume", "data import", "MCP server", "partition key", or error messages from Zilliz Cloud.
Use when the user wants to check usage, view invoices, or manage payment methods on Zilliz Cloud.
Use when the user wants to create, list, describe, delete, suspend, resume, or modify Zilliz Cloud clusters.
Use when the user wants to create, list, describe, drop, rename, load, release, or manage collections and collection aliases in Milvus.
Use when the user wants to create, list, describe, or drop databases in Milvus.
| name | backup |
| description | Use when the user wants to create, list, describe, delete, export, or restore backups, or manage backup policies on Zilliz Cloud. |
--cluster-id directly.zilliz backup create --cluster-id <cluster-id>
# Optional:
# --database <database-name>
# --collection <collection-name>
# --backup-type <CLUSTER|COLLECTION>
# Or use raw JSON: --body '{...}'
zilliz backup list
# Optional:
# --project-id <filter-by-project-id>
# --cluster-id <filter-by-cluster-id>
# --creation-method <MANUAL|AUTO>
# --backup-type <CLUSTER|COLLECTION>
# Pagination: --page-size <n> --page <n>
# Fetch all pages: --all
zilliz backup describe --cluster-id <cluster-id> --backup-id <backup-id>
zilliz backup delete --cluster-id <cluster-id> --backup-id <backup-id-to-delete>
zilliz backup export \
--cluster-id <cluster-id> \
--backup-id <backup-id> \
--integration-id <storage-integration-id>
# Optional: --directory <directory>
zilliz backup restore-cluster \
--cluster-id <source-cluster-id> \
--backup-id <backup-id-to-restore> \
--project-id <target-project-id> \
--name <new-cluster-name> \
--cu-size <compute-units-for-new-cluster> \
--collection-status <LOADED|NOT_LOADED>
zilliz backup restore-collection \
--cluster-id <source-cluster-id> \
--backup-id <backup-id> \
--dest-cluster-id <destination-cluster-id>
# Or use raw JSON: --body '{"collections": [{"source": "col1", "target": "col1_restored"}]}'
zilliz backup describe-policy --cluster-id <cluster-id>
zilliz backup update-policy --cluster-id <cluster-id> --auto-backup <true|false>
# Optional:
# --frequency <frequency>
# --start-time <start-time>
# --retention-days <days-to-retain-backups>
# Or use raw JSON: --body '{...}'
Frequency: daily | weekdays | weekends | 1-7 (1=Mon, 7=Sun), e.g. 1,3,5
Start time: HH:MM or HH:MM-HH:MM (time window), e.g. 02:00 or 03:00-05:00
--collection is provided, it's a COLLECTION backup; otherwise it's a CLUSTER backup.backup describe to check progress.--integration-id for export refers to a cloud storage integration configured in the Zilliz Cloud console (see import skill for setup guidance).