Enhanced ALARMPROGRAM for backups

Hi There, I want to be able to create a new file for every log backup switch. I was thinking of doing the following 1) have the script use perl:dbi to get current log number 2) run the ontape -a 3) copy the file to contain the log_number 4) touch a new file for LTAPEDEV 5) have an OS job rsync these log_numbered files offsite. In this way I have a set of files that tell me exactly what logs should be in them. Similar to Oracle archive redo logs. Is this a valid approach or is there a better way of doing this. I can't have a tape device ( or want one ). Regards Chris

Why not simply use the ALARMPROGRAM to catch the logid which is full. Event 23 is initiated each time a log becomes full. BUNNY On Thu, 3 Jul 2003 01:45:55 -0400 (EDT) "CHRIS PRIEST" <chris.priest@asic.gov.au> wrote: > Hi There, > > I want to be able to create a new file for every log backup switch. I was thinking of doing the following > > 1) have the script use perl:dbi to get current log number > 2) run the ontape -a > 3) copy the file to contain the log_number > 4) touch a new file for LTAPEDEV > 5) have an OS job rsync these log_numbered files offsite. > > In this way I have a set of files that tell me exactly what logs should be in them. Similar to Oracle archive redo logs. > > Is this a valid approach or is there a better way of doing this. I can't have a tape device ( or want one ). > > Regards > > Chris > -- Mit freundlichen Grüßen Gerd Kaluzinski \\\\\\\\|// (o o) --------------------------------------------------ooO-(_)-Ooo--- Gerd Kaluzinski mailto:gerd.kaluzinski@bytec.de Manager Consulting mailto:support@bytec.de Informix Certified Senior System Engineer http://www.bytec.de BYTEC GmbH Telefon: 07541-585-1019 Hermann-Metzger-Str. 7 Fax : 07541-585-2019 88045 Friedrichshafen Ooo. -------------------------------------------------.ooO----( )--- ( ) (_/ \\\\_)

----LNX_Thu_Jul_03_2003_09:47:57_V3.33-- Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable >Datum: 2003.07.03 08:59:23 >Sender: CHRIS PRIEST <chris.priest@asic.gov.au> > > I want to be able to create a new file for every log backup switch. > I was thinking of doing the following > > 1) have the script use perl:dbi to get current log number > 2) run the ontape -a > 3) copy the file to contain the log_number > 4) touch a new file for LTAPEDEV > 5) have an OS job rsync these log_numbered files offsite. > =2E.. > Is this a valid approach or is there a better way of doing this. I can'= t >have a tape device ( or want one ). = Hi, = we are doing something like that with an enhanced alarm-script, too. 1) the number of the completed log is passed to the alarm script as param= eter automatically , you don't need an extra program to get the current log 2) ontape -a expects input from stdin - you have to use something like echo ..... | ontape -a or ontape -a << eof .... 3) move, not copy = You have to make sure that the script (at least the ontape -a / move ) ru= ns only once at the same time - if the logical logs are filling rapidly you = might run into problems otherwise. = You can get a lot of small files with the logical logs - in the case of a= restore you have to process them one after the other (with manual input) - noprob= lem, but you have to know that. And the restore will take more time if youhave= a lot of small files. = After moving the log backup compressing (gzip) might be a good idea. = I think somewhere on the IIUG-site there is a script/example doing all these things. = Regards Andreas Kutsche ------------------------------------------------ SPAR Oesterreichische Warenhandels-AG Hauptzentrale Europastra=DFe 3 A-5015 Salzburg = Telefon : +43 662 4470 24423 E-Mail : Andreas.KUTSCHE@spar.at Internet: http://www.spar.at ------------------------------------------------ = ----LNX_Thu_Jul_03_2003_09:47:57_V3.33----