Forum Discussion

NBU35's avatar
NBU35
Level 6
10 years ago
Solved

SQL DB backup failure

Hi 

Client Win 2000, SQL 2000,  NetBackup 6.5.5

master & media 7.6.0.3, Solaris 10.

database backup of all sql db are running fine except one. Its backup are failing with EC6.

and following errors we can see in evenet veiwer:

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

3041 : BACKUP failed to complete the command backup database "DB_NAME" to VIRTUAL_DEVICE='VNBU0-5656-5684-1424077140' with blocksize = 65536, maxtransfersize = 4194304, buffercount = 2”

 

 

 

7.6
Backup and Recovery
NetBackup
Not Applicable
  • revarooo's avatar
    revarooo
    10 years ago

    Check out these Technotes which covers similar errors:

    http://www.symantec.com/business/support/index?page=content&id=TECH207801

     

     

    http://www.symantec.com/business/support/index?page=content&id=TECH179424

    Cause

    Virtual memory limitation on the client system which sometimes is cleared up after reboot.

    Solution

     If issue persists after reboot, engage Microsoft Support to further look at the SQL-VDI Flush failure errors reported by SQL Server.

  • revarooo's avatar
    revarooo
    Level 6
    10 years ago

    Check out these Technotes which covers similar errors:

    http://www.symantec.com/business/support/index?page=content&id=TECH207801

     

     

    http://www.symantec.com/business/support/index?page=content&id=TECH179424

    Cause

    Virtual memory limitation on the client system which sometimes is cleared up after reboot.

    Solution

     If issue persists after reboot, engage Microsoft Support to further look at the SQL-VDI Flush failure errors reported by SQL Server.

  • Marianne's avatar
    Marianne
    Level 6
    10 years ago

    Client Win 2000, SQL 2000,  NetBackup 6.5.5 

    Oh dear............................................................

    No support here from Microsoft or Symantec.
    Are dba's and system owners aware of this?

    To get back to this one db - this is obviously an environment that has worked fine before, right?

    SQL dba will have to determine what is currently wrong with this db. 
    NBU is merely reporting the error.

    Errors in SQL vdi or errorlog?

    Can dba do a dump to disk of this db?

    Errors seen in NBU dbclient log? (logging level of 3)

  • NBU35's avatar
    NBU35
    Level 6
    10 years ago

    Hey Marianne..

    apology for delayed response, I was not available on forum for some days.

    This issue solved by reboot, got to know there were some low memory issue on server & it is a non prod server and planned for decommissioning, thats why customer did not opt to upgrade it.