Change LOG filename - Veritas Backup Exec

This is a discussion on Change LOG filename - Veritas Backup Exec ; In our environment we have NW51 servers running BE90. These servers will be in our 170+ branches, 17 have been rolled out so far. We have a simple batch program that helps a user in the branch check if the ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: Change LOG filename

  1. Change LOG filename

    In our environment we have NW51 servers running BE90. These servers will be
    in our 170+ branches, 17 have been rolled out so far. We have a simple batch
    program that helps a user in the branch check if the backup was good by
    displaying the log file. We have done this for years with NW4x servers and
    ArcServe...the process must stay the same. These are un-trainable users, the
    simple batch file is too much for some of them! The reason for the batch
    file; if they say no (backup was bad) we will not allow processing until a
    good backup runs. This is extremely important for our environment.

    The snag: Although set to maintain one log file, we have not found a way to
    consistently have BE use the same name.
    Example name: sys\bkupexec\log\00000001.Daily_Backup.3.1

    Name changes 3.1, 3.2, 3.3...etc. Why 3.x???? How do I set BE 9.0 (build
    from CD) to consistently name the log file with the same name?

    Thanks in advance.



  2. Re: Change LOG filename

    I don't feel that there is any way to do that, because each of the output
    needs to go in to a separate file.
    The best solution that I could think of is to write a simple utility that
    will run at regular intervals on your server and look out for new log files
    in the directory and pipe it's contents(append/overwrite) to another common
    file of yours.


    "Robert Villafranca" wrote in message
    news:3d1e554b$1@hronntp01....
    > In our environment we have NW51 servers running BE90. These servers will

    be
    > in our 170+ branches, 17 have been rolled out so far. We have a simple

    batch
    > program that helps a user in the branch check if the backup was good by
    > displaying the log file. We have done this for years with NW4x servers and
    > ArcServe...the process must stay the same. These are un-trainable users,

    the
    > simple batch file is too much for some of them! The reason for the batch
    > file; if they say no (backup was bad) we will not allow processing until a
    > good backup runs. This is extremely important for our environment.
    >
    > The snag: Although set to maintain one log file, we have not found a way

    to
    > consistently have BE use the same name.
    > Example name: sys\bkupexec\log\00000001.Daily_Backup.3.1
    >
    > Name changes 3.1, 3.2, 3.3...etc. Why 3.x???? How do I set BE 9.0 (build
    > from CD) to consistently name the log file with the same name?
    >
    > Thanks in advance.
    >
    >




+ Reply to Thread