SQL Server Performance

Backup problem

Discussion in 'Third Party Tools' started by oryand, Jul 27, 2003.

  1. oryand New Member

    Hello,

    I am using Veritas Netbackup 4.5 to (remote) backup my databases,
    sometimes, I have backup problems...

    The veritas people didn't find errors in the product.
    Somebody have an idea ?

    This is the error that I found in the errorlog:

    BACKUP failed to complete the command backup database "Amalot" to VIRTUAL_DEVICE='VNBU0-1896-3268' with blocksize = 512, maxtransfersize = 65536, buffercount = 1, differential

    BackupMedium::ReportIoError: write failure on backup device 'VNBU0-1896-3268'. Operating system error 995(error not found).

    Internal I/O request 0x2E227B50: Op: Write, pBuffer: 0x09C00200, Size: 512, Position: 0, UMS: Internal: 0x305561, InternalHigh: 0x2A20021, Offset: 0x70000, OffsetHigh: 0x3E80000, m_buf: 0x01000000, m_len: 150994944, m_actualBytes: 0, m_errcode: 995, BackupFile: VNBU0-1896-3268

    BackupVirtualDeviceFile::RequestDurableMedia: Flush failure on backup device 'VNBU0-1896-3268'. Operating system error 995(error not found).


    Thanks,
    Oryan
  2. Chappy New Member

    If these errors dont mean much to veritas people, I think they mean even less to us <img src='/community/emoticons/emotion-1.gif' alt=':)' /><br />But assuming a software fault has been ruled out, and its an intermittent problem, I would start working on the basis that the problem is one of the following:<br /><br />1) Faulty media - presumably youve tried with lots of tapes and get same error<br /><br />2) Network errors or throughput problems - do you have a local backup device you can backup to see if you get the same error.<br /><br />3) Faulty backup device <br /><br />Dont know what else to suggest, sorry<br />
  3. vbkenya New Member

    Think hardware! for now.

    Nathan H.O.
    Moderator
    SQL-Server-Performance.com
  4. Argyle New Member

    If you type "net helpmsg 995" in a command window you will see what the operating system reports as the error:
    "The I/O operation has been aborted because of either a thread exit or an application request."

    Might not mean much but it hints in the direction of media or hardware issue as mentioned by Chappy and Nathan.

    /Argyle
  5. satya Moderator

    Calculated responses by other Peers, also try running BACKUP statements from QA for the databases and see the results.

    Also try to test run on test environment and see any issues with S/w itself (mismatched .dlls).

    HTH

    _________
    Satya SKJ
    Moderator
    SQL-Server-Performance.Com
  6. timodee New Member

    Are you using the SQL extension for Netbackup? If not, you will need to configure SQL to backup databases to a directory on the hard drive, and have Netbackup pull the files from here (and exclude the SQL directories.)

    A couple of suggestions to determine the source of the problem:

    1) Can you backup files (not SQL databases) from this server? Create a test job that backs up some files (I personally have a test job that backs up c:winntsystem32driversetchosts).

    If (1) works, then the communications between the SQL server and the Netbackup server are fine, and there could be a configuration error in the SQL extension.

    2) If not...often the culprit is a problem with the tape/scsi connection. Try setting up a new Storage Unit in Netbackup - but make it the type "disk". Then re-try the the test job for the one-file backup. If this works, then you have a tape/Scsi problems. If not...

    3) Then you could have communication problems from the SQL server to the netbackup server. Open up a COMMAND window, and go to (Veritas Install Directory)
    etbackupin. Type bpclntcmd /? Then following the prompts, try to communicate to the netbackup server. Do the same from the NBU server to the SQL server. I often find that Netbackup needs a hosts file mapping ip addresses to names to backup servers consistently on busy networks.



    Timothy Mooney
    Optimal Computing
    Westchester County, NY
    www.optimalcomputing.com
  7. dktiger New Member

    Hello,
    I've got the same error.

    We also have tried resolve this problem w/ Microsoft and Veritas.

    1. We've tested with local database backup, it's successful.(Because SQL Server doesn't create the VDI(Virtual Device Interface) instance.)

    2. Checked the NIC fault. (It's ok.). Additionally, checked the negotiation problem between switch and backup client. These are set up w/ 100M full duplex link speed mode.

    3. Checked the time range(According to veritas support web-based, it sometimes happened error by trying backup File system and Database at the same time.). It's OK.

    What, how long do we have to verify and try to get the answer?(for Veritas and Microsoft)

    VERITAS didn't have any answers. and also, Microsoft doesn't have anything too.
    How can we resolve this problem?

    Please, let me get the resolution.

    Thanks.

    Ted Kim
    Sr. System Engineer
    CJ Systems
  8. satya Moderator

    Best to use legendary BACKUP/RESTORE statements with the help of job scheduler in SQL server, this is the one of the reason not to use third party tools for core database activities.

    At this stage you should depend on the BACKUP/RESTORE jobs and make sure you're optimum with the backup sets.

    _________
    Satya SKJ
    Moderator
    SQL-Server-Performance.Com
  9. mjohndrow New Member

    I had the problem today on a new server I built. My resolution was to get the latest patch for NetBackup. It updated bpcd.exe to version 3.4.1.175. I also had the problem on another server I didn't apply the latest patch , but did update bpcd.exe with version 3.4.1.175. bada bing! fixed

    good luck!
  10. dktiger New Member

    Hello.

    Different version of netbackup. our version is 4.5. Patch 2...Actually. published Patch 5 over. But, we can't apply w/ latest patch becase operate too many servers about 400 over Windows-based systems.Applying netbackup patch, Unix system is very easy, but NT is not.

    Regarding the error, "Flush failure on backup VDI(Virtual Device Interface)", we have looked at many sources w/ VERITAS AND MICROSOFT.

    Symptom: Netbackup process bphdb's memory access violation error. and unexpected exit().

    Cause: It was not compatible with Netbackup process "bphdb" and SQL Server backup agent. So to speak, shared memory problem on VDI.

    Resolution:
    1. Setup w/ latest service pack(Win 2K SP4 over, Win SQL Server 2000 SP 3 over)
    2. With Looking at w/ Dr.Watson/Event log at the ponint of the exit(), Debug these processes. Actually, Netbackup symbol table needed.


    Ted Kim
    Sr. System Engineer
    CJ Systems
  11. satya Moderator

    I think as specified by John, the patch for netbackup should fix such issues.

    _________
    Satya SKJ
    Moderator
    SQL-Server-Performance.Com
  12. dktiger New Member

    Sometimes, It might be impossible for you to patch systems. And should be find exact cause of the errors.

    Ted Kim
    Sr. System Engineer
    CJ Systems
  13. satya Moderator

    100% agree.

    _________
    Satya SKJ
    Moderator
    SQL-Server-Performance.Com
  14. umxa012 New Member

    Directory not found. Can not backup directory Resource\#23120;#20047;#23621;#19285;#20256;#27758;#28265;#23653;#12633;#13617;#14643;#21792;#8267;#28271;.pdf and its subdirectories.

    ay

    emmanuel
  15. satya Moderator

    Check whether the specified directory exists and permission for the account used too.

    Satya SKJ
    Moderator
    http://www.SQL-Server-Performance.Com/forum
    This posting is provided “AS IS” with no rights for the sake of knowledge sharing.
  16. ourdai New Member

    Had exactly the same issue. Could not backup but could restore OK.
    Tried backing up to disc, OK. Changed back to tape, failed again.

    Try these action points this sorted it for us.

    Ensure that the tape is appendable and if not erase it and return it to the scratch pool.

    Make sure that the Policy Volume Pool is active and has media available.

Share This Page