cancel
Showing results for 
Search instead for 
Did you mean: 

SQL backup problem

Vjeksa
Level 4

Hi,

I've problem with backup on one SQL server.

Environment:

Master/media  server: Win 2008 R2, Netbackup 7.6.0.1

SQL server: Win2012 R2, Netbackup 7.7.3, SQL Server 2014

 

Job details

6.4.2017. 11:44:49 - Info nbjm(pid=3500) starting backup job (jobid=1973) for client hrs000185, policy EBC_SQL_HRS000185_F_dnevni, schedule SQL_F_dnevni
6.4.2017. 11:44:49 - Info nbjm(pid=3500) requesting MEDIA_SERVER_WITH_ATTRIBUTES resources from RB for backup job (jobid=1973, request id:{0CD5D045-6B22-428E-95E9-337A03E1BADF})
6.4.2017. 11:44:49 - requesting resource dd860bj-Data_SQL
6.4.2017. 11:44:49 - requesting resource filebackup.NBU_CLIENT.MAXJOBS.hrs000185
6.4.2017. 11:44:49 - requesting resource filebackup.NBU_POLICY.MAXJOBS.EBC_SQL_HRS000185_F_dnevni
6.4.2017. 11:44:50 - granted resource filebackup.NBU_CLIENT.MAXJOBS.hrs000185
6.4.2017. 11:44:50 - granted resource filebackup.NBU_POLICY.MAXJOBS.EBC_SQL_HRS000185_F_dnevni
6.4.2017. 11:44:50 - granted resource dd860bj-Data_SQL
6.4.2017. 11:44:50 - estimated 0 Kbytes needed
6.4.2017. 11:44:50 - Info nbjm(pid=3500) started backup (backupid=hrs000185_1491471890) job for client hrs000185, policy EBC_SQL_HRS000185_F_dnevni, schedule SQL_F_dnevni on storage unit dd860bj-Data_SQL
6.4.2017. 11:44:50 - started process bpbrm (11188)
6.4.2017. 11:44:53 - Info bpbrm(pid=11188) hrs000185 is the host to backup data from
6.4.2017. 11:44:53 - Info bpbrm(pid=11188) reading file list for client
6.4.2017. 11:44:53 - connecting
6.4.2017. 11:44:57 - Info bpbrm(pid=11188) starting bphdb on client
6.4.2017. 11:44:58 - connected; connect time: 0:00:05
6.4.2017. 11:44:58 - Info bphdb(pid=9496) Backup started
6.4.2017. 11:45:40 - Info dbclient(pid=8052) INF - BACKUP STARTED USING
6.4.2017. 11:45:40 - Info dbclient(pid=8052) Microsoft SQL Server 2014 (SP2-CU2-GDR) (KB3194718) - 12.0.5532.0 (X64)
6.4.2017. 11:45:40 - Info dbclient(pid=8052) Oct 5 2016 20:28:25
6.4.2017. 11:45:40 - Info dbclient(pid=8052) Copyright (c) Microsoft Corporation
6.4.2017. 11:45:40 - Info dbclient(pid=8052) Standard Edition (64-bit) on Windows NT 6.3 <X64> (Build 9600: ) (Hypervisor)
6.4.2017. 11:45:40 - Info dbclient(pid=8052) Batch = C:\Program Files\Veritas\NetBackup\DbExt\MsSql\ttt.bch, Op# = 1
6.4.2017. 11:45:50 - Info dbclient(pid=8052) INF - Using backup image HRS000185.MSSQL7.HRS000185.db.Erste.~.7.001of001.20170406114536..C
6.4.2017. 11:46:01 - Info dbclient(pid=8052) INF - backup database "Erste" to VIRTUAL_DEVICE='VNBU0-8052-8684-1491471947' with stats = 10, blocksize = 65536, maxtransfersize = 4194304, buffercount = 2
6.4.2017. 11:46:21 - Info dbclient(pid=8052) INF - Number of stripes: 1, Number of buffers per stripe 2.
6.4.2017. 11:46:31 - Info dbclient(pid=8052) INF - Created VDI object for SQL Server instance <HRS000185>. Connection timeout is <300> seconds.
6.4.2017. 12:02:16 - Info dbclient(pid=8052) ERR - Error in VxBSACreateObject: 3.
6.4.2017. 12:02:26 - Info dbclient(pid=8052) CONTINUATION: - System detected error, operation aborted.
6.4.2017. 12:02:47 - Info dbclient(pid=8052) ERR - Error in GetCommand: 0x80770004.
6.4.2017. 12:02:47 - Info dbclient(pid=8052) DBMS MSG - ODBC return code <-1>, SQL State <37000>, SQL Message <3202><[Microsoft][SQL Server Native Client 11.0][SQL Server]Write on "VNBU0-8052-8684-1491471947" failed: 995(The I/O operation has been aborted because of either a thread exit or an application request.)>.
6.4.2017. 12:02:57 - Info dbclient(pid=8052) CONTINUATION: - An abort request is preventing anything except termination actions.
6.4.2017. 12:03:07 - Info dbclient(pid=8052) DBMS MSG - SQL Message <3271><[Microsoft][SQL Server Native Client 11.0][SQL Server]A nonrecoverable I/O error occurred on file "VNBU0-8052-8684-1491471947:" 995(The I/O operation has been aborted because of either a thread exit or an application request.).>
6.4.2017. 12:03:17 - Info dbclient(pid=8052) DBMS MSG - SQL Message <3013><[Microsoft][SQL Server Native Client 11.0][SQL Server]BACKUP DATABASE is terminating abnormally.>
6.4.2017. 12:03:27 - Info dbclient(pid=8052) ERR - Error found executing <backup database "Erste" to VIRTUAL_DEVICE='VNBU0-8052-8684-1491471947' with stats = 10, blocksize = 65536, maxtransfersize = 4194304, buffercount = 2>.
6.4.2017. 12:04:02 - Info dbclient(pid=8052) INF - OPERATION #1 of batch C:\Program Files\Veritas\NetBackup\DbExt\MsSql\ttt.bch FAILED with STATUS 1 (0 is normal). Elapsed time = 1103(1103) seconds.
6.4.2017. 12:04:15 - Info dbclient(pid=8052) INF - Results of executing <C:\Program Files\Veritas\NetBackup\DbExt\MsSql\ttt.bch>:
6.4.2017. 12:04:15 - Info dbclient(pid=8052) <0> operations succeeded. <1> operations failed.
6.4.2017. 12:04:25 - Info dbclient(pid=8052) INF - The following object(s) were not backed up successfully.
6.4.2017. 12:04:35 - Info dbclient(pid=8052) INF - Erste
6.4.2017. 12:04:35 - Error bpbrm(pid=11188) from client hrs000185: ERR - command failed: none of the requested files were backed up (2)
6.4.2017. 12:04:35 - Error bpbrm(pid=11188) from client hrs000185: ERR - bphdb exit status = 2: none of the requested files were backed up
6.4.2017. 12:04:37 - Info bphdb(pid=9496) done. status: 2: none of the requested files were backed up
6.4.2017. 12:04:38 - end writing
none of the requested files were backed up(2)

 

Windows 

04/06/2017 12:02:34, SQLSERVERAGENT, Warning, The 1 pager operator(s) responsible for alert 'Severity 16' are currently off duty so cannot be paged.,(4),310, HRS000185

04/06/2017 12:02:33,MSSQLSERVER, Error, BackupVirtualDeviceFile::RequestDurableMedia:Flush failure no backup device 'VNBU0-8052-8684-1491471947'.Operating System error 995 (The I/O has been aborted because of either a thread exit or an application request.)., (2),18210, HRS000185/Administrator, HRS000185

4/06/2017 12:02:33, SQLVDI, Error, SQLVDI: Loc=TriggerAbort.Desc=invoked, ErrorCode=(0). Process=7232. Thread=296. Server. Instance=MSSSQLSERVER. VD=Global\VNBU0-8052-8684-1491471947_SQLVDIMemoryName_0.,(0),1,,HRS000185

04/06/2017 12:02:33,MSSQLSERVER, Error,BackupIoRequest::ReportError: write failure on backup device 'VNBU0-8052-8684-1491471947'.Operating System error 995 (The I/O has been aborted because of either a thread exit or an application request.)., (6),18210, HRS000185/Administrator, HRS000185

04/06/2017 12:02:33,MSSQLSERVER, Error,BACKUP failed to complete the command BACKUP DATABASE Erste. Check the backup application log for detailed messages.,(6),18210, HRS000185/Administrator, HRS000185

4/06/2017 12:02:33, SQLVDI, Error, SQLVDI: Loc=SignalAbort.Desc=Client initiates abort. ErrorCode=(0). Process=8052. Thread=8184.Client. Instance=. VD=Global\VNBU0-8052-8684-1491471947_SQLVDIMemoryName_0.,(0),1,,HRS000185

 

Local SQL backup is working fine

Windows file sistem backup is working fine

 

?????

6 REPLIES 6

Marianne
Level 6
Partner    VIP    Accredited Certified

Master/media  server: Win 2008 R2, Netbackup 7.6.0.1

SQL server: Win2012 R2, Netbackup 7.7.3, SQL Server 2014

This config is not supported. The client cannot be a higher version than the master/media server.

You need to upgrade the master/media server to 7.7.3 as well.

You are lucky that filesystem backups are working.

 

 

I've already situation where client version is higher than media /master and backup is woking fine.

I can downgrade client to 7.6.0.1 .,but this version is not supported with SQL 2014.

Just to mention I've situation with version 7.6.0.1 on client/media/server and backup database on SQL 2014 is working fine. 

After downgrade client version to 7.6.0.1 backup is working OK.

Marianne
Level 6
Partner    VIP    Accredited Certified

Why don't you want to upgrade your master to 7.7.3?

Are you aware that all NBU versions up to 7.6.1.2 ran out of support on 1 Feb 2017?

Because it's easier to download/upgrade client agent then master/media in our environment.
Yes, plan is to upgrade to v8.0 next week.
Is there any known issue with that version?

 

Marianne
Level 6
Partner    VIP    Accredited Certified

I only mentioned 7.7.3 because it matches the client version and it is a recent, supported version.

I have not seen any issues with 8.0, other than the new features and the pre-upgrade steps.
Do not start with upgrade unless you have read about the new web service and required user, new security features, etc...

I have upgraded a NetBackup Appliance from 2.6.1 (7.6.1) to 3.0 (8.0) about 3 weeks ago and have really come to appreciate the beauty of the Appliances - the upgrade process on the Appliances really takes care of everything.
All went increadibly smooth and all is good (although it's a small lab environment). 

If the problem returns after the upgrade, please create dbclient log folder on SQL client and increase logging level to 3.