Following up on this, I just realized that the output from DumpPreUserCmd is being stored under the XferLOG and the errors logs. If I open the backup's primary log file it only shows the rsync activity, but all my dumpPreUserCmd output is still being written to the detailed log files. I still need to confirm that the backup will hard-fail on an error from my user cmd, which is required for me to be aware that a database or table dump was not successful.
On Thu, 2019-08-15 at 14:54 -0500, Mike Hughes wrote: I use a DumpPreUserCmd to kick off a database dump script. This script used to log its actions within each server's BackupPC log so I could verify which databases and tables were dumped, which were skipped, etc. It looks like a change was made which stops these logs from being written to the BackupPC logfile: https://github.com/backuppc/backuppc/issues/285 I guess my question is, was this intentional? Do I need to manage my process logfile outside of BackupPC? Second question: are we still sending a termination signal if UserCmdCheckStatus exits with a failure? Thanks! -- Mike -- Mike Hughes <m...@visionary.com<mailto:m...@visionary.com>> Visionary Services, inc.
_______________________________________________ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List: https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki: http://backuppc.wiki.sourceforge.net Project: http://backuppc.sourceforge.net/
