NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

Media Manager status code 119

Media Manager status code 119
HOWTO90986 | 2013-10-02
How To | CMS-XML

Media Manager status code 119

Media Manager status code 119
HOWTO51335 | 2012-11-19
How To | CMS-XML

Media Manager status code: 119

Media Manager status code : 119
HOWTO35445 | 2010-10-29
How To | CMS-XML

VMWare Application State Capture backup fails with the following error: host is unreachable

6/26/2014 17:02:39.429 [Debug] NB 51216 ncfnbcs 366 PID:7068 TID:6752 File ID:366 [No context] 1 [NBCSConnection::connect] Could not connect to host : exchvm01.test.lab (../NBCSConnection.cpp: 119 )
TECH194457 | 2014-10-13
Technical Solutions | CMS-XML

Windows BMR client fails with status code 1, "Failed sending the discovery".

Master server oid= 119 bmrd log:
TECH192858 | 2014-01-16
Technical Solutions | CMS-XML

GENERAL ERROR: When the backup of a Linux client is initiated, the Bare Metal Restore (BMR) job (bmrsavecfg) fails with "Operation Status: 1" reported. Error v-128-18 can also be found in unified logs.

Obtain the bmrsavecfg (originator id 121) log from the client with debug level 5 and diagnostic level 6. Similarly, generate the bmrd (OID 119 ) log from the master.
TECH60242 | 2014-01-17
Technical Solutions | CMS-XML

Storage Lifecycle Policies fail with Status 190

12:21:35. 119 [10908.7792] 16 bpduplicate: INF - found no images or media matching the selection criteria
TECH185132 | 2013-09-16
Technical Solutions | CMS-XML

VMware backups failing with status 13: file read failed.

P4: nbuVmwareTools.dll P5: 5.0.12. 119 P6: 4f18edc6
TECH199087 | 2013-03-11
Technical Solutions | CMS-XML

Netbackup catalog restore fails with status 47 or 25

Just configuring media host override option correctly, indicating that master server will read the tape, will not solve the problem, the admin log will show how that master still tries to connect with media server: 17:45:16. 119 [496.5284] 2 vnet_connect_to_service_or_vnetd: vnet_vnetd.c.3570: 3570: vnet_async_connect failed: 18 0x00000012 17:45:16.119 [496.5284] 2 nb_connect_to_vnetd_or_legacy: comm.c.2030: vnet_connect_to_vnetd_or_service failed: 18
TECH70578 | 2012-08-18
Technical Solutions | CMS-XML

Vault Status 287:Tape Library is not ejecting its full capacity

15:44:18.309 [9240758] 5 tldcd:tld_main: TLD(0) closing/unlocking robotic path 15:44:18.318 [9240758] 2 TAO: ace_select_reactor_notify::notify [handle=8]: write to notification pipe handle failed: System call timed out ( 119 ) detail.log:
TECH172314 | 2012-07-28
Technical Solutions | CMS-XML

File backup failed with error code 13 when OS had unmounted NFS volume.

Error bpbrm socket read failed: errno = 119 - System call timed out
TECH180530 | 2012-07-28
Technical Solutions | CMS-XML

Catalog backups fail with status 2 - none of the requested files were backed up

#### HERE there is no log for 1.200 minutes #### 12:28:53. 119 [19881] 16 NBDBsystem: System call failed with status : 256 12:28:53.120 [19881] 16 rebuild_db: Error calling dbunload
TECH191598 | 2012-06-25
Technical Solutions | CMS-XML

Informix restore hangs and then fails with status 5 or 2826; socket read failed: errno = 62 - Timer expired

11:54:24.117 [5199] 2 bpbrm read_parent_msg: read from parent ack_keep_alive 11:54:24. 119 [5199] 2 bpbrm multiplexed_restore: bpbrm.c.16766: keep-alive acknowleged: 0 0 0x00000000 11:54:33.500 [5221] 16 bpbrm readline: socket read failed: errno = 62 - Timer expired
TECH177248 | 2011-12-20
Technical Solutions | CMS-XML

NDMP Remote backup results in Status 49 client did not start.

Nov 17 08:33:19 s807p1 netbackup[21382]: [ID 702911 daemon.error] OID: 119 :v-1-6 Unable to load configuration settings.
TECH146965 | 2011-09-23
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:59.827 [22497] 4 write_backup: successfully wrote backup id client4_1249905329, copy 1, 545 Kbytes 12:01:00. 119 [22497] 2 write_backup: waiting 10 seconds for start of another backup 12:01:34.778 [22497] 4 write_backup: successfully wrote backup id client2_1249905339, copy 1, 545 Kbytes
TECH135606 | 2011-04-26
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?