Two BackupExec Issues - Veritas Backup Exec

This is a discussion on Two BackupExec Issues - Veritas Backup Exec ; Backup Exec Issues Currently running 8.0, 3316 We are having a few problems with our current configuration. Based on the messages on this newsgroup, we are not the only ones. Here are our issues: OFO problem. OFO is running on ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: Two BackupExec Issues

  1. Two BackupExec Issues


    Backup Exec Issues
    Currently running 8.0, 3316

    We are having a few problems with our current configuration.
    Based on the messages on this newsgroup, we are not the only ones.
    Here are our issues:

    OFO problem. OFO is running on a remote Windows NT 4.0 SP6a Server. BE
    is running on a Windows 2000 SP1 server. We are getting the standard "Volume
    out of space and cannot be incremented message". When we installed the OFO,
    we used the defaults. When we first got this message, we increased the min
    and max to 300 and 500 respectively. We received the same error message
    the next day. We then changed the min and max to 500 and 1000, and hardcoded
    the location to be D:\OFO_TEMP and made sure the agent has full access to
    the folder. The next day, we received the same error message, although
    the backup did proceed further this day. At this point, we upgraded our
    version of BE on the backup server from v8 3315 to v83316. Without upgrading
    the OFO, we also changed our min and max options to 5GB and 7.5GB. The next
    day we received the message "OFO: Unknown error: 0x5aa. Also, when we were
    not using OFO, our backups would backup everything (65 GB), but would report
    approximately 7 files were corrupted and would not be able to be restored.
    This of course caused the backup job to fail. This is the reason why we
    installed OFO. Unfortunately, when OFO runs out of space, the job aborts!!
    When we received this latest message (the 0x5aa error), OFO fails to initialize,
    but the job runs anyway and backs up all data and lets us know which files
    it was unable to backup (marked as corrupted). Our understanding based on
    a technote for these corrupted files is that they are open and cannot be
    backed up correctly. The technote actually refers to Outlook PST files.
    We experienced this error on these Outlook files as well a a few on Quicken's
    QuickBook products (we believe the application was left open and running).
    Of course I would rather have the job complain about the 7 or so files it
    thinks are corrupt, but still backup the other 65 GB of data!!

    The other problem we are having has to do with the "Query Entity" error.
    We get this error randomly. We have two Adaptec SCSI 29160 cards installed
    in a Dell PowerEdge 1300 server. Each card has an HP DLT80e drive connected
    to it. These drives are identified as Quantum 1 and Quantum 2. The error
    we are receiving is: "Storage Device "Quantum 2" reported an error on a
    request to query entity information. Error reported: The object invoked
    has disconnected from its clients. An unknown error occured on Device "Quantum
    2"". This has happened three times in the last week. These cards are and
    DLT drives are about two weeks old. The HP DLT IV tapes are all brand new
    (two weeks old).

    For tonights backup, we will try uninstalling the current OFO, rebooting,
    installing the new version of the OFO (if in fact it has actually changed
    from 3315 to 3316) and rebooting, and set the min and max to 3GB each. Our
    backup kicks off at 10 PM, and I cannot see us changing more than 3 GB of
    data in the 5 hour window the backup takes. As far as the other error, I
    have seen a message on this newsgroup concerning uninstalling the Veritas
    tape drivers and re-installing the default MS drivers. I don't believe we
    ever installed the Vertitas drivers, so thats not really an option for us.

    If anyone has any comments, I would love to hear them.

    Thanks...

    Todd
    Todd.Klimek@marchfirst.com

  2. Re: Two BackupExec Issues

    The post about drivers was probably to replace the MS drivers with
    Veritas drivers or those provided by the mfg. The MS drivers are quite
    generic and the low timeout values can cause many SCSI related errors.

    Todd wrote:
    >
    > Backup Exec Issues
    > Currently running 8.0, 3316
    >
    > We are having a few problems with our current configuration.
    > Based on the messages on this newsgroup, we are not the only ones.
    > Here are our issues:
    >
    > OFO problem. OFO is running on a remote Windows NT 4.0 SP6a Server. BE
    > is running on a Windows 2000 SP1 server. We are getting the standard "Volume
    > out of space and cannot be incremented message". When we installed the OFO,
    > we used the defaults. When we first got this message, we increased the min
    > and max to 300 and 500 respectively. We received the same error message
    > the next day. We then changed the min and max to 500 and 1000, and hardcoded
    > the location to be D:\OFO_TEMP and made sure the agent has full access to
    > the folder. The next day, we received the same error message, although
    > the backup did proceed further this day. At this point, we upgraded our
    > version of BE on the backup server from v8 3315 to v83316. Without upgrading
    > the OFO, we also changed our min and max options to 5GB and 7.5GB. The next
    > day we received the message "OFO: Unknown error: 0x5aa. Also, when we were
    > not using OFO, our backups would backup everything (65 GB), but would report
    > approximately 7 files were corrupted and would not be able to be restored.
    > This of course caused the backup job to fail. This is the reason why we
    > installed OFO. Unfortunately, when OFO runs out of space, the job aborts!!
    > When we received this latest message (the 0x5aa error), OFO fails to initialize,
    > but the job runs anyway and backs up all data and lets us know which files
    > it was unable to backup (marked as corrupted). Our understanding based on
    > a technote for these corrupted files is that they are open and cannot be
    > backed up correctly. The technote actually refers to Outlook PST files.
    > We experienced this error on these Outlook files as well a a few on Quicken's
    > QuickBook products (we believe the application was left open and running).
    > Of course I would rather have the job complain about the 7 or so files it
    > thinks are corrupt, but still backup the other 65 GB of data!!
    >
    > The other problem we are having has to do with the "Query Entity" error.
    > We get this error randomly. We have two Adaptec SCSI 29160 cards installed
    > in a Dell PowerEdge 1300 server. Each card has an HP DLT80e drive connected
    > to it. These drives are identified as Quantum 1 and Quantum 2. The error
    > we are receiving is: "Storage Device "Quantum 2" reported an error on a
    > request to query entity information. Error reported: The object invoked
    > has disconnected from its clients. An unknown error occured on Device "Quantum
    > 2"". This has happened three times in the last week. These cards are and
    > DLT drives are about two weeks old. The HP DLT IV tapes are all brand new
    > (two weeks old).
    >
    > For tonights backup, we will try uninstalling the current OFO, rebooting,
    > installing the new version of the OFO (if in fact it has actually changed
    > from 3315 to 3316) and rebooting, and set the min and max to 3GB each. Our
    > backup kicks off at 10 PM, and I cannot see us changing more than 3 GB of
    > data in the 5 hour window the backup takes. As far as the other error, I
    > have seen a message on this newsgroup concerning uninstalling the Veritas
    > tape drivers and re-installing the default MS drivers. I don't believe we
    > ever installed the Vertitas drivers, so thats not really an option for us.
    >
    > If anyone has any comments, I would love to hear them.
    >
    > Thanks...
    >
    > Todd
    > Todd.Klimek@marchfirst.com


+ Reply to Thread