oz0 server backup
Write one archive of every management table, read in one snapshot while servers keep running, and for a dev server its Temporal database too.
For: Operators and developers looking up a command.
Write one archive of every management table, read in one snapshot while servers keep running, and for a dev server its Temporal database too. The master key is not in it: keep that apart, and give it to server restore. The archive holds job content and sealed secrets, so store it as you store the database. A cluster's Temporal databases are backed up with PostgreSQL's own tools.
Usage
oz0 server backup --out FILE [flags]
oz0 server backup [command]
Subcommands
Flags
| Flag | Type | Default | Description |
|---|---|---|---|
--data-dir | string | ~/.local/share/orchestrator-zero | server data directory |
--db-file | file | a file (- for stdin) holding the PostgreSQL URL of the management database, such as postgres://oz0:PASSWORD@db:5432/oz0 (or set OZ0_DB); the URL can carry a password, so it never goes on the command line | |
--dev | bool | a dev server's data directory (--data-dir) instead of a cluster's database | |
--out (-o) | string | the archive to write, such as oz0-backup.tar.gz |
Inherited flags
| Flag | Type | Default | Description |
|---|---|---|---|
--context | string | $OZ0_CONTEXT or <config dir>/orchestrator-zero/context.json | CLI context file written by server init |
--log-level | string | info | log level: debug, info, warn or error |
See all oz0 commands and the global flags.