Still Getting Errors after updating v7.3 to build 2575 w/patches - Veritas Backup Exec

This is a discussion on Still Getting Errors after updating v7.3 to build 2575 w/patches - Veritas Backup Exec ; After upgrading Backup Exec v7.3 to build 2575 (2nd Edition) and applying the post2575 and spanfix patches, I still receive the following error during the verify portion of my backups... Verify of "\\SUPPORTLOGIC\D$ " Backup set #140 on storage media ...

+ Reply to Thread
Results 1 to 5 of 5

Thread: Still Getting Errors after updating v7.3 to build 2575 w/patches

  1. Still Getting Errors after updating v7.3 to build 2575 w/patches

    After upgrading Backup Exec v7.3 to build 2575 (2nd Edition) and applying
    the post2575 and spanfix patches, I still receive the following error during
    the verify portion of my backups...

    Verify of "\\SUPPORTLOGIC\D$ "
    Backup set #140 on storage media #2
    Backup set description: "Bobcat/Scraper/Saleslogic/Supportlogic"
    Verify started on 12/3/99 at 1:19:20 AM.
    Unexpected end of backup set encountered on HP Quantum DLT418.
    ^ ^ ^ ^ ^

    Any insights out there would be greatly appreciated.

    I have two autoloader backup devices attached to the backup server which run
    simultaneously during backup jobs. I've been suspecting that this might be
    the problem.

    Frank



  2. Re: Still Getting Errors after updating v7.3 to build 2575 w/patches

    See TechNote ID: 010-103259. Talks about multi-Volume backupsets
    when a single object spans volumes ie. large IS/DS or SQL databases

    Veritas has a link to a Fix in the Tech Note.

    Frank Wagner wrote:

    > After upgrading Backup Exec v7.3 to build 2575 (2nd Edition) and applying
    > the post2575 and spanfix patches, I still receive the following error during
    > the verify portion of my backups...
    >
    > Verify of "\\SUPPORTLOGIC\D$ "
    > Backup set #140 on storage media #2
    > Backup set description: "Bobcat/Scraper/Saleslogic/Supportlogic"
    > Verify started on 12/3/99 at 1:19:20 AM.
    > Unexpected end of backup set encountered on HP Quantum DLT418.
    > ^ ^ ^ ^ ^
    >
    > Any insights out there would be greatly appreciated.
    >
    > I have two autoloader backup devices attached to the backup server which run
    > simultaneously during backup jobs. I've been suspecting that this might be
    > the problem.
    >
    > Frank



  3. Re: Still Getting Errors after updating v7.3 to build 2575 w/patches

    Ken,

    This is where I got the idea to upgrade to the second edition of build 2575
    with the post 2575 and spanfix patches; however, even after this upgrade --
    which is what TechNote ID: 010-103259 suggests to resolve this problem --
    I'm still receiving the same error message in my backups. I even tried to
    reinstall the latest version and reapply the patches to no avail.


    Ken Putnam wrote in message
    news:384810D0.60F7BAD7@zd.com...
    > See TechNote ID: 010-103259. Talks about multi-Volume backupsets
    > when a single object spans volumes ie. large IS/DS or SQL databases
    >
    > Veritas has a link to a Fix in the Tech Note.
    >
    > Frank Wagner wrote:
    >
    > > After upgrading Backup Exec v7.3 to build 2575 (2nd Edition) and

    applying
    > > the post2575 and spanfix patches, I still receive the following error

    during
    > > the verify portion of my backups...
    > >
    > > Verify of "\\SUPPORTLOGIC\D$ "
    > > Backup set #140 on storage media #2
    > > Backup set description: "Bobcat/Scraper/Saleslogic/Supportlogic"
    > > Verify started on 12/3/99 at 1:19:20 AM.
    > > Unexpected end of backup set encountered on HP Quantum DLT418.
    > > ^ ^ ^ ^ ^
    > >
    > > Any insights out there would be greatly appreciated.
    > >
    > > I have two autoloader backup devices attached to the backup server which

    run
    > > simultaneously during backup jobs. I've been suspecting that this might

    be
    > > the problem.
    > >
    > > Frank

    >




  4. Re: Still Getting Errors after updating v7.3 to build 2575 w/patches

    In article <38482125@hronntp01.?>, Frank Wagner
    writes
    >This is where I got the idea to upgrade to the second edition of build 2575
    >with the post 2575 and spanfix patches; however, even after this upgrade --
    >which is what TechNote ID: 010-103259 suggests to resolve this problem --
    >I'm still receiving the same error message in my backups. I even tried to
    >reinstall the latest version and reapply the patches to no avail.


    The only thought I've got is to reinstall the latest tape and loader
    drivers.

    Beyond that, all I can think of is checking the firmware on your loader
    and DLT drive is up to date, and your SCSI controller driver is up to
    date, but that's at the "desperately grabbing at straws" level and may
    inadvertently make things worse.


    If SpanFix hasn't worked for you, and you're sure your drivers are up to
    date, I suggest you email a report to Veritas Support. Presumably you
    have checked that bengine.exe is the new (SpanFix) version, and you've
    stopped and restarted the BENT services to make sure it's that version
    that's running (it's unlikely that you haven't - normally you have to
    stop the BENT services to change the file over).





    David
    --
    David Wood david@wood2.demon.co.uk
    Please post any replies to this group - "post and mail" is not needed.
    DISCLAIMER: I am not an employee of Veritas, merely a user who's trying
    to share his ideas and experience. Follow my advice at your own risk.

  5. Re: Still Getting Errors after updating v7.3 to build 2575 w/patches

    Frank -

    I'm almost in the same boat, but I'm posting in hopes that maybe someone can
    help read the tea leaves.

    My problem is in doing a SQL Server 7.0 multi-tape *backup*. After filling
    the first tape, a little bit of data is written to the second tape
    (presumably a buffer being flushed) and then the backup fails with the
    following Event Log messages from SQL Server:

    18210 :
    BackupMedium::ReportIoError: write failure on backup device
    'BackupExecSqlAgent_PRIMARY_00'. Operating system error 995(The I/O
    operation has been aborted because of either a thread exit or an
    application request.).

    followed by:

    18210 :
    BackupVirtualDeviceFile::RequestDurableMedia: Flush failure on backup device
    'BackupExecSqlAgent_PRIMARY_00'. Operating system error 995(The I/O
    operation has been aborted because of either a thread exit or an
    application request.).

    followed by:

    Job "DRG Full Backup" ended in an error state. Examine recent event log
    entries and the Job History for details.

    The BE error message reports:

    WARNING: "DRG?PRIMARY" is a corrupt file.
    This file cannot verify.

    I've done all the dance steps you've tried. I was even told by support that
    I should install the Veritas driver for my Exabyte Eliant 820 drive - which
    I had not done because it's not on the device list on the Web. I was told
    that support had a different list that included it (I had been using the
    Exabyte NT driver). This change actually seems to make things worse, as it
    fails after only a few megabytes. I'm still completely up a creek!

    - Ed

    Frank Wagner wrote in message
    news:3847f978@hronntp01....
    > After upgrading Backup Exec v7.3 to build 2575 (2nd Edition) and applying
    > the post2575 and spanfix patches, I still receive the following error

    during
    > the verify portion of my backups...
    >
    > Verify of "\\SUPPORTLOGIC\D$ "
    > Backup set #140 on storage media #2
    > Backup set description: "Bobcat/Scraper/Saleslogic/Supportlogic"
    > Verify started on 12/3/99 at 1:19:20 AM.
    > Unexpected end of backup set encountered on HP Quantum DLT418.
    > ^ ^ ^ ^ ^
    >
    > Any insights out there would be greatly appreciated.
    >
    > I have two autoloader backup devices attached to the backup server which

    run
    > simultaneously during backup jobs. I've been suspecting that this might be
    > the problem.
    >
    > Frank
    >
    >




+ Reply to Thread