DBAegis Community v1.0.0: test your backup and restore workflow #2
ILOGICSOFT
announced in
Announcements
Replies: 1 comment
|
Companion resource: the database restore drill checklist is now available as an indexable guide at https://dbaegis.com/database-restore-drill-checklist.html and as a reusable public Gist at https://gist.github.com/ILOGICSOFT/934327a2d6b4eadc2832f441b2a25989. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Backups are only useful if you can restore them.
DBAegis Community v1.0.0 is available for DBAs, SREs, platform engineers, and
self-hosters who want a visible, self-hosted backup-and-restore workflow instead
of scattered commands and undocumented recovery steps.
Community scope
The no-license-required Community edition currently supports DBAegis-local
logical backup and restore for:
It includes one local administrator, up to three active database connections,
up to three schedules, backup history, restore jobs, and basic retention. Cloud
storage, physical backup/restore, PITR, additional engines, notifications,
RBAC/MFA, LDAP, audit/reporting, and self-backup are paid-edition capabilities.
Start here
Start on a clean, non-production Linux VM. Verify the release checksum, connect
a non-production database, run a logical backup, and restore into a disposable
target. Then validate the recovered data with an application-relevant query.
Ten design partners wanted
We are looking for ten practitioners willing to test one real Community
workflow. The evaluation is deliberately small:
whether the workflow improved recovery confidence.
There is no requirement to buy anything or publish a testimonial. We will not
use your name, company, quote, or results without explicit permission.
Reply here if you want to participate, use Discussions for questions and ideas,
or open an issue for a reproducible defect. Do not post credentials, customer
data, hostnames, storage URIs, logs containing secrets, or backup contents.
Suspected vulnerabilities should be reported privately through GitHub Security
Advisories.
Product site: https://dbaegis.com/
All reactions