Detailed log of:
- Issue discovery (files backup being skipped)
- Root cause analysis (/tmp space exhaustion)
- Solution implemented (disk staging directory)
- Process status and monitoring
Created: 2026-04-25 19:15 CDT
Backup status: Full 1.4TB in progress
Problem:
- /tmp is a tmpfs mount with only 3.9GB space
- Backing up 1.4TB Nextcloud files requires space for tar and zstd compression
- Both mysqldump and tar were failing with 'No space left on device'
Solution:
- Changed TEMP_DIR from /tmp to /mnt/nextcloud-data/.backup-staging
- /mnt/nextcloud-data has 487GB free space (sufficient for compressed backups)
- Staging directory is automatically cleaned up after successful upload to B2
Impact:
- Backup process now completes successfully for full 1.4TB Nextcloud datasets
- No changes to B2 credentials or configuration
- Backward compatible with existing backup configurations
- Complete backup script for native Nextcloud (MySQL + files)
- Systemd service and timer for daily automated backups at 2 AM
- Backblaze B2 integration with secure credential storage
- Incremental backup support with 30-day retention
- zstd compression for 40-70% storage reduction
- Comprehensive documentation and deployment guides
- Successfully tested with first backup: 203MB DB + 1.3GB files
- Cost-optimized: ~/bin/bash.01-0.02/month for 1.5GB data
Deployment Details:
- Installed B2 CLI via pipx
- Created backup directories at /opt/nextcloud-backup/
- Configured systemd timer for daily execution at 2 AM
- First backup verified in B2 bucket: jg-nextcloud
- Automated scheduling enabled and tested
Documentation includes:
- Deployment report with complete setup details
- Quick start guide for future deployments
- Comprehensive technical reference
- Troubleshooting procedures
- File manifest and index
jgitta