Database Vault vs Medusa

Database Vault is a cloud service for automating database backups and restoring earlier snapshots. It supports PostgreSQL, MySQL, MongoDB, Firebase, and Supabase; the supported-database list also includes SQLite. Backup schedules can be hourly, daily, weekly, or custom. Users can review backup history and restore a point-in-time snapshot, including through a one-click restore to a new database. The service monitors failures, retries automatically, and provides notifications and operation logs. Its dashboard tracks backup frequency, storage use, and success rates. Database Vault says backups are encrypted with AES-256 before storage and connection strings are encrypted at rest and never logged. It runs on Google Cloud Platform infrastructure, which it describes as SOC 2 Type II certified, and advertises a 99.9% uptime SLA for backup operations. The Free plan includes 1 GB of storage and 7-day retention. Starter costs $9 a month and supports up to three databases; Pro costs $15 a month and supports up to ten. Backups remain accessible for 30 days after cancellation.

Medusa is a command-line backup system for Apache Cassandra that runs on Linux in a self-hosted deployment. It supports full and differential backups, single-node backup and restore, and cluster-wide restores in place or to a remote location. Backup destinations include local storage, Google Cloud Storage, Azure Blob Storage, AWS S3, and compatible S3 services. It supports clusters using either single tokens or vnodes. Its verify command checks backup completion, manifest and file presence, and file hashes; MD5 checks can be enabled, while file size is checked by default. Configuration documentation covers client SSL settings and S3 server-side encryption with KMS or customer-provided keys. Retention settings can purge backups by age or count. Installation instructions cover pip and Debian packages, including offline installation, and describe installing Medusa on each Cassandra node. It requires Python 3.9 or newer and is licensed under Apache-2.0. A stated constraint is that it does not support Cassandra deployments with multiple data-folder directories.