NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

NetBackup status code: 299

NetBackup status code : 299
HOWTO104211 | 2014-11-20
How To | CMS-XML

NetBackup status code: 142

09:36:48. 299 [527] 32 fs_dev_rt_check: FTL - snapshot method: nbu_snap abort - required VxFS dynamic linked libraries for NetBackup are not installed. Please visit the Symantec support website, and refer to Technote number 262225 for further information.
HOWTO104063 | 2014-11-20
How To | CMS-XML

Backups to WORM media in a MKS STU fail with status 83 during tape unmount on Windows

09:47:04. 299 [5978.7868] 16 io_open: cannot open file , The system cannot find the path specified. (3)
TECH223001 | 2014-07-17
Technical Solutions | CMS-XML

Ten second connection delays cause status 25 after upgrading mediaserver to NetBackup 7.1

...snip... 17:46:36. 299 [2368.4288] 2 ProcessRequests: ... 0: msg: Request vn_request_connect_forward_socket(10) 17:46:36.299 [2368.4288] 2 vnet_generate_hashes
TECH162303 | 2014-04-09
Technical Solutions | CMS-XML

Backup Error = WIN32 13: The data is invalid

Some files produce this error when getting backed up: bpbkar log snip: 6:00:08. 299 AM: [7668.6716] 2 tar_base::v_vtarmsgw: ERR - failure reading file: R:\datawarehouse\a\bigfile.abc (WIN32 13: The data is invalid.
TECH143884 | 2012-01-16
Technical Solutions | CMS-XML

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

22:37:56.298 [29676] 2 KMSCLIB::kmsGetKeyAndKad: Entering function....(KMSClib.cpp:583) 22:37:56. 299 [29676] 2 KMSCLIB::GetQueryableFacetInstance: Entering function....(KMSClib.cpp:207) 22:37:56.299 [29676] 2 KMSCLIB::InitOrb: Entering function....(KMSClib.cpp:158)
TECH73324 | 2009-01-10
Technical Solutions | CMS-XML

bpfis errors in problem report | Symantec Connect

13:55:02. 299 [1204.2348] <2> vnet_async_connect: ../../libvlibs/vnet_connect.c.1376: 0: getsockopt so_error returned: 10060 0x0000274c
Connect Forums | HTML

We are getting the Errors:When we click on Device Monitor error "invalid host name 136" | Symantec Connect

01:04:27.294 [19406] <4> uninitialize: (0) Destroying the orb 01:04:27. 299 [19406] <2> Orb::destroyOrb: orb has reference count: 0(Orb.cpp:1571) 01:04:27.299 [19406] <4> emmlib_uninitialize: (0) Successfully released EMM session and database objects
Connect Forums | HTML

File Read error on netbackup client 7.0 | Symantec Connect

07:58:37.279 [20840588] <4> is_excluded: Excluded /oracle/E8P/sapdata4 by exclud e_list entry /oracle*/*/sapdata*/ 07:58:37. 299 [20840588] <4> is_excluded: Excluded /oracle/E8P/sapdata5 by exclud e_list entry /oracle*/*/sapdata*/
Connect Forums | HTML

NDMP bakup failing with status 99 | Symantec Connect

14:39:23.389 [4665] <2> db_end: Need to collect reply 14:39:28.298 [4665] <2> ConnectionCache::connectAndCache: Acquiring new connection for host ampsnbma, query type 78 14:39:28. 299 [4665] <2> vnet_pbxconnect: pbxConnectEx Succeeded
Connect Forums | HTML

191 errors on Duplcation Jobs | Symantec Connect

21:25:07. 299 [3104.5212] <2> process_more_read_dup_images: Got bpduplicate acknowledgement status: 0, err: 0
Connect Forums | HTML

Status Code Chart

298 299 300
TECH58686 | 2014-02-18
Technical Solutions | CMS-XML

Error 1311.Source file not found when upgrading from NetBackup version 7.0 to version 7.1

Check the properties of the downloaded and extracted netbackup_7.1_win folder. Although it contains 238 Files, and 30 Folders the Size reported is only 1.90 GB (2,046, 299 ,206 bytes) Compare to the extracted netbackup_7.1_win folder on a working installation, which has a size of 2.24 GB
TECH168797 | 2011-10-11
Technical Solutions | CMS-XML

NetBackup messages

there is no available MAP for ejecting See NetBackup status code : 299 there was a conflicting specification
HOWTO103773 | 2014-11-20
How To | CMS-XML

NBDB fails to start after modifyinig the vxdbms.conf

14:10:26.298 [21888] 16 readvxdbms_conffile: Illegal configuration file: /u01/db/data/vxdbms.conf 14:10:26. 299 [21888] 16 nbdb_ping: Error reading vxdbms.conf 14:10:26.299 [21888] 4 nbdb_ping: Database [NBDB] is not available.
TECH141060 | 2013-08-28
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?