Skip to content

Releases: SisyphusMD/archiver

v0.3.2 - New Import and Export Functions

07 Jun 04:00
Compare
Choose a tag to compare

[0.3.2] - 2024-06-06

Improved

  • 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

v0.3.1 - Fixed Pruning

06 Jun 19:17
Compare
Choose a tag to compare

[0.3.1] - 2024-06-06

Fixed

  • Fixed pruning (backup rotations)

v0.3.0 - Massive Argument Improvements

05 Jun 23:42
Compare
Choose a tag to compare

[0.3.0] - 2024-06-05

!!!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
    • '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

v0.2.3 - Add 'archiver' to PATH

04 Jun 14:42
Compare
Choose a tag to compare

[0.2.3] - 2024-06-04

Fixed

  • 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'.

v0.2.2 - Multiple Improvements

04 Jun 03:57
Compare
Choose a tag to compare

[0.2.2] - 2024-06-03

Improved

  • 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'.

v0.2.1 - Improved LOCKFILE mechanism

03 Jun 03:36
Compare
Choose a tag to compare

[0.2.1] - 2024-06-02

Improved

  • 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.

v0.2.0 - Major Speed Improvements

01 Jun 23:05
Compare
Choose a tag to compare

[0.2.0] - 2024-06-01

Improved

  • Major improvements to speed. Backup to primary storage for all repositories completes first, then each secondary storage copies sequentially.

v0.1.1 - Fixed Prune (Backup Rotations)

01 Jun 20:53
Compare
Choose a tag to compare

[0.1.1] - 2024-06-01

Fixed

  • Fixed the Duplicacy Prune function. Backup rotations work now.

v0.1.0 - Archiver Initial Release

01 Jun 01:20
Compare
Choose a tag to compare

[0.1.0] - 2024-05-31

I am excited to announce the first official release of Archiver, a powerful and highly configurable tool to easily automate backups.

  • Archiver will automate the backup of any configured directory to any number of SFTP and B2 storage backends.
  • By default, it will back up all files and subdirectories within any configured directory.
  • Archiver can optionally:
    • Include and exclude files and subdirectories from the backups.
    • Run custom bash scripts before and after each backup operation.
    • Configure custom restore scripts to quickly get your services running again when the worst happens.

Key Features:

  • Efficient Deduplication: Utilizes Duplicacy for block-level deduplication.
  • Secure Backups: Ensures data integrity and confidentiality with encryption.
  • Flexible Configuration: Easy setup and customization through a simple configuration file.
  • Automated Rotation: Smart backup rotation policies.
  • Easy Restoration: Restore scripts to quickly recover from data loss.
  • Notifications: Pushover notifications for backup statuses.
  • Multiple Storage Backends: Supports SFTP and BackBlaze B2.

Getting Started

Check out the GitHub repository for more details and to get started!

Feedback and Contributions

I highly encourage users to report any issues, suggest features, and contribute to the project. Your feedback is invaluable in helping me improve Archiver.