Object storage
Any S3-compatible bucket, such as MinIO, Ceph RGW or AWS S3, with multipart uploads.
VICTOR PRODUCT / BACKUP & RECOVERY
Victor schedules backups to storage you control and keeps restore points alongside each VM. Recover whole machines or individual disks, with Enterprise options for incremental, encrypted, verified and immutable backups.
Community backups and restore · Enterprise protection features labeled01 / EVERY DISK, ONE INSTANT
Each backup exports the VM’s definition and every disk at the same instant, through the engine’s own APIs. Backups are quiesced through the guest agent where it runs, otherwise crash-consistent.
Restore the whole VM or any of its disks, in place or as a new VM, on the same cluster or another one.
02 / TARGETS YOU OWN
Victor tests a target before saving it: it writes a small file, lists it and reads it back. Credentials are sealed and never returned.
Any S3-compatible bucket, such as MinIO, Ceph RGW or AWS S3, with multipart uploads.
An NFS share you mount at the same path on every victord host; Victor refuses a path that isn’t an NFS mount.
A directory path, useful for labs and small sites.
Host key required; Victor never trusts on first use. Files are written to a partial file and renamed into place.
victorctl backup target add minio --kind s3 --endpoint https://minio.example:9000 \
--bucket vms --prefix prod --access-key victor --secret-key-file ./minio.secret
victorctl backup job add nightly --target minio --tag prod --cron "0 2 * * *" \
--timezone America/New_York --keep-last 7
victorctl backup point restore POINT --new --cluster cl-b --power-on --waitresource "victor_backup_target" "minio" {
name = "minio"
kind = "s3"
s3 = {
endpoint = "https://minio.example:9000"
bucket = "vms"
access_key_id = "victor"
secret_access_key = var.minio_secret_key
}
}03 / BY EDITION
| Capability | Community | Enterprise |
|---|---|---|
| Backup type | Scheduled full exports | Incremental, with content-addressed deduplication |
| Encryption | — | AES-256-GCM with a key per target |
| Verification | — | Verification and test restores |
| Retention | By count and age | Grandfather-father-son (GFS) |
| Copies and immutability | — | Copy jobs; S3 Object Lock |
| Restore | Whole VM or a disk, in place or as new | Plus file-level restore (ext4, XFS, Btrfs, NTFS, FAT) and instant recovery on KVM clusters |
On classic KVM VMs, incremental and encrypted points hold the boot disk only today; full exports hold every disk. Object Lock is tested on MinIO. Instant recovery and test restores work on KVM clusters only. Tape, SMB targets and cross-target deduplication are not available.


04 / THE ECOSYSTEM
A changed-block backup API, served over NBD with TLS, lets backup vendors read incremental changes. It is in Community.
On KubeVirt, Kubernetes backup tools work alongside Victor’s own backups. Velero with CSI snapshots is certified, and the VM page shows what each tool covers.
Victor also backs up its own configuration to encrypted archives on a schedule.
FAQ
An Enterprise feature that boots a backup job’s block-level restore point as a new VM at once while its disk copies in the background. It is available for classic KVM VMs; KubeVirt does not support it today. #
Yes. The default alarm pack includes failed VM backups and failed backup jobs. #
No. Backup and restore are part of Community. A license never stops VMs or running automation; if an Enterprise license expires, Enterprise features keep working through a grace period, then become read-only rather than disappearing. #
NEXT STEP
Tell us where backups go today and what your recovery objectives are.