Dar-backup

This is a maintenance script with improvements, no new functionality.

From the git log:

- results of backup and catalog operations now shown separately
- improved check of par2 files
- Now always log result of backup, test and restore verification
- cleanup now also cleanup a backup's catalog
- document a way to make systemd services work with a non-stardard location of dar
- various smallish documentation updates
- "--version" now emits a notice on license and no warranty
- a not fully working example of compiling dar on ubuntu
- test runner emits which 'dar' is used for the unit tests
- Github Actions V4 now used
- mk-DEV.sh script for easy usage of new dev version in daily use
- no more need for sudo in unit tests


SHA256:
49dc81d170c48060fb598a682cdfc867cfcf684dd170464c086ae1191f2f0511 dar-backup-linux-v1.5.2.tar.gz

This is a bugfix release for a few issues around catalogs
- catalog additions now more lenient via the "-ai" option, my pCloud issue has gone :-)
- an error at startup looking for backup difinition in the wrong place when checking for catalogs fixed
- catalog doc updated
- example of removing a specific backup added to main README

SHA256:
2eb2e4cc5e952f02f50673ad9fb81f08bfb8fd4ba47b0ad0c612ad86dcb627ea dar-backup-linux-v1.5.1.tar.gz

I have merged my "dar manager" branch to main, and created this release.

The dar-backup scripts now maintains a dar catalog for each backup definition. This makes is easier to restore files spread over FULL, DIFF and INC archives.

The use of catalogs are by default set to "n" in the dar-backup.conf file. Switch to "y" when you are ready :-)

I have used the dar-manager branch for months and consider it safe to use. Improvements and especially the issue with my pCloud storage will be investigated over time.

SHA256:
d2a8016765d66a800b5010df5dd6c15640d7170dcbfbbb936e647e1818271387 dar-backup-linux-v1.5.0.tar.gz

This is a maintenance/bugfix release with some changes, no new functionality.

During the yearly backups, I encountered a bug when generating the par2 files. It occurred only on the file system mounted from the cloud. I ended up refactoring how the par2 files are generated, which had the added benefit of a more simple setup.

- par2 now generated from within the script - not using the dar integrated system (allows for async par2 generation on the remote server)
- a small fix in the installer to make sure scripts are executable
- no exit if a backup definition fails, do the next one

SHA256:
898212dad3a3dfd4dd1f105acdd67d0401c7038f3808b76788e3f40f853a4459 dar-backup-linux-v1.4.3.tar.gz
SUCCESS: a release tarball from tag: "v1.4.3" was produced

Bugfix:

- cleanup.sh data parsing error, October not recognized.

Changes:

- --version print license info
- --list-files option removed, extremely slow and I never used it
- ls-archives.sh --listdef option implemented

SHA256:
a3495b076ff820ac5a311811c24a619f72dc2e548925ffb54ef5a1ddce60d280 dar-backup-linux-v1.4.2.tar.gz

Fix:
- systemd services fix, so that timers work as expected, if reboots do not happen nightly.

Improvements:
- cleanup.sh --cleanup-specific-archive <archive> removes the archive + par2 files, no matter the age of the archive.
- ls-archives.sh --backupdef <definition> lists only the archives for the specified backup definition.
- dar-backup.sh --version prints the version.
- much less chatty log messages, use --verbose to have more printed.

SHA256:
74dc9bf2ca405844f67c2031dc1c19b8f6f75438c94e4035038377b2e9ccd255 dar-backup-linux-v1.4.1.tar.gz