Hide Forgot
Description of problem: Once backup is completed (rear mkbackup), customer would like to log message that "backup complete" with a timestamp and location of the backup so the result can be inserted into a database. Version-Release number of selected component (if applicable): rear-1.17.2-1.el7.noarch How reproducible: Always Steps to Reproduce: Currently there is no provision to log message after successful backup completion. Actual results: Currently there is no provision to log message after successful backup completion. Expected results: Have some kind of provision to log message after successful backup completion only. Additional info: As a temporary hack, I modified /usr/sbin/rear bash script itself to log such message. # Check for and run the requested workflow if has_binary WORKFLOW_$WORKFLOW; then Log "Running $WORKFLOW workflow" WORKFLOW_$WORKFLOW "${ARGS[@]}" Log "Finished running $WORKFLOW workflow $BACKUP_URL" LogPrint "Finished running $WORKFLOW workflow $BACKUP_URL `date` " <<<<<< Added this line to print any messages and access variables else VERBOSE=1 LogPrint "ERROR: The specified command '$WORKFLOW' does not exist !" EXIT_CODE=1 fi I have not completely tested above but looks possible to get notification from here.
I would prefer to create a Pull Request to upstream. Relevant issue for it is: https://github.com/rear/rear/issues/1023 Relevant upstream Pull Request: https://github.com/rear/rear/pull/1022 We will see whether upstream accept it.
(In reply to Petr Hracek from comment #3) > I would prefer to create a Pull Request to upstream. > Relevant issue for it is: https://github.com/rear/rear/issues/1023 > Relevant upstream Pull Request: https://github.com/rear/rear/pull/1022 > > We will see whether upstream accept it. Thanks. hopefully it will get merge upstream and then downstream a well.
See upstream comments and feel free to comment it. https://github.com/rear/rear/pull/1022
(In reply to Petr Hracek from comment #10) > See upstream comments and feel free to comment it. > https://github.com/rear/rear/pull/1022 Thanks.
rebase to rear-2.00 will fix this issue
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:2052