-
v0.5.1 Stable
released this
2026-01-13 11:57:54 -08:00 | 277 commits to main since this releaseAdded
- SSH public key display after bundle export for easy SFTP server configuration
Fixed
- Symlink for
archiver.lognow uses relative path, resolving correctly when logs directory is mounted outside container - Bundle backup (
.oldfile) handling improved to remove existing backup before creating new one
Downloads
-
Source code (ZIP)
1 download
-
Source code (TAR.GZ)
1 download
-
v0.5.0 Stable
released this
2026-01-13 11:57:25 -08:00 | 279 commits to main since this releaseAdded
- Docker Support: Run Archiver in containers on any platform
- Interactive setup mode generates bundle file without Linux installation
- Automated backups with cron scheduling or manual execution
- Multi-architecture images (linux/amd64, linux/arm64) published to GHCR
- Bundle Commands:
archiver bundle exportandarchiver bundle importfor managing configuration - Health Check:
archiver healthcheckcommand for monitoring system health
Changed
- BREAKING: Renamed export/import to bundle terminology
archiver export→archiver bundle exportarchiver import→archiver bundle import- Directory:
exports/→bundle/ - Environment:
EXPORT_PASSWORD→BUNDLE_PASSWORD
- Bundle file is now always
bundle.tar.enc(previous version saved as.old, no timestamps) - Cron jobs now scheduled for invoking user instead of root user
- Logs now show storage target name (e.g., "Service: Synology") instead of generic "Archiver" during copy/wrap-up operations
Fixed
- Setup script now handles special characters (like
$) in passwords and API keys correctly - Setup script now creates bundle file even if one wasn't imported
- Setup script improved S3 region prompt with better examples and optional handling
- Setup script and bundle-export script now work correctly in Docker (no SUDO_USER dependency)
- Cron schedule now properly created from setup script for the correct user
- Log viewer now properly exits when backup completes instead of hanging
- Restored files now have correct ownership matching the invoking user
- Directory ownership fixed when restoring to non-existent directory
- Removed obsolete
PRUNE_KEEP_ARRAYfrom log output - Better error messages when running setup on unsupported platforms
Improved
- Setup script auto-imports existing bundle files
- Version pinning for reliable installations
- Platform detection provides helpful Docker guidance for non-Linux systems
- Cron instructions now show correct commands for user crontab
Migration Notes
Migrating from v0.4.x to v0.5.0 (Bundle Terminology)
The export/import functionality has been renamed to use "bundle" terminology:
- Export file location changed:
exports/directory is nowbundle/ - Commands renamed:
archiver export→archiver bundle exportarchiver import→archiver bundle import
- Bundle file naming: Files are now always named
bundle.tar.enc(previous versions saved as.old, no timestamps) - Environment variable: For Docker,
EXPORT_PASSWORDis nowBUNDLE_PASSWORD
Action Required for existing export files:
- Rename your
exports/directory tobundle/ - Rename your export file to
bundle.tar.enc - Use the new
archiver bundle exportandarchiver bundle importcommands going forward
Migrating from Traditional Installation to Docker
Docker installation is now the recommended deployment method. Legacy installation will be deprecated in v0.7.0.
Steps to migrate:
-
Export your configuration (from your current traditional install):
archiver bundle exportThis creates
bundle/bundle.tar.encwith your config and keys encrypted. -
Save your bundle password: Remember the password you used to encrypt the bundle - you'll need it for Docker.
-
Set up Docker Compose:
services: archiver: container_name: archiver image: ghcr.io/sisyphusmd/archiver:0.5.0 restart: unless-stopped environment: TZ: "UTC" # Examples: "America/New_York", "Europe/London", "Asia/Tokyo" BUNDLE_PASSWORD: "your-bundle-password-here" CRON_SCHEDULE: "0 3 * * *" # Optional - backup will wait for manual invocation if not set volumes: - /path/to/bundle.tar.enc:/opt/archiver/bundle/bundle.tar.enc - /path/to/logs:/opt/archiver/logs # Optional - for log persistence - /path/to/service_directories:/path/to/service_directories # Container path must match SERVICE_DIRECTORIES in your config.sh hostname: backup-server # Optional - used in backup snapshot IDs -
Important: Volume paths inside the container must match the
SERVICE_DIRECTORIESpaths in yourconfig.sh. If your config has/home/user/data, mount it to the same path:-/home/user/data:/home/user/data -
Start the container:
docker compose up -d -
Verify: Check logs with
docker logs -f archiver
Note: You can run both traditional and Docker installations side-by-side during migration for testing.
Downloads
-
Source code (ZIP)
1 download
-
Source code (TAR.GZ)
0 downloads
- Docker Support: Run Archiver in containers on any platform
-
v0.4.1 Stable
released this
2025-06-07 19:04:26 -07:00 | 282 commits to main since this releaseFixed
- Added missing restore function for S3 storage backend.
- Fixed ownership of new local directory when restoring.
Downloads
-
Source code (ZIP)
1 download
-
Source code (TAR.GZ)
1 download
-
v0.4.0 Stable
released this
2025-06-06 22:38:00 -07:00 | 286 commits to main since this releaseAdded
- S3 storage backend support added alongside existing SFTP and B2 backends.
Improved
- Setup script explicitly checks for export file existence, skipping import gracefully if no exports exist.
Downloads
-
Source code (ZIP)
1 download
-
Source code (TAR.GZ)
1 download
-
v0.3.2 Stable
released this
2024-06-06 20:58:52 -07:00 | 301 commits to main since this releaseImproved
- Added import and export functions to backup your config.sh and keys files
- Setup script will auto-import any export file placed in the archiver repo directory
- Setup script also ensures you have an export file, and places it in an 'exports' directory
Downloads
-
Source code (ZIP)
1 download
-
Source code (TAR.GZ)
1 download
-
v0.3.1 Stable
released this
2024-06-06 12:16:52 -07:00 | 318 commits to main since this releaseFixed
- Fixed pruning (backup rotations)
Downloads
-
Source code (ZIP)
1 download
-
Source code (TAR.GZ)
1 download
-
v0.3.0 Stable
released this
2024-06-05 16:41:04 -07:00 | 357 commits to main since this release!!!BREAKING CHANGE!!!
- Calling the script with no argument will no longer initiate a backup
- Must use the full command with argument: 'archiver start'
- If you have cronjobs scheduled without the 'start' argument, they will no longer initiate a backup without editing to include 'start'
- You can edit your cronjobs with the following command: 'sudo crontab -e'
- i.e. '0 3 * * * archiver start'
Improved
- Massive argument improvements:
- Arguments are now single words, not prefaced by '--'
- archiver start|stop|pause|resume|restart|logs|status|setup|uninstall|restore|help
- 'archiver' command with no argument (or with 'help' argument) prints a guide to available arguments
- 'start':
- 'archiver start' is now required to initiate a backup
- may need to edit 'sudo crontab -e' if it previously did not include the 'start' argument
- 'archiver start logs' to initiate a backup and view logs
- 'archiver start prune|retain' prune and retain will override the behavior to prune or retain backups for this run only
- logs and prune|retain can be combined
- 'archiver start' is now required to initiate a backup
- 'stop|pause|resume':
- 'archiver stop|pause|resume' manually stops, pauses, or resumes a running backup
- 'archiver resume' can be combined with 'logs'
- 'logs'
- 'archiver logs' will display the logs of a running backup (but no longer starts a new backup)
- 'status'
- 'archiver status' prints whether or not there is a currently running backup process
- 'restart'
- 'archiver restart' will stop any running backup and start a new one from the beginning
- similar to 'archiver start' can be used with logs|prune|retain
- 'restore'
- 'archiver restore' will run the restore script
- 'help'
- 'archiver help' will display information about available commands and arguments
- 'setup|uninstall'
- 'archiver setup|uninstall' will run the setup or uninstall scripts
- although, on first run, setup will require './archiver.sh setup' from the archiver dir, given archiver will not be in the PATH yet
- uninstall function coming soon
- Arguments are now single words, not prefaced by '--'
Downloads
-
Source code (ZIP)
1 download
-
Source code (TAR.GZ)
1 download
-
v0.2.3 Stable
released this
2024-06-04 07:41:08 -07:00 | 395 commits to main since this releaseFixed
- Fixed LOCKFILE being left by main.sh.
Improved
- Setup script places archiver in PATH.
- Please run './setup.sh' again from the archiver repo directory to make this change.
- You can skip all sections of the setup script by typing 'n' when prompted. The script will make this change regardless.
- You should now run Archiver backups with the command 'archiver'.
- This is global, no more need to change to your archiver directory.
- It accepts arguments, such as 'archiver --view-logs' and 'archiver --stop'. More arguments to come soon.
- Cron can also call 'archiver' directly: (e.g. '0 3 * * * archiver').
- To edit your prior cronjob, run 'sudo crontab -e', and replace the path to the archiver script with simply 'archiver'.
- Please run './setup.sh' again from the archiver repo directory to make this change.
Downloads
-
Source code (ZIP)
0 downloads
-
Source code (TAR.GZ)
1 download
-
v0.2.2 Stable
released this
2024-06-03 20:56:54 -07:00 | 402 commits to main since this releaseImproved
- Scripts will auto-escalate to sudo now. So README no longer recommends to run with sudo.
- Logs all go to a single file now for easier viewing.
- Reorganized directory structure.
- Stop is now an argument './archiver.sh --stop'.
Downloads
-
Source code (ZIP)
1 download
-
Source code (TAR.GZ)
1 download
-
v0.2.1 Stable
released this
2024-06-02 20:15:52 -07:00 | 414 commits to main since this releaseImproved
- The LOCKFILE mechanism is much more robust now.
- Setting the stage for all commands to be through "sudo archiver --argument" rather than through calling various scripts.
Downloads
-
Source code (ZIP)
1 download
-
Source code (TAR.GZ)
1 download