NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

NetBackup status code: 313

NetBackup status code : 313
HOWTO104225 | 2014-11-20
How To | CMS-XML

Catalog backup fails with STATUS CODE: 35

13:26:03.310 [13971] 2 exec_catalog_dr_protection: Sending DR image info via email 13:26:03. 313 [13971] 4 db_dr_generate_report: ? 13:26:03.356 [13971] 4 db_dr_send_report: ?
TECH191339 | 2013-04-25
Technical Solutions | CMS-XML

Query based VMware Backup using Calendar schedule may fail with Status: 196 (client backup was not attempted because backup window closed)

6/1/2012 00:18:47.771 [CompoundJob::shouldStartChildJob] (ID:000000000205ee10 CTX:000000000207ccd8) Will not run stream 313 (vmclient01.test.com) because it falls outside of the child start window of 0:20:00 (1200)(CompoundJob.cpp:932)
TECH190338 | 2012-09-24
Technical Solutions | CMS-XML

Shadow Copy Components backup finishes Status 1

9:13:32. 313 AM: [6980.6584] 2 ov_log::v_globallogex: ERR - beds_ss_access::v_openforread(): fs_openobj() Failed! (0xe000fedd:A failure occurred accessing the object list.
TECH150097 | 2012-09-04
Technical Solutions | CMS-XML

Intermittent status 25 during backups after upgrading media servers to NetBackup 7.1

23:30:28.707 [7429] 2 bpbrm multiplexed_backup: calling read_media_msg for DATASOCKET. 23:30:30. 313 [7429] 2 bpbrm read_media_msg: read from media manager: ncb_datasocket myclient_1332646226 /tmp/vnet-25305332646230239218000000001-fjaibx ;1ae04168899fb3196aa9ba5f8d4d6665;10;3600
TECH185997 | 2012-07-02
Technical Solutions | CMS-XML

Oracle RMAN backups with Oracle metadata collection fail with status 26 and status 1.

However, the value for the log_archive_format is expected to be unique, so that insertion is attempted and will fail with sql error 2007072 due to being a duplicate. 15:44:24. 313 dars 363 [getNBUname] 41e4b940: getNBUname: returning log_archive_format
TECH170966 | 2012-01-04
Technical Solutions | CMS-XML

For a status 48, how to identify the hostname and host that cannot resolve it.

14:59:38.141 [6056.5828] 2 hosts_equal: gethostbyname failed for GUIclient: No such host is known ...snip... 14:59:38. 313 [6056.5828] 2 bpbrm copy_rename_file: params: GUIclient GUIclient
TECH142526 | 2010-10-22
Technical Solutions | CMS-XML

GENERAL ERROR: VMWare Consolidated Backup type 2 or 3 backups fail to index files level information, but the VMDK backup is successful.

4:21:23.219 PM: [5496.5968] 2 tar_base::v_vtarmsgw: INF - FIML initialize 4:21:23. 313 PM: [5496.5968] 2 tar_base::v_vtarmsgw: INF - VxMS error - severity 2. 4:21:23.313 PM: [5496.5968] 2 tar_base::v_vtarmsgw: INF - VxMS Error message 1 = vf_newpgn: couldn t initialize libohrestore.dll
TECH66536 | 2010-01-08
Technical Solutions | CMS-XML

BUG REPORT: Jobs error out with status code 196 due to Enterprise Media Manager (EMM) refusing connections

04/05/08 00:23:04. 313 [Debug] NB 51216 nbemm 111 PID:3730 TID:15 File ID:111 [No
TECH60366 | 2009-01-31
Technical Solutions | CMS-XML

GENERAL ERROR: When performing Active Directory Granular Backups, the name of the media server is decided by the name configured in NetBackup Enterprise Media Manager Server(EMM)

EVIDENCE nbfsd log on the client: 14:18:50. 313 [3780.3784] 2 logparams: C:\Program Files\Veritas\NetBackup\bin\nbfs mount -server mediaserver1 -port 7394 -cred 997a88abe90a99e64ee871814a5db2f9b9ef9d504d664cc748a46baf02afd461535144bf95a747e3dc0269bef4152a9ca46494c3ab3435505148a6eb8a196ab6 *
TECH73149 | 2009-01-08
Technical Solutions | CMS-XML

BUG REPORT: Intermittent 83 errors using NetBackup Key Management Service (KMS)

22:37:56.309 [29676] 2 TAO: TAO (29676|1) created new ORB kmslib 22:37:56. 313 [29676] 2 TAO: PBXIOP (29676|1) pbxiop_acceptor::open_i() trying to listen on port 1556 22:37:56.377 [29676] 2 TAO: PBXIOP (29676|1) pbxiop_acceptor::open_i cannot open acceptor in port range (1556,1557)- : No such file or directory
TECH73324 | 2009-01-10
Technical Solutions | CMS-XML

The status code 58 Can’t connect to client | Symantec Connect

The status code 58 Can’t connect to client 02:00:04.312 [24252] <2> vnet_async_connect: vnet_vnetd.c.3812: ran out of time before connect: 302 0x0000012e 02:00:04. 313 [24252] <2> vnet_connect_to_service_or_vnetd: vnet_vnetd.c.3571: vnet_async_connect failed: 18 0x00000012 02:00:04.313 [24252] <2> nb_connect_to_vnetd_or_legacy: comm.c.2030: vnet_connect_to_vnetd_or_service failed: 18
Connect Forums | HTML

Backup failing with Error code 23 on Solaris client NBU version 6.5.6 | Symantec Connect

01:13:28.261 [11631] <2> bpcd main: Not using VxSS authentication with alnnisnb01-bu 01:13:28. 313 [11631] <2> bpcd main: bpcd_get_version_rqst 01:13:28.383 [11631] <2> bpcd main: bpcd_get_version_rqst
Connect Forums | HTML

Backup failing with status 59 | Symantec Connect

Backup failing with status 59 16:28:07. 313 [25373] <2> do_pbx_service: ../../libvlibs/vnet_connect.c.1776: 0: via PBX: VNETD CONNECT FROM 10.207.80.10.54091 TO 10.203.2.44.1556 fd = 4
Connect Forums | HTML

NDMP bakup failing with status 99 | Symantec Connect

14:37:50. 313 [4665] <2> db_end: Need to collect reply 14:37:54.900 [4665] <2> ConnectionCache::connectAndCache: Acquiring new connection for host ampsnbma, query type 78 14:37:54.904 [4665] <2> vnet_pbxconnect: pbxConnectEx Succeeded
Connect Forums | HTML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?