RE: /dev/null device being used by onbar

/dev/null tells the engine you do not want to back it up. You must change this to something else. What storage manager are you using and have you configured it? Why are you using onbar rather than ontape? MW > > -----Original Message----- > > From: owner-informix-list@iiug.org > > [mailto:owner-informix-list@iiug.org]On Behalf Of reclspeak > > Sent: Wednesday, 18 June 2003 2:46 a.m. > > To: informix-list@iiug.org > > Subject: /dev/null device being used by onbar > > > > > > > > I'm in the process of configuring onbar for an old, previously not > > backed-up Informix 7.31 UC5. > > > > A whole system backup of dbspaces with onbar -b -w seems to go fine, > > except for the error; > > > > 2003-06-17 15:16:00 14902 14901 ERROR: Unable to start the > > logical log > > backup: Log backup to device '/dev/null' not allowed > > > > Which I thought might be a red herring, as I was doing a full > > dbspace backup. > > > > However, performing just a logical log backup with onbar -l > > produces the > > same error. > > > > 2003-06-17 15:24:00 15858 15857 ERROR: Unable to start the > > logical log > > backup: Log backup to device '/dev/null' not allowed > > > > /dev/null is the value for LTAPEDEV in onconfig, but is this the > > variable that is being pointed-to, and if so, what should > it point to? > > Is /dev/null defined as the device to backup to anywhere else? > > > > Thanks in anticipation > > > > > > recl > > > > -- > > Posted via http://dbforums.com > sending to informix-list

The storage manager is ISM. onbar is being used, only because I have no experience of ontape, and I want to back-up to a file system. I'm not an Informix DBA, and the client has no one with such skills, but I have rolled-out onbar with OmniBack in the past. At present I can back-up dbspaces to a file systems, but not logical logs, which are re-directed to /dev/null, rather than the ISM_ARC directory labeled and mounted with ism_op. Other than onconfig, are there any other locations where /dev/null will be configured to for logical logs to be written? Regards recl -- Posted via http://dbforums.com

LTAPEDEV set to "/dev/null" is a Special Feature in Informix which tells it to bypass the entire LOG process. You must change this to anything but "/dev/null". You can even just set it to the default "/dev/tapedev" (The device does not need to actually exist) Then stop and restart the instance. The error with the Whole system backup occurs because after the backup is complete it then backs up the current LOG file. When you are using onbar, it will actually write to the ISM Pools specified by the paramaters "ISM_DATA_POOL" for backups and "ISM_LOG_POOL" for backing up the LOGS. Bill reclspeak <member31001@dbforums.com> wrote in message news:<3015183.1055927667@dbforums.com>... > The storage manager is ISM. > > onbar is being used, only because I have no experience of ontape, and I > want to back-up to a file system. I'm not an Informix DBA, and the > client has no one with such skills, but I have rolled-out onbar with > OmniBack in the past. > > At present I can back-up dbspaces to a file systems, but not logical > logs, which are re-directed to /dev/null, rather than the ISM_ARC > directory labeled and mounted with ism_op. > > Other than onconfig, are there any other locations where /dev/null will > be configured to for logical logs to be written? > > Regards > > > recl

Your getting this message because LTAPEDEV is set to /dev/null. The storage manager has nothing to do with the error. Though LTAPEDEV and TAPEDEV are used with ontape, if LTAPEDEV is set to /dev/null the Informix instance discards the logical logs, thinking that the Informix DBA planned this. By setting LTAPEDEV to anything other than /dev/null (i.e. "/devnull" or "dummy") will prevent the instance from discarding the logical logs. Hope this information helps. Good luck. Brice Avila reclspeak <member31001@dbforums.com> wrote in message news:<3015183.1055927667@dbforums.com>... > The storage manager is ISM. > > onbar is being used, only because I have no experience of ontape, and I > want to back-up to a file system. I'm not an Informix DBA, and the > client has no one with such skills, but I have rolled-out onbar with > OmniBack in the past. > > At present I can back-up dbspaces to a file systems, but not logical > logs, which are re-directed to /dev/null, rather than the ISM_ARC > directory labeled and mounted with ism_op. > > Other than onconfig, are there any other locations where /dev/null will > be configured to for logical logs to be written? > > Regards > > > recl

Thanks Brice, Bill & Murray I changed the LTAPEDEV value in onconfig and stopped and re-started ism. It didn't take initially, so I started onmonitor and again changed the, stopped and re-started again and this time it has taken. recl -- Posted via http://dbforums.com

Wow! That's impressive. I've seen seasoned DBAs weep at onbar. And only last week I saw someone experience major follicular loss trying to get it to behave with OmniBack. Where are you based? Andy <member31001@dbforums.com> wrote in message news:<3015183.1055927667@dbforums.com>... > The storage manager is ISM. > > onbar is being used, only because I have no experience of ontape, and I > want to back-up to a file system. I'm not an Informix DBA, and the > client has no one with such skills, but I have rolled-out onbar with > OmniBack in the past. > > At present I can back-up dbspaces to a file systems, but not logical > logs, which are re-directed to /dev/null, rather than the ISM_ARC > directory labeled and mounted with ism_op. > > Other than onconfig, are there any other locations where /dev/null will > be configured to for logical logs to be written? > > Regards > > > recl