Overview
Theironcore-backup CLI manages every aspect of Ironcore Backup Solution — backup
operations, restore operations, datastores, namespaces, jobs, retention policies,
replication, and encryption keys. The CLI is available on all Polystack control plane
nodes and on any host where the backup client package is installed.
Prerequisites
- An active Polystack account with project membership
- The
ironcore-backupCLI installed — see CLI Setup - An API token or interactive credentials with appropriate roles
Authentication
- Interactive Login
- API Token
- Environment File
Interactive login
~/.config/ironcore-backup/credentials for the session.Backup Operations
ironcore-backup backup create
Create a one-shot backup of a workload.
| Flag | Type | Required | Description |
|---|---|---|---|
--type | vm | container | host | yes | Workload type |
--source-id | string | yes (vm/container) | Source workload identifier |
--source | path | yes (host) | Source path on the host |
--backup-id | string | yes (host) | Backup identifier for grouping snapshots |
--repository | string | yes | Target datastore |
--namespace | string | no | Namespace within the datastore |
--keyfile | path | no | Client-side encryption key file |
--include | glob | no | File patterns to include |
--exclude | glob | no | File patterns to exclude |
Restore Operations
ironcore-backup vm restore
Restore an entire VM. Use --live to start the VM immediately while restore continues
in the background.
Live-restore a VM
| Flag | Description |
|---|---|
--snapshot | Source snapshot reference |
--target-host | Compute host to restore to |
--live | Start VM while restore continues in background |
--storage | Target storage backend |
--rename | Optional new name for the restored VM |
ironcore-backup file restore
Restore individual files or directories from a snapshot.
Restore a single file
Restore a directory as a tar archive
Snapshot Management
ironcore-backup snapshot list
List snapshots in a datastore
Filter by namespace
Filter by source
ironcore-backup snapshot show
Show metadata, size, and the file listing inside a snapshot.
ironcore-backup snapshot remove
Backup Jobs
ironcore-backup job create
Schedule a recurring backup.
Daily incremental at 02:00 with 7-day retention
Weekly full backup with 3-week retention
ironcore-backup job list
ironcore-backup job run
Trigger a scheduled job immediately.
Datastores and Namespaces
ironcore-backup datastore create
ironcore-backup namespace create
Replication and Sync
ironcore-backup sync create
Replicate snapshots from a local datastore to a remote site.
Weekly archival sync to Backup site
| Flag | Description |
|---|---|
--source | Local datastore name |
--remote | Configured remote site name |
--remote-repository | Datastore name on the remote site |
--direction | push (local → remote) or pull (remote → local) |
--schedule | systemd-style schedule (for example Sun 04:30 or daily) |
--encrypt | Encrypt snapshots in transit |
--bwlimit | Maximum bandwidth in MiB/s |
ironcore-backup sync run
Verification
ironcore-backup verify start
Verify all snapshots in a datastore
Verify a single snapshot
ironcore-backup verify status
Encryption Keys
ironcore-backup key create
Generate a client-side encryption key
ironcore-backup key paperkey
Print the encryption key as a paper-friendly QR + hex block for offline secure storage.
If the encryption key is lost, the encrypted backups are unrecoverable. Always
store the paperkey in a physical safe at the Backup site.
Tape Operations
ironcore-backup tape backup
ironcore-backup tape inventory
ironcore-backup tape restore
Diagnostics
ironcore-backup status
ironcore-backup task list
ironcore-backup task log
Next Steps
Create a Backup
Step-by-step procedure to create your first backup.
Schedule a Job
Build recurring backup jobs that match your retention policy.
Restore Options
Compare live-restore, full restore, and file-level restore.
Admin Guide
Provision datastores, retention, replication, and security as an administrator.
