#1110 Issue closed: 'mkbackuponly' and 'restoreonly' do not copy the logfile to the right places¶

Labels: enhancement, fixed / solved / done, won't fix / can't fix / obsolete, minor bug

jsmeix opened issue at 2016-12-07 11:14:¶

'mkbackuponly' does not copy its logfile to the NETFS place and
'restoreonly' does not copy its logfile into the recovered system.

I noticed this while working on multiple backups
cf. https://github.com/rear/rear/issues/1088
but it is a general issue.

jsmeix commented at 2016-12-13 13:30:¶

Since https://github.com/rear/rear/pull/1121
'restoreonly' copies its logfile into the recovered system
via wrapup/default/990_copy_logfile.sh so that now after e.g.

# rear -C basic_system -d -D recover
# rear -C home_backup -d -D restoreonly & rear -C opt_backup -d -D restoreonly & wait

one gets in the recovered system

# ls -l /root/rear-*
lrwxrwxrwx 1 root root 59 Dec 13 14:00 /root/rear-2016-12-13T13:00:01+00:00.log -> /var/log/rear/recover/rear-f79-recover-basic_system-716.log
lrwxrwxrwx 1 root root 62 Dec 13 14:10 /root/rear-2016-12-13T13:10:36+00:00.log -> /var/log/rear/recover/rear-f79-restoreonly-opt_backup-2935.log
lrwxrwxrwx 1 root root 63 Dec 13 14:10 /root/rear-2016-12-13T13:10:38+00:00.log -> /var/log/rear/recover/rear-f79-restoreonly-home_backup-2934.log

# ls -l /var/log/rear/recover/*.log
-rw-r--r-- 1 root root 1140771 Dec 13 14:00 /var/log/rear/recover/rear-f79-recover-basic_system-716.log
-rw-r--r-- 1 root root  921264 Dec 13 14:10 /var/log/rear/recover/rear-f79-restoreonly-home_backup-2934.log
-rw-r--r-- 1 root root  920443 Dec 13 14:10 /var/log/rear/recover/rear-f79-restoreonly-opt_backup-2935.log

jsmeix commented at 2016-12-14 12:09:¶

As far as I see making 'mkbackuponly' copy its logfile
to the NETFS place requires either major changes
or dirty hacks because for 'mkbackup' that happens
via output/default/950_copy_result_files.sh
but the 'output' stange is not run for 'mkbackuponly'.

For ReaR 2-0 I will not do anything more here.

For ReaR 2.1 I would like to completely clean up the logging
and then - I hope - things get cleanly solved everywhere.

I close the issue as "fixed" for 'restoreonly'
and "won't fix" for 'mkbackuponly'.

---

[Export of Github issue for rear/rear.]