Highlighted

MS SQL backups for a single Database happening partially

Hi All,

Master Server: Sun Solarisn  5.10
NBu version: 7.5.0.6

MS Sql Server:

Microsoft windows server 2003

SQL server version 2008

Nbu version : 7.5.0.6, Client server

Media Server
Solaris10
NBu version: 7.5.0.6


My SQL backup for a perticular database is failing continuously with status 1. While the other databases on the server are getiing successfuly backed up everyday.

The logs are mentioned below which state that the backup has happened partially :

 

INF - BACKUP STARTED USING
Microsoft SQL Server 2008 (SP3) - 10.0.5500.0 (Intel X86) 
Sep 22 2011 00:28:06 
Copyright (c) 1988-2008 Microsoft Corporation
Standard Edition on Windows NT 5.2 <X86> (Build 3790: Service Pack 2) (VM) 
Batch = diff_2008.bch, Op# = 1
INF - Using backup image mlxibgmbiap3.MSSQL7.MLXIBGMBIAP3\SQL2008STD.inc.lts.~.7.001of001.20141226180614..C
INF - backup database "lts" to VIRTUAL_DEVICE='VNBU0-23664-12980-1419597378' with  stats = 10, blocksize = 65536, maxtransfersize = 4194304, buffercount = 2, differential
INF - Number of stripes: 1, Number of buffers per stripe 2.
INF - Created VDI object for SQL Server instance <SQL2008STD>. Connection timeout is <300> seconds.
ERR - Error in GetConfiguration: 0x80770003.
    CONTINUATION: - The api was waiting and the timeout interval had elapsed.
ERR - Error in VDS->Close: 0x80770004.
    CONTINUATION: - An abort request is preventing anything except termination actions.
INF - OPERATION #1 of batch diff_2008.bch FAILED with STATUS 1 (0 is normal). Elapsed time = 321(0) seconds


The script is as follows:

OPERATION BACKUP
DATABASE "lts"
SQLHOST "mlxibgmbiap3"
SQLINSTANCE "SQL2008STD"
NBSERVER "HYDT5440-NBMS"
MAXTRANSFERSIZE 6
BLOCKSIZE 7
DUMPOPTION INCREMENTAL
NUMBUFS 2
ENDOPER TRUE

If I try to start a backup for the individual database after making sure that no " dbbackup.exe or dbbackex.exe" process are running I get the below mentioned errors:

OPERATION BACKUP
DATABASE "lts"
SQLHOST "mlxibgmbiap3"
SQLINSTANCE "SQL2008STD"
NBSERVER "HYDT5440-NBMS"
MAXTRANSFERSIZE 6
BLOCKSIZE 7
POLICY MLXIBGMBIAP3-SQL2008STD-DIFF
NUMBUFS 2
ENDOPER TRUE

INF - BACKUP STARTED USING
Microsoft SQL Server 2008 (SP3) - 10.0.5500.0 (Intel X86) 
Sep 22 2011 00:28:06 
Copyright (c) 1988-2008 Microsoft Corporation
Standard Edition on Windows NT 5.2 <X86> (Build 3790: Service Pack 2) (VM) 
Batch = C:\Program Files\Veritas\NetBackup\dbext\mssql\temp\__11_12_18_261_00.bch, Op# = 1
INF - Using backup image mlxibgmbiap3.MSSQL7.MLXIBGMBIAP3\SQL2008STD.db.lts.~.7.001of001.20141226111220..C
INF - backup database "lts" to VIRTUAL_DEVICE='VNBU0-24244-23880-1419572542' 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 <SQL2008STD>. Connection timeout is <300> seconds.
ERR - Error in GetConfiguration: 0x80770003.
    CONTINUATION: - The api was waiting and the timeout interval had elapsed.
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\temp\__11_12_18_261_00.bch FAILED with STATUS 1 (0 is normal). Elapsed time = 311(0) seconds.
INF - Results of executing <C:\Program Files\Veritas\NetBackup\dbext\mssql\temp\__11_12_18_261_00.bch>: 
<0> operations succeeded. <1> operations failed.
INF - The following object(s) were not backed up successfully.
INF - lts


Kindly sugest how to know the reason for the partial backup and way to resolve it.


Thanks.

 

1 Solution

Accepted Solutions
Highlighted
Accepted Solution!

Have you checked MS-SQL

Have you checked MS-SQL errorlog and VDI logs as well?

All I can see in the dbclient log is a 5 minute timeout.
Try to increase VDI and NBU timeouts:
In backup script, add:

VDITIMEOUTSECONDS 900

On Media server, increase Client Connect and Client Read Timeout to 900.

We have seen that large databases may even need timeouts of 1800.

View solution in original post

7 Replies
Highlighted

You will have to look at your

You will have to look at your application logs for more information. Netbackup runs the script and waits for the backup image to be passed along from SQL. You have to troubleshoot what is happening on the SQL server. 

There are many things that could be conflicting with the backup.

Here is an example:

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

Highlighted

Not enough info in this

Not enough info in this log.

Create dbclient folder on the client under C:\Program Files\Veritas\NetBackup\logs and retry backup for this database.
Copy the log to dbclient.txt and upload as File attachment.

Also check Windows Event Viewer Application log and SQL 'error' log for possible reasons.

Highlighted

Hi Marianne, Kindly find the

Hi Marianne,

Kindly find the attached dbclient logs and snapshots of application error logs.

Highlighted

Any help please.....

Any help please.....

Highlighted
Accepted Solution!

Have you checked MS-SQL

Have you checked MS-SQL errorlog and VDI logs as well?

All I can see in the dbclient log is a 5 minute timeout.
Try to increase VDI and NBU timeouts:
In backup script, add:

VDITIMEOUTSECONDS 900

On Media server, increase Client Connect and Client Read Timeout to 900.

We have seen that large databases may even need timeouts of 1800.

View solution in original post

Re: Have you checked MS-SQL

Hi Marianne,

how to increase the VDI time.

 

Regards

Subbu

7658961548

Highlighted

Re: Have you checked MS-SQL

You need to add it to the backup script as per my post above.

If you need further assistance, please start a new discussion with details of your issue .