Gitea dump has now settings for
- temp folder (GITEA_TEMP_DIR)
- new name for working dir (GITEA_WORKING_DIR) from old (GITEA_TMP)
MySQL and PostgreSQL exports have a run time output per db dump set and not only at the end of the full run
CHECK_INTERVAL or SUB_CHECK_INTERVAL in module settings.
If set to 1, will check everytime.
Ever other number is for n days after last check.
FORCE_CHECK for check if repository has been setup os now renamed
FORCE_VERIFY but FORCE_CHECK is currently still honored but deprecated
all *function* shell scripts will abort if run on their own
Print info on last check time if set in info block
Internal updates:
All separator lines are now printf strings for central control.
All module used config/settings file names use $MODULE name
Check functionality is in its own file
Because we added borg check functionality, some of the Options have been
renamed:
-C -> -V
-E -> -e (as it is a sub)
-C: check
-y: --verify-data
-p: prefix or glob for check
Internal variables with CHECK have been renamed or changed to VERIFY
Borg -C without any extra parameters is equal to borg check.
-y adds the --verify-data and -p is a mix of the -P and -a options. If
there is a "*" in the option then -a will be used, else -P
Note that repair command has to be run manually. Run -C with -v
(verbose) to see the repair command structure.
borg check can take a long time on very large repositories.
* file backup borg folder has now -file name inside. Old folder must be
manuall renamed
* All modules have the module id name as prefix in the backup set,
_borg_backup_set_prefix_cleanup.sh needs to be run before to clean up
all names or prune will not correctly delete old entries
New -T for one time target backup with custom prefix to have backups
outside the automated prune. -D option to delete this set
Add borg 1.2 support for compact which is called after delete and prune
to actually clean up the space.
-b borg executable and BORG_EXECUTEABLE override setting if borg is not
in path or another borg executable should be used
If nothing set in the settings file some entries need to be default set:
COMPRESSION
COMPRESSION_LEVEL
ENCRYPTION
FORCE_CHECK
KEEP_LAST
KEEP_HOURS
KEEP_DAYS
KEEP_WEEKS
KEEP_MONTHS
KEEP_YEARS
If these variables are empty after settings file is ready they are set
to the default value. After that the sub configs override those settings
New module for zabbix settings backup based on zabbix-dump
Move the _BORG_CALL and _BORG_PRUNE base calls to functions.check
instead of each module (they are all the same)
Update Readme file
Update default settings and remove KEEP so the original defaults are
used
Add a .gitignore for all other files that can appear in this
folder
(.config, .cache, settings files, etc)
Add backward compability check for file backup to
not auto add -file for
the file module unless flag is set
(FILE_REPOSITORY_COMPATIBLE)
