Comet Backup

A Protected Item describes the files, application, system or virtual environment to protect. The Storage Vault identifies where the copy lives, such as S3-compatible cloud storage, local disk or a self-hosted gateway. This split lets an operator connect different backup jobs to the appropriate destination.

The client can run a job manually or on a schedule. A practical setup includes choosing the exact files or workload, exclusions, destination vault and job timing; then checking the completed job record and actual recovered data.

A restore can select the vault, Protected Item, snapshot, files and destination path. Test a small file restore and a representative larger recovery so operators know how to locate the right point in time and where the recovered data will be written.

Retention rules can be applied at the vault or item level, with an item rule overriding the vault setting. Check those rules before relying on a given recovery window or storage budget; a scheduled backup does not by itself prove that the needed old version is retained.

Comet says each vault's data is compressed, encrypted and deduplicated. Deduplication is scoped to the vault rather than all vaults, which matters when deciding whether multiple trusted devices should share one vault or remain separated for access control.

The feature comparison covers workstations, servers, NAS, virtual platforms, SaaS data and databases. Availability and charge can vary by platform and workload, so test the exact Protected Item type and restore path the customer needs rather than relying on the broad category label.

Cloud-hosted management reduces console infrastructure work through vendor-managed startup and maintenance. Self-hosted management gives the team its own console deployment, with the Growth plan including a second license for a replica or multi-site use. Either way, the operator still has to configure clients, vaults, retention and recovery.