Releases: framps/raspiBackup
Releases · framps/raspiBackup
v0.7.1.1
Features (1)
- Allow specifying DEFAULT_TELEGRAM_THREADID for threaded Telegram notifications (#899)
Note: This release is not officially published.
To update local raspiBackup use either way:
- Reinstall raspiBackup from scratch
- Update local raspiBackup manually
curl -sSLO https://www.linux-tips-and-tricks.de/raspiBackup.sh
sudo mv ./raspiBackup.sh /usr/local/bin
sudo raspiBackup.sh --updateConfig
v0.7.1
v0.7.0.3
v0.7.0.2
Bugfixes (4)
- systemd journal is not excluded in rsync backups #859
- Backups are recycled even the move of the temporary backup directory fails #847
- Issue after upgrade from 0.6.9.1 to 0.7.0.1 #852 (Fix for an unsupported environment)
- PUSHOVER_ADDITIONAL_OPTIONS not appending properly (v7.0) #845 (Didn't make it into 0.7.0.1)
v0.7.0.1
v0.7.0
Features (4)
- Include the OS release info in backup directory names #791
- Shrink or expand last partition when a partition oriented backup was restored #750
- Allow to specify for partition oriented backup which partitions should be restored and allow to not format the partitions with option -00 #749
- Use a temporary backup directory #628
Enhancements (6)
- Change default backuptype used without any configuration from dd to rsync #814
- Add "device" parameter for Pushover Notifications #802
- Check for a new release with option -U #796
- For a partition oriented backup check if the same partitions were saved in a previous backup #793
- Exclude systemd journal from tar backup #789
- Add sfdisk sanity check #728
- Support F2Fs #722
- Use shellcheck to make raspiBackup more robust #561
- Various minor enhancements
Bugfixes (0)
- PARTUUIDs are not updated when option -0 is used in restore #816
For a complete and detailed list of issues in this release see here
v0.6.9
Features (2)
Enhancements (5)
- Issues when restore or update is called in a RO directory #653
- Restore fails because sfdisk format changed in Bullseye #659
- Export useful variables for extensions #598
- Checking for hard link capability doesn't give enough time for the test link to be created #571
- Regenerate UUID and PARTUUID during restore #683
- Ask to install missing packages #705
Bugfixes (2)
- ??? RBK0034E: Datei /usr/local/etc/raspiBackup.conf.new nicht gefunden. #616
- Option -m with a parameter string, e.g. "some test" aborts raspiBackup #607
For a complete and detailed list of issues in this release see here
v0.6.8.1
v0.6.8
Features (3)
- NVMe support for CM4 #412 (was already available inofficially as 0.6.7.1)
- Pushover support for notifications #550
- Slack support for notifications #551
Enhancements (7)
- Write message when there is no version and sha set in code #536
- Create something like DEFAULT_FINAL_COMMANDS #535
- Write backup tool messages also on screen and in message file/email #531
- Disable progress messages (option -g) if raspiBackup is executed in background #527
- Catch cleanup errors and let raspiBackup fail #520
- Automount creates /media/pi directory with ACLs and aborts raspiBackup #516
- Restore aborts if usbmount is installed #515
Bugfixes (2)
- Backup mount point not stored in backup #513
- RBK0273E received because
@eaDir
exists in backup dir on a Synology #530
For a complete and detailed list of issues in this release see here
v0.6.7.1
This release is raspiBackup v0.6.7 with NVMe support included.
Note: It's not officially published given the number of users as of now is only one. Next official release of raspiBackup will base on this release. Thank you very much to the donator of a full blown CM4 with NVMe storage which allowed me to add and test the CM4 support.
If you want to use this release visit this page and follow the instructions.