SQL jobs randomly failing and locking databases (7.5.0.1)

The eeb did fix the issue with locking the databases.  But now instead of locking the database it just skips it.  So we fix one issue only to now need to troubleshoot another.

On the bright side atleast only a couple of databases are failing instead of almost all of them.

Just to let you know the trouble now is i am recieving error 13s (file read failed) and at times error 1.  And of course this is randomly happening.  Every day its a toss up as to which server and database it might be.

Support seems to beleive its a timeout issue between the media server and the client but we have adjusted the time outs and its still happening.

Hi everyone

 i am experiencing error 6 and 2 in my new environmnet (NBU 7.5.0.3 windows2003/8, SQL Db backups) dbbackex hanging on the client side sometimes it reboots the production servers when trying to kill the process, i have applied the NB_7.5.0.3 SQL EEB client agent form support on my SQL servers and no luck.

 

And all of the SQL DB are on full recovery mode

anyone with the solution for this issue please help i have two servers that was last backed-up on the 18/08/2012 and the other on the 29/08/2012.

one of the servers

012/09/06 06:44:17 AM - Info dbclient(pid=4688) USER - Operation inhibited by NetBackup for Microsoft SQL Server: Only a full or incremental database backup can be performed on database <A2i_xCat_DBs> because it uses the simple recovery model or has 'truncate log on checkpoint' set.
2012/09/06 06:44:19 AM - Info dbclient(pid=4688) INF - OPERATION #1 of batch C:\Program Files\Veritas\NetBackup\dbext\mssql\temp\SAPSQLTransaction[0].bch1346907079[0].bch FAILED with STATUS 1 (0 is normal). Elapsed time = 5(5) seconds.
2012/09/06 06:44:32 AM - Info dbclient(pid=4688) USER - Operation inhibited by NetBackup for Microsoft SQL Server: Only a full or incremental database backup can be performed on database <MDMCATALOGUE_Z000> because it uses the simple recovery model or has 'truncate log on checkpoint' set.
2012/09/06 06:44:34 AM - Info dbclient(pid=4688) INF - OPERATION #2 of batch C:\Program Files\Veritas\NetBackup\dbext\mssql\temp\SAPSQLTransaction[0].bch1346907079[0].bch FAILED with STATUS 1 (0 is normal). Elapsed time = 3(3) seconds.
2012/09/06 06:44:48 AM - Info dbclient(pid=4688) USER - Operation inhibited by NetBackup for Microsoft SQL Server: Only a full or incremental database backup can be performed on database <MDMCATALOGUE_m000> because it uses the simple recovery model or has 'truncate log on checkpoint' set.
2012/09/06 06:44:50 AM - Info dbclient(pid=4688) INF - OPERATION #3 of batch C:\Program Files\Veritas\NetBackup\dbext\mssql\temp\SAPSQLTransaction[0].bch1346907079[0].bch FAILED with STATUS 1 (0 is normal). Elapsed time = 3(3) seconds.
2012/09/06 06:45:03 AM - Info dbclient(pid=4688) INF - BACKUP STARTED USING       
2012/09/06 06:45:03 AM - Info dbclient(pid=4688) Microsoft SQL Server 2005 - 9.00.4035.00 (X64)     
2012/09/06 06:45:03 AM - Info dbclient(pid=4688) Nov 24 2008 16:17:31        
2012/09/06 06:45:03 AM - Info dbclient(pid=4688) Copyright (c) 1988-2005 Microsoft Corporation       
2012/09/06 06:45:03 AM - Info dbclient(pid=4688) Enterprise Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 2)
2012/09/06 06:45:03 AM - Info dbclient(pid=4688) Batch = C:\Program Files\Veritas\NetBackup\dbext\mssql\temp\SAPSQLTransaction[0].bch1346907079[0].bch, Op# = 4     
2012/09/06 06:45:03 AM - Info dbclient(pid=4688) INF - Using backup image C75FSRM003.MSSQL7.C75FSRM003.trx.SRP.~.7.001of001.20120906065308..C      
2012/09/06 06:45:03 AM - Info dbclient(pid=4688) INF - backup log "SRP" to VIRTUAL_DEVICE='VNBU0-4688-4540-1346907189' with  stats = 10, blocksize = 65536, maxtransfersize = 4194304, buffercount = 2
2012/09/06 06:45:03 AM - Info dbclient(pid=4688) INF - Number of stripes: 1, Number of buffers per stripe 2.
2012/09/06 06:45:04 AM - Info dbclient(pid=4688) INF - Created VDI object for SQL Server instance <C75FSRM003>. Connection timeout is <300> seconds.
2012/09/06 06:50:04 AM - Info dbclient(pid=4688) ERR - Error in GetConfiguration: 0x80770003.      
2012/09/06 06:50:04 AM - Info dbclient(pid=4688)     CONTINUATION: - The api was waiting and the timeout interval had elapsed.
2012/09/06 06:50:04 AM - Info dbclient(pid=4688) DBMS MSG - ODBC return code <-1>, SQL State <37000>, SQL Message <4214><[Microsoft][SQL Native Client][SQL Server]BACKUP LOG cannot be performed because there is no current database backup.>.
2012/09/06 06:50:04 AM - Info dbclient(pid=4688) DBMS MSG - SQL Message <3013><[Microsoft][SQL Native Client][SQL Server]BACKUP LOG is terminating abnormally.>
2012/09/06 06:50:04 AM - Info dbclient(pid=4688) ERR - Error found executing <backup log "SRP" to VIRTUAL_DEVICE='VNBU0-4688-4540-1346907189' with  stats = 10, blocksize = 65536, maxtransfersize = 4194304, buffercount = 2>.
2012/09/06 06:50:06 AM - Info dbclient(pid=4688) ERR - Error in VDS->Close: 0x80770004.      
2012/09/06 06:50:06 AM - Info dbclient(pid=4688)     CONTINUATION: - An abort request is preventing anything except termination actions.
2012/09/06 06:50:06 AM - Info dbclient(pid=4688) INF - OPERATION #4 of batch C:\Program Files\Veritas\NetBackup\dbext\mssql\temp\SAPSQLTransaction[0].bch1346907079[0].bch FAILED with STATUS 1 (0 is normal). Elapsed time = 305(305) seconds.
2012/09/06 06:50:20 AM - Info dbclient(pid=4688) USER - Operation inhibited by NetBackup for Microsoft SQL Server: Only a full backup can be performed on the master database.
2012/09/06 06:50:22 AM - Info dbclient(pid=4688) INF - OPERATION #5 of batch C:\Program Files\Veritas\NetBackup\dbext\mssql\temp\SAPSQLTransaction[0].bch1346907079[0].bch FAILED with STATUS 1 (0 is normal). Elapsed time = 3(3) seconds.
2012/09/06 06:50:35 AM - Info dbclient(pid=4688) USER - Operation inhibited by NetBackup for Microsoft SQL Server: Only a full or incremental database backup can be performed on database <model> because it uses the simple recovery model or has 'truncate log on checkpoint' set.
2012/09/06 06:50:37 AM - Info dbclient(pid=4688) INF - OPERATION #6 of batch C:\Program Files\Veritas\NetBackup\dbext\mssql\temp\SAPSQLTransaction[0].bch1346907079[0].bch FAILED with STATUS 1 (0 is normal). Elapsed time = 3(3) seconds.
2012/09/06 06:50:50 AM - Info dbclient(pid=4688) USER - Operation inhibited by NetBackup for Microsoft SQL Server: Only a full or incremental database backup can be performed on database <msdb> because it uses the simple recovery model or has 'truncate log on checkpoint' set.
2012/09/06 06:50:52 AM - Info dbclient(pid=4688) INF - OPERATION #7 of batch C:\Program Files\Veritas\NetBackup\dbext\mssql\temp\SAPSQLTransaction[0].bch1346907079[0].bch FAILED with STATUS 1 (0 is normal). Elapsed time = 3(3) seconds.
2012/09/06 06:50:55 AM - Info dbclient(pid=4688) INF - Results of executing <C:\Program Files\Veritas\NetBackup\dbext\mssql\temp\SAPSQLTransaction[0].bch1346907079[0].bch>:     
2012/09/06 06:50:55 AM - Info dbclient(pid=4688) <0> operations succeeded. <7> operations failed.      
2012/09/06 06:50:55 AM - Info dbclient(pid=4688) INF - The following object(s) were not backed up successfully.  
2012/09/06 06:50:55 AM - Info dbclient(pid=4688) INF - A2i_xCat_DBs         
2012/09/06 06:50:55 AM - Info dbclient(pid=4688) INF - MDMCATALOGUE_Z000         
2012/09/06 06:50:55 AM - Info dbclient(pid=4688) INF - MDMCATALOGUE_m000         
2012/09/06 06:50:55 AM - Info dbclient(pid=4688) INF - SRP         
2012/09/06 06:50:55 AM - Info dbclient(pid=4688) INF - master         
2012/09/06 06:50:55 AM - Info dbclient(pid=4688) INF - model         
2012/09/06 06:50:55 AM - Info dbclient(pid=4688) INF - msdb         
2012/09/06 06:50:55 AM - Info dbclient(pid=4688) INF - This batch was run 2 times and resulted in 0 successful backup(s) and 7 failure(s) after repeated attempts.

 

Thank you

Sorry buddy but have have been working with support for almost 2 months on this and I stil get error 83, 6, 2, and 1 almost every single day.  Just this morning i sent 300mb worth of logs to them. 

Sorry to say this but atleast i know that upgrading to 7.5.0.3 does not resolve the problem because i have been wondering if it would.

As you can see there are LOTS of people having this very same issue and i am ashamed to admit that i have been putting up with this for 2 months.  A fix should have been released by now.

The eeb did resolve my issue with dbbackex.exe so i dont know if thats a 7.5.0.1 thing or not. 

i will definitly update this post as soon as support provides me with something.

Does anyone have any new findings to report? 

Because I have been instructed by support that i need to call microsoft to have them look into performance tuning my sql instances to try and resolve the error 6's. 

I find it odd that i went from no sql failures to every sql server haveing failures and performance tuning is what i should do to fix it.

I did opened the microsoft ticket this morning so i will report back whatever they suggest.

 

I'm seeing the same issue.  I'll be opening a call with Symantec likely next Monday or Tuesday.  Sounds like 7.5.0.3 patch resolves some of the errors but not all of them?  Is that correct?

I'm still running Server 7.0 - this is the only client I've taken to 7.5.

For 7.5.0.3 please open a case with support and reference etrack 2846239.

Please mark as solution if this resolves your issue.

 

Please open a case with support and reference etrack 2846239

Please mark this as solution if this resolves your issue.

 

Dyneshia,

 

Is the 7.5.0.3 you are referring to the client version or the Server version?  I'm currently on Server 7.0

with Client 7.5.0.1.

Thank you!

 

You are stating that your Master server is 7.0 ??  And the cleint is 7.5.0.1 ?

If so you muct upgrade your Master server to at least 7.5 .  Prefrebly 7.5.0.1 however the base install of 7.5 will work.

If you mean your Master server is 7.5 then yes you can have your SQL server at 7.5.0.1 or 7.5.0.3.  When I referred 7.5.0.3 I was reffering to the client.