none of the requested files were backed up(2)

[Zahid_Haseeb]

I am using WIn2003 Server with Veritas Netbackup Server6.5.......I am trying to take the backup of MS SQL but having the below error. i can take the backup of flat files from the same client machine but not able to take the backup of SQL database. i can successfully ping each other and the names/IP are being resolved successfully


 
ACTIVITY MONITOR
10/19/2009 5:04:19 PM - requesting resource DotNet-

10/19/2009 5:04:19 PM - requesting resource veritas.NBU_CLIENT.MAXJOBS.Server-1

10/19/2009 5:04:19 PM - requesting resource veritas.NBU_POLICY.MAXJOBS.DotnetDatabase_245_testDB

10/19/2009 5:04:20 PM - granted resource veritas.NBU_CLIENT.MAXJOBS.Server-1

10/19/2009 5:04:20 PM - granted resource veritas.NBU_POLICY.MAXJOBS.DotnetDatabase_245_testDB

10/19/2009 5:04:20 PM - granted resource MediaID=@aaaaT;Path=M:\DotNet;MediaServer=Veritas

10/19/2009 5:04:20 PM - granted resource DotNet-

10/19/2009 5:04:20 PM - estimated 0 kbytes needed

10/19/2009 5:04:21 PM - started process bpbrm (10196)

10/19/2009 5:04:22 PM - connecting

10/19/2009 5:04:23 PM - connected; connect time: 00:00:01

10/19/2009 5:09:38 PM - end writing

none of the requested files were backed up(2)


STATUS VIEW from Client SIde

OPERATION BACKUP

DATABASE "DotnetDatabase"

SQLHOST "SERVER-1"

NBSERVER "VERITAS"

MAXTRANSFERSIZE 6

BLOCKSIZE 7

NUMBUFS 2

ENDOPER TRUE

INF - BACKUP STARTED USING

Microsoft SQL Server 2005 - 9.00.3200.00 (X64) 

Oct  2 2007 12:23:02 

Copyright (c) 1988-2005 Microsoft Corporation

Enterprise Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 2) 

Batch = C:\Program Files\Veritas\NetBackup\DbExt\MsSql\Veritas.Database.bch, Op# = 1

INF - Using backup image SERVER-1.MSSQL7.SERVER-1.db.DotnetDatabase.~.7.001of001.20091019135341..C

INF - backup database "DotnetDatabase" to VIRTUAL_DEVICE='VNBU0-136-4248-1255942421' with  stats = 10, blocksize = 65536, maxtransfersize = 4194304, buffercount = 2

INF - Number of stripes: 1, Number of buffers per stripe 2.

INF - Created VDI object for SQL Server instance <SERVER-1>. Connection timeout is <300> seconds.

Backup started Mon Oct 19 13:54:50 2009

ERR - Error in VxBSACreateObject: 3.

    CONTINUATION: - System detected error, operation aborted.

ERR - Error in GetCommand: 0x80770004.

    CONTINUATION: - An abort request is preventing anything except termination actions.

DBMS MSG - ODBC return code <-1>, SQL State <37000>, SQL Message <3202><[Microsoft][SQL Native Client][SQL Server]Write on "VNBU0-136-4248-1255942421" failed: 995(The I/O operation has been aborted because of either a thread exit or an application request.)>.

DBMS MSG - SQL Message <3271><[Microsoft][SQL Native Client][SQL Server]A nonrecoverable I/O error occurred on file "VNBU0-136-4248-1255942421:" 995(The I/O operation has been aborted because of either a thread exit or an application request.).>

DBMS MSG - SQL Message <3013><[Microsoft][SQL Native Client][SQL Server]BACKUP DATABASE is terminating abnormally.>

ERR - Error found executing <backup database "DotnetDatabase" to VIRTUAL_DEVICE='VNBU0-136-4248-1255942421' with  stats = 10, blocksize = 65536, maxtransfersize = 4194304, buffercount = 2>.

ERR - Error in VDS->Close: 0x80770004.

    CONTINUATION: - An abort request is preventing anything except termination actions.

INF - OPERATION #1 of batch C:\Program Files\Veritas\NetBackup\DbExt\MsSql\Veritas.Database.bch FAILED with STATUS 1 (0 is normal). Elapsed time = 2035(2035) seconds.

INF - Results of executing <C:\Program Files\Veritas\NetBackup\DbExt\MsSql\Veritas.Database.bch>: 

<0> operations succeeded. <1> operations failed.

INF - The following object(s) were not backed up successfully.

INF - DotnetDatabase

[Marianne]

Is 'Veritas' the Master as well as Media server?
Confirm that NBSERVER in the SQL scripts points to the master server and not a media server.

From the Activity Monitor output, it seems as if the backup fails after 5 minutes. For database backups, the default CLIENT_READ_TIMEOUT of 5 minutes is normally not enough. Increase this timeout on the media server to 900 (15 minutes) and see if that makes a difference.
Also ensure that you have a dbclient log directory on the client. Check dbclient log if backup still fails.

[Zahid_Haseeb]

Yes the Master Server is also the Media Server. My default timeout was 300 and i changed it to 3600 in Veritas Admin Console-->Host properties-->Client....and also in Veritas Admin Console-->Host properties-->Master Server 

[Zahid_Haseeb]

 Any reply will be appreciated

[Srikanth_Gubbal]

1. Change the log on to account in service and restart service.(optional)

2. After changing log on account(in services) prepare new script using Backup Sql Server objects(from client) for all the failed db's and start backup from master server using this newly prepared script.

[cobussmitJHB]

I have tried a few solutions including the TCP offload and are still getting the error that none of my files could be backed up (2) on SQL.

[Marianne]

Please post dbclient log file.

[ayodeji]

try backing up the SQL DB as flat files. lets see if it will work

[stu52]

Are you initiating the backup using the NBU SQL GUI on the SQL server?

Can you provide us with a listing of the policy that you are using?  Use the following command:

bppllist <policyname> -L

[stu52]

If the service account that the NetBackup client services is only running as a local admin and it doesn't have any SQL SA rights, then running a job like this from the backup server side will fail.

However, if a SQL DBA with SA rights runs the backup from the SQL server with the same conditions on the NetBackup client service, it will work just fine.

To fix this, you would have to give the NetBackup client service account SQL SA rights.  Then you can run the backup from the master server.

[rjrumfelt]

and was reading through it, then noticed how old the thread was and feel like I wasted my time >: |

Please, when encountering a problem that someone else has had, and the suggestions in their thread do not solve the problem, please start a new thread.

Follow the suggestions here so far - post the dbclient log, let us see how your policy is configured.

[Andy_Welburn]

We really do need old posts to be locked down.