Results 1 to 8 of 8
  1. #1
    Join Date
    Jun 2003
    Posts
    15

    Unanswered: Level 0 backup instead of Level 1 backup.

    Hi,
    We are using IDS 7.31 and TSM 5.2.
    In the bar_act.log the following WARNING is given : "WARNING: psapload does not have a level 0 backup", when I try to take a level 1 backup! The result is that a level 0 backup is taken, and not a level 1 backup.
    It looks like after a level 1 backup , the next backup has to be a level 0 backup, but I thought it was possible to have several level 1 backups one after the other.
    Can someone explain ?
    best regards,
    Erwin.

  2. #2
    Join Date
    Aug 2003
    Location
    Argentina
    Posts
    780
    Hi Ewin,

    I suggest you that run one whole back-up level 0, in place of level 1.
    A back should exist up of level 0 before being able to do other levels.

    Gustavo.

  3. #3
    Join Date
    Jun 2003
    Posts
    15

    L1 archives

    Hi,

    This is the scheme we designed to use :

    saturday L0
    monday L1
    tuesday L1
    wednesday L1
    thursday L1
    friday L1

    what we see is, that every tuesday , a L0 is taken instead of a L1;

    best regards,
    Erwin.

  4. #4
    Join Date
    Apr 2003
    Location
    Phoenix, AZ
    Posts
    177
    So Tuesday reverts to a L0. What happens on Wednesday? Sounds to me like something is affecting the sysutils database. Are you changing logging on any db?
    Fred Prose

  5. #5
    Join Date
    Jun 2003
    Posts
    15
    The other days the L1 backup is taken as it should be.
    No changes of logging at all.

  6. #6
    Join Date
    Aug 2003
    Location
    Argentina
    Posts
    780
    Hi Erwin,

    I suggest that run level 0 back-up as "onbar -b -w -L 0", not onbar -b -L 0.

    Tnks.

    Gustavo.

  7. #7
    Join Date
    Jun 2003
    Posts
    15
    Hi,

    # less full.sh
    su - informix -c onbar -b -w -L0
    #

    that is what we do already,

    thanks,
    best regards.

    Erwin.

  8. #8
    Join Date
    Apr 2003
    Location
    Phoenix, AZ
    Posts
    177
    Sounds to me like one of the following:

    1. Between the Monday and Tuesday backup something is run which removes entries from one of the "bar_" tables in sysutils. You can dump the contents after the monday night L1 and before the Tuesday L1 if someone doesn't "fess" up. This is what onbar uses to determine if it's got a clean L0.

    2. Someone is makeing structural changes to physical or logical logs (add, changing sizes, or moving)

    3. Someone is changing logging mode on a database.

    You have a 24 hour window to hunt down and kill the offender. Check crons (root, informix). Good hunting.
    Fred Prose

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •