Features and support
What the current Acrynite release supports, and the limits worth knowing before you rely on it.
Capabilities
| Capability | Description |
|---|---|
| Database registration | Register PostgreSQL connection profiles. |
| Connection testing | Test registered PostgreSQL database connections. |
| Storage registration | Register S3 and S3-compatible destinations. |
| Logical backups | Create PostgreSQL logical dumps. |
| Physical backups | Create PostgreSQL physical base backups. |
| Backup catalog | Record backup runs and associated manifests. |
| Backup history | List and inspect previous backup operations. |
| Scheduling | Configure recurring backup operations. |
| WAL archiving | Configure PostgreSQL WAL archiving. |
| Recovery points | Inspect known physical backups and configured WAL destinations. |
| Restore planning | Inspect a proposed restore operation. |
| Physical restore | Recover into an isolated Docker PostgreSQL container. |
| Logical restore | Restore into a separately registered PostgreSQL target. |
Support matrix
| Component | Current support |
|---|---|
| Database engine | PostgreSQL |
| Remote object storage | Amazon S3 and S3-compatible storage |
| Local destination | Local filesystem |
| Logical backup | Supported |
| Physical backup | Supported |
| Recurring schedules | Supported |
| WAL archiving | Supported |
| Physical recovery target | Docker |
| Logical recovery target | Registered PostgreSQL database |
| Build from source | Go 1.26 or later |
Logical versus physical backups
A logical backup exports database objects and data using PostgreSQL logical dump tooling, which suits migration and portability. A physical backup captures the cluster's data files with pg_basebackup and, combined with a continuous WAL archive, supports point-in-time recovery. A physical backup alone is not sufficient for point-in-time recovery.
What we do not claim
Acrynite does not advertise MySQL, Azure Blob Storage, Google Drive or other engines and providers as supported. It does not promise zero data loss, guaranteed recovery or specific recovery times. Successful recovery depends on the backup, WAL continuity, PostgreSQL configuration, permissions, storage availability and the recovery environment.