Status = 4201: Incorrect snapshot method configuration or snapshot method not compatible for protect

[T_N]

Hi All;

I have SQL backup job failed with error:

07/24/2017 18:26:58 - Info dbclient (pid=11072) Initiating Create Snapshot using method VSS:prov_type=0,max_snapshots=1,snap_attr=0,method=VSS.

07/24/2017 18:28:04 - Info dbclient (pid=11072) Execution of Create Snapshot failed. Status = 4201: Incorrect snapshot method configuration or snapshot method not compatible for protecting backup selection entries. 

07/24/2017 18:28:04 - Info dbclient (pid=11072) Incorrect snapshot method configuration or snapshot method not compatible for protecting backup selection entries. (4201) 

it fails sometime but the most time it completed successfully. I changed aut to vss in Perform snashot backup option but it keeps failing. Anyone know to fix it ? Thank you.

Tom

[Marianne]

Please try to give as much as possible when you need assistance.

What type of policy is this?
If VMware with 'Enable SQL Server Recovery', have you checked all the requirements as per NetBackup for VMware Administrator's Guide ?

Please tell us all the steps that you have followed.

[T_N]

type of policy = MS_SQL_Server. Question is I have many client in SQL-Tier5 policy, they are working well , except this client failed in last couple days, I copied to new backup policy SQL-Tier5_vss and changed from auto to vss in Perform Snapshot backup Option. it completed successfully after I kicked off backup job but it failed the day after.

[Thiago_Ribeiro]

Hi @T_N,

Is this SQL Server AlwaysOn? If yes, are you backin up a specific node?

Im asking you because I saw that you enabled perform snapshots backup checkbox...

Other thing, are you using NetBackup AIR? I saw in your policy storage DC_to_DR_DD5_14_days, is this a SLP or SUG?

Regards,

Thiago Ribeiro

[T_N]

I use pure disk on netbackup appliance to backup

[Marianne]

@T_N, 

Please answer all the questions asked by @Thiago_Ribeiro?

My questions to you: 

Why did you select the snapshot tick-box?

Have you seen the heading above this section?

Snapshot Client and Replication Director

Have you read up in NetBackup for Microsoft SQL Server Administrator's Guide    about Snapshot Client?
Chapter 2: 
For information on support for Snapshot Client, see the following document:
Snapshot Client Compatibility List

Chapter 8 Using NetBackup for SQL Server with Snapshot Client 

Can you confirm that you have checked and confirmed all requirements?

If you are unsure of what Snapshot Client or Replicator Director is, please de-select the snapshot tick-box.

A normal MS-SQL policy should not have the snapshot option selected.

[T_N]

it shows error when I turn off snapshot option:

07/28/2017 08:03:58 - Info bpbrm (pid=141850) CDCIPATCH01 is the host to backup data from
07/28/2017 08:03:58 - Info bpbrm (pid=141850) reading file list for client
07/28/2017 08:03:59 - Info bpbrm (pid=141850) starting bphdb on client
07/28/2017 08:04:00 - Info bphdb (pid=10252) Backup started
07/28/2017 08:07:36 - Info bpbrm (pid=141850) validating image for client CDCIPATCH01
07/28/2017 08:07:36 - Info bphdb (pid=10252) done. status: 0: the requested operation was successfully completed
07/28/2017 08:31:53 - Info nbjm (pid=31999) starting backup job (jobid=12157443) for client CDCIPATCH01, policy SQL-Tier5_vss, schedule Full
07/28/2017 08:31:53 - Info nbjm (pid=31999) requesting MEDIA_SERVER_WITH_ATTRIBUTES resources from RB for backup job (jobid=12157443, request id:{1EA05848-7399-11E7-9D02-56CB566325E3})
07/28/2017 08:31:53 - requesting resource stu_disk_cdcnetbudd5
07/28/2017 08:31:53 - requesting resource xxx02.NBU_CLIENT.MAXJOBS.CDCIPATCH01
07/28/2017 08:31:53 - requesting resource xxx02.NBU_POLICY.MAXJOBS.SQL-Tier5_vss
07/28/2017 08:31:54 - granted resource  xxx02.NBU_CLIENT.MAXJOBS.CDCIPATCH01
07/28/2017 08:31:54 - granted resource  xxx02.NBU_POLICY.MAXJOBS.SQL-Tier5_vss
07/28/2017 08:31:54 - granted resource  stu_disk_xxxdd5
07/28/2017 08:31:54 - estimated 0 kbytes needed
07/28/2017 08:31:54 - Info nbjm (pid=31999) started backup (backupid=CDCIPATCH01_1501248714) job for client CDCIPATCH01, policy SQL-Tier5_vss, schedule Full on storage unit stu_disk_xxxdd5
07/28/2017 08:31:54 - started process bpbrm (pid=141850)
07/28/2017 08:32:10 - connecting
07/28/2017 08:32:11 - connected; connect time: 0:00:00
07/28/2017 08:32:15 - Info dbclient (pid=7304) INF - BACKUP STARTED USING
07/28/2017 08:32:15 - Info dbclient (pid=7304) Microsoft SQL Server 2008 R2 (SP1) - 10.50.2500.0 (X64)
07/28/2017 08:32:15 - Info dbclient (pid=7304) Jun 17 2011 00:54:03
07/28/2017 08:32:15 - Info dbclient (pid=7304) Copyright (c) Microsoft Corporation
07/28/2017 08:32:15 - Info dbclient (pid=7304) Express Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (Hypervisor)
07/28/2017 08:32:15 - Info dbclient (pid=7304) Batch = C:\Program Files\Veritas\NetBackup\DbExt\MsSql\bkup.bch, Op# = 1
07/28/2017 08:32:15 - Info dbclient (pid=7304) INF - Using backup image CDCIPATCH01.MSSQL7.CDCIPATCH01\SMSQL2008.db.CSSiteData.~.7.001of001.20170728063213..C
07/28/2017 08:32:15 - Info dbclient (pid=7304) INF - backup database "CSSiteData" to VIRTUAL_DEVICE='VNBU0-7304-6308-1501248735' with  stats = 10, blocksize = 65536, maxtransfersize = 4194304, buffercount = 2
07/28/2017 08:32:15 - Info dbclient (pid=7304) INF - Number of stripes: 1, Number of buffers per stripe 2.
07/28/2017 08:32:15 - Info dbclient (pid=7304) INF - Created VDI object for SQL Server instance <SMSQL2008>. Connection timeout is <300> seconds.
07/28/2017 08:32:33 - Info dbclient (pid=7304) INF - ODBC return code <2>, SQL State <01000>, SQL Message <3211><[Microsoft][SQL Server Native Client 10.0][SQL Server]10 percent processed.>.
07/28/2017 08:32:39 - Info dbclient (pid=7304) INF - ODBC return code <2>, SQL State <01000>, SQL Message <3211><[Microsoft][SQL Server Native Client 10.0][SQL Server]20 percent processed.>.
07/28/2017 08:32:46 - Info dbclient (pid=7304) INF - ODBC return code <2>, SQL State <01000>, SQL Message <3211><[Microsoft][SQL Server Native Client 10.0][SQL Server]30 percent processed.>.
07/28/2017 08:32:52 - Info dbclient (pid=7304) INF - ODBC return code <2>, SQL State <01000>, SQL Message <3211><[Microsoft][SQL Server Native Client 10.0][SQL Server]40 percent processed.>.
07/28/2017 08:32:58 - Info dbclient (pid=7304) INF - ODBC return code <2>, SQL State <01000>, SQL Message <3211><[Microsoft][SQL Server Native Client 10.0][SQL Server]50 percent processed.>.
07/28/2017 08:33:04 - Info dbclient (pid=7304) INF - ODBC return code <2>, SQL State <01000>, SQL Message <3211><[Microsoft][SQL Server Native Client 10.0][SQL Server]60 percent processed.>.
07/28/2017 08:33:10 - Info dbclient (pid=7304) INF - ODBC return code <2>, SQL State <01000>, SQL Message <3211><[Microsoft][SQL Server Native Client 10.0][SQL Server]70 percent processed.>.
07/28/2017 08:33:16 - Info dbclient (pid=7304) INF - ODBC return code <2>, SQL State <01000>, SQL Message <3211><[Microsoft][SQL Server Native Client 10.0][SQL Server]80 percent processed.>.
07/28/2017 08:33:22 - Info dbclient (pid=7304) INF - ODBC return code <2>, SQL State <01000>, SQL Message <3211><[Microsoft][SQL Server Native Client 10.0][SQL Server]90 percent processed.>.
07/28/2017 08:33:29 - Info dbclient (pid=7304) INF - Thread has been closed for stripe #0
07/28/2017 08:33:32 - Info dbclient (pid=7304) INF - OPERATION #1 of batch C:\Program Files\Veritas\NetBackup\DbExt\MsSql\bkup.bch SUCCEEDED with STATUS 0 (0 is normal). Elapsed time = 78(64) seconds
07/28/2017 08:33:35 - Info dbclient (pid=7304) INF - BACKUP STARTED USING
07/28/2017 08:33:35 - Info dbclient (pid=7304) Microsoft SQL Server 2008 R2 (SP1) - 10.50.2500.0 (X64)
07/28/2017 08:33:35 - Info dbclient (pid=7304) Jun 17 2011 00:54:03
07/28/2017 08:33:35 - Info dbclient (pid=7304) Copyright (c) Microsoft Corporation
07/28/2017 08:33:35 - Info dbclient (pid=7304) Express Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (Hypervisor)
07/28/2017 08:33:35 - Info dbclient (pid=7304) Batch = C:\Program Files\Veritas\NetBackup\DbExt\MsSql\bkup.bch, Op# = 2
07/28/2017 08:33:35 - Info dbclient (pid=7304) INF - Using backup image CDCIPATCH01.MSSQL7.CDCIPATCH01\SMSQL2008.db.master.~.7.001of001.20170728063333..C
07/28/2017 08:33:35 - Info dbclient (pid=7304) INF - backup database "master" to VIRTUAL_DEVICE='VNBU0-7304-9124-1501248815' with  stats = 10, blocksize = 65536, maxtransfersize = 4194304, buffercount = 2
07/28/2017 08:33:35 - Info dbclient (pid=7304) INF - Number of stripes: 1, Number of buffers per stripe 2.
07/28/2017 08:33:35 - Info dbclient (pid=7304) INF - Created VDI object for SQL Server instance <SMSQL2008>. Connection timeout is <300> seconds.
07/28/2017 08:33:43 - Info dbclient (pid=7304) INF - Thread has been closed for stripe #0
07/28/2017 08:33:46 - Info dbclient (pid=7304) INF - OPERATION #2 of batch C:\Program Files\Veritas\NetBackup\DbExt\MsSql\bkup.bch SUCCEEDED with STATUS 0 (0 is normal). Elapsed time = 12(1) seconds
07/28/2017 08:33:49 - Info dbclient (pid=7304) INF - BACKUP STARTED USING
07/28/2017 08:33:49 - Info dbclient (pid=7304) Microsoft SQL Server 2008 R2 (SP1) - 10.50.2500.0 (X64)
07/28/2017 08:33:49 - Info dbclient (pid=7304) Jun 17 2011 00:54:03
07/28/2017 08:33:49 - Info dbclient (pid=7304) Copyright (c) Microsoft Corporation
07/28/2017 08:33:49 - Info dbclient (pid=7304) Express Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (Hypervisor)
07/28/2017 08:33:49 - Info dbclient (pid=7304) Batch = C:\Program Files\Veritas\NetBackup\DbExt\MsSql\bkup.bch, Op# = 3
07/28/2017 08:33:49 - Info dbclient (pid=7304) INF - Using backup image CDCIPATCH01.MSSQL7.CDCIPATCH01\SMSQL2008.db.model.~.7.001of001.20170728063348..C
07/28/2017 08:33:49 - Info dbclient (pid=7304) INF - backup database "model" to VIRTUAL_DEVICE='VNBU0-7304-12264-1501248829' with  stats = 10, blocksize = 65536, maxtransfersize = 4194304, buffercount = 2
07/28/2017 08:33:49 - Info dbclient (pid=7304) INF - Number of stripes: 1, Number of buffers per stripe 2.
07/28/2017 08:33:49 - Info dbclient (pid=7304) INF - Created VDI object for SQL Server instance <SMSQL2008>. Connection timeout is <300> seconds.
07/28/2017 08:33:58 - Info dbclient (pid=7304) INF - Thread has been closed for stripe #0
07/28/2017 08:34:00 - Info dbclient (pid=7304) INF - OPERATION #3 of batch C:\Program Files\Veritas\NetBackup\DbExt\MsSql\bkup.bch SUCCEEDED with STATUS 0 (0 is normal). Elapsed time = 12(1) seconds
07/28/2017 08:34:03 - Info dbclient (pid=7304) INF - BACKUP STARTED USING
07/28/2017 08:34:03 - Info dbclient (pid=7304) Microsoft SQL Server 2008 R2 (SP1) - 10.50.2500.0 (X64)
07/28/2017 08:34:03 - Info dbclient (pid=7304) Jun 17 2011 00:54:03
07/28/2017 08:34:03 - Info dbclient (pid=7304) Copyright (c) Microsoft Corporation
07/28/2017 08:34:03 - Info dbclient (pid=7304) Express Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (Hypervisor)
07/28/2017 08:34:03 - Info dbclient (pid=7304) Batch = C:\Program Files\Veritas\NetBackup\DbExt\MsSql\bkup.bch, Op# = 4
07/28/2017 08:34:03 - Info dbclient (pid=7304) INF - Using backup image CDCIPATCH01.MSSQL7.CDCIPATCH01\SMSQL2008.db.msdb.~.7.001of001.20170728063402..C
07/28/2017 08:34:03 - Info dbclient (pid=7304) INF - backup database "msdb" to VIRTUAL_DEVICE='VNBU0-7304-7224-1501248843' with  stats = 10, blocksize = 65536, maxtransfersize = 4194304, buffercount = 2
07/28/2017 08:34:03 - Info dbclient (pid=7304) INF - Number of stripes: 1, Number of buffers per stripe 2.
07/28/2017 08:34:03 - Info dbclient (pid=7304) INF - Created VDI object for SQL Server instance <SMSQL2008>. Connection timeout is <300> seconds.
07/28/2017 08:34:12 - Info dbclient (pid=7304) INF - Thread has been closed for stripe #0
07/28/2017 08:34:14 - Info dbclient (pid=7304) INF - OPERATION #4 of batch C:\Program Files\Veritas\NetBackup\DbExt\MsSql\bkup.bch SUCCEEDED with STATUS 0 (0 is normal). Elapsed time = 12(2) seconds
07/28/2017 08:34:18 - Info dbclient (pid=7304) INF - BACKUP STARTED USING
07/28/2017 08:34:18 - Info dbclient (pid=7304) Microsoft SQL Server 2008 R2 (SP1) - 10.50.2500.0 (X64)
07/28/2017 08:34:18 - Info dbclient (pid=7304) Jun 17 2011 00:54:03
07/28/2017 08:34:18 - Info dbclient (pid=7304) Copyright (c) Microsoft Corporation
07/28/2017 08:34:18 - Info dbclient (pid=7304) Express Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (Hypervisor)
07/28/2017 08:34:18 - Info dbclient (pid=7304) Batch = C:\Program Files\Veritas\NetBackup\DbExt\MsSql\bkup.bch, Op# = 5
07/28/2017 08:34:18 - Info dbclient (pid=7304) INF - Using backup image CDCIPATCH01.MSSQL7.CDCIPATCH01\SMSQL2008.db.SNMPSiteData.~.7.001of001.20170728063416..C
07/28/2017 08:34:18 - Info dbclient (pid=7304) INF - backup database "SNMPSiteData" to VIRTUAL_DEVICE='VNBU0-7304-9120-1501248858' with  stats = 10, blocksize = 65536, maxtransfersize = 4194304, buffercount = 2
07/28/2017 08:34:18 - Info dbclient (pid=7304) INF - Number of stripes: 1, Number of buffers per stripe 2.
07/28/2017 08:34:18 - Info dbclient (pid=7304) INF - Created VDI object for SQL Server instance <SMSQL2008>. Connection timeout is <300> seconds.
07/28/2017 08:34:26 - Info dbclient (pid=7304) INF - Thread has been closed for stripe #0
07/28/2017 08:34:28 - Info dbclient (pid=7304) INF - OPERATION #5 of batch C:\Program Files\Veritas\NetBackup\DbExt\MsSql\bkup.bch SUCCEEDED with STATUS 0 (0 is normal). Elapsed time = 12(1) seconds
07/28/2017 08:34:31 - Info dbclient (pid=7304) INF - BACKUP STARTED USING
07/28/2017 08:34:31 - Info dbclient (pid=7304) Microsoft SQL Server 2008 R2 (SP1) - 10.50.2500.0 (X64)
07/28/2017 08:34:31 - Info dbclient (pid=7304) Jun 17 2011 00:54:03
07/28/2017 08:34:31 - Info dbclient (pid=7304) Copyright (c) Microsoft Corporation
07/28/2017 08:34:31 - Info dbclient (pid=7304) Express Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (Hypervisor)
07/28/2017 08:34:31 - Info dbclient (pid=7304) Batch = C:\Program Files\Veritas\NetBackup\DbExt\MsSql\bkup.bch, Op# = 6
07/28/2017 08:34:31 - Info dbclient (pid=7304) INF - Using backup image CDCIPATCH01.MSSQL7.CDCIPATCH01\SMSQL2008.db.SystemManager7.~.7.001of001.20170728063430..C
07/28/2017 08:34:31 - Info dbclient (pid=7304) INF - backup database "SystemManager7" to VIRTUAL_DEVICE='VNBU0-7304-3492-1501248871' with  stats = 10, blocksize = 65536, maxtransfersize = 4194304, buffercount = 2
07/28/2017 08:34:31 - Info dbclient (pid=7304) INF - Number of stripes: 1, Number of buffers per stripe 2.
07/28/2017 08:34:32 - Info dbclient (pid=7304) INF - Created VDI object for SQL Server instance <SMSQL2008>. Connection timeout is <300> seconds.
07/28/2017 08:34:45 - Info dbclient (pid=7304) INF - ODBC return code <2>, SQL State <01000>, SQL Message <3211><[Microsoft][SQL Server Native Client 10.0][SQL Server]10 percent processed.>.
07/28/2017 08:34:51 - Info dbclient (pid=7304) INF - ODBC return code <2>, SQL State <01000>, SQL Message <3211><[Microsoft][SQL Server Native Client 10.0][SQL Server]20 percent processed.>.
07/28/2017 08:34:57 - Info dbclient (pid=7304) INF - ODBC return code <2>, SQL State <01000>, SQL Message <3211><[Microsoft][SQL Server Native Client 10.0][SQL Server]30 percent processed.>.
07/28/2017 08:34:57 - Info dbclient (pid=7304) INF - SQL Message <3211><[Microsoft][SQL Server Native Client 10.0][SQL Server]40 percent processed.>
07/28/2017 08:35:03 - Info dbclient (pid=7304) INF - ODBC return code <2>, SQL State <01000>, SQL Message <3211><[Microsoft][SQL Server Native Client 10.0][SQL Server]50 percent processed.>.
07/28/2017 08:35:10 - Info dbclient (pid=7304) INF - ODBC return code <2>, SQL State <01000>, SQL Message <3211><[Microsoft][SQL Server Native Client 10.0][SQL Server]60 percent processed.>.
07/28/2017 08:35:10 - Info dbclient (pid=7304) INF - SQL Message <3211><[Microsoft][SQL Server Native Client 10.0][SQL Server]70 percent processed.>
07/28/2017 08:35:16 - Info dbclient (pid=7304) INF - ODBC return code <2>, SQL State <01000>, SQL Message <3211><[Microsoft][SQL Server Native Client 10.0][SQL Server]80 percent processed.>.
07/28/2017 08:35:22 - Info dbclient (pid=7304) INF - Thread has been closed for stripe #0
07/28/2017 08:35:25 - Info dbclient (pid=7304) INF - OPERATION #6 of batch C:\Program Files\Veritas\NetBackup\DbExt\MsSql\bkup.bch SUCCEEDED with STATUS 0 (0 is normal). Elapsed time = 55(43) seconds
07/28/2017 08:35:27 - Info dbclient (pid=7304) INF - Results of executing <C:\Program Files\Veritas\NetBackup\DbExt\MsSql\bkup.bch>:
07/28/2017 08:35:27 - Info dbclient (pid=7304) <6> operations succeeded. <0> operations failed.
07/28/2017 08:35:48 - end writing
the requested operation was successfully completed  (0)

[Marianne]

I took a long time to reply because I took the time to actually read through the backup details and carefully copied and pasted relevant details for you.

What error do you see?

I see successful backup:
07/28/2017 08:03:58 - Info bpbrm (pid=141850) CDCIPATCH01 is the host to backup data from
....
07/28/2017 08:07:36 - Info bphdb (pid=10252) done. status: 0: the requested operation was successfully completed

Please go through the details carefully.
There are multiple databases that are being backed up.
Each database backup is represented by Op# and OPERATION.

So,
07/28/2017 08:32:15 - Op# = 1 : backup database "CSSiteData"
07/28/2017 08:33:32 - Info dbclient (pid=7304) INF - OPERATION #1 ... SUCCEEDED with STATUS 0 (0 is normal). Elapsed time = 78(64) seconds

07/28/2017 08:33:35 - Op# = 2 : backup database "master"
07/28/2017 08:33:46 -  OPERATION #2 ... SUCCEEDED with STATUS 0. Elapsed time = 12(1) seconds

07/28/2017 08:33:49 - Op# = 3 : backup database "model"
07/28/2017 08:34:00 - OPERATION #3 ... SUCCEEDED with STATUS 0 Elapsed time = 12(1) seconds

07/28/2017 08:34:03 - Op# = 4 : backup database "msdb"
07/28/2017 08:34:14 - OPERATION #4 SUCCEEDED with STATUS 0 . Elapsed time = 12(2) seconds

07/28/2017 08:34:18 - Op# = 5 : backup database "SNMPSiteData"
07/28/2017 08:34:28 - OPERATION #5 ... SUCCEEDED with STATUS 0. Elapsed time = 12(1) seconds

07/28/2017 08:34:31 - Op# = 6 : backup database "SystemManager7"
07/28/2017 08:35:25 - OPERATION #6 ... SUCCEEDED with STATUS 0 (0 is normal). Elapsed time = 55(43) seconds

07/28/2017 08:35:27 - Info dbclient (pid=7304) <6> operations succeeded.
<0> operations failed.
07/28/2017 08:35:48 - end writing
the requested operation was successfully completed (0)

[T_N]

I changed friday schedule from 6 PM to 9 PM, it worked well but yesterday it keeps failing because it was started @ 6 PM , here the mssql log from yesterday:

Microsoft SQL Server 2008 R2 (SP1) - 10.50.2500.0 (X64)
Jun 17 2011 00:54:03
Copyright (c) Microsoft Corporation
Express Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (Hypervisor)
Batch = C:\Program Files\Veritas\NetBackup\DbExt\MsSql\bkup.bch, Op# = 2
INF - Using backup image CDCIPATCH01.MSSQL7.CDCIPATCH01\SMSQL2008.db.master.~.7.001of001.20170730161159..C
INF - backup database "master" to VIRTUAL_DEVICE='VNBU0-5788-6864-1501456321' with snapshot
INF - Number of stripes: 1, Number of buffers per stripe 2.
INF - Created VDI object for SQL Server instance <SMSQL2008>. Connection timeout is <300> seconds.
ERR - Error in VxBSAWaitForFileListStatus: 36.
    CONTINUATION: - The creation of the frozen image failed.
INF - Thread has been closed for stripe #0
ERR - A panic close was issued to dbclient #0.
INF - OPERATION #2 of batch C:\Program Files\Veritas\NetBackup\DbExt\MsSql\bkup.bch FAILED with STATUS 1 (0 is normal). Elapsed time = 73(73) seconds.
INF - BACKUP STARTED USING
Microsoft SQL Server 2008 R2 (SP1) - 10.50.2500.0 (X64)
Jun 17 2011 00:54:03
Copyright (c) Microsoft Corporation
Express Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (Hypervisor)
Batch = C:\Program Files\Veritas\NetBackup\DbExt\MsSql\bkup.bch, Op# = 3
INF - Using backup image CDCIPATCH01.MSSQL7.CDCIPATCH01\SMSQL2008.db.model.~.7.001of001.20170730161314..C
INF - backup database "model" to VIRTUAL_DEVICE='VNBU0-5788-8964-1501456395' with snapshot
INF - Number of stripes: 1, Number of buffers per stripe 2.
INF - Created VDI object for SQL Server instance <SMSQL2008>. Connection timeout is <300> seconds.
INF - Thread has been closed for stripe #0
INF - OPERATION #3 of batch C:\Program Files\Veritas\NetBackup\DbExt\MsSql\bkup.bch SUCCEEDED with STATUS 0 (0 is normal). Elapsed time = 618(617) seconds
INF - BACKUP STARTED USING
Microsoft SQL Server 2008 R2 (SP1) - 10.50.2500.0 (X64)
Jun 17 2011 00:54:03
Copyright (c) Microsoft Corporation
Express Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (Hypervisor)
Batch = C:\Program Files\Veritas\NetBackup\DbExt\MsSql\bkup.bch, Op# = 4
INF - Using backup image CDCIPATCH01.MSSQL7.CDCIPATCH01\SMSQL2008.db.msdb.~.7.001of001.20170730162335..C
INF - backup database "msdb" to VIRTUAL_DEVICE='VNBU0-5788-11972-1501457016' with snapshot
INF - Number of stripes: 1, Number of buffers per stripe 2.
INF - Created VDI object for SQL Server instance <SMSQL2008>. Connection timeout is <300> seconds.
ERR - Error in VxBSAWaitForFileListStatus: 36.
    CONTINUATION: - The creation of the frozen image failed.
INF - Thread has been closed for stripe #0
ERR - A panic close was issued to dbclient #0.
DBMS MSG - ODBC return code <-1>, SQL State <37000>, SQL Message <3271><[Microsoft][SQL Server Native Client 10.0][SQL Server]A nonrecoverable I/O error occurred on file "VNBU0-5788-11972-1501457016:" 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 Server Native Client 10.0][SQL Server]BACKUP DATABASE is terminating abnormally.>
ERR - Error found executing <backup database "msdb" to VIRTUAL_DEVICE='VNBU0-5788-11972-1501457016' with snapshot>.
INF - OPERATION #4 of batch C:\Program Files\Veritas\NetBackup\DbExt\MsSql\bkup.bch FAILED with STATUS 1 (0 is normal). Elapsed time = 68(68) seconds.
INF - BACKUP STARTED USING
Microsoft SQL Server 2008 R2 (SP1) - 10.50.2500.0 (X64)
Jun 17 2011 00:54:03
Copyright (c) Microsoft Corporation
Express Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (Hypervisor)
Batch = C:\Program Files\Veritas\NetBackup\DbExt\MsSql\bkup.bch, Op# = 5
INF - Using backup image CDCIPATCH01.MSSQL7.CDCIPATCH01\SMSQL2008.db.SNMPSiteData.~.7.001of001.20170730162445..C
INF - backup database "SNMPSiteData" to VIRTUAL_DEVICE='VNBU0-5788-12272-1501457087' with snapshot
INF - Number of stripes: 1, Number of buffers per stripe 2.
INF - Created VDI object for SQL Server instance <SMSQL2008>. Connection timeout is <300> seconds.
ERR - Error in VxBSAWaitForFileListStatus: 36.
    CONTINUATION: - The creation of the frozen image failed.
INF - Thread has been closed for stripe #0
ERR - A panic close was issued to dbclient #0.
INF - OPERATION #5 of batch C:\Program Files\Veritas\NetBackup\DbExt\MsSql\bkup.bch FAILED with STATUS 1 (0 is normal). Elapsed time = 68(68) seconds.
INF - BACKUP STARTED USING
Microsoft SQL Server 2008 R2 (SP1) - 10.50.2500.0 (X64)
Jun 17 2011 00:54:03
Copyright (c) Microsoft Corporation
Express Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (Hypervisor)
Batch = C:\Program Files\Veritas\NetBackup\DbExt\MsSql\bkup.bch, Op# = 6
INF - Using backup image CDCIPATCH01.MSSQL7.CDCIPATCH01\SMSQL2008.db.SystemManager7.~.7.001of001.20170730162555..C
INF - backup database "SystemManager7" to VIRTUAL_DEVICE='VNBU0-5788-5580-1501457157' with snapshot
INF - Number of stripes: 1, Number of buffers per stripe 2.
INF - Created VDI object for SQL Server instance <SMSQL2008>. Connection timeout is <300> seconds.
INF - Thread has been closed for stripe #0
INF - OPERATION #6 of batch C:\Program Files\Veritas\NetBackup\DbExt\MsSql\bkup.bch SUCCEEDED with STATUS 0 (0 is normal). Elapsed time = 619(617) seconds
INF - Results of executing <C:\Program Files\Veritas\NetBackup\DbExt\MsSql\bkup.bch>:
<3> operations succeeded. <3> operations failed.
INF - The following object(s) were not backed up successfully.
INF - master
INF - msdb
INF - SNMPSiteData

[Marianne]

I believe your original query was solved.

Scheduling backup times is something that you need to carefully plan after consultation with dba's and server owners.

[T_N]

I rescheduled backup windows, backup jobs work well.

[Marianne]

Yes. As per my post of 2 weeks ago:
Scheduling backup times is something that you need to carefully plan after consultation with dba's and server owners..

I am pleased to know that we could help you.