Log Backup Already Running

When using ON-Bar to create a backup, the message log backup is already running in the bar_act.log file, or the message Process exited with return code 152 in the online.log file do not indicate a problem. They can appear under the following circumstances:

• The ALARMPROGRAM configuration parameter is set to log_full.sh. Periodically, events cause log_full.sh to trigger the onbar -b -l command. If a log fills while the onbar -b -l command is running, then ON-Bar backs up that log as well. If the backup has not completed by the time of the next event trigger, it generates a warning in the bar_act.log file. At the time of the next event trigger, the log backup can continue.
• A level-0 archive (especially when started with the -w option) first archives the database and then automatically start the onbar -b -l command to back up any logical logs that are currently full and not yet backed up. There might not be a log_full.sh message in online.log, because the onbar -b -l command is started directly.
• When you mount a new tape after filling a previous tape, a log_full.sh event is scheduled but not triggered. As soon as the next log fills and generates an event trigger in the log_full.sh file, all available logs are archived. You can force the archive by running onbar -b -l or force log_full.sh to be triggered by running onmode -l.