informix logical logs and onbar 152 error - Veritas Net Backup

This is a discussion on informix logical logs and onbar 152 error - Veritas Net Backup ; When performing a logical log backup, we are receiving a 152 error from onbar b/c our LTAPEDEV is set to /dev/null. If we change this value to a local volume, will the volume be used in the log backup or ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: informix logical logs and onbar 152 error

  1. informix logical logs and onbar 152 error


    When performing a logical log backup, we are receiving a 152 error from onbar
    b/c our LTAPEDEV is set to /dev/null. If we change this value to a local
    volume, will the volume be used in the log backup or will it be ignored and
    go directly to the netbackup media servers?

  2. Re: informix logical logs and onbar 152 error


    -- Here is the answer to my question...

    In Informix when you set LTAPEDEV to /dev/null (this is within Informix's
    database configuration file, typically
    $INFORMIXDIR/etc/onconfig) the server detects this at startup and essentially
    "throws away" the logical logs as soon as they are no longer needed on disk.
    This means that they will not be available to be backed up when OnBar (the
    Informix-supplied piece of the backup puzzle, akin to RMAN in Oracle) tries
    to send them to NBU to be backed up.

    LTAPEDEV is only used by the native Informix backup tools (ontape and onarchive),
    but in order to have successful log backups to NBU, they will need to set
    this parameter to something other than /dev/null (and I believe it does need
    to be a legitimate file or device - if they have no tape devices on the box,
    they can just create a file owned by Informix:Informix with write permission
    and set LTAPEDEV to that.) If LTAPEDEV was set to /dev/null at the time
    the Informix server was started, they will have to restart it after changing
    LTAPEDEV (as the server make that "throw the log files away" decision at
    startup time based on the value of LTAPEDEV.)

    The answer to their actual question, therefore, is that LTAPEDEV, when set
    to a local volume, will be ignored as long as they are using OnBar and/or
    NBU to do their backups. Running ontape or onarchive, however, will use
    that volume (so don't run ontape or onarchive ;-))


+ Reply to Thread