Separate machine
Vault has its own disks, accounts, and OS. A hypervisor root does not give you the repository.
Backups that stay put when an admin account is stolen. A separate appliance pulls your disks, encrypts them, and refuses to delete anything before its retention date.
Vault has its own disks, accounts, and OS. A hypervisor root does not give you the repository.
The node serves extents read-only. The appliance pulls. A node cannot push, overwrite, or delete a backup.
Every object has a retain_until time. A later job can extend it. Nothing can shorten it.
The offsite copy goes into an S3 bucket in COMPLIANCE mode. The bucket refuses deletes until the date, even from the account that wrote it.
Data is chunked, encrypted, and packed. The manifest is signed. A tampered pack fails verify instead of restoring bad data.
Deleting a target, lowering retention, installing a licence, or changing a role waits for a security officer.
The console shows a grade per target. storage-enforced means a bucket with Object Lock holds the data. appliance-enforced means the appliance software enforces it, and root on the appliance can still delete the files. none is S3 without Object Lock. Use Object Lock for anything you would be unhappy to lose.
The repository is a ZFS pool on the appliance. A two-disk stripe has no redundancy. Build a mirror if you want one. Vault does not replace an offsite copy.
Vault 0.1.x works with kcore 0.7.0 and has its own release numbers. Price is by quote.