LTAPEDEV

I have a bit of confusion with the LTAPEDEV parameter. If I set a path to this parameter, will the logs automatically start backing up when full, or is there something else that tells the database server to backup the logs?

You need to setup/verify that the alarmprogram (script/program defined in the parameter by that name) is configured to backup the logs. Each time there's a log switch the script/program will be called. Regards. On Tue, Apr 18, 2017 at 11:33 PM, BENJI LONG <ruggedmouse@hotmail.com> wrote: > I have a bit of confusion with the LTAPEDEV parameter. If I set a path to > this > parameter, will the logs automatically start backing up when full, or is > there > something else that tells the database server to backup the logs? > > > ************************************************************ > ******************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > -- Fernando Nunes Portugal http://informix-technology.blogspot.com My email works... but I don't check it frequently... --001a11450afc1c4135054d789aba

Ok, I will look that up. Thanks Fernando

In the literature, I found Edit the ALARMPROGRAM script ($INFORMIXDIR/etc/alarmprogram.sh Set the BACKUPLOGS parameter within the file to Y. Change the backup program from onbar -b -l to ontape -a -d. but on our prod server, it is set to N. I went into the onconfig file, and the path is set to a different script called /etc/log_full.sh Is this just another way of setting it up? That is confusing to me...

You need to change the ALARMPROGRAM entry to point to alarmprogram.sh rather than log_full.sh and make the changes suggested. That will work if you will be using onbar for logical log backups. You will also have to change onbar and its arguments in the script to ontape and the appropriate arguments if you want to use ontape instead. Art Art S. Kagel, President and Principal Consultant ASK Database Management www.askdbmgt.com Blog: http://informix-myview.blogspot.com/ Disclaimer: Please keep in mind that my own opinions are my own opinions and do not reflect on the IIUG, nor any other organization with which I am associated either explicitly, implicitly, or by inference. Neither do those opinions reflect those of other individuals affiliated with any entity with which I am affiliated nor those of the entities themselves. On Wed, Apr 19, 2017 at 8:29 AM, BENJI LONG <ruggedmouse@hotmail.com> wrote: > In the literature, I found Edit the ALARMPROGRAM script > ($INFORMIXDIR/etc/alarmprogram.sh > Set the BACKUPLOGS parameter within the file to Y. > Change the backup program from onbar -b -l to ontape -a -d. > > but on our prod server, it is set to N. > I went into the onconfig file, and the path is set to a different script > called /etc/log_full.sh > > Is this just another way of setting it up? That is confusing to me... > > > ************************************************************ > ******************* > Forum Note: Use "Reply" to post a response in the discussion forum. > > --94eb2c11b594ba25bb054d8587e3

We are using ontape. That alarm program on our prod database is set to log_full.sh. I just set up the salesdemo database, and just did a bull backup command followed by the restore command, so I'm guessing there weren't any logs so it didn't ask me to restore the logs. I'll try and make some inserts and try to figure out how to simulate a failure before the log was written and another one after the log was written to disk.