Onbar & rewinding of tape

Hi Steven ! I have scheduled job that runs every 2 hours with 'onbar -l'. No problems with this. If you want to know, if this data will be written at the beginning of the tape or not - refer to your Storage Manager manual. When you told to onbar run some backup/redtore, onbar simply reads data and pass this data to the Storage Manager. Tape management is SM headache. -- ------------------------------------------------- With best regards, Yuri Dovgart SAP R/3, Informix technical consultant, Informix Certified Professional, Senior System Consultant System Architecture and High Availability Systems, 'Telecominvest' company Email y_dovgart@tci.ukrtel.net ICQ 39284285 > > I am thinking of trying a new strategy of backing up the logs via > "onbar -l -c" scheduled by cron, but am not sure whether each time that a > new job is fired, whether the tape would be rewind and get the previous > content erased, or would it continued where the previous job left the tape. > > Any suggestions? > > thanks > Steven >

Hi, I am using Informix IDS 7.30FC7XK1 on HPUX 11.0, with OmniBack II ver 3.1. Currently I am having issues with backing up of logical logs with "onbar -l -C" as sometimes, I encountered the following message in my online.server.log file 16:13:18 Logical Log 39910 - Backup Aborted Aborted by client. and also the following is reported in my /tmp/bar_act.log (for OmniBack) XBSA Error (BSACreateObject): A system error occurred. Aborting XB SA session. As I am running SAP on my system, I need to backup the logical logs continually. HP had not been able to solve this issue with the OmniBack as yet. I am thinking of trying a new strategy of backing up the logs via "onbar -l -c" scheduled by cron, but am not sure whether each time that a new job is fired, whether the tape would be rewind and get the previous content erased, or would it continued where the previous job left the tape. Any suggestions? thanks Steven

I have experienced this error with ISM and with Legato. Therefore, I decided I mkust be doing something wrong. So here's the deal; The "server" and "client" environment variables must be set. For example NSR_SERVER for Legato ISM_SERVER for ISM and I'll bet there is a set for OMNIBACK too. The issue is the database engine captures the environment when started. This could be from the informix command line ksh or the root bourne-shell cron/init.d environment or the root command line sh or ksh. If you use ALARMPROG and log_full.sh then I'll bet it works sometimes and not others. The best way to troubleshoot this is...hardcode the XXXX_SERVER and XXXX_CLIENT environment variables in the log_full.sh script. Test it from informix and from the init scripts. I'll bet it works just "ducky". Or stick the command /usr/bin/env >>/tmp/logfulldebug.out 2>&1 in the log_full.sh script and see what outputs to the .out file. Compare this to a cammand line env and one of your environment variables will be either missing or you'll see XXXX_SERVER= set to "NULL". Hope this points you in a good direction. Tom "Steven" <steven_lee@jjsea.com> wrote in message news:B50E86F7.245A%steven_lee@jjsea.com... > Hi, > > I am using Informix IDS 7.30FC7XK1 on HPUX 11.0, with OmniBack II ver 3.1. > > Currently I am having issues with backing up of logical logs with > > "onbar -l -C" > > as sometimes, I encountered the following message in my online.server.log > file > > 16:13:18 Logical Log 39910 - Backup Aborted > Aborted by client.> > and also the following is reported in my /tmp/bar_act.log (for OmniBack) > > XBSA Error (BSACreateObject): A system error occurred. Aborting XB > SA session. > > > As I am running SAP on my system, I need to backup the logical logs > continually. > > HP had not been able to solve this issue with the OmniBack as yet. > > > I am thinking of trying a new strategy of backing up the logs via > "onbar -l -c" scheduled by cron, but am not sure whether each time that a > new job is fired, whether the tape would be rewind and get the previous > content erased, or would it continued where the previous job left the tape. > > Any suggestions? > > thanks > Steven >