Re: onbar backup error on informix

Hi, a) please check that in your onconfig file you have set BAR_BSALIB_PATH to the absolute path name. That means you cannot use an environment variable ($INFORMIXDIR in your case) when specifying a value in the onconfig file. (I'm not sure you are aware of this and used $INFORMIXDIR only to describe the setting in your e-mail, or whether you actually used it in your onconfig file.) b) just creating a device with/in ISM is not quite sufficient. I'm not sure what exactly you have done. A typical minimum sequence of commands to run in ISM when setting it up initially would be like this: ism_startup -init ism_add -admin informix@onbarfix ism_add -device /work/martinfu/731/nsr_data -type file ism_add -device /work/martinfu/731/nsr_logs -type file ism_op -label /work/martinfu/731/nsr_data -volume data1 -pool ISMData ism_op -label /work/martinfu/731/nsr_logs -volume logs1 -pool ISMLogs ism_op -mount /work/martinfu/731/nsr_data ism_op -mount /work/martinfu/731/nsr_logs Note: This command sequence sets up devices and volumes for the backup of dbspaces and logical logs. Next paragraph c) will say more about this ... These are straight from one of my scripts. The directories (nsr_data and nsr_logs) have to exist before running the commands. I run the whole script us user "root", although technically it would suffice to run the first 2 commands only as user "root" and the remaining commands as user "informix". c) As noted in your ON-Bar activity log file, you are not backing up logical log files. This means that in your onconfig file you have LTAPEDEV set to "/dev/null". However, for restore of any dbspace backup that is not a whole system backup, you will need to restore logical logs. That means after having fixed the problem with the storage manager and after successfully doing your backup with "onbar -b", you unfortunately will never be able to restore it ... Either you need to backup all the logical logs as well (hence I included the commands for ISM setup to backup logical logs in the above sequence). Then you will be able to restore them. Or you need to do whole system backup and restore only, which is denoted by the "-w" flag to the ON-Bar commands. Please see manual "Backup and Restore Guide" for more information on this. Note: In newer versions (and I think even newer IDS 7.31 versions), there have been several fixes to this problem. Nowadays you will not be able to start a non-whole-system backup when your LTAPEDEV is set to /dev/null, and you will even get a descriptive error message explaining the reason. Whole system backup is of course allowed, but you will still get a warning to alert you to the restrictions for restore. d) If all this does not help, you can set onconfig file parameter BAR_DEBUG to something higher than 0 (zero), e.g. 6 and set BAR_DEBUG_FILE to an absolute path name for the debug log file. Then run the ON-Bar command (no need to restart IDS). The output in the file hopefully will contain some more information about the problem. Regards, Martin -- Martin Fuerderer IBM Informix Development Munich, Germany Information Management owner-informix-list@iiug.org wrote on 01.09.2005 05:39:48: > Hi. i have an hpux system running informix 7.31 which includes onbar > and informix storage manager ISM. I?ve configured (i think) ism to > backup to hard disk by adding an informix user administrator an adding > a device type=file pointing at some directory i created. i set > BAR_BSALIB_PATH to $INFORMIXDIR/lib/libbsa.sl on my onconfig file. > When i run unbar -b to create a backup i get this on my bar_act.log: > > > 2005-08-31 20:23:23 11304 11302 /u/informix/bin/onbar_d -b > 2005-08-31 20:23:23 11304 11302 Logical Logs will not be backed up > because LTAPEDEV value is /dev/null > 2005-08-31 20:23:25 11304 11302 Begin level 0 backup rootdbs. > 2005-08-31 20:23:25 11304 11302 Successfully connected to Storage > Manager. > 2005-08-31 20:23:25 11304 11302 XBSA Error (BSACreateObject): A > system error occurred. Aborting XBSA session. > 2005-08-31 20:23:26 11304 11302 /u/informix/bin/onbar_d: process > exit 3 (0x03) > > > Nothing is reported on ISM log direcories. Any ideas? Thanks. > > -- sending to informix-list