Database Vault vs Percona Backup for MongoDB

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.

Percona Backup for MongoDB (PBM) is a free, open-source tool for consistent backups and restores of MongoDB replica sets and sharded clusters. It supports point-in-time recovery by saving oplog slices between backups. Operators can manage operations from its command-line interface or through a web interface with Percona Monitoring and Management. PBM offers logical, physical and incremental physical backups, plus backups of selected databases or collections; whole-database backups can include users and roles. Destinations include Amazon S3, Google Cloud Storage, MinIO and compatible storage, filesystem servers, Azure Blob Storage, Oracle Cloud Infrastructure Object Storage and Alibaba Cloud OSS. Backup types depend on database product, version and storage engine. MongoDB Community and Enterprise Edition support logical backups only. Physical backups require Percona Server for MongoDB 7.0 or newer and WiredTiger. PBM is self-hosted and lists Linux among its platforms. It uses MongoDB authentication and authorization, and requires a PBM user in the admin database for each replica set. Percona recommends systemd credentials rather than storing connection credentials in plaintext environment variables or service files.