Scope and prerequisites
Protect repository passwords/S3 credentials and independently retain the recovery key before enrollment. This reference describes the reviewed newer source CLI. Use the exact approved installed kit and authenticated operator terminal on the designated disposable VM. A marketing/documentation publication does not install these commands or qualify the host. Keep provider console, private configuration, original journals and independent recovery available. Never substitute placeholder digests, automatically accept a confirmation or reset a blocked journal. Inspect a read-only plan first where the family supports planning; apply is a separate explicit reviewed step. Credentials belong in the protected file parameters, not command-line secret values.
Parsed command family
panelctl backup-destination plan|apply
Exact parsed options
| Option | Parser default | Purpose |
|---|---|---|
--id |
"" |
stable logical destination ID |
--display-name |
"" |
operator-facing destination name |
--kind |
"" |
local or s3 |
--scope |
"" |
account or panel |
--account |
"" |
account ID for account scope |
--password-file |
"" |
private root-owned repository-password file |
--s3-credential-file |
"" |
private root-owned typed S3 credential JSON file |
--s3-endpoint |
"" |
canonical HTTPS S3-compatible endpoint |
--s3-bucket |
"" |
S3 bucket |
--s3-region |
"" |
optional S3 region |
--s3-prefix |
"" |
optional repository prefix |
--s3-path-style |
false |
record path-style endpoint policy |
--recovery-key-label |
"" |
escrowed recovery-key label |
--recovery-key-provider |
"" |
operator_escrow or external_kms |
--escrow-access-file |
"" |
private root-owned escrow access-control JSON file |
--escrow-verified-at |
"" |
RFC3339 time of off-machine escrow verification |
--minimum-free-bytes |
1<<30 |
minimum free bytes retained at staging/repository destination |
--bandwidth-bytes-per-second |
0 |
optional bandwidth ceiling; zero is unlimited |
--timeout |
time.Hour |
bounded backup destination operation timeout |
--plan |
"" |
digest of the current reviewed destination plan |
--authorize |
"" |
exact destination enrollment authorization phrase |
--confirm-escrow |
"" |
exact off-machine recovery-key confirmation phrase |
Local and S3-specific review
The source supports kind local or s3. S3 endpoint must be canonical HTTPS with the reviewed bucket/region/prefix/path-style policy and private typed credential file. This is not Google Drive or SFTP OAuth/setup. Retain off-machine escrow verification, access control and recovery label/provider. Plan/apply enrollment must preserve independent recovery; a configured repository is not proof of successful full-machine restore.
Verify and handle failure
Read the command result and retained operation/report, then inspect actual owned service state. A saved metadata file or successful verification is not necessarily apply. On stale digest, unknown layout, unavailable agent, partial effect or uncertain delivery, retain the evidence and follow the exact release recovery procedure. Do not disable AppArmor, remove locks/receipts, overwrite unrelated files or claim a source-only test as installed success.