backup_create
Make an encrypted backup of one of the user's servers now, through Termalin's backup job for that server, and wait for it (up to about a minute; a longer one keeps running and shows up in backup_list). Call it BEFORE a risky change — a migration, a config rewrite, a bulk delete — and say so in 'label'. A job can hold folders and databases (PostgreSQL, MySQL/MariaDB, also inside a Docker container) — the archive then has a .sql dump of each. The server needs a confirmed backup job: if it has none, propose one with backup_job_create (it is a draft until the owner confirms it in the cabinet, which makes the encryption key); a draft can't be run. Uses the owner's storage quota, and keeps the job's 'keep last' count: when that many archives exist, the oldest one is removed.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"host": "<host>"
},
"name": "backup_create"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| job | No | Name of the backup job when the server has several (default: the first) | |
| host | Yes | Server id or exact name from hosts_list | |
| label | No | Why this backup is being made, e.g. 'before upgrading postgres' |