ERR - exit status:

Question

AUTOMATIC_DATABASE_BACKUPApr&nbsp;2,&nbsp;2019&nbsp;1:56:30&nbsp;PM&nbsp;-&nbsp;Info&nbsp;nbjm&nbsp;(pid=6452)&nbsp;starting&nbsp;backup&nbsp;job&nbsp;(jobid=7972396)&nbsp;for&nbsp;client&nbsp;************,&nbsp;policy&nbsp;Prophix-DBs,&nbsp;schedule&nbsp;Hourly
Apr&nbsp;2,&nbsp;2019&nbsp;1:56:30&nbsp;PM&nbsp;-&nbsp;Info&nbsp;nbjm&nbsp;(pid=6452)&nbsp;requesting&nbsp;MEDIA_SERVER_ONLY&nbsp;resources&nbsp;from&nbsp;RB&nbsp;for&nbsp;backup&nbsp;job&nbsp;(jobid=7972396,&nbsp;request&nbsp;id:{15A07788-7AD1-4032-A3EB-329244BF4990})
Apr&nbsp;2,&nbsp;2019&nbsp;1:56:30&nbsp;PM&nbsp;-&nbsp;requesting&nbsp;resource&nbsp;&nbsp;M**T-SQL
Apr&nbsp;2,&nbsp;2019&nbsp;1:56:30&nbsp;PM&nbsp;-&nbsp;estimated&nbsp;0&nbsp;kbytes&nbsp;needed
Apr&nbsp;2,&nbsp;2019&nbsp;1:56:30&nbsp;PM&nbsp;-&nbsp;Info&nbsp;nbjm&nbsp;(pid=6452)&nbsp;started&nbsp;backup&nbsp;(backupid=************_1554202590)&nbsp;job&nbsp;for&nbsp;client&nbsp;************,&nbsp;policy&nbsp;Prophix-DBs,&nbsp;schedule&nbsp;Hourly&nbsp;on&nbsp;storage&nbsp;unit&nbsp;
Apr&nbsp;2,&nbsp;2019&nbsp;1:56:32&nbsp;PM&nbsp;-&nbsp;started&nbsp;process&nbsp;bpbrm&nbsp;(pid=8832)
Apr&nbsp;2,&nbsp;2019&nbsp;1:56:33&nbsp;PM&nbsp;-&nbsp;Info&nbsp;bpbrm&nbsp;(pid=8832)&nbsp;************&nbsp;is&nbsp;the&nbsp;host&nbsp;to&nbsp;backup&nbsp;data&nbsp;from
Apr&nbsp;2,&nbsp;2019&nbsp;1:56:33&nbsp;PM&nbsp;-&nbsp;Info&nbsp;bpbrm&nbsp;(pid=8832)&nbsp;reading&nbsp;file&nbsp;list&nbsp;for&nbsp;client
Apr&nbsp;2,&nbsp;2019&nbsp;1:56:34&nbsp;PM&nbsp;-&nbsp;connecting
Apr&nbsp;2,&nbsp;2019&nbsp;1:56:35&nbsp;PM&nbsp;-&nbsp;Info&nbsp;bpbrm&nbsp;(pid=8832)&nbsp;starting&nbsp;bphdb&nbsp;on&nbsp;client
Apr&nbsp;2,&nbsp;2019&nbsp;1:56:35&nbsp;PM&nbsp;-&nbsp;Info&nbsp;bphdb&nbsp;(pid=12072)&nbsp;Backup&nbsp;started
Apr&nbsp;2,&nbsp;2019&nbsp;1:56:35&nbsp;PM&nbsp;-&nbsp;connected;&nbsp;connect&nbsp;time:&nbsp;0:00:00
Apr&nbsp;2,&nbsp;2019&nbsp;1:56:36&nbsp;PM&nbsp;-&nbsp;Info&nbsp;dbclient&nbsp;(pid=5164)&nbsp;INF&nbsp;-&nbsp;Intelligent&nbsp;policy&nbsp;initiated&nbsp;by&nbsp;server&nbsp;&lt;srv-snbu01.M**T.ru&gt;
Apr&nbsp;2,&nbsp;2019&nbsp;1:56:37&nbsp;PM&nbsp;-&nbsp;Info&nbsp;dbclient&nbsp;(pid=5164)&nbsp;INF&nbsp;-&nbsp;Intelligent&nbsp;policy&nbsp;&lt;Prophix-DBs&gt;&nbsp;is&nbsp;valid.&nbsp;The&nbsp;input&nbsp;file&nbsp;&lt;C:\Program&nbsp;Files\Veritas\NetBackup\dbext\mssql\input.12072.0.0402119.135635&gt;&nbsp;has&nbsp;been&nbsp;parsed&nbsp;successfully
Apr&nbsp;2,&nbsp;2019&nbsp;1:56:38&nbsp;PM&nbsp;-&nbsp;Info&nbsp;dbclient&nbsp;(pid=5164)&nbsp;INF&nbsp;-&nbsp;Instance&nbsp;server&nbsp;name&nbsp;resolved&nbsp;to:&nbsp;&lt;PROPHIX-APP&gt;
Apr&nbsp;2,&nbsp;2019&nbsp;1:56:40&nbsp;PM&nbsp;-&nbsp;Info&nbsp;dbclient&nbsp;(pid=5164)&nbsp;INF&nbsp;-&nbsp;Intelligent&nbsp;policy&nbsp;&lt;Prophix-DBs&gt;&nbsp;has&nbsp;resulted&nbsp;in&nbsp;&lt;1&gt;&nbsp;batch&nbsp;operation(s).
Apr&nbsp;2,&nbsp;2019&nbsp;1:56:41&nbsp;PM&nbsp;-&nbsp;Info&nbsp;dbclient&nbsp;(pid=5164)&nbsp;INF&nbsp;-&nbsp;Intelligent&nbsp;policy&nbsp;&lt;Prophix-DBs&gt;:&nbsp;&lt;1&gt;&nbsp;operation(s)&nbsp;will&nbsp;protect&nbsp;the&nbsp;database&nbsp;transaction&nbsp;logs.
Apr&nbsp;2,&nbsp;2019&nbsp;1:56:42&nbsp;PM&nbsp;-&nbsp;Info&nbsp;dbclient&nbsp;(pid=5164)&nbsp;INF&nbsp;-&nbsp;Intelligent&nbsp;policy&nbsp;preprocessing&nbsp;has&nbsp;finished,&nbsp;created&nbsp;temporary&nbsp;batch&nbsp;file&nbsp;&lt;__13_56_39_925_00.bch&gt;,&nbsp;and&nbsp;submitted&nbsp;it&nbsp;to&nbsp;the&nbsp;backend&nbsp;agent&nbsp;for&nbsp;processing
Apr&nbsp;2,&nbsp;2019&nbsp;1:56:43&nbsp;PM&nbsp;-&nbsp;Info&nbsp;dbclient&nbsp;(pid=5164)&nbsp;INF&nbsp;-&nbsp;Querying&nbsp;master.sys.database_recovery_status&nbsp;to&nbsp;determine&nbsp;last_log_backup_lsn&nbsp;for&nbsp;database&nbsp;Dev_PROPHIX_FactDb
Apr&nbsp;2,&nbsp;2019&nbsp;1:56:44&nbsp;PM&nbsp;-&nbsp;Info&nbsp;dbclient&nbsp;(pid=5164)&nbsp;INF&nbsp;-&nbsp;A&nbsp;full&nbsp;backup&nbsp;has&nbsp;already&nbsp;been&nbsp;performed&nbsp;on&nbsp;this&nbsp;database.
Apr&nbsp;2,&nbsp;2019&nbsp;1:56:45&nbsp;PM&nbsp;-&nbsp;Info&nbsp;dbclient&nbsp;(pid=5164)&nbsp;INF&nbsp;-&nbsp;No&nbsp;conversion&nbsp;required&nbsp;for&nbsp;transaction&nbsp;log&nbsp;backup.
Apr&nbsp;2,&nbsp;2019&nbsp;1:56:47&nbsp;PM&nbsp;-&nbsp;Info&nbsp;dbclient&nbsp;(pid=5164)&nbsp;INF&nbsp;-&nbsp;BACKUP&nbsp;STARTED&nbsp;USING
Apr&nbsp;2,&nbsp;2019&nbsp;1:56:47&nbsp;PM&nbsp;-&nbsp;Info&nbsp;dbclient&nbsp;(pid=5164)&nbsp;Microsoft&nbsp;SQL&nbsp;Server&nbsp;2016&nbsp;(SP1-CU11)&nbsp;(KB4459676)&nbsp;-&nbsp;13.0.4528.0&nbsp;(X64)&nbsp;
Apr&nbsp;2,&nbsp;2019&nbsp;1:56:47&nbsp;PM&nbsp;-&nbsp;Info&nbsp;dbclient&nbsp;(pid=5164)&nbsp;Aug&nbsp;30&nbsp;2018&nbsp;21:57:02&nbsp;
Apr&nbsp;2,&nbsp;2019&nbsp;1:56:47&nbsp;PM&nbsp;-&nbsp;Info&nbsp;dbclient&nbsp;(pid=5164)&nbsp;Copyright&nbsp;(c)&nbsp;Microsoft&nbsp;Corporation
Apr&nbsp;2,&nbsp;2019&nbsp;1:56:47&nbsp;PM&nbsp;-&nbsp;Info&nbsp;dbclient&nbsp;(pid=5164)&nbsp;Enterprise&nbsp;Edition:&nbsp;Core-based&nbsp;Licensing&nbsp;(64-bit)&nbsp;on&nbsp;Windows&nbsp;Server&nbsp;2016&nbsp;Standard&nbsp;10.0&nbsp;&lt;X64&gt;&nbsp;(Build&nbsp;14393:&nbsp;)&nbsp;(Hypervisor)&nbsp;
Apr&nbsp;2,&nbsp;2019&nbsp;1:56:47&nbsp;PM&nbsp;-&nbsp;Info&nbsp;dbclient&nbsp;(pid=5164)&nbsp;Batch&nbsp;=&nbsp;__13_56_39_925_00.bch,&nbsp;Op#&nbsp;=&nbsp;1
Apr&nbsp;2,&nbsp;2019&nbsp;1:56:49&nbsp;PM&nbsp;-&nbsp;Info&nbsp;dbclient&nbsp;(pid=5164)&nbsp;INF&nbsp;-&nbsp;Using&nbsp;backup&nbsp;image&nbsp;PROPHIX-APP.MSSQL7.PROPHIX-APP.trx.Dev_PROPHIX_FactDb.~.7.001of001.20190402135646..C
Apr&nbsp;2,&nbsp;2019&nbsp;1:56:50&nbsp;PM&nbsp;-&nbsp;Info&nbsp;dbclient&nbsp;(pid=5164)&nbsp;INF&nbsp;-&nbsp;backup&nbsp;log&nbsp;"Dev_PROPHIX_FactDb"&nbsp;to&nbsp;VIRTUAL_DEVICE='VNBU0-5164-7736-1554202609'&nbsp;with&nbsp;&nbsp;compression,&nbsp;&nbsp;stats&nbsp;=&nbsp;10,&nbsp;checksum,&nbsp;stop_on_error,&nbsp;blocksize&nbsp;=&nbsp;65536,&nbsp;maxtransfersize&nbsp;=&nbsp;4194304,&nbsp;buffercount&nbsp;=&nbsp;2
Apr&nbsp;2,&nbsp;2019&nbsp;1:56:51&nbsp;PM&nbsp;-&nbsp;Info&nbsp;dbclient&nbsp;(pid=5164)&nbsp;INF&nbsp;-&nbsp;Number&nbsp;of&nbsp;stripes:&nbsp;1,&nbsp;Number&nbsp;of&nbsp;buffers&nbsp;per&nbsp;stripe&nbsp;2.
Apr&nbsp;2,&nbsp;2019&nbsp;1:56:52&nbsp;PM&nbsp;-&nbsp;Info&nbsp;dbclient&nbsp;(pid=5164)&nbsp;INF&nbsp;-&nbsp;Setting&nbsp;backup&nbsp;catalog&nbsp;name&nbsp;to:&nbsp;************
Apr&nbsp;2,&nbsp;2019&nbsp;1:56:52&nbsp;PM&nbsp;-&nbsp;Info&nbsp;dbclient&nbsp;(pid=5164)&nbsp;INF&nbsp;-&nbsp;Created&nbsp;VDI&nbsp;object&nbsp;for&nbsp;SQL&nbsp;Server&nbsp;instance&nbsp;&lt;PROPHIX-APP&gt;.&nbsp;Connection&nbsp;timeout&nbsp;is&nbsp;&lt;300&gt;&nbsp;seconds.
Apr&nbsp;2,&nbsp;2019&nbsp;3:36:21&nbsp;PM&nbsp;-&nbsp;Info&nbsp;dbclient&nbsp;(pid=5164)&nbsp;ERR&nbsp;-&nbsp;Error&nbsp;in&nbsp;VxBSACreateObject:&nbsp;3.
Apr&nbsp;2,&nbsp;2019&nbsp;3:36:23&nbsp;PM&nbsp;-&nbsp;Info&nbsp;dbclient&nbsp;(pid=5164)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CONTINUATION:&nbsp;-&nbsp;System&nbsp;detected&nbsp;error,&nbsp;operation&nbsp;aborted.
Apr&nbsp;2,&nbsp;2019&nbsp;3:36:25&nbsp;PM&nbsp;-&nbsp;Info&nbsp;dbclient&nbsp;(pid=5164)&nbsp;ERR&nbsp;-&nbsp;Error&nbsp;in&nbsp;GetCommand:&nbsp;0x80770004.
Apr&nbsp;2,&nbsp;2019&nbsp;3:36:26&nbsp;PM&nbsp;-&nbsp;Info&nbsp;dbclient&nbsp;(pid=5164)&nbsp;INF&nbsp;-&nbsp;OPERATION&nbsp;#1&nbsp;of&nbsp;batch&nbsp;__13_56_39_925_00.bch&nbsp;FAILED&nbsp;with&nbsp;STATUS&nbsp;1&nbsp;(0&nbsp;is&nbsp;normal).&nbsp;Elapsed&nbsp;time&nbsp;=&nbsp;5980(5980)&nbsp;seconds.
Apr&nbsp;2,&nbsp;2019&nbsp;3:36:27&nbsp;PM&nbsp;-&nbsp;Info&nbsp;dbclient&nbsp;(pid=5164)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CONTINUATION:&nbsp;-&nbsp;An&nbsp;abort&nbsp;request&nbsp;is&nbsp;preventing&nbsp;anything&nbsp;except&nbsp;termination&nbsp;actions.
Apr&nbsp;2,&nbsp;2019&nbsp;3:36:29&nbsp;PM&nbsp;-&nbsp;Info&nbsp;dbclient&nbsp;(pid=5164)&nbsp;INF&nbsp;-&nbsp;Results&nbsp;of&nbsp;executing&nbsp;&lt;__13_56_39_925_00.bch&gt;:&nbsp;
Apr&nbsp;2,&nbsp;2019&nbsp;3:36:29&nbsp;PM&nbsp;-&nbsp;Info&nbsp;dbclient&nbsp;(pid=5164)&nbsp;&lt;0&gt;&nbsp;operations&nbsp;succeeded.&nbsp;&lt;1&gt;&nbsp;operations&nbsp;failed.
Apr&nbsp;2,&nbsp;2019&nbsp;3:36:30&nbsp;PM&nbsp;-&nbsp;Info&nbsp;dbclient&nbsp;(pid=5164)&nbsp;INF&nbsp;-&nbsp;The&nbsp;following&nbsp;object(s)&nbsp;were&nbsp;not&nbsp;backed&nbsp;up&nbsp;successfully.
Apr&nbsp;2,&nbsp;2019&nbsp;3:36:32&nbsp;PM&nbsp;-&nbsp;Info&nbsp;dbclient&nbsp;(pid=5164)&nbsp;INF&nbsp;-&nbsp;Dev_PROPHIX_FactDb
Apr&nbsp;2,&nbsp;2019&nbsp;3:36:32&nbsp;PM&nbsp;-&nbsp;Error&nbsp;bpbrm&nbsp;(pid=8832)&nbsp;from&nbsp;client&nbsp;************:&nbsp;ERR&nbsp;-&nbsp;exit&nbsp;status:&nbsp;&lt;2&gt;
Apr&nbsp;2,&nbsp;2019&nbsp;3:36:33&nbsp;PM&nbsp;-&nbsp;Error&nbsp;bpbrm&nbsp;(pid=8832)&nbsp;from&nbsp;client&nbsp;************:&nbsp;ERR&nbsp;-&nbsp;bphdb&nbsp;exit&nbsp;status&nbsp;=&nbsp;2:&nbsp;none&nbsp;of&nbsp;the&nbsp;requested&nbsp;files&nbsp;were&nbsp;backed&nbsp;up
Apr&nbsp;2,&nbsp;2019&nbsp;3:36:33&nbsp;PM&nbsp;-&nbsp;Info&nbsp;bphdb&nbsp;(pid=12072)&nbsp;done.&nbsp;status:&nbsp;2:&nbsp;none&nbsp;of&nbsp;the&nbsp;requested&nbsp;files&nbsp;were&nbsp;backed&nbsp;up
Apr&nbsp;2,&nbsp;2019&nbsp;3:36:33&nbsp;PM&nbsp;-&nbsp;end&nbsp;writing
none&nbsp;of&nbsp;the&nbsp;requested&nbsp;files&nbsp;were&nbsp;backed&nbsp;up&nbsp; (2)

ANDApr&nbsp;2,&nbsp;2019&nbsp;1:56:55&nbsp;PM&nbsp;-&nbsp;Info&nbsp;nbjm&nbsp;(pid=6452)&nbsp;starting&nbsp;backup&nbsp;job&nbsp;(jobid=7972398)&nbsp;for&nbsp;client&nbsp;************,&nbsp;policy&nbsp;Prophix-DBs,&nbsp;schedule&nbsp;Hourly
Apr&nbsp;2,&nbsp;2019&nbsp;1:56:55&nbsp;PM&nbsp;-&nbsp;Info&nbsp;nbjm&nbsp;(pid=6452)&nbsp;requesting&nbsp;STANDARD_RESOURCE&nbsp;resources&nbsp;from&nbsp;RB&nbsp;for&nbsp;backup&nbsp;job&nbsp;(jobid=7972398,&nbsp;request&nbsp;id:{4BE15C6D-B68B-4B9C-9EF5-A90C8B765BB2})
Apr&nbsp;2,&nbsp;2019&nbsp;1:56:55&nbsp;PM&nbsp;-&nbsp;requesting&nbsp;resource&nbsp;&nbsp;MONT-SQL
Apr&nbsp;2,&nbsp;2019&nbsp;1:56:55&nbsp;PM&nbsp;-&nbsp;requesting&nbsp;resource&nbsp;&nbsp;MASTER.NBU_CLIENT.MAXJOBS.************
Apr&nbsp;2,&nbsp;2019&nbsp;1:56:55&nbsp;PM&nbsp;-&nbsp;awaiting&nbsp;resource&nbsp;MONT-SQL.&nbsp;Maximum&nbsp;job&nbsp;count&nbsp;has&nbsp;been&nbsp;reached&nbsp;for&nbsp;the&nbsp;storage&nbsp;unit.
Apr&nbsp;2,&nbsp;2019&nbsp;1:58:55&nbsp;PM&nbsp;-&nbsp;Info&nbsp;nbjm&nbsp;(pid=6452)&nbsp;Waiting&nbsp;in&nbsp;NetBackup&nbsp;scheduler&nbsp;work&nbsp;queue&nbsp;on&nbsp;server&nbsp;MASTER
Apr&nbsp;2,&nbsp;2019&nbsp;2:00:55&nbsp;PM&nbsp;-&nbsp;Info&nbsp;nbjm&nbsp;(pid=6452)&nbsp;Waiting&nbsp;in&nbsp;NetBackup&nbsp;scheduler&nbsp;work&nbsp;queue&nbsp;on&nbsp;server&nbsp;MASTER
Apr&nbsp;2,&nbsp;2019&nbsp;2:02:55&nbsp;PM&nbsp;-&nbsp;Info&nbsp;nbjm&nbsp;(pid=6452)&nbsp;Waiting&nbsp;in&nbsp;NetBackup&nbsp;scheduler&nbsp;work&nbsp;queue&nbsp;on&nbsp;server&nbsp;MASTER
Apr&nbsp;2,&nbsp;2019&nbsp;2:04:55&nbsp;PM&nbsp;-&nbsp;Info&nbsp;nbjm&nbsp;(pid=6452)&nbsp;Waiting&nbsp;in&nbsp;NetBackup&nbsp;scheduler&nbsp;work&nbsp;queue&nbsp;on&nbsp;server&nbsp;MASTER
Apr&nbsp;2,&nbsp;2019&nbsp;2:06:55&nbsp;PM&nbsp;-&nbsp;Info&nbsp;nbjm&nbsp;(pid=6452)&nbsp;Waiting&nbsp;in&nbsp;NetBackup&nbsp;scheduler&nbsp;work&nbsp;queue&nbsp;on&nbsp;server&nbsp;MASTER
Apr&nbsp;2,&nbsp;2019&nbsp;2:08:55&nbsp;PM&nbsp;-&nbsp;Info&nbsp;nbjm&nbsp;(pid=6452)&nbsp;Waiting&nbsp;in&nbsp;NetBackup&nbsp;scheduler&nbsp;work&nbsp;queue&nbsp;on&nbsp;server&nbsp;MASTER
Apr&nbsp;2,&nbsp;2019&nbsp;2:10:55&nbsp;PM&nbsp;-&nbsp;Info&nbsp;nbjm&nbsp;(pid=6452)&nbsp;Waiting&nbsp;in&nbsp;NetBackup&nbsp;scheduler&nbsp;work&nbsp;queue&nbsp;on&nbsp;server&nbsp;MASTER
Apr&nbsp;2,&nbsp;2019&nbsp;2:12:55&nbsp;PM&nbsp;-&nbsp;Info&nbsp;nbjm&nbsp;(pid=6452)&nbsp;Waiting&nbsp;in&nbsp;NetBackup&nbsp;scheduler&nbsp;work&nbsp;queue&nbsp;on&nbsp;server&nbsp;MASTER
Apr&nbsp;2,&nbsp;2019&nbsp;2:14:55&nbsp;PM&nbsp;-&nbsp;Info&nbsp;nbjm&nbsp;(pid=6452)&nbsp;Waiting&nbsp;in&nbsp;NetBackup&nbsp;scheduler&nbsp;work&nbsp;queue&nbsp;on&nbsp;server&nbsp;MASTER
Apr&nbsp;2,&nbsp;2019&nbsp;2:16:55&nbsp;PM&nbsp;-&nbsp;Info&nbsp;nbjm&nbsp;(pid=6452)&nbsp;Waiting&nbsp;in&nbsp;NetBackup&nbsp;scheduler&nbsp;work&nbsp;queue&nbsp;on&nbsp;server&nbsp;MASTER
Apr&nbsp;2,&nbsp;2019&nbsp;2:18:55&nbsp;PM&nbsp;-&nbsp;Info&nbsp;nbjm&nbsp;(pid=6452)&nbsp;Waiting&nbsp;in&nbsp;NetBackup&nbsp;scheduler&nbsp;work&nbsp;queue&nbsp;on&nbsp;server&nbsp;MASTER
Apr&nbsp;2,&nbsp;2019&nbsp;2:20:55&nbsp;PM&nbsp;-&nbsp;Info&nbsp;nbjm&nbsp;(pid=6452)&nbsp;Waiting&nbsp;in&nbsp;NetBackup&nbsp;scheduler&nbsp;work&nbsp;queue&nbsp;on&nbsp;server&nbsp;MASTER
Apr&nbsp;2,&nbsp;2019&nbsp;2:22:55&nbsp;PM&nbsp;-&nbsp;Info&nbsp;nbjm&nbsp;(pid=6452)&nbsp;Waiting&nbsp;in&nbsp;NetBackup&nbsp;scheduler&nbsp;work&nbsp;queue&nbsp;on&nbsp;server&nbsp;MASTER
Apr&nbsp;2,&nbsp;2019&nbsp;2:24:55&nbsp;PM&nbsp;-&nbsp;Info&nbsp;nbjm&nbsp;(pid=6452)&nbsp;Waiting&nbsp;in&nbsp;NetBackup&nbsp;scheduler&nbsp;work&nbsp;queue&nbsp;on&nbsp;server&nbsp;MASTER
Apr&nbsp;2,&nbsp;2019&nbsp;2:26:55&nbsp;PM&nbsp;-&nbsp;Info&nbsp;nbjm&nbsp;(pid=6452)&nbsp;Waiting&nbsp;in&nbsp;NetBackup&nbsp;scheduler&nbsp;work&nbsp;queue&nbsp;on&nbsp;server&nbsp;MASTER
Apr&nbsp;2,&nbsp;2019&nbsp;2:28:55&nbsp;PM&nbsp;-&nbsp;Info&nbsp;nbjm&nbsp;(pid=6452)&nbsp;Waiting&nbsp;in&nbsp;NetBackup&nbsp;scheduler&nbsp;work&nbsp;queue&nbsp;on&nbsp;server&nbsp;MASTER
Apr&nbsp;2,&nbsp;2019&nbsp;2:30:55&nbsp;PM&nbsp;-&nbsp;Info&nbsp;nbjm&nbsp;(pid=6452)&nbsp;Waiting&nbsp;in&nbsp;NetBackup&nbsp;scheduler&nbsp;work&nbsp;queue&nbsp;on&nbsp;server&nbsp;MASTER
Apr&nbsp;2,&nbsp;2019&nbsp;2:32:55&nbsp;PM&nbsp;-&nbsp;Info&nbsp;nbjm&nbsp;(pid=6452)&nbsp;Waiting&nbsp;in&nbsp;NetBackup&nbsp;scheduler&nbsp;work&nbsp;queue&nbsp;on&nbsp;server&nbsp;MASTER
Apr&nbsp;2,&nbsp;2019&nbsp;2:34:55&nbsp;PM&nbsp;-&nbsp;Info&nbsp;nbjm&nbsp;(pid=6452)&nbsp;Waiting&nbsp;in&nbsp;NetBackup&nbsp;scheduler&nbsp;work&nbsp;queue&nbsp;on&nbsp;server&nbsp;MASTER
Apr&nbsp;2,&nbsp;2019&nbsp;2:36:55&nbsp;PM&nbsp;-&nbsp;Info&nbsp;nbjm&nbsp;(pid=6452)&nbsp;Waiting&nbsp;in&nbsp;NetBackup&nbsp;scheduler&nbsp;work&nbsp;queue&nbsp;on&nbsp;server&nbsp;MASTER
Apr&nbsp;2,&nbsp;2019&nbsp;2:38:55&nbsp;PM&nbsp;-&nbsp;Info&nbsp;nbjm&nbsp;(pid=6452)&nbsp;Waiting&nbsp;in&nbsp;NetBackup&nbsp;scheduler&nbsp;work&nbsp;queue&nbsp;on&nbsp;server&nbsp;MASTER
Apr&nbsp;2,&nbsp;2019&nbsp;2:40:55&nbsp;PM&nbsp;-&nbsp;Info&nbsp;nbjm&nbsp;(pid=6452)&nbsp;Waiting&nbsp;in&nbsp;NetBackup&nbsp;scheduler&nbsp;work&nbsp;queue&nbsp;on&nbsp;server&nbsp;MASTER
Apr&nbsp;2,&nbsp;2019&nbsp;2:42:55&nbsp;PM&nbsp;-&nbsp;Info&nbsp;nbjm&nbsp;(pid=6452)&nbsp;Waiting&nbsp;in&nbsp;NetBackup&nbsp;scheduler&nbsp;work&nbsp;queue&nbsp;on&nbsp;server&nbsp;MASTER
Apr&nbsp;2,&nbsp;2019&nbsp;2:44:55&nbsp;PM&nbsp;-&nbsp;Info&nbsp;nbjm&nbsp;(pid=6452)&nbsp;Waiting&nbsp;in&nbsp;NetBackup&nbsp;scheduler&nbsp;work&nbsp;queue&nbsp;on&nbsp;server&nbsp;MASTER
Apr&nbsp;2,&nbsp;2019&nbsp;2:46:55&nbsp;PM&nbsp;-&nbsp;Info&nbsp;nbjm&nbsp;(pid=6452)&nbsp;Waiting&nbsp;in&nbsp;NetBackup&nbsp;scheduler&nbsp;work&nbsp;queue&nbsp;on&nbsp;server&nbsp;MASTER
Apr&nbsp;2,&nbsp;2019&nbsp;2:48:55&nbsp;PM&nbsp;-&nbsp;Info&nbsp;nbjm&nbsp;(pid=6452)&nbsp;Waiting&nbsp;in&nbsp;NetBackup&nbsp;scheduler&nbsp;work&nbsp;queue&nbsp;on&nbsp;server&nbsp;MASTER
Apr&nbsp;2,&nbsp;2019&nbsp;2:50:55&nbsp;PM&nbsp;-&nbsp;Info&nbsp;nbjm&nbsp;(pid=6452)&nbsp;Waiting&nbsp;in&nbsp;NetBackup&nbsp;scheduler&nbsp;work&nbsp;queue&nbsp;on&nbsp;server&nbsp;MASTER
Apr&nbsp;2,&nbsp;2019&nbsp;2:52:55&nbsp;PM&nbsp;-&nbsp;Info&nbsp;nbjm&nbsp;(pid=6452)&nbsp;Waiting&nbsp;in&nbsp;NetBackup&nbsp;scheduler&nbsp;work&nbsp;queue&nbsp;on&nbsp;server&nbsp;MASTER
Apr&nbsp;2,&nbsp;2019&nbsp;2:54:55&nbsp;PM&nbsp;-&nbsp;Info&nbsp;nbjm&nbsp;(pid=6452)&nbsp;Waiting&nbsp;in&nbsp;NetBackup&nbsp;scheduler&nbsp;work&nbsp;queue&nbsp;on&nbsp;server&nbsp;MASTER
Apr&nbsp;2,&nbsp;2019&nbsp;2:55:39&nbsp;PM&nbsp;-&nbsp;granted&nbsp;resource&nbsp;&nbsp;MASTER.NBU_CLIENT.MAXJOBS.************
Apr&nbsp;2,&nbsp;2019&nbsp;2:55:39&nbsp;PM&nbsp;-&nbsp;granted&nbsp;resource&nbsp;&nbsp;MediaID=@aaaa6;DiskVolume=PureDiskVolume;DiskPool=DDUPool-01;Path=PureDiskVolume;StorageServer=srv-snbu08.mont.ru;MediaServer=srv-snbu03.mont.ru
Apr&nbsp;2,&nbsp;2019&nbsp;2:55:39&nbsp;PM&nbsp;-&nbsp;granted&nbsp;resource&nbsp;&nbsp;DiskStorage-1
Apr&nbsp;2,&nbsp;2019&nbsp;2:55:39&nbsp;PM&nbsp;-&nbsp;estimated&nbsp;2857766&nbsp;kbytes&nbsp;needed
Apr&nbsp;2,&nbsp;2019&nbsp;2:55:39&nbsp;PM&nbsp;-&nbsp;Info&nbsp;nbjm&nbsp;(pid=6452)&nbsp;started&nbsp;backup&nbsp;(backupid=************_1554206139)&nbsp;job&nbsp;for&nbsp;client&nbsp;************,&nbsp;policy&nbsp;Prophix-DBs,&nbsp;schedule&nbsp;Hourly&nbsp;on&nbsp;storage&nbsp;unit&nbsp;DiskStorage-1
Apr&nbsp;2,&nbsp;2019&nbsp;2:55:41&nbsp;PM&nbsp;-&nbsp;started&nbsp;process&nbsp;bpbrm&nbsp;(pid=12200)
Apr&nbsp;2,&nbsp;2019&nbsp;2:55:41&nbsp;PM&nbsp;-&nbsp;Info&nbsp;bpbrm&nbsp;(pid=12200)&nbsp;************&nbsp;is&nbsp;the&nbsp;host&nbsp;to&nbsp;backup&nbsp;data&nbsp;from
Apr&nbsp;2,&nbsp;2019&nbsp;2:55:42&nbsp;PM&nbsp;-&nbsp;connecting
Apr&nbsp;2,&nbsp;2019&nbsp;2:55:42&nbsp;PM&nbsp;-&nbsp;Info&nbsp;bpbrm&nbsp;(pid=12200)&nbsp;reading&nbsp;file&nbsp;list&nbsp;for&nbsp;client
Apr&nbsp;2,&nbsp;2019&nbsp;2:55:43&nbsp;PM&nbsp;-&nbsp;Info&nbsp;bpbrm&nbsp;(pid=12200)&nbsp;listening&nbsp;for&nbsp;client&nbsp;connection
Apr&nbsp;2,&nbsp;2019&nbsp;2:55:44&nbsp;PM&nbsp;-&nbsp;Info&nbsp;bpbrm&nbsp;(pid=12200)&nbsp;INF&nbsp;-&nbsp;Client&nbsp;read&nbsp;timeout&nbsp;=&nbsp;900
Apr&nbsp;2,&nbsp;2019&nbsp;2:55:44&nbsp;PM&nbsp;-&nbsp;Info&nbsp;bpbrm&nbsp;(pid=12200)&nbsp;accepted&nbsp;connection&nbsp;from&nbsp;client
Apr&nbsp;2,&nbsp;2019&nbsp;2:55:44&nbsp;PM&nbsp;-&nbsp;Info&nbsp;dbclient&nbsp;(pid=5164)&nbsp;Backup&nbsp;started
Apr&nbsp;2,&nbsp;2019&nbsp;2:55:44&nbsp;PM&nbsp;-&nbsp;Info&nbsp;bptm&nbsp;(pid=11352)&nbsp;start
Apr&nbsp;2,&nbsp;2019&nbsp;2:55:45&nbsp;PM&nbsp;-&nbsp;connected;&nbsp;connect&nbsp;time:&nbsp;0:00:00
Apr&nbsp;2,&nbsp;2019&nbsp;2:55:45&nbsp;PM&nbsp;-&nbsp;Info&nbsp;bptm&nbsp;(pid=11352)&nbsp;using&nbsp;262144&nbsp;data&nbsp;buffer&nbsp;size
Apr&nbsp;2,&nbsp;2019&nbsp;2:55:45&nbsp;PM&nbsp;-&nbsp;Info&nbsp;bptm&nbsp;(pid=11352)&nbsp;setting&nbsp;receive&nbsp;network&nbsp;buffer&nbsp;to&nbsp;1049600&nbsp;bytes
Apr&nbsp;2,&nbsp;2019&nbsp;2:55:45&nbsp;PM&nbsp;-&nbsp;Info&nbsp;bptm&nbsp;(pid=11352)&nbsp;using&nbsp;30&nbsp;data&nbsp;buffers
Apr&nbsp;2,&nbsp;2019&nbsp;2:55:47&nbsp;PM&nbsp;-&nbsp;Info&nbsp;bptm&nbsp;(pid=11352)&nbsp;start&nbsp;backup
Apr&nbsp;2,&nbsp;2019&nbsp;3:19:03&nbsp;PM&nbsp;-&nbsp;Info&nbsp;bptm&nbsp;(pid=11352)&nbsp;backup&nbsp;child&nbsp;process&nbsp;is&nbsp;pid&nbsp;10980.10236
Apr&nbsp;2,&nbsp;2019&nbsp;3:19:03&nbsp;PM&nbsp;-&nbsp;begin&nbsp;writing
Apr&nbsp;2,&nbsp;2019&nbsp;3:19:03&nbsp;PM&nbsp;-&nbsp;Info&nbsp;bptm&nbsp;(pid=10980)&nbsp;start
Apr&nbsp;2,&nbsp;2019&nbsp;3:39:06&nbsp;PM&nbsp;-&nbsp;Info&nbsp;dbclient&nbsp;(pid=5164)&nbsp;done.&nbsp;status:&nbsp;41:&nbsp;network&nbsp;connection&nbsp;timed&nbsp;out
Apr&nbsp;2,&nbsp;2019&nbsp;3:39:06&nbsp;PM&nbsp;-&nbsp;end&nbsp;writing;&nbsp;write&nbsp;time:&nbsp;0:20:03
network&nbsp;connection&nbsp;timed&nbsp;out&nbsp; (41)

marianne · Answer

svasilev&nbsp;
My time is very limited to read logs, but I have started to go through the previous logs.
This is what I have seen:
Backup started here:12:48:37.302 [2252.14528] &lt;4&gt; CreateNewImage: INF - backing up File:&lt;/nikta-sql-clr.mont.ru:NIKTA-SQL-N2/MSSQL7/NIKTA-SQL-AG/db/MontNikta/~/7/001of001/20190408094826//C&gt;
There is no indication of what happened between these 2 timestamps:12:48:37.755 13:27:57.562
But data collection within SQL only started here:
13:29:23.937 [2252.14528] &lt;4&gt; CDBbackmain::CollectFEDS: INF - Database &lt; MontNikta &gt; in SQL Instance &lt; MSSQLSERVER &gt; has a size of &lt; 225000.00 MB &gt;13:29:23.937 [2252.14528] &lt;4&gt; CDBbackmain::CollectFEDS: INF - FEDS Data: Job ID &lt; 8012046 &gt;, Virtual Name &lt; nikta-sql-clr.mont.ru &gt;, Backup ID &lt; &gt;, Instance &lt; MSSQLSERVER &gt;, AG &lt; NIKTA-SQL-AG &gt;, Database &lt; MontNikta &gt;
13:40:43.291 [2252.6784] &lt;4&gt; CODBCaccess::LogODBCerr: INF - ODBC return code &lt;2&gt;, SQL State &lt;01000&gt;, SQL Message &lt;3211&gt;&lt;[Microsoft][SQL Server Native Client 11.0][SQL Server]10 percent processed.&gt;.
14:05:28.979 [2252.6784] &lt;4&gt; CODBCaccess::LogODBCerr: INF - ODBC return code &lt;2&gt;, SQL State &lt;01000&gt;, SQL Message &lt;3211&gt;&lt;[Microsoft][SQL Server Native Client 11.0][SQL Server]20 percent processed.&gt;.
15:13:00.754 [2252.6784] &lt;4&gt; CODBCaccess::LogODBCerr: INF - ODBC return code &lt;2&gt;, SQL State &lt;01000&gt;, SQL Message &lt;3211&gt;&lt;[Microsoft][SQL Server Native Client 11.0][SQL Server]30 percent processed.&gt;.
It seems that data transfer then got to a halt, with timeout after 30 minutes:
15:33:00.256 [2252.14528] &lt;16&gt; writeToServer: ERR - send() to server on socket failed:15:33:00.256 [2252.14528] &lt;16&gt; dbc_put: ERR - failed sending data to server15:33:00.256 [2252.14528] &lt;4&gt; closeApi: INF - EXIT STATUS 6: the backup failed to back up the requested files
Have a look at the timestamps between start, 10, 20 and 30%:The 1st 10% took 11 minutes. So, acceptable read speed of more than 34 MB/sec.The next 10% took 25 minutes.To get from 20% to 30% took 68 minutes.&nbsp;
So, it looks like possible resource issues on the SQL server during backup.
You will need the assistance of server owner and SQL dba to monitor the server during backup.The need to check system performance - cpu and memory.Check Event Viewer Application and System logs.Check SQL&nbsp;VDI.log, and ERRORLOG.
From NBU point of view, these logs will confirm up to when data and metadata was received from the SQL client:bpbrm on the media server (connection, metadata and timeout info)bptm on media server (data received from client)All of these logs should be at minimum of level 3.&nbsp;

svasilev · Answer

What is the problem?Backup runs on schedule

marianne · Answer

Please share dbclient log on the SQL client. Logging level 3 should be sufficient.If dbclient log folder does not exist, please create it under ...netbackup\logs and set logging level to 3 for this client in Host Properties.
Please copy log file to dbclient.txt and upload as attachment.&nbsp;

svasilev · Answer

dbclient.txt in attachmenthelp us please

svasilev · Answer

HelloWe have a new error - 2 (job 1) &gt; 2 (job 2) &gt; 41&nbsp; (job 3)Full backup - job 1:Apr&nbsp;8,&nbsp;2019&nbsp;4:43:19&nbsp;PM&nbsp;-&nbsp;Info&nbsp;nbjm&nbsp;(pid=6452)&nbsp;starting&nbsp;backup&nbsp;job&nbsp;(jobid=8013185)&nbsp;for&nbsp;client&nbsp;srv-snbu01.dom.ru,&nbsp;policy&nbsp;NIKTA-DBs,&nbsp;schedule&nbsp;Weekly
Apr&nbsp;8,&nbsp;2019&nbsp;4:43:19&nbsp;PM&nbsp;-&nbsp;Info&nbsp;nbjm&nbsp;(pid=6452)&nbsp;requesting&nbsp;MEDIA_SERVER_ONLY&nbsp;resources&nbsp;from&nbsp;RB&nbsp;for&nbsp;backup&nbsp;job&nbsp;(jobid=8013185,&nbsp;request&nbsp;id:{71499A86-9497-488D-9764-C80504CFE895})
Apr&nbsp;8,&nbsp;2019&nbsp;4:43:19&nbsp;PM&nbsp;-&nbsp;requesting&nbsp;resource&nbsp;&nbsp;DiskStorage-1
Apr&nbsp;8,&nbsp;2019&nbsp;4:43:19&nbsp;PM&nbsp;-&nbsp;requesting&nbsp;resource&nbsp;&nbsp;srv-snbu01.dom.ru.NBU_CLIENT.MAXJOBS.srv-snbu01.dom.ru
Apr&nbsp;8,&nbsp;2019&nbsp;4:43:19&nbsp;PM&nbsp;-&nbsp;granted&nbsp;resource&nbsp;&nbsp;srv-snbu01.dom.ru.NBU_CLIENT.MAXJOBS.srv-snbu01.dom.ru
Apr&nbsp;8,&nbsp;2019&nbsp;4:43:20&nbsp;PM&nbsp;-&nbsp;estimated&nbsp;0&nbsp;kbytes&nbsp;needed
Apr&nbsp;8,&nbsp;2019&nbsp;4:43:20&nbsp;PM&nbsp;-&nbsp;begin&nbsp;Parent&nbsp;Job
Apr&nbsp;8,&nbsp;2019&nbsp;4:43:20&nbsp;PM&nbsp;-&nbsp;begin&nbsp;Application&nbsp;Resolver:&nbsp;Start&nbsp;Notify&nbsp;Script
Apr&nbsp;8,&nbsp;2019&nbsp;4:43:20&nbsp;PM&nbsp;-&nbsp;Info&nbsp;RUNCMD&nbsp;(pid=8492)&nbsp;started
Apr&nbsp;8,&nbsp;2019&nbsp;4:43:20&nbsp;PM&nbsp;-&nbsp;Info&nbsp;RUNCMD&nbsp;(pid=8492)&nbsp;exiting&nbsp;with&nbsp;status:&nbsp;0
Operation&nbsp;Status:&nbsp;0
Apr&nbsp;8,&nbsp;2019&nbsp;4:43:20&nbsp;PM&nbsp;-&nbsp;end&nbsp;Application&nbsp;Resolver:&nbsp;Start&nbsp;Notify&nbsp;Script;&nbsp;elapsed&nbsp;time&nbsp;0:00:00
Apr&nbsp;8,&nbsp;2019&nbsp;4:43:20&nbsp;PM&nbsp;-&nbsp;begin&nbsp;Application&nbsp;Resolver:&nbsp;Step&nbsp;By&nbsp;Condition
Operation&nbsp;Status:&nbsp;0
Apr&nbsp;8,&nbsp;2019&nbsp;4:43:20&nbsp;PM&nbsp;-&nbsp;end&nbsp;Application&nbsp;Resolver:&nbsp;Step&nbsp;By&nbsp;Condition;&nbsp;elapsed&nbsp;time&nbsp;0:00:00
Apr&nbsp;8,&nbsp;2019&nbsp;4:43:20&nbsp;PM&nbsp;-&nbsp;begin&nbsp;Application&nbsp;Resolver:&nbsp;Resolver&nbsp;Discovery
Operation&nbsp;Status:&nbsp;0
Apr&nbsp;8,&nbsp;2019&nbsp;4:43:21&nbsp;PM&nbsp;-&nbsp;end&nbsp;Application&nbsp;Resolver:&nbsp;Resolver&nbsp;Discovery;&nbsp;elapsed&nbsp;time&nbsp;0:00:01
Apr&nbsp;8,&nbsp;2019&nbsp;4:43:21&nbsp;PM&nbsp;-&nbsp;begin&nbsp;Application&nbsp;Resolver:&nbsp;Policy&nbsp;Execution&nbsp;Manager&nbsp;Preprocessed
Operation&nbsp;Status:&nbsp;2
Apr&nbsp;9,&nbsp;2019&nbsp;12:59:47&nbsp;AM&nbsp;-&nbsp;end&nbsp;Application&nbsp;Resolver:&nbsp;Policy&nbsp;Execution&nbsp;Manager&nbsp;Preprocessed;&nbsp;elapsed&nbsp;time&nbsp;8:16:26
Apr&nbsp;9,&nbsp;2019&nbsp;12:59:47&nbsp;AM&nbsp;-&nbsp;begin&nbsp;Application&nbsp;Resolver:&nbsp;Stop&nbsp;On&nbsp;Error
Operation&nbsp;Status:&nbsp;0
Apr&nbsp;9,&nbsp;2019&nbsp;12:59:47&nbsp;AM&nbsp;-&nbsp;end&nbsp;Application&nbsp;Resolver:&nbsp;Stop&nbsp;On&nbsp;Error;&nbsp;elapsed&nbsp;time&nbsp;0:00:00
Apr&nbsp;9,&nbsp;2019&nbsp;12:59:47&nbsp;AM&nbsp;-&nbsp;begin&nbsp;Application&nbsp;Resolver:&nbsp;End&nbsp;Notify&nbsp;Script
Apr&nbsp;9,&nbsp;2019&nbsp;12:59:48&nbsp;AM&nbsp;-&nbsp;Info&nbsp;RUNCMD&nbsp;(pid=1520)&nbsp;started
Apr&nbsp;9,&nbsp;2019&nbsp;12:59:48&nbsp;AM&nbsp;-&nbsp;Info&nbsp;RUNCMD&nbsp;(pid=1520)&nbsp;exiting&nbsp;with&nbsp;status:&nbsp;0
Operation&nbsp;Status:&nbsp;0
Apr&nbsp;9,&nbsp;2019&nbsp;12:59:48&nbsp;AM&nbsp;-&nbsp;end&nbsp;Application&nbsp;Resolver:&nbsp;End&nbsp;Notify&nbsp;Script;&nbsp;elapsed&nbsp;time&nbsp;0:00:01
Operation&nbsp;Status:&nbsp;2
Apr&nbsp;9,&nbsp;2019&nbsp;12:59:48&nbsp;AM&nbsp;-&nbsp;end&nbsp;Parent&nbsp;Job;&nbsp;elapsed&nbsp;time&nbsp;8:16:28
none&nbsp;of&nbsp;the&nbsp;requested&nbsp;files&nbsp;were&nbsp;backed&nbsp;up&nbsp; (2)Job 2:Apr&nbsp;8,&nbsp;2019&nbsp;4:43:21&nbsp;PM&nbsp;-&nbsp;Info&nbsp;nbjm&nbsp;(pid=6452)&nbsp;starting&nbsp;backup&nbsp;job&nbsp;(jobid=8013186)&nbsp;for&nbsp;client&nbsp;nikta-sql.dom.ru,&nbsp;policy&nbsp;NIKTA-DBs,&nbsp;schedule&nbsp;Weekly
Apr&nbsp;8,&nbsp;2019&nbsp;4:43:21&nbsp;PM&nbsp;-&nbsp;Info&nbsp;nbjm&nbsp;(pid=6452)&nbsp;requesting&nbsp;MEDIA_SERVER_ONLY&nbsp;resources&nbsp;from&nbsp;RB&nbsp;for&nbsp;backup&nbsp;job&nbsp;(jobid=8013186,&nbsp;request&nbsp;id:{8CAD7B27-479F-467A-AE9D-10C1B5174C4F})
Apr&nbsp;8,&nbsp;2019&nbsp;4:43:21&nbsp;PM&nbsp;-&nbsp;requesting&nbsp;resource&nbsp;&nbsp;DiskStorage-1
Apr&nbsp;8,&nbsp;2019&nbsp;4:43:22&nbsp;PM&nbsp;-&nbsp;estimated&nbsp;0&nbsp;kbytes&nbsp;needed
Apr&nbsp;8,&nbsp;2019&nbsp;4:43:22&nbsp;PM&nbsp;-&nbsp;Info&nbsp;nbjm&nbsp;(pid=6452)&nbsp;started&nbsp;backup&nbsp;(backupid=nikta-sql.dom.ru_1554731001)&nbsp;job&nbsp;for&nbsp;client&nbsp;nikta-sql.dom.ru,&nbsp;policy&nbsp;NIKTA-DBs,&nbsp;schedule&nbsp;Weekly&nbsp;on&nbsp;storage&nbsp;unit&nbsp;
Apr&nbsp;8,&nbsp;2019&nbsp;4:43:23&nbsp;PM&nbsp;-&nbsp;started&nbsp;process&nbsp;bpbrm&nbsp;(pid=4992)
Apr&nbsp;8,&nbsp;2019&nbsp;4:43:24&nbsp;PM&nbsp;-&nbsp;connecting
Apr&nbsp;8,&nbsp;2019&nbsp;4:43:24&nbsp;PM&nbsp;-&nbsp;Info&nbsp;bpbrm&nbsp;(pid=4992)&nbsp;nikta-sql.dom.ru&nbsp;is&nbsp;the&nbsp;host&nbsp;to&nbsp;backup&nbsp;data&nbsp;from
Apr&nbsp;8,&nbsp;2019&nbsp;4:43:24&nbsp;PM&nbsp;-&nbsp;Info&nbsp;bpbrm&nbsp;(pid=4992)&nbsp;reading&nbsp;file&nbsp;list&nbsp;for&nbsp;client
Apr&nbsp;8,&nbsp;2019&nbsp;4:43:25&nbsp;PM&nbsp;-&nbsp;Info&nbsp;bpbrm&nbsp;(pid=4992)&nbsp;starting&nbsp;bphdb&nbsp;on&nbsp;client
Apr&nbsp;8,&nbsp;2019&nbsp;4:43:25&nbsp;PM&nbsp;-&nbsp;Info&nbsp;bphdb&nbsp;(pid=11096)&nbsp;Backup&nbsp;started
Apr&nbsp;8,&nbsp;2019&nbsp;4:43:25&nbsp;PM&nbsp;-&nbsp;connected;&nbsp;connect&nbsp;time:&nbsp;0:00:00
Apr&nbsp;8,&nbsp;2019&nbsp;4:43:26&nbsp;PM&nbsp;-&nbsp;Info&nbsp;dbclient&nbsp;(pid=5324)&nbsp;INF&nbsp;-&nbsp;Intelligent&nbsp;policy&nbsp;initiated&nbsp;by&nbsp;server&nbsp;&lt;srv-snbu01.dom.ru&gt;
Apr&nbsp;8,&nbsp;2019&nbsp;4:43:27&nbsp;PM&nbsp;-&nbsp;Info&nbsp;dbclient&nbsp;(pid=5324)&nbsp;INF&nbsp;-&nbsp;Intelligent&nbsp;policy&nbsp;&lt;NIKTA-DBs&gt;&nbsp;is&nbsp;valid.&nbsp;The&nbsp;input&nbsp;file&nbsp;&lt;C:\Program&nbsp;Files\Veritas\NetBackup\dbext\mssql\input.11096.0.0408119.164325&gt;&nbsp;has&nbsp;been&nbsp;parsed&nbsp;successfully
Apr&nbsp;8,&nbsp;2019&nbsp;4:43:30&nbsp;PM&nbsp;-&nbsp;Info&nbsp;dbclient&nbsp;(pid=5324)&nbsp;INF&nbsp;-&nbsp;Instance&nbsp;server&nbsp;name&nbsp;resolved&nbsp;to:&nbsp;&lt;NIKTA-SQL-N2&gt;
Apr&nbsp;8,&nbsp;2019&nbsp;4:43:31&nbsp;PM&nbsp;-&nbsp;Info&nbsp;dbclient&nbsp;(pid=5324)&nbsp;INF&nbsp;-&nbsp;Intelligent&nbsp;policy&nbsp;&lt;NIKTA-DBs&gt;&nbsp;has&nbsp;resulted&nbsp;in&nbsp;&lt;1&gt;&nbsp;batch&nbsp;operation(s).
Apr&nbsp;8,&nbsp;2019&nbsp;4:43:34&nbsp;PM&nbsp;-&nbsp;Info&nbsp;dbclient&nbsp;(pid=5324)&nbsp;INF&nbsp;-&nbsp;Intelligent&nbsp;policy&nbsp;&lt;NIKTA-DBs&gt;:&nbsp;&lt;1&gt;&nbsp;operation(s)&nbsp;will&nbsp;protect&nbsp;full&nbsp;databases.
Apr&nbsp;8,&nbsp;2019&nbsp;4:43:36&nbsp;PM&nbsp;-&nbsp;Info&nbsp;dbclient&nbsp;(pid=5324)&nbsp;INF&nbsp;-&nbsp;Intelligent&nbsp;policy&nbsp;preprocessing&nbsp;has&nbsp;finished,&nbsp;created&nbsp;temporary&nbsp;batch&nbsp;file&nbsp;&lt;__16_43_31_830_00.bch&gt;,&nbsp;and&nbsp;submitted&nbsp;it&nbsp;to&nbsp;the&nbsp;backend&nbsp;agent&nbsp;for&nbsp;processing
Apr&nbsp;8,&nbsp;2019&nbsp;4:43:41&nbsp;PM&nbsp;-&nbsp;Info&nbsp;dbclient&nbsp;(pid=5324)&nbsp;INF&nbsp;-&nbsp;BACKUP&nbsp;STARTED&nbsp;USING
Apr&nbsp;8,&nbsp;2019&nbsp;4:43:41&nbsp;PM&nbsp;-&nbsp;Info&nbsp;dbclient&nbsp;(pid=5324)&nbsp;Microsoft&nbsp;SQL&nbsp;Server&nbsp;2016&nbsp;(SP2-CU1)&nbsp;(KB4135048)&nbsp;-&nbsp;13.0.5149.0&nbsp;(X64)&nbsp;
Apr&nbsp;8,&nbsp;2019&nbsp;4:43:41&nbsp;PM&nbsp;-&nbsp;Info&nbsp;dbclient&nbsp;(pid=5324)&nbsp;May&nbsp;19&nbsp;2018&nbsp;09:41:57&nbsp;
Apr&nbsp;8,&nbsp;2019&nbsp;4:43:41&nbsp;PM&nbsp;-&nbsp;Info&nbsp;dbclient&nbsp;(pid=5324)&nbsp;Copyright&nbsp;(c)&nbsp;Microsoft&nbsp;Corporation
Apr&nbsp;8,&nbsp;2019&nbsp;4:43:41&nbsp;PM&nbsp;-&nbsp;Info&nbsp;dbclient&nbsp;(pid=5324)&nbsp;Enterprise&nbsp;Edition:&nbsp;Core-based&nbsp;Licensing&nbsp;(64-bit)&nbsp;on&nbsp;Windows&nbsp;Server&nbsp;2016&nbsp;Standard&nbsp;10.0&nbsp;&lt;X64&gt;&nbsp;(Build&nbsp;14393:&nbsp;)&nbsp;(Hypervisor)&nbsp;
Apr&nbsp;8,&nbsp;2019&nbsp;4:43:41&nbsp;PM&nbsp;-&nbsp;Info&nbsp;dbclient&nbsp;(pid=5324)&nbsp;Batch&nbsp;=&nbsp;__16_43_31_830_00.bch,&nbsp;Op#&nbsp;=&nbsp;1
Apr&nbsp;8,&nbsp;2019&nbsp;4:43:44&nbsp;PM&nbsp;-&nbsp;Info&nbsp;dbclient&nbsp;(pid=5324)&nbsp;INF&nbsp;-&nbsp;Using&nbsp;backup&nbsp;image&nbsp;nikta-sql-clr.dom.ru:NIKTA-SQL-N2/MSSQL7/NIKTA-SQL-AG/db/MontNikta/~/7/001of001/20190408134340//C
Apr&nbsp;8,&nbsp;2019&nbsp;4:43:46&nbsp;PM&nbsp;-&nbsp;Info&nbsp;dbclient&nbsp;(pid=5324)&nbsp;INF&nbsp;-&nbsp;backup&nbsp;database&nbsp;"MontNikta"&nbsp;to&nbsp;VIRTUAL_DEVICE='VNBU0-5324-10808-1554731024'&nbsp;with&nbsp;&nbsp;stats&nbsp;=&nbsp;10,&nbsp;checksum,&nbsp;stop_on_error,&nbsp;blocksize&nbsp;=&nbsp;65536,&nbsp;maxtransfersize&nbsp;=&nbsp;4194304,&nbsp;buffercount&nbsp;=&nbsp;2
Apr&nbsp;8,&nbsp;2019&nbsp;4:43:48&nbsp;PM&nbsp;-&nbsp;Info&nbsp;dbclient&nbsp;(pid=5324)&nbsp;INF&nbsp;-&nbsp;Availability&nbsp;group&nbsp;database&nbsp;detected.&nbsp;Setting&nbsp;backup&nbsp;catalog&nbsp;name&nbsp;to:&nbsp;nikta-sql-clr.dom.ru
Apr&nbsp;8,&nbsp;2019&nbsp;4:43:48&nbsp;PM&nbsp;-&nbsp;Info&nbsp;dbclient&nbsp;(pid=5324)&nbsp;INF&nbsp;-&nbsp;Number&nbsp;of&nbsp;stripes:&nbsp;1,&nbsp;Number&nbsp;of&nbsp;buffers&nbsp;per&nbsp;stripe&nbsp;2.
Apr&nbsp;8,&nbsp;2019&nbsp;4:43:51&nbsp;PM&nbsp;-&nbsp;Info&nbsp;dbclient&nbsp;(pid=5324)&nbsp;INF&nbsp;-&nbsp;Created&nbsp;VDI&nbsp;object&nbsp;for&nbsp;SQL&nbsp;Server&nbsp;instance&nbsp;&lt;NIKTA-SQL-N2&gt;.&nbsp;Connection&nbsp;timeout&nbsp;is&nbsp;&lt;300&gt;&nbsp;seconds.
Apr&nbsp;8,&nbsp;2019&nbsp;4:45:27&nbsp;PM&nbsp;-&nbsp;Info&nbsp;dbclient&nbsp;(pid=5324)&nbsp;INF&nbsp;-&nbsp;ODBC&nbsp;return&nbsp;code&nbsp;&lt;2&gt;,&nbsp;SQL&nbsp;State&nbsp;&lt;01000&gt;,&nbsp;SQL&nbsp;Message&nbsp;&lt;3211&gt;&lt;[Microsoft][SQL&nbsp;Server&nbsp;Native&nbsp;Client&nbsp;11.0][SQL&nbsp;Server]10&nbsp;percent&nbsp;processed.&gt;.
Apr&nbsp;8,&nbsp;2019&nbsp;4:46:48&nbsp;PM&nbsp;-&nbsp;Info&nbsp;dbclient&nbsp;(pid=5324)&nbsp;INF&nbsp;-&nbsp;ODBC&nbsp;return&nbsp;code&nbsp;&lt;2&gt;,&nbsp;SQL&nbsp;State&nbsp;&lt;01000&gt;,&nbsp;SQL&nbsp;Message&nbsp;&lt;3211&gt;&lt;[Microsoft][SQL&nbsp;Server&nbsp;Native&nbsp;Client&nbsp;11.0][SQL&nbsp;Server]20&nbsp;percent&nbsp;processed.&gt;.
Apr&nbsp;8,&nbsp;2019&nbsp;5:09:02&nbsp;PM&nbsp;-&nbsp;Info&nbsp;dbclient&nbsp;(pid=5324)&nbsp;INF&nbsp;-&nbsp;ODBC&nbsp;return&nbsp;code&nbsp;&lt;2&gt;,&nbsp;SQL&nbsp;State&nbsp;&lt;01000&gt;,&nbsp;SQL&nbsp;Message&nbsp;&lt;3211&gt;&lt;[Microsoft][SQL&nbsp;Server&nbsp;Native&nbsp;Client&nbsp;11.0][SQL&nbsp;Server]30&nbsp;percent&nbsp;processed.&gt;.
Apr&nbsp;8,&nbsp;2019&nbsp;6:30:33&nbsp;PM&nbsp;-&nbsp;Info&nbsp;dbclient&nbsp;(pid=5324)&nbsp;INF&nbsp;-&nbsp;ODBC&nbsp;return&nbsp;code&nbsp;&lt;2&gt;,&nbsp;SQL&nbsp;State&nbsp;&lt;01000&gt;,&nbsp;SQL&nbsp;Message&nbsp;&lt;3211&gt;&lt;[Microsoft][SQL&nbsp;Server&nbsp;Native&nbsp;Client&nbsp;11.0][SQL&nbsp;Server]40&nbsp;percent&nbsp;processed.&gt;.
Apr&nbsp;8,&nbsp;2019&nbsp;8:05:33&nbsp;PM&nbsp;-&nbsp;Info&nbsp;dbclient&nbsp;(pid=5324)&nbsp;INF&nbsp;-&nbsp;ODBC&nbsp;return&nbsp;code&nbsp;&lt;2&gt;,&nbsp;SQL&nbsp;State&nbsp;&lt;01000&gt;,&nbsp;SQL&nbsp;Message&nbsp;&lt;3211&gt;&lt;[Microsoft][SQL&nbsp;Server&nbsp;Native&nbsp;Client&nbsp;11.0][SQL&nbsp;Server]50&nbsp;percent&nbsp;processed.&gt;.
Apr&nbsp;8,&nbsp;2019&nbsp;8:51:49&nbsp;PM&nbsp;-&nbsp;Info&nbsp;dbclient&nbsp;(pid=5324)&nbsp;INF&nbsp;-&nbsp;ODBC&nbsp;return&nbsp;code&nbsp;&lt;2&gt;,&nbsp;SQL&nbsp;State&nbsp;&lt;01000&gt;,&nbsp;SQL&nbsp;Message&nbsp;&lt;3211&gt;&lt;[Microsoft][SQL&nbsp;Server&nbsp;Native&nbsp;Client&nbsp;11.0][SQL&nbsp;Server]60&nbsp;percent&nbsp;processed.&gt;.
Apr&nbsp;8,&nbsp;2019&nbsp;10:02:46&nbsp;PM&nbsp;-&nbsp;Info&nbsp;dbclient&nbsp;(pid=5324)&nbsp;INF&nbsp;-&nbsp;ODBC&nbsp;return&nbsp;code&nbsp;&lt;2&gt;,&nbsp;SQL&nbsp;State&nbsp;&lt;01000&gt;,&nbsp;SQL&nbsp;Message&nbsp;&lt;3211&gt;&lt;[Microsoft][SQL&nbsp;Server&nbsp;Native&nbsp;Client&nbsp;11.0][SQL&nbsp;Server]70&nbsp;percent&nbsp;processed.&gt;.
Apr&nbsp;8,&nbsp;2019&nbsp;11:00:46&nbsp;PM&nbsp;-&nbsp;Info&nbsp;dbclient&nbsp;(pid=5324)&nbsp;INF&nbsp;-&nbsp;ODBC&nbsp;return&nbsp;code&nbsp;&lt;2&gt;,&nbsp;SQL&nbsp;State&nbsp;&lt;01000&gt;,&nbsp;SQL&nbsp;Message&nbsp;&lt;3211&gt;&lt;[Microsoft][SQL&nbsp;Server&nbsp;Native&nbsp;Client&nbsp;11.0][SQL&nbsp;Server]80&nbsp;percent&nbsp;processed.&gt;.
Apr&nbsp;9,&nbsp;2019&nbsp;12:06:15&nbsp;AM&nbsp;-&nbsp;Info&nbsp;dbclient&nbsp;(pid=5324)&nbsp;INF&nbsp;-&nbsp;ODBC&nbsp;return&nbsp;code&nbsp;&lt;2&gt;,&nbsp;SQL&nbsp;State&nbsp;&lt;01000&gt;,&nbsp;SQL&nbsp;Message&nbsp;&lt;3211&gt;&lt;[Microsoft][SQL&nbsp;Server&nbsp;Native&nbsp;Client&nbsp;11.0][SQL&nbsp;Server]90&nbsp;percent&nbsp;processed.&gt;.
Apr&nbsp;9,&nbsp;2019&nbsp;12:59:23&nbsp;AM&nbsp;-&nbsp;Info&nbsp;dbclient&nbsp;(pid=5324)&nbsp;ERR&nbsp;-&nbsp;Error&nbsp;in&nbsp;VxBSASendData:&nbsp;1.
Apr&nbsp;9,&nbsp;2019&nbsp;12:59:26&nbsp;AM&nbsp;-&nbsp;Info&nbsp;dbclient&nbsp;(pid=5324)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CONTINUATION:&nbsp;-&nbsp;All&nbsp;backup&nbsp;jobs&nbsp;have&nbsp;completed.
Apr&nbsp;9,&nbsp;2019&nbsp;12:59:28&nbsp;AM&nbsp;-&nbsp;Info&nbsp;dbclient&nbsp;(pid=5324)&nbsp;ERR&nbsp;-&nbsp;Internal&nbsp;error.&nbsp;See&nbsp;the&nbsp;dbclient&nbsp;log&nbsp;for&nbsp;more&nbsp;information.
Apr&nbsp;9,&nbsp;2019&nbsp;12:59:29&nbsp;AM&nbsp;-&nbsp;Info&nbsp;dbclient&nbsp;(pid=5324)&nbsp;DBMS&nbsp;MSG&nbsp;-&nbsp;ODBC&nbsp;return&nbsp;code&nbsp;&lt;-1&gt;,&nbsp;SQL&nbsp;State&nbsp;&lt;37000&gt;,&nbsp;SQL&nbsp;Message&nbsp;&lt;3202&gt;&lt;[Microsoft][SQL&nbsp;Server&nbsp;Native&nbsp;Client&nbsp;11.0][SQL&nbsp;Server]Write&nbsp;on&nbsp;"VNBU0-5324-10808-1554731024"&nbsp;failed:&nbsp;995(The&nbsp;I/O&nbsp;operation&nbsp;has&nbsp;been&nbsp;aborted&nbsp;because&nbsp;of&nbsp;either&nbsp;a&nbsp;thread&nbsp;exit&nbsp;or&nbsp;an&nbsp;application&nbsp;request.)&gt;.
Apr&nbsp;9,&nbsp;2019&nbsp;12:59:29&nbsp;AM&nbsp;-&nbsp;Info&nbsp;dbclient&nbsp;(pid=5324)&nbsp;ERR&nbsp;-&nbsp;Error&nbsp;in&nbsp;VxBSAGetServerError:&nbsp;6.
Apr&nbsp;9,&nbsp;2019&nbsp;12:59:30&nbsp;AM&nbsp;-&nbsp;Info&nbsp;dbclient&nbsp;(pid=5324)&nbsp;DBMS&nbsp;MSG&nbsp;-&nbsp;SQL&nbsp;Message&nbsp;&lt;3271&gt;&lt;[Microsoft][SQL&nbsp;Server&nbsp;Native&nbsp;Client&nbsp;11.0][SQL&nbsp;Server]A&nbsp;nonrecoverable&nbsp;I/O&nbsp;error&nbsp;occurred&nbsp;on&nbsp;file&nbsp;"VNBU0-5324-10808-1554731024:"&nbsp;995(The&nbsp;I/O&nbsp;operation&nbsp;has&nbsp;been&nbsp;aborted&nbsp;because&nbsp;of&nbsp;either&nbsp;a&nbsp;thread&nbsp;exit&nbsp;or&nbsp;an&nbsp;application&nbsp;request.).&gt;
Apr&nbsp;9,&nbsp;2019&nbsp;12:59:30&nbsp;AM&nbsp;-&nbsp;Info&nbsp;dbclient&nbsp;(pid=5324)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CONTINUATION:&nbsp;-&nbsp;The&nbsp;system&nbsp;cannot&nbsp;find&nbsp;the&nbsp;file&nbsp;specified.
Apr&nbsp;9,&nbsp;2019&nbsp;12:59:31&nbsp;AM&nbsp;-&nbsp;Info&nbsp;dbclient&nbsp;(pid=5324)&nbsp;DBMS&nbsp;MSG&nbsp;-&nbsp;SQL&nbsp;Message&nbsp;&lt;3013&gt;&lt;[Microsoft][SQL&nbsp;Server&nbsp;Native&nbsp;Client&nbsp;11.0][SQL&nbsp;Server]BACKUP&nbsp;DATABASE&nbsp;is&nbsp;terminating&nbsp;abnormally.&gt;
Apr&nbsp;9,&nbsp;2019&nbsp;12:59:31&nbsp;AM&nbsp;-&nbsp;Info&nbsp;dbclient&nbsp;(pid=5324)&nbsp;ERR&nbsp;-&nbsp;Error&nbsp;in&nbsp;VxBSAEndData:&nbsp;6.
Apr&nbsp;9,&nbsp;2019&nbsp;12:59:32&nbsp;AM&nbsp;-&nbsp;Info&nbsp;dbclient&nbsp;(pid=5324)&nbsp;ERR&nbsp;-&nbsp;Error&nbsp;found&nbsp;executing&nbsp;&lt;backup&nbsp;database&nbsp;"MontNikta"&nbsp;to&nbsp;VIRTUAL_DEVICE='VNBU0-5324-10808-1554731024'&nbsp;with&nbsp;&nbsp;stats&nbsp;=&nbsp;10,&nbsp;checksum,&nbsp;stop_on_error,&nbsp;blocksize&nbsp;=&nbsp;65536,&nbsp;maxtransfersize&nbsp;=&nbsp;4194304,&nbsp;buffercount&nbsp;=&nbsp;2&gt;.
Apr&nbsp;9,&nbsp;2019&nbsp;12:59:32&nbsp;AM&nbsp;-&nbsp;Info&nbsp;dbclient&nbsp;(pid=5324)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;CONTINUATION:&nbsp;-&nbsp;The&nbsp;handle&nbsp;used&nbsp;to&nbsp;associate&nbsp;this&nbsp;call&nbsp;with&nbsp;a&nbsp;previous&nbsp;VxBSAInit()&nbsp;call&nbsp;is&nbsp;invalid.
Apr&nbsp;9,&nbsp;2019&nbsp;12:59:34&nbsp;AM&nbsp;-&nbsp;Info&nbsp;dbclient&nbsp;(pid=5324)&nbsp;INF&nbsp;-&nbsp;OPERATION&nbsp;#1&nbsp;of&nbsp;batch&nbsp;__16_43_31_830_00.bch&nbsp;FAILED&nbsp;with&nbsp;STATUS&nbsp;1&nbsp;(0&nbsp;is&nbsp;normal).&nbsp;Elapsed&nbsp;time&nbsp;=&nbsp;29753(29753)&nbsp;seconds.
Apr&nbsp;9,&nbsp;2019&nbsp;12:59:38&nbsp;AM&nbsp;-&nbsp;Info&nbsp;dbclient&nbsp;(pid=5324)&nbsp;INF&nbsp;-&nbsp;Results&nbsp;of&nbsp;executing&nbsp;&lt;__16_43_31_830_00.bch&gt;:&nbsp;
Apr&nbsp;9,&nbsp;2019&nbsp;12:59:38&nbsp;AM&nbsp;-&nbsp;Info&nbsp;dbclient&nbsp;(pid=5324)&nbsp;&lt;0&gt;&nbsp;operations&nbsp;succeeded.&nbsp;&lt;1&gt;&nbsp;operations&nbsp;failed.
Apr&nbsp;9,&nbsp;2019&nbsp;12:59:41&nbsp;AM&nbsp;-&nbsp;Info&nbsp;dbclient&nbsp;(pid=5324)&nbsp;INF&nbsp;-&nbsp;The&nbsp;following&nbsp;object(s)&nbsp;were&nbsp;not&nbsp;backed&nbsp;up&nbsp;successfully.
Apr&nbsp;9,&nbsp;2019&nbsp;12:59:43&nbsp;AM&nbsp;-&nbsp;Info&nbsp;dbclient&nbsp;(pid=5324)&nbsp;INF&nbsp;-&nbsp;MontNikta
Apr&nbsp;9,&nbsp;2019&nbsp;12:59:46&nbsp;AM&nbsp;-&nbsp;Error&nbsp;bpbrm&nbsp;(pid=4992)&nbsp;from&nbsp;client&nbsp;nikta-sql.dom.ru:&nbsp;ERR&nbsp;-&nbsp;exit&nbsp;status:&nbsp;&lt;2&gt;
Apr&nbsp;9,&nbsp;2019&nbsp;12:59:46&nbsp;AM&nbsp;-&nbsp;Error&nbsp;bpbrm&nbsp;(pid=4992)&nbsp;from&nbsp;client&nbsp;nikta-sql.dom.ru:&nbsp;ERR&nbsp;-&nbsp;bphdb&nbsp;exit&nbsp;status&nbsp;=&nbsp;2:&nbsp;none&nbsp;of&nbsp;the&nbsp;requested&nbsp;files&nbsp;were&nbsp;backed&nbsp;up
Apr&nbsp;9,&nbsp;2019&nbsp;12:59:47&nbsp;AM&nbsp;-&nbsp;Info&nbsp;bphdb&nbsp;(pid=11096)&nbsp;done.&nbsp;status:&nbsp;2:&nbsp;none&nbsp;of&nbsp;the&nbsp;requested&nbsp;files&nbsp;were&nbsp;backed&nbsp;up
Apr&nbsp;9,&nbsp;2019&nbsp;12:59:47&nbsp;AM&nbsp;-&nbsp;end&nbsp;writing
none&nbsp;of&nbsp;the&nbsp;requested&nbsp;files&nbsp;were&nbsp;backed&nbsp;up&nbsp; (2)Job 3:Apr&nbsp;8,&nbsp;2019&nbsp;4:43:50&nbsp;PM&nbsp;-&nbsp;Info&nbsp;bpbrm&nbsp;(pid=1660)&nbsp;nikta-sql-n2.dom.ru&nbsp;is&nbsp;the&nbsp;host&nbsp;to&nbsp;backup&nbsp;data&nbsp;from
Apr&nbsp;8,&nbsp;2019&nbsp;4:43:50&nbsp;PM&nbsp;-&nbsp;Info&nbsp;bpbrm&nbsp;(pid=1660)&nbsp;reading&nbsp;file&nbsp;list&nbsp;for&nbsp;client
Apr&nbsp;8,&nbsp;2019&nbsp;4:43:51&nbsp;PM&nbsp;-&nbsp;Info&nbsp;bpbrm&nbsp;(pid=1660)&nbsp;listening&nbsp;for&nbsp;client&nbsp;connection
Apr&nbsp;8,&nbsp;2019&nbsp;4:43:52&nbsp;PM&nbsp;-&nbsp;Info&nbsp;bpbrm&nbsp;(pid=1660)&nbsp;INF&nbsp;-&nbsp;Client&nbsp;read&nbsp;timeout&nbsp;=&nbsp;900
Apr&nbsp;8,&nbsp;2019&nbsp;4:43:52&nbsp;PM&nbsp;-&nbsp;Info&nbsp;bpbrm&nbsp;(pid=1660)&nbsp;accepted&nbsp;connection&nbsp;from&nbsp;client
Apr&nbsp;8,&nbsp;2019&nbsp;4:43:52&nbsp;PM&nbsp;-&nbsp;Info&nbsp;dbclient&nbsp;(pid=5324)&nbsp;Backup&nbsp;started
Apr&nbsp;8,&nbsp;2019&nbsp;4:43:52&nbsp;PM&nbsp;-&nbsp;Info&nbsp;bptm&nbsp;(pid=2296)&nbsp;start
Apr&nbsp;8,&nbsp;2019&nbsp;4:43:52&nbsp;PM&nbsp;-&nbsp;Info&nbsp;bptm&nbsp;(pid=2296)&nbsp;using&nbsp;262144&nbsp;data&nbsp;buffer&nbsp;size
Apr&nbsp;8,&nbsp;2019&nbsp;4:43:53&nbsp;PM&nbsp;-&nbsp;Info&nbsp;bptm&nbsp;(pid=2296)&nbsp;setting&nbsp;receive&nbsp;network&nbsp;buffer&nbsp;to&nbsp;1049600&nbsp;bytes
Apr&nbsp;8,&nbsp;2019&nbsp;4:43:53&nbsp;PM&nbsp;-&nbsp;Info&nbsp;bptm&nbsp;(pid=2296)&nbsp;using&nbsp;30&nbsp;data&nbsp;buffers
Apr&nbsp;8,&nbsp;2019&nbsp;4:43:54&nbsp;PM&nbsp;-&nbsp;Info&nbsp;bptm&nbsp;(pid=2296)&nbsp;start&nbsp;backup
Apr&nbsp;8,&nbsp;2019&nbsp;4:43:55&nbsp;PM&nbsp;-&nbsp;Info&nbsp;nbjm&nbsp;(pid=6452)&nbsp;starting&nbsp;backup&nbsp;job&nbsp;(jobid=8013187)&nbsp;for&nbsp;client&nbsp;nikta-sql-n2.dom.ru,&nbsp;policy&nbsp;NIKTA-DBs,&nbsp;schedule&nbsp;Weekly
Apr&nbsp;8,&nbsp;2019&nbsp;4:43:55&nbsp;PM&nbsp;-&nbsp;Info&nbsp;nbjm&nbsp;(pid=6452)&nbsp;requesting&nbsp;STANDARD_RESOURCE&nbsp;resources&nbsp;from&nbsp;RB&nbsp;for&nbsp;backup&nbsp;job&nbsp;(jobid=8013187,&nbsp;request&nbsp;id:{8770D3B7-7E05-466C-B93B-F8BA9EC73500})
Apr&nbsp;8,&nbsp;2019&nbsp;4:43:55&nbsp;PM&nbsp;-&nbsp;requesting&nbsp;resource&nbsp;&nbsp;DiskStorage-1
Apr&nbsp;8,&nbsp;2019&nbsp;4:43:55&nbsp;PM&nbsp;-&nbsp;requesting&nbsp;resource&nbsp;&nbsp;srv-snbu01.dom.ru.NBU_CLIENT.MAXJOBS.nikta-sql-n2.dom.ru
Apr&nbsp;8,&nbsp;2019&nbsp;4:43:55&nbsp;PM&nbsp;-&nbsp;granted&nbsp;resource&nbsp;&nbsp;srv-snbu01.dom.ru.NBU_CLIENT.MAXJOBS.nikta-sql-n2.dom.ru
Apr&nbsp;8,&nbsp;2019&nbsp;4:43:55&nbsp;PM&nbsp;-&nbsp;granted&nbsp;resource&nbsp;&nbsp;MediaID=@aaaa6;DiskVolume=PureDiskVolume;DiskPool=DDUPool-01;Path=PureDiskVolume;StorageServer=srv-snbu08.dom.ru;MediaServer=srv-snbu02.dom.ru
Apr&nbsp;8,&nbsp;2019&nbsp;4:43:55&nbsp;PM&nbsp;-&nbsp;granted&nbsp;resource&nbsp;&nbsp;DiskStorage-1
Apr&nbsp;8,&nbsp;2019&nbsp;4:43:55&nbsp;PM&nbsp;-&nbsp;estimated&nbsp;0&nbsp;kbytes&nbsp;needed
Apr&nbsp;8,&nbsp;2019&nbsp;4:43:55&nbsp;PM&nbsp;-&nbsp;Info&nbsp;nbjm&nbsp;(pid=6452)&nbsp;started&nbsp;backup&nbsp;(backupid=nikta-sql-clr.dom.ru_1554731035)&nbsp;job&nbsp;for&nbsp;client&nbsp;nikta-sql-n2.dom.ru,&nbsp;policy&nbsp;NIKTA-DBs,&nbsp;schedule&nbsp;Weekly&nbsp;on&nbsp;storage&nbsp;unit&nbsp;DiskStorage-1
Apr&nbsp;8,&nbsp;2019&nbsp;4:43:57&nbsp;PM&nbsp;-&nbsp;started&nbsp;process&nbsp;bpbrm&nbsp;(pid=1660)
Apr&nbsp;8,&nbsp;2019&nbsp;4:43:58&nbsp;PM&nbsp;-&nbsp;connecting
Apr&nbsp;8,&nbsp;2019&nbsp;4:44:00&nbsp;PM&nbsp;-&nbsp;connected;&nbsp;connect&nbsp;time:&nbsp;0:00:00
Apr&nbsp;8,&nbsp;2019&nbsp;4:44:01&nbsp;PM&nbsp;-&nbsp;Info&nbsp;bptm&nbsp;(pid=2296)&nbsp;backup&nbsp;child&nbsp;process&nbsp;is&nbsp;pid&nbsp;6588.8124
Apr&nbsp;8,&nbsp;2019&nbsp;4:44:01&nbsp;PM&nbsp;-&nbsp;Info&nbsp;bptm&nbsp;(pid=6588)&nbsp;start
Apr&nbsp;8,&nbsp;2019&nbsp;4:44:09&nbsp;PM&nbsp;-&nbsp;begin&nbsp;writing
Apr&nbsp;9,&nbsp;2019&nbsp;12:58:45&nbsp;AM&nbsp;-&nbsp;Info&nbsp;dbclient&nbsp;(pid=5324)&nbsp;done.&nbsp;status:&nbsp;41:&nbsp;network&nbsp;connection&nbsp;timed&nbsp;out
Apr&nbsp;9,&nbsp;2019&nbsp;12:58:55&nbsp;AM&nbsp;-&nbsp;end&nbsp;writing;&nbsp;write&nbsp;time:&nbsp;8:14:46
network&nbsp;connection&nbsp;timed&nbsp;out&nbsp; (41)dbclient in&nbsp;attachment

Forum Discussion

ERR - exit status: <2> <41>

Related Content

Re: sql backups are partially successful

Re: question about the type of jobs 22 and 28

problem with upgrading remote and locally the be agent to 14.2 (log attached) FATAL ERROR 1714

Problem in backup Virtual Machine Hyper V - the backup failed to back up the requested files(6)

Re: STATUS CODE: 6 " the backup failed to back up the requested files"