- Update version string to 5.1.14
- Update CHANGELOG with v5.1.10-v5.1.14 features
- Update README with new enterprise features
- Remove development files from repository
- Add sensitive files to .gitignore
- Move Quick Start to top of README for immediate 'try it now' experience
- Add 30-second quickstart with direct download and backup commands
- Include both PostgreSQL and MySQL examples in quick start
- Add comparison matrix vs pgBackRest and Barman in docs/COMPARISON.md
- Remove emoji formatting to maintain enterprise documentation standards
- Improve user flow: Show → Try → Learn feature details
- Enhanced professional tone across all markdown files
- Replaced visual indicators with clear text-based labels
- Standardized formatting for business-appropriate documentation
- Updated CHANGELOG.md, README.md, and technical documentation
- Improved readability for enterprise deployment scenarios
- Maintained all technical content while enhancing presentation
Fixes from Opus code review:
- PostgreSQL: Use native TEXT format for COPY (matches FROM stdin header)
- MySQL: Escape backticks in restore to prevent SQL injection
- MySQL: Add SHOW BINARY LOG STATUS fallback for MySQL 8.0.22+
- Fix duration calculation to accurately track backup time
Updated messaging: We built our own machines - really big step.
🚀 MAJOR RELEASE - Complete Independence from External Tools
This release implements native Go database engines that eliminate
ALL external dependencies (pg_dump, mysqldump, pg_restore, etc.).
Major Changes:
- Native PostgreSQL engine with pgx protocol support
- Native MySQL engine with go-sql-driver implementation
- Advanced data type handling for all database types
- Zero external tool dependencies
- New CLI flags: --native, --fallback-tools, --native-debug
- Comprehensive architecture for future enhancements
Technical Impact:
- Pure Go implementation for all backup operations
- Direct database protocol communication
- Improved performance and reliability
- Simplified deployment with single binary
- Backward compatibility with all existing features
🎉 Version 4.0.0 - Stable Release
Major Features Now Fully Working:
- Incremental backups (--backup-type incremental --base-backup <path>)
- Notification system (SMTP + webhook via environment variables)
- Full enterprise deployment examples (Ansible, K8s, Terraform)
This release represents feature-complete, production-ready state.
Breaking Changes from v3.x:
- CLI flags synced with documentation
- Notify package now active (reads NOTIFY_* env vars)
Tested:
- All unit tests pass
- go vet clean
- Cross-platform builds successful
BREAKING CHANGE: The --instance flag is renamed to --server to avoid
collision with Prometheus's reserved 'instance' label.
Migration:
- Update cronjobs: --instance → --server
- Update Grafana dashboard (included) or use new JSON
- Metrics now output server= instead of instance=
BREAKING CHANGE: Removed 'large-db' as standalone profile
New Design:
- Resource Profiles now purely represent VM capacity:
conservative, balanced, performance, max-performance
- LargeDBMode is a separate boolean toggle that modifies any profile:
- Reduces ClusterParallelism and Jobs by 50%
- Forces MaxLocksPerTxn = 8192
- Increases MaintenanceWorkMem
TUI Changes:
- 'l' key now toggles LargeDBMode ON/OFF instead of applying large-db profile
- New 'Large DB Mode' setting in settings menu
- Settings are persisted to .dbbackup.conf
This allows any resource profile to be combined with large database
optimization, giving users more flexibility on both small and large VMs.
CRITICAL FIXES:
- Encryption detection false positive (IsBackupEncrypted returned true for ALL files)
- 12 cmd.Wait() deadlocks fixed with channel-based context handling
- TUI timeout bugs: 60s->10min for safety checks, 15s->60s for DB listing
- diagnose.go timeouts: 60s->5min for tar/pg_restore operations
- Panic recovery added to parallel backup/restore goroutines
- Variable shadowing fix in restore/engine.go
These bugs caused pg_dump backups to fail through TUI for months.
- Add install/uninstall and metrics commands to command table
- Add Systemd Integration section with install examples
- Add Prometheus Metrics section with textfile and HTTP exporter docs
- Update Features list with systemd and metrics highlights
- Rebuild all platform binaries
Features:
- restore diagnose command for backup file analysis
- Deep COPY block verification for truncated dump detection
- PGDMP signature and gzip integrity validation
- Detailed error reports with --save-debug-log flag
- Ring buffer stderr capture (prevents OOM on 2M+ errors)
- Error classification with actionable recommendations
TUI Enhancements:
- Automatic dump validity safety check before restore
- Press 'd' in archive browser to diagnose backups
- Press 'd' in restore preview for debug log toggle
- Debug logs saved to /tmp on failure when enabled
Documentation:
- Updated README with diagnose command and examples
- Updated CHANGELOG with full feature list
- Updated restore preview screenshots
- Add --dry-run/-n flag for backup commands with comprehensive preflight checks
- Database connectivity validation
- Required tools availability check
- Storage target and permissions verification
- Backup size estimation
- Encryption and cloud storage configuration validation
- Implement GFS (Grandfather-Father-Son) retention policies
- Daily/Weekly/Monthly/Yearly tier classification
- Configurable retention counts per tier
- Custom weekly day and monthly day settings
- ISO week handling for proper week boundaries
- Add notification system with SMTP and webhook support
- SMTP email notifications with TLS/STARTTLS
- Webhook HTTP notifications with HMAC-SHA256 signing
- Slack-compatible webhook payload format
- Event types: backup/restore started/completed/failed, cleanup, verify, PITR
- Configurable severity levels and retry logic
- Update README.md with documentation for all new features
- Remove emoticons and bloated content
- Clean professional documentation
- Include all TUI screenshots
- Match actual application features
- Reduce from 1537 to ~380 lines
Implements cluster cleanup option for CLI (matches TUI functionality).
Features:
- --clean-cluster flag drops all user databases before restore
- Preserves system databases (postgres, template0, template1)
- Shows databases to be dropped in dry-run mode
- Requires --confirm for safety
- Warns user with 🔥 icon when enabled
- Can combine with --workdir for full disaster recovery
Use cases:
- Disaster recovery scenarios (clean slate restore)
- Prevent database conflicts during cluster restore
- Ensure consistent cluster state
Examples:
# Disaster recovery
dbbackup restore cluster backup.tar.gz --clean-cluster --confirm
# Combined with workdir
dbbackup restore cluster backup.tar.gz \
--clean-cluster \
--workdir /mnt/storage/restore_tmp \
--confirm
Chef's kiss backup tool! 👨🍳💋
Sanitized all production-specific paths:
- /u01/dba/restore_tmp → /mnt/storage/restore_tmp
- /u01/dba/dumps/ → /mnt/backups/
Changed in:
- cmd/restore.go: Help text and flag description
- internal/restore/safety.go: Error message tip
- README.md: All documentation examples
- bin/*: Rebuilt all platform binaries
This ensures no production environment paths are exposed in public code/docs.
Replaced actual production database names with generic examples:
- test00, teststablekc, keycloak, stabledc → myapp_production, myapp_analytics, users_db, inventory_db, reports_db
- Updated archive filenames to generic examples
- Changed dates to generic future dates
- Adjusted database counts (7 → 5)
- Modified file sizes to be more generic
This ensures no production-specific information is exposed in public documentation.
Completed TUI documentation with missing screens:
- Database Status & Health Check:
* Connection status with checkmark
* Database info (type, host, port, user, version)
* Backup directory location
* Database count
* Health status indicator
- Backup Archive Manager (List & Manage):
* Total archives and size summary
* Sortable table with filename, format, size, date
* Status indicators (✓ valid, ⚠ old, ✗ invalid)
* Cursor navigation
* Keyboard shortcuts for restore/verify/info/delete/refresh
All TUI screens now documented accurately!
Replaced outdated backup progress view with actual TUI implementation:
- Backup Execution (in progress):
* Shows type, database, duration
* Spinner animation with status message
* Cancel instruction
- Backup Completed (success):
* Completion status with checkmark
* Backup details (filename, size, location, databases)
* SHA-256 verification confirmed
* Return to menu instruction
Removed old progress bar style (45%, ETA, Speed) that's not in current TUI.
Now accurately reflects the actual backup execution screen.
Added missing TUI screen examples for restore operations:
- Restore Preview screen showing:
* Archive information (file, format, size, date)
* Cluster restore options with existing databases list
* Safety checks with status indicators (✓/✗/⚠)
* Cleanup warning when enabled
* Keyboard shortcuts
- Restore Progress screen showing:
* Current phase and status with spinner
* Database being restored with size
* Elapsed time
* Cancel instruction
Both screens match actual TUI implementation.
Enhanced documentation for --workdir flag:
- Added to Cluster Restore command reference section
- Added example to restore examples with clear "special case" comment
- Explained use case: VMs with small system disk but large NFS mounts
- Clarified it's NOT needed for standard deployments
- Prevents confusion about when to use this flag
Updated to match actual TUI implementation:
- Shows all 13 configuration fields with current values
- Includes database type cycling (PostgreSQL/MySQL/MariaDB)
- Shows Current Configuration summary section
- Displays keyboard shortcuts (↑/↓ navigate, Enter edit, 's' save, 'r' reset, 'q' menu)
- Matches screenshot appearance
The interactive menu display was outdated. Updated to match current implementation:
- Shows database engine switcher (PostgreSQL/MySQL/MariaDB)
- Lists all 13 menu options with separators
- Includes new features: Sample backup, Cluster operations, Active operations, History
- Matches actual TUI appearance from screenshots
Solves disk space issues on VMs with small system disks but large NFS mounts.
Use case:
- VM has small / partition (e.g., 7.8G with 2.3G used)
- Backup archive on NFS mount (e.g., /u01/dba with 140G free)
- Restore fails: "insufficient disk space: 74.7% used - need at least 4x archive size"
Solution:
- Added --workdir flag to restore cluster command
- Allows specifying alternative extraction directory
- Interactive confirmation required for safety
- Updated error messages with helpful tip
Example:
dbbackup restore cluster backup.tar.gz --workdir /u01/dba/restore_tmp --confirm
This is environmental, not a bug. Code working brilliantly! 👨🍳💋
