Johannes Meixner

I postponed it to the ReaR v3.1 milestone because things work with dracut stuff in the recovery system so this could be cleaned up for ReaR v3.1 as time permits.

@lzaoral my pleasure!

There are two different kind of progress things here. ReaR's own progress subsystem via usr/share/rear/lib/progresssubsystem.nosh that shows ProgressInfo "Backed up XXX MiB [avg YYY KiB/sec]" messages which seems to not...

@milleld1 your https://github.com/rear/rear/files/11391181/local.txt contains (without comments): ``` OUTPUT=ISO BACKUP_PROG_ARCHIVE="backup_$( date '+%Y-%m-%d-%H%M' )-F" BACKUP=RSYNC BACKUP_URL=rsync://otherhost/home/rearbackupslocation EXCLUDE_MOUNTPOINTS=( '/mnt/16G_thumb_drive' /SOMEDISKIDONTNEED )} ``` I am not a 'BACKUP=RSYNC' user but as far as I...

The current behaviour is now better explained in default.conf via https://github.com/rear/rear/commit/586293c291d4e2f6864dfac7a1233bbdfe787126

As far as I understand it RSYNC_PREFIX is meant to specify the location of the backup, but with current code only the prefix can be specified and the actual location...

@milleld1 only an offhanded and untested idea: Does it perhaps somehow improve things for you when you replace in your usr/share/rear/backup/RSYNC/default/500_make_rsync_backup.sh script the hardcoded '/backup' with '$BACKUP_PROG_ARCHIVE'? In theory that...

@pcahyna could you perhaps have a look here as time permits? I ask you in particular because some time ago you did some code changes also for BACKUP=RSYNC (in particular...

@pcahyna no worries and no need to be sorry! First things first and as time permits. I have same working conditions and restrictions. For a current example see my https://github.com/rear/rear/pull/2961...

@bwelterl only to be on the safe side: When 'tar' is called with explicitly specified files or directories it will archive all explicitly specified files or directories regardless on which...