pcahyna

Re **Note 1** : that's real and is one of the many oddities I noticed (but not fixed) when working on PR #2831 , see https://github.com/rear/rear/pull/2831#issuecomment-1170105155 (the 4th bullet point)....

@oldunclez generally I have found that the rsync-over-ssh seems to be better supported and tested than rsyncd. See the third bullet point in https://github.com/rear/rear/pull/2831#issuecomment-1170105155 that might affect you. Please check...

@oldunclez I then consider **note 2** solved and focus only on **note 1**. I think the only solution is to disable the reporting of disk space used and disk full...

@fadamo wow, I have not thought about a possibility of such a workaround, thanks for sharing it!

Regarding the backup method, the manual page has this: BACKUP=GALAXY Use CommVault Galaxy 5 to restore the data. BACKUP=GALAXY7 Use CommVault Galaxy 7 to restore the data. BACKUP=GALAXY10 Use CommVault...

I forgot to ask: what is actually the "bad" initrd size (when it fails to boot) and "good" size (when it boots)?

@fadamo could you please be more specific? What backup method and BACKUP_URL are you using? And which file does "the code" refer to?

Thank you for the information, and what version of ReaR is this? A log above shows 2.4, is that the case also for the version you are experimenting with?

> In current ReaR 2.7 code there is > no longer a global variable RSYNC_PORT. > Instead there is a function `rsync_port()` to me it seemed that `RSYNC_*` variables have...

Concerning > In this case here `set -eu -o pipefail` > (therein in particular the `set -e` part) > would hinder the user to do some "dirty hacks" I am...