Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
Database Servers
DB2InformixIngresMS SQLOraclePervasive.SQLPostgreSQLProgressSybase
Desktop Databases
FileMakerFoxProMS AccessParadox
General
General DB TopicsDatabase Theory
Related Topics
Java Development.NET DevelopmentVB DevelopmentMore Topics ...

Database Forum / Informix Topics / July 2004

Tip: Looking for answers? Try searching our database.

Informix using onbar + ontape together

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Nat - 29 Jul 2004 15:39 GMT
I am doing backup with onbar. I have also set my alamrprogram to
backup the logical logs using ontape -a.
The problem is that the onbar tries to backup the current logical
using onbar and it takes ages!!!
Is there a way to solve this???
I run out of logical logs if I have many data modifications while the
onbar is slowly (+ 2 hours) backuping THE logical log.
Thanks in advance.

Nati

I am sending relevant info below.

Extract from online.log
========================
00:32:15  Archive on rootdbs, logdbs, prepaga1dbs, prepaga2dbs,
prepaga3dbs, prepaga4dbs, witceldbs Completed.
00:32:15  Logical Log 49696 - Backup Started
00:32:15  Logical Log 49696 Complete, timestamp:1746951802.
00:35:21  Fuzzy Checkpoint Completed:  duration was 0 seconds, 1367
buffers not flushed,
timestamp: 1746954168.
00:35:21  Checkpoint loguniq 49697, logpos 0x75124, timestamp:
1746954168
....
....
....
03:05:21  Maximum server connections 1404
03:08:54  Logical Log 49696 - Backup Completed

Backup script
==============
spmprod:/usr/informix/etc $ cat  /usr/informix/cron/backup.sh
# Instancia prepaga
. /usr/informix/.profile

echo `date`" - Backup comienza"

$INFORMIXDIR/bin/onbar -b -w
$INFORMIXDIR/bin/onmode -F

echo `date`" - Backup finalizado $?"

spmprod:/usr/informix/etc $

Extract of my onconfig
======================
# System Archive Tape Device

#TAPEDEV                /dev/tapedev    # Tape device path
TAPEDEV         /dev/null       # Tape device path
TAPEBLK         1024            # Tape block size (Kbytes)
TAPESIZE        0               # Maximum amount of data to put on
tape (Kbytes)

# Log Archive Tape Device

LTAPEDEV        /archives/spmprod/logfile       # Log tape device path
#LTAPEDEV       /dev/null       # Log tape device path
LTAPEBLK        1024            # Log tape block size (Kbytes)
LTAPESIZE       0               # Max amount of data to put on log
tape (Kbytes)

# To automatically backup logical logs, edit alarmprogram.sh and set
# BACKUPLOGS=Y
ALARMPROGRAM    /usr/informix/etc/alarmprogram.sh # Alarm program path
# ALARMPROGRAM    /usr/informix/scripts/log_full.sh # Alarm program
path
TBLSPACE_STATS  1               # Maintain tblspace statistics

Part of my alarmprogram.sh
==========================

BACKUP_CMD="ontape -a"
...
...
# If there is already a logical log backup don't launch onbar again.
       if ( `test x${BACKUPLOGS}  = xY` ) then
         $BACKUP_CMD <<EOF 2>&1 >> /dev/null

n
EOF
#          $BACKUP_CMD 2>&1 >> /dev/null
         EXIT_STATUS=$?

        # Capturo el nro de log
        c=1
        for b in $3; do
           if [[ $c -eq 3 ]]; then logno=$b; fi
           c=$(( c + 1 ))
        done

         # El backup es a disco, asigno el nr
Art S. Kagel - 29 Jul 2004 14:52 GMT
You cannot mix ontape and onbar.  If you have to restore IB that onbar cannot
read the logical log tapes/files that ontape makes.  Change your alarm
program to use onbar.

Art S. Kagel

> I am doing backup with onbar. I have also set my alamrprogram to backup the
> logical logs using ontape -a. The problem is that the onbar tries to backup
[quoted text clipped - 82 lines]
>
>           # El backup es a disco, asigno el nr
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.