NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

NetBackup status code: 312

NetBackup status code : 312
HOWTO90721 | 2013-10-02
How To | CMS-XML

NetBackup status code: 312

NetBackup status code : 312
HOWTO51069 | 2012-11-19
How To | CMS-XML

NetBackup status code: 312

NetBackup status code : 312
HOWTO35180 | 2010-10-29
How To | CMS-XML

NDMP restores fail with media error EXIT STATUS 85

11:35:47.282 [4712.6328] 2 read_backup: using 32 data buffers 11:36:09.872 [4712.6328] 2 read_data: read short block, 312 bytes, sending to socket 11:36:10.059 [4712.6328] 2 bp_sts_read_image_non_512: adjusting offset or length to a 512 byte boundry
TECH214057 | 2014-02-24
Technical Solutions | CMS-XML

Backup of client behind firewall fails with status code 24 (socket write failed) despite port 13782 and 13724 being open.

Module: @(#) $Source: src/ncf/tfi/lib/Packer.cpp,v $ $Revision: 1.89 $ , Function: Packer::getBuffer(), Line: 656 Module: tar_tfi::getBuffer, Function: H:\7104\src\cl\clientpc\util\tar_tfi.cpp, Line: 312 Local Address: [::]:0
TECH202245 | 2013-12-02
Technical Solutions | CMS-XML

Exchange 2007 backup fails with status 40 "network connection broken"

2:38:35.508 PM: [5372.7320] 16 dtcp_write: TCP - failure: send socket ( 312 ) (TCP 10053: Software caused connection abort)
TECH75088 | 2013-10-24
Technical Solutions | CMS-XML

Backups of the same client using some media servers fail with status 21: socket open failed

14:22:38.330 [12439640] 2 vnet_pop_string: vnet.c.268: Function failed: 9 0x00000009 14:22:38.330 [12439640] 2 vnet_pop_signed: vnet.c. 312 : Function failed: 9 0x00000009 14:22:38.330 [12439640] 2 ProcessRequests: vnetd.c.298: vnet_pop_signed failed: 9 0x00000009
TECH129303 | 2013-10-24
Technical Solutions | CMS-XML

GENERAL ERROR: Exchange backups fail with Status Code 13 - 0xc7ff000d: A communications error occurred while attempting to perform a local backup.

10:47:23.000 PM: [800.765] 2 tar_base::v_vtarmsgw: WRN - wanted buffer size: 65536 10:50:17. 312 PM: [800.765] 2 tar_base::v_vtarmsgw: INF - EXIT STATUS 13: file read failed Additionally, in the Exchange server s Application Event log, the following is observed:
TECH38563 | 2013-10-23
Technical Solutions | CMS-XML

Shadow Copy Components backup finishes Status 1

0 File(s) 0 bytes 9 Dir(s) 12,952,461, 312 bytes free In this case, C:\Program Files\Veritas has been turned into a Junction Point pointing to F:\Veritas.
TECH177496 | 2013-09-06
Technical Solutions | CMS-XML

VMware backups failing with status 13: file read failed.

P1: bpbkar32.exe P2: 7.500. 312 .605 P3: 4fcec628
TECH199087 | 2013-03-11
Technical Solutions | CMS-XML

The "bpexpdate -deassignempty" command returns status code 97 after applying NetBackup version 7.5.0.3 or 7.5.0.4.

log bpexpdate start: 15:25:20. 312 [3948.5804] 2 bpexpdate: VERBOSE = 5 15:25:20.312 [3948.5804] 2 logparams: -deassignempty -force
TECH199730 | 2013-02-20
Technical Solutions | CMS-XML

Unable to receive email notification when a backup job fails with status 196 or status 800

2012/08/29 10:20:19. 312 [domailing] entered; status = 196(JobDefinition.cpp:2169)
TECH198543 | 2012-10-18
Technical Solutions | CMS-XML

Shadow Copy Components backup finishes Status 1

bin in brUtil::GenerateFileList 9:13:32. 312 AM: [6980.6584] 2 ov_log::v_globallog: INF - brUtil::SetObjectsList( ): Failed to apply the component exclusion list 9:13:32.312 AM: [6980.6584] 2 ov_log::v_globallog: INF - Status CODE (0x0000007b) generating Component System Files file list in SHADOW::OpenComponent
TECH150097 | 2012-09-04
Technical Solutions | CMS-XML

user-directed backup of thousands of files fails with status 21 or status 25 before the data transfer begins

15:27:50.859 [10276.5756] 2 bpbrm ... sending bpsched msg: CONNECTING TO CLIENT FOR myclient_1308320695 15:27:51. 312 [10276.5756] 2 logconnections: BPCD CONNECT FROM 2.2.2.2.60352
TECH168191 | 2011-08-26
Technical Solutions | CMS-XML

Many small jobs in a large MPX group may result in slow performance and status 13 or status 6

12:00:03.249 [22497] 2 logconnections: BPDBM CONNECT FROM 2.2.2.2.33301 TO 1.1.1.1.13724 12:00:04. 312 [22497] 2 logconnections: BPDBM CONNECT FROM 2.2.2.2.33303 TO 1.1.1.1.13724
TECH135606 | 2011-04-26
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?