Backup Exec 9.1 log files - Veritas Backup Exec

This is a discussion on Backup Exec 9.1 log files - Veritas Backup Exec ; Running BE 9.1on Windows 2000 server with all latest service packs. My problem is with the BE log file format ie XML. We have to keep all backup log files indefinately to comply with US federal laws (Sarbanes Oxley). In ...

+ Reply to Thread
Results 1 to 4 of 4

Thread: Backup Exec 9.1 log files

  1. Backup Exec 9.1 log files


    Running BE 9.1on Windows 2000 server with all latest service packs.
    My problem is with the BE log file format ie XML.
    We have to keep all backup log files indefinately to comply with US federal
    laws
    (Sarbanes Oxley). In past versions the log files were .TXT and I ran a utility
    as a
    post job command that copied and renamed the log file to central location
    and then
    deleted the original file (BEXxx.txt) from the data directory. This was perfect
    for my needs as when the backup jobs ran the next night the log files would
    have the
    same numbers again ie BEX00.txt, BEX01.txt etc each day.
    Now the log files are XML and numbers are incremental even if the log files
    are deleted, so the utility does not work any more. I know there is a utility
    to convert
    the log files from XML to TXT but as the log files are numbered incrementally
    then
    this utility has to be run manually.
    Does anybody know how to automatically (or use the post job command) to convert
    the log files to text and stop them incrementing

  2. Re: Backup Exec 9.1 log files

    Steve Birtles wrote:
    > Running BE 9.1on Windows 2000 server with all latest service packs.
    > My problem is with the BE log file format ie XML.
    > We have to keep all backup log files indefinately to comply with US federal
    > laws
    > (Sarbanes Oxley). In past versions the log files were .TXT and I ran a utility
    > as a
    > post job command that copied and renamed the log file to central location
    > and then
    > deleted the original file (BEXxx.txt) from the data directory. This was perfect
    > for my needs as when the backup jobs ran the next night the log files would
    > have the
    > same numbers again ie BEX00.txt, BEX01.txt etc each day.
    > Now the log files are XML and numbers are incremental even if the log files
    > are deleted, so the utility does not work any more. I know there is a utility
    > to convert
    > the log files from XML to TXT but as the log files are numbered incrementally
    > then
    > this utility has to be run manually.
    > Does anybody know how to automatically (or use the post job command) to convert
    > the log files to text and stop them incrementing


    You could use XCOPY with the /D switch and no operand

    /D:m-d-y Copies files changed on or after the specified date.
    If no date is given, copies only those files whose
    source time is newer than the destination time.

  3. Re: Backup Exec 9.1 log files

    Steve Birtles wrote:
    > Ken Putnam wrote:
    >
    >>Steve Birtles wrote:
    >>
    >>>Running BE 9.1on Windows 2000 server with all latest service packs.
    >>>My problem is with the BE log file format ie XML.
    >>>We have to keep all backup log files indefinately to comply with US federal
    >>>laws
    >>>(Sarbanes Oxley). In past versions the log files were .TXT and I ran a

    >
    > utility
    >
    >>>as a
    >>>post job command that copied and renamed the log file to central location
    >>>and then
    >>>deleted the original file (BEXxx.txt) from the data directory. This was

    >
    > perfect
    >
    >>>for my needs as when the backup jobs ran the next night the log files

    >
    > would
    >
    >>>have the
    >>>same numbers again ie BEX00.txt, BEX01.txt etc each day.
    >>>Now the log files are XML and numbers are incremental even if the log

    >
    > files
    >
    >>>are deleted, so the utility does not work any more. I know there is a

    >
    > utility
    >
    >>>to convert
    >>>the log files from XML to TXT but as the log files are numbered incrementally
    >>>then
    >>>this utility has to be run manually.
    >>>Does anybody know how to automatically (or use the post job command) to

    >
    > convert
    >
    >>>the log files to text and stop them incrementing

    >>
    >>You could use XCOPY with the /D switch and no operand
    >>
    >> /D:m-d-y Copies files changed on or after the specified date.
    >> If no date is given, copies only those files whose
    >> source time is newer than the destination time.

    >
    > Ken thanks for the response. Unfortunately we run around ten backup jobs
    > per night onto five tape drives so this generates ten log files so this solution
    > could not work as each log file needs to go to a seperate folder.



    Well -

    As long as there is more than a few seconds between end-of-job for
    various jobs, you can script a dir listing, sorted by date, grab the
    latest, rename and copy. Run this as a POST CMD for each job so that
    you rename each file the way you want it

    Using REXX for windows, I did this for several automated tasks awhile ago.

  4. Re: Backup Exec 9.1 log files


    Ken Putnam wrote:
    >Steve Birtles wrote:
    >> Running BE 9.1on Windows 2000 server with all latest service packs.
    >> My problem is with the BE log file format ie XML.
    >> We have to keep all backup log files indefinately to comply with US federal
    >> laws
    >> (Sarbanes Oxley). In past versions the log files were .TXT and I ran a

    utility
    >> as a
    >> post job command that copied and renamed the log file to central location
    >> and then
    >> deleted the original file (BEXxx.txt) from the data directory. This was

    perfect
    >> for my needs as when the backup jobs ran the next night the log files

    would
    >> have the
    >> same numbers again ie BEX00.txt, BEX01.txt etc each day.
    >> Now the log files are XML and numbers are incremental even if the log

    files
    >> are deleted, so the utility does not work any more. I know there is a

    utility
    >> to convert
    >> the log files from XML to TXT but as the log files are numbered incrementally
    >> then
    >> this utility has to be run manually.
    >> Does anybody know how to automatically (or use the post job command) to

    convert
    >> the log files to text and stop them incrementing

    >
    >You could use XCOPY with the /D switch and no operand
    >
    > /D:m-d-y Copies files changed on or after the specified date.
    > If no date is given, copies only those files whose
    > source time is newer than the destination time.

    Ken thanks for the response. Unfortunately we run around ten backup jobs
    per night onto five tape drives so this generates ten log files so this solution
    could not work as each log file needs to go to a seperate folder.

+ Reply to Thread