However, it's really sad that pgBackRest has been closed, because I was led by pgBackRest in some sense when started Databasus

I want to share the latest important updates for my open source tool for scheduled database backups (with focus on PostgreSQL).

A quick recap:

- Supported databases: PostgreSQL, MySQL, MariaDB and MongoDB

- Many storage destinations: local storage, S3, Google Drive, Dropbox, SFTP, rclone and more

- Notifications: Slack, Discord, Telegram, email, webhook

GitHub - https://github.com/databasus/databasus

Website - https://databasus.com

In 2025 Databasus renamed from Postgresus when it became popular and support for other databases was added.

Primary audience for the project is developers, DevOps engineers and DBAs. Now project is the most GitHub starred repository for backups (surpassed even WAL-G and pgBackRest). There are ~240k pulls from Docker Hub (both of previous Postgresus and Databasus images).

New features:

1. GFS retention policy

GFS is an acronym for Grandfather-Father-Son. It allows to keep last N hourly, daily, weekly, monthly and yearly backups.

This is needed to keep backups over wide period of time within reasonable storage space.

Before only X days or months were supported.

By default now is used:

- Keep 24 hourly backups

- Keep 7 daily backups

- Keep 4 weekly backups

- Keep 12 monthly backups

- Keep 3 yearly backups

Usually this strategy is used by enterprises which needs long period of backups retention.

2. Encrypted backups are stored along with their metadata to decrypt them without Databasus itself

Before, if server with Databasus is destroyed, you were not able to decrypt backups without Databasus itself. So you had to make backups of Databasus internal DB.

Now backups are stored in S3\Google Drive\other storages with meaningful names with their encryption metadata in format:

- {database-name}-{timestamp}-{backup-id}.dump

- {database-name}-{timestamp}-{backup-id}.dump.metadata

In case of server destruction, you need only `secret.key` to decrypt backups and restore via pg_dump, mysqlbackup, mongodump or other tools. It is important for me to not vendor-lock users on my tool (even despite the fast it's OSS)

Full guide - https://databasus.com/how-to-recover-without-databasus

Comments URL: https://news.ycombinator.com/item?id=47110339

Points: 3

# Comments: 0

To restore database - it should be empty (otherwise conflicts are possible)

Technically, you can try to restore to filled DB. But don't think it makes sense to try

WAL-G is about PITR backups, Databasus is about logical ones.

From one side, Databasus usually is slower when database is large.

From another side, it's much easier to use (especially when you have a lot of DBs).

In the future, I am considering implementing incremental backups and following a similar approach as WAL-G or pgBackRest do. But it will be one of options, not mandatory one

Website - https://databasus.com

GitHub - https://github.com/databasus/databasus

Main features:

- Scheduled backups for multiple PostgreSQL, MySQL, MariaDB and MongoDB databases

- Storage to S3, Cloudflare R2, Google Drive, Azure Blob, NAS, SFTP, rclone, etc.

- Notifications about backup status via email, Telegram, Slack, Discord, MS Teams and customizable webhooks

- Works with both self-hosted and managed PostgreSQL (RDS, Cloud SQL, etc.)

- Runs as a single Docker container or via Helm on Kubernetes, can be installed via script

- There are workspaces and role-based access with audit logs

Comments URL: https://news.ycombinator.com/item?id=46410656

Points: 10

# Comments: 7

Website - https://postgresus.com

GitHub - https://github.com/RostislavDugin/postgresus

Main features:

- Scheduled backups for multiple PostgreSQL databases

- Storage to S3, Cloudflare R2, Google Drive, Azure Blob, NAS, etc.

- Notifications about backup status via email, Telegram, Slack, Discord, MS Teams and customizable webhooks

- Works with both self-hosted and managed PostgreSQL (RDS, Cloud SQL, etc.)

- Runs as a single Docker container or via Helm on Kubernetes, can be installed via script

New in 2.0:

- Database health checks and alerts

- Workspaces, users and audit logs for teams

- Encryption for secrets and backup files

- Improved compression defaults

- Refreshed UI with dark theme

Comments URL: https://news.ycombinator.com/item?id=46230961

Points: 3

# Comments: 1

What it is: minimal log collection system + search UI focused on developer ergonomics. There are libraries for Java, Go, Python, JavaScript, C#, PHP.

Usage examples and playground are placed on the website - https://logbull.com.

Features: - per-project isolation (within single instance); - API keys; - optional domain/IP filtering limits; - retention settings; - users management and audit logs.

Deployment is made via Docker or via .sh script.

Tech stack: Go backend + React UI, PostgreSQL as DB, OpenSearch for storage/search, Valkey for caching and rate limiting.

The project is open source under Apache 2.0 license.

Comments URL: https://news.ycombinator.com/item?id=45730397

Points: 1

# Comments: 0