cancel
Showing results for 
Search instead for 
Did you mean: 

Error 12 and 14 , backups

Hi Tech,

Its been lot of trouble working with  2008 R2, and I see most of the Clients with policy Servers_Windows_SO been failing. 

is this related to snapshot issues , and does Volume Shadow Copy Component restart will fix it ?

Need advice.

Backupsets

Shadow Copy Components:\
C:\

 

Logs
03/16/2021 19:49:20 - Info nbjm (pid=6268) starting backup job (jobid=1752351) for client ClientName.MyCompany, policy Servers_Windows_SO, schedule Diario
03/16/2021 19:49:20 - Info nbjm (pid=6268) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=1752351, request id:{4941B982-1412-4167-BA2B-8CF2AC5D21E2})
03/16/2021 19:49:20 - requesting resource su_MediaServerA_dedup
03/16/2021 19:49:20 - requesting resource Master.myCompany.NBU_CLIENT.MAXJOBS.ClientName.MyCompany
03/16/2021 19:49:20 - requesting resource Master.myCompany.NBU_POLICY.MAXJOBS.Servers_Windows_SO
03/16/2021 19:49:20 - granted resource Master.myCompany.NBU_CLIENT.MAXJOBS.ClientName.MyCompany
03/16/2021 19:49:20 - granted resource Master.myCompany.NBU_POLICY.MAXJOBS.Servers_Windows_SO
03/16/2021 19:49:20 - granted resource MediaID=@aaaab;DiskVolume=PureDiskVolume;DiskPool=MediaServer.myCompany_dedup;Path=PureDiskVolume;StorageServer=MediaserverA.MyCompany;MediaServer=MediaserverA.MyCompany
03/16/2021 19:49:20 - granted resource su_MediaServerA_dedup
03/16/2021 19:49:20 - estimated 26123794 kbytes needed
03/16/2021 19:49:20 - begin Parent Job
03/16/2021 19:49:20 - begin Snapshot: Start Notify Script
03/16/2021 19:49:20 - Info RUNCMD (pid=11680) started
03/16/2021 19:49:20 - Info RUNCMD (pid=11680) exiting with status: 0
Operation Status: 0
03/16/2021 19:49:20 - end Snapshot: Start Notify Script; elapsed time 0:00:00
03/16/2021 19:49:20 - begin Snapshot: Step By Condition
Operation Status: 0
03/16/2021 19:49:20 - end Snapshot: Step By Condition; elapsed time 0:00:00
03/16/2021 19:49:20 - begin Snapshot: Stream Discovery
Operation Status: 0
03/16/2021 19:49:20 - end Snapshot: Stream Discovery; elapsed time 0:00:00
03/16/2021 19:49:20 - begin Snapshot: Bare Metal Restore Save
03/16/2021 19:49:21 - started process bpbrm (pid=2424)
03/16/2021 19:49:26 - collecting BMR information
03/16/2021 19:49:26 - connecting
03/16/2021 19:49:27 - connected; connect time: 0:00:00
03/16/2021 19:49:27 - transfering BMR information to the master server
03/16/2021 19:49:27 - connecting
03/16/2021 19:49:27 - connected; connect time: 0:00:00
03/16/2021 19:49:37 - BMR information transfer successful
03/16/2021 19:49:37 - Info bmrsavecfg (pid=0) done. status: 0: the requested operation was successfully completed
03/16/2021 19:49:37 - end writing
Operation Status: 0
03/16/2021 19:49:37 - end Snapshot: Bare Metal Restore Save; elapsed time 0:00:17
03/16/2021 19:49:37 - begin Snapshot: Read File List
Operation Status: 0
03/16/2021 19:49:37 - end Snapshot: Read File List; elapsed time 0:00:00
03/16/2021 19:49:37 - begin Snapshot: Create Snapshot
03/16/2021 19:49:38 - started process bpbrm (pid=9648)
03/16/2021 19:49:42 - Info bpbrm (pid=9648) ClientName.MyCompany is the host to backup data from
03/16/2021 19:49:42 - Info bpbrm (pid=9648) reading file list for client
03/16/2021 19:49:42 - Info bpbrm (pid=9648) start bpfis on client
03/16/2021 19:49:43 - Info bpbrm (pid=9648) Starting create snapshot processing
03/16/2021 19:49:45 - Info bpfis (pid=18196) Backup started
03/16/2021 19:49:55 - Info bpfis (pid=18196) done. status: 0
03/16/2021 19:49:55 - end Snapshot: Create Snapshot; elapsed time 0:00:18
03/16/2021 19:49:55 - Info bpfis (pid=18196) done. status: 0: the requested operation was successfully completed
03/16/2021 19:49:55 - end writing
Operation Status: 0
03/16/2021 19:49:55 - end Parent Job; elapsed time 0:00:35
03/16/2021 19:49:55 - Info nbjm (pid=6268) snapshotid=ClientName.MyCompany_1615934960
03/16/2021 19:49:55 - begin Snapshot: Policy Execution Manager Preprocessed
Operation Status: 12

03/16/2021 21:24:12 - end Snapshot: Policy Execution Manager Preprocessed; elapsed time 1:34:17
03/16/2021 21:24:12 - begin Snapshot: Stop On Error
Operation Status: 0
03/16/2021 21:24:12 - end Snapshot: Stop On Error; elapsed time 0:00:00
03/16/2021 21:24:12 - begin Snapshot: Delete Snapshot
03/16/2021 21:24:12 - end Snapshot: Delete Snapshot; elapsed time 0:00:00
03/16/2021 21:24:12 - begin Snapshot: End Notify Script
03/16/2021 21:24:12 - Info RUNCMD (pid=9332) started
03/16/2021 21:24:12 - Info RUNCMD (pid=9332) exiting with status: 0
Operation Status: 0
03/16/2021 21:24:12 - end Snapshot: End Notify Script; elapsed time 0:00:00
Operation Status: 12

03/17/2021 00:24:15 - Info bpbrm (pid=11252) Starting delete snapshot processing
03/17/2021 00:24:19 - Info bpfis (pid=7172) Backup started
03/17/2021 00:24:24 - Info bpfis (pid=7172) done. status: 0
03/17/2021 00:24:24 - Info bpfis (pid=7172) done. status: 0: the requested operation was successfully completed
file open failed (12)

 

bpbkar logs

22:50:27.567 [12748.8168] <2> tar_base::V_vTarMsgW: JBD - accelerator sent 1400777216 bytes out of 7116442112 bytes to server, optimization 80.3%
22:50:27.567 [12748.6184] <4> tar_base::keepaliveThread: INF - keepalive thread terminating (reason: WAIT_OBJECT_0)
22:50:27.567 [12748.8168] <4> tar_base::stopKeepaliveThread: INF - keepalive thread has exited. (reason: WAIT_OBJECT_0)
22:50:27.769 [12748.8168] <4> send_msg_to_monitor: INF - in send_msg_to_monitor()...
22:50:27.769 [12748.8168] <2> tar_base::V_vTarMsgW: INF - EXIT STATUS 12: file open failed
22:50:27.769 [12748.8168] <4> tar_backup::backup_done_state: INF - Not waiting for server status
22:50:27.769 [12748.8168] <4> dos_backup::fscp_fini: INF - backup status:<12>
22:50:27.769 [12748.8168] <4> dos_backup::fscp_fini: INF - checkpointed backup is not complete, keeping current tracklog
22:50:27.769 [12748.8168] <4> dos_backup::_change_journal_finalize: INF - finalizing change journal usage for file directive:<C:\> with backup status:<12>
22:50:27.769 [12748.8168] <2> NBJournalData::_update_journal_info_one: not writing journal info, the backup status:<12> for <C:\> is not successful
22:50:27.769 [12748.8168] <4> dos_backup::_change_journal_finalize: INF - finalizing change journal usage for guid:<\\?\Volume{59f85943-43f6-11e2-9020-806e6f6e6963}> <backup status=12>
22:50:27.769 [12748.8168] <2> NBJournalData::_update_journal_info_one: not writing journal info, the backup status:<12> for <C:\> is not successful
22:50:27.769 [12748.8168] <4> dos_backup::_change_journal_finalize: INF - finalizing change journal usage for guid:<\\?\Volume{164c879a-43bc-11e2-87b0-0050569e006f}> <backup status=12>
22:50:29.033 [12748.8168] <4> OVStopCmd: INF - EXIT - status = 0
22:50:29.033 [12748.8168] <2> tar_base::V_Close: closing...
22:50:29.033 [12748.8168] <4> dos_backup::tfs_reset: INF - Snapshot deletion start
22:50:29.033 [12748.8168] <4> V_Snapshot::V_Snapshot_Destroy: INF - No snapshot ID, snapshot destruction failed
22:50:41.404 [12748.8168] <2> ov_log::V_GlobalLog: INF - BEDS_Term(): enter - InitFlags:0x00000101
22:50:41.404 [12748.8168] <2> ov_log::V_GlobalLog: INF - BEDS_Term(): ubs specifics: 0x001d0000
22:50:42.012 [12748.8168] <16> dtcp_read: TCP - failure: recv socket (460) (TCP 10053: Software caused connection abort)
22:50:43.026 [12748.8168] <16> dtcp_read: TCP - failure: recv socket (460) (TCP 10053: Software caused connection abort)
22:50:44.040 [12748.8168] <16> dtcp_read: TCP - failure: recv socket (460) (TCP 10053: Software caused connection abort)
22:50:45.054 [12748.8168] <16> dtcp_read: TCP - failure: recv socket (460) (TCP 10053: Software caused connection abort)

1 Solution

Accepted Solutions
Accepted Solution!

Re: Error 12 and 14 , backups

@RaviNS 

I have a lot of sympathy seeing that you are battling with aging environment - the OS and NBU versions are longer supported by Microsoft or Veritas.
This means that you are basically on your own as far as troubleshooting is concerned.

To troubleshoot snapshot issues, you need to enable bpfis logging as well, check Windows Event Viewer logs and use commands such as
vssadmin list providers
vssadmin list writers

One more thing : please copy logs to a .txt file (e.g. bpbkar.txt) and upload as attachment.
We need full logs to assist with troubleshooting as log snippets do not help to see what lead to the error.

View solution in original post

2 Replies
Accepted Solution!

Re: Error 12 and 14 , backups

@RaviNS 

I have a lot of sympathy seeing that you are battling with aging environment - the OS and NBU versions are longer supported by Microsoft or Veritas.
This means that you are basically on your own as far as troubleshooting is concerned.

To troubleshoot snapshot issues, you need to enable bpfis logging as well, check Windows Event Viewer logs and use commands such as
vssadmin list providers
vssadmin list writers

One more thing : please copy logs to a .txt file (e.g. bpbkar.txt) and upload as attachment.
We need full logs to assist with troubleshooting as log snippets do not help to see what lead to the error.

View solution in original post

Re: Error 12 and 14 , backups

Thank you Marriane , Helping us over the years 

Restarting VSS , WMI and Com services did work as usual