Backup & Restore¶
Protect your print history with database backups and restore when needed.
Overview¶
Bambuddy's backup system:
- Full database backup - All your data in one file
- User settings included - Preferences preserved
- Archives included - Print history saved
- ZIP format - Includes 3MF files and thumbnails when selected
- GitHub backup - Automatic cloud backup of profiles and settings
GitHub Profile Backup¶
Automatically backup your K-profiles, cloud profiles, and app settings to a GitHub repository.
Setup¶
- Create a GitHub repository (can be private)
- Generate a Personal Access Token (PAT):
- Go to GitHub → Settings → Developer settings → Personal access tokens → Tokens (classic)
- Generate a new token with
reposcope
- Configure in Bambuddy:
- Go to Settings → Backup & Restore
- Enter your repository URL (e.g.,
https://github.com/username/bambuddy-backup) - Enter your PAT
- Click Test Connection to verify
Bambu Cloud Login Required
GitHub backup requires you to be logged into Bambu Cloud to access your cloud profiles and K-profiles. Login via Profiles → Cloud Profiles.
What's Backed Up¶
| Data | Description |
|---|---|
| K-profiles | Per-printer pressure advance profiles (organized by serial number) |
| Cloud profiles | Filament, printer, and process profiles from Bambu Cloud |
| App settings | Application configuration (when enabled) |
Schedule Options¶
| Schedule | Description |
|---|---|
| Hourly | Backup runs every hour |
| Daily | Backup runs once per day (midnight) |
| Weekly | Backup runs once per week (Sunday midnight) |
Manual Backup¶
Click Backup Now to trigger an immediate backup.
Repository Structure¶
repo/
├── backup_metadata.json
├── kprofiles/
│ └── {serial_number}/
│ ├── 0.2.json
│ ├── 0.4.json
│ └── ...
├── cloud_profiles/
│ ├── filament.json
│ ├── printer.json
│ └── process.json
└── settings/
└── app_settings.json
Backup History¶
View backup history in the Backup History section:
- Status (success, failed, skipped)
- Trigger (manual or scheduled)
- Files changed
- Commit SHA (linked to GitHub)
Skip Unchanged
Bambuddy only creates a commit when data has actually changed, avoiding unnecessary commits.
Creating a Local Backup¶
Manual Backup¶
- Go to Settings > Backup & Restore
- Click Download Backup
- Wait for backup to complete (progress indicator shown)
- ZIP file downloads automatically
Don't Navigate Away
During backup/restore, stay on the page. The UI blocks navigation to prevent data corruption.
Backup Contents¶
The backup is a complete ZIP file containing:
| Data | Included |
|---|---|
| Database (all tables) | |
| Print archives (3MF files) | |
| Archive thumbnails | |
| Timelapse videos | |
| Library files | |
| Library thumbnails | |
| Project files | |
| Printer icons | |
| Plate calibration data | |
| Virtual printer uploads |
Complete by Definition
The new backup system copies the entire database file and all data directories. No data can be missed because everything is included automatically.
Backup File¶
Format¶
Backup files are ZIP archives:
ZIP Structure¶
bambuddy-backup-YYYYMMDD-HHMMSS.zip
├── bambuddy.db # Complete SQLite database
├── archive/ # All archive data
│ ├── <archive_id>/ # Individual archive folders
│ │ ├── *.3mf # Archived print files
│ │ ├── thumbnail.png # Thumbnails
│ │ ├── timelapse.mp4 # Timelapses
│ │ ├── source.3mf # Original source 3MF
│ │ ├── *.f3d # Fusion 360 files
│ │ └── photos/*.jpg # Photo attachments
│ └── library/ # File Manager
│ ├── files/ # Uploaded files
│ └── thumbnails/ # Generated thumbnails
├── virtual_printer/ # Pending uploads
├── projects/ # Project files
├── icons/ # Custom printer icons
└── plate_calibration/ # Plate detection references
File Size¶
Typical sizes depend on your archive content:
- Small archive (100 prints, no timelapses): ~100-500 MB
- Medium archive (500 prints, some timelapses): ~1-5 GB
- Large archive (1000+ prints, full timelapses): ~10+ GB
Large Backups
If you have many timelapse videos, backups can be large. Consider periodic cleanup of old timelapses.
Restoring from Backup¶
Full Restore¶
Restore everything from a backup ZIP:
- Go to Settings > Backup & Restore
- Click Restore Backup
- Select your backup ZIP file
- Wait for restore to complete (progress indicator shown)
- Restart Bambuddy when prompted
Full Restore Overwrites
A full restore replaces all current data including the database and all files. Create a backup first!
Restart Required
After restore, you must restart Bambuddy for changes to take effect. The database connection is replaced during restore.
Portable Backups¶
Backups are fully portable between installations:
- Different servers: Move from one machine to another
- Different paths: Works even if data directory changed
- Different Docker volumes: Migrate between container setups
The backup system stores relative paths internally, so files work correctly regardless of where Bambuddy is installed.
Manual Database Access¶
Location¶
The database is stored at:
Direct Backup¶
Copy the database file directly:
Stop Bambuddy First
Stop Bambuddy before copying to ensure consistency.
SQLite Tools¶
Use SQLite tools for advanced operations:
Downloading Archives¶
3MF files aren't in database backups. Download separately:
Individual Download¶
- Open an archive
- Click Download 3MF
Bulk Export¶
- Go to Archives
- Click Export
- Select Include 3MF files
- Download the archive
Recovery Scenarios¶
Lost Database¶
If database is corrupted or deleted:
- Stop Bambuddy
- Remove corrupted
bambuddy.db - Start Bambuddy (creates fresh database)
- Go to Settings > Backup
- Restore from your backup
New Installation¶
Moving to a new server:
- Install Bambuddy on new server
- Copy backup file to new server
- Go to Settings > Backup
- Full restore from backup
Data Migration¶
Moving between versions:
- Create backup on old version
- Upgrade Bambuddy
- If needed, restore from backup
Best Practices¶
Recommended Backup Frequency¶
| Frequency | Good For |
|---|---|
| Daily | Active printing (set a reminder) |
| Weekly | Regular use |
| Monthly | Light use |
Storage¶
- Keep backups off the Bambuddy server
- Use cloud storage (Dropbox, Google Drive, etc.)
- Keep multiple versions
Testing¶
- Periodically test restoring
- Verify backup integrity
- Document your backup process
Tips¶
Before Major Changes
Always backup before upgrading or making big configuration changes.
Off-Site Storage
Store at least one backup off-site (cloud or another location).
Regular Testing
Test your restore process periodically to ensure backups work.
Version in Filename
Include date and version in backup filenames for easy identification.
3MF Backup
For complete backup, also download your 3MF files separately.