NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

NetBackup status code: 120

NetBackup status code : 120
HOWTO90541 | 2013-10-02
How To | CMS-XML

NetBackup status code: 120

NetBackup status code : 120
HOWTO50889 | 2012-11-19
How To | CMS-XML

NetBackup status code: 120

NetBackup status code : 120
HOWTO34999 | 2010-10-29
How To | CMS-XML

A backup of a large DFSR data set intermittently finishes with Status 1

Volume Shadow Copy Error : VSS spent more than 120 seconds trying to open and flush all the volumes in the shadow-copy set. This caused volume \\?\Volume{a19dca72-d24e-42d3-9eee-6917105b3047}\ to timeout waiting for the hold-writes phase of shadow-copy creation. Trying again when disk activity is lower may solve this problem.
TECH225512 | 2014-10-20
Technical Solutions | CMS-XML

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

17:48:36 .611 [2368.4288] 2 vnet_sock_ready: ... 0: max_time: 120 0x00000078
TECH162303 | 2014-04-09
Technical Solutions | CMS-XML

Oracle backup failing with status 6, RMAN error shows ora-27206: requested file not found in media management catalog

oracle_client.mydomain.com 10.162.25. 120 10.162.25.120
TECH146739 | 2013-11-12
Technical Solutions | CMS-XML

AIR replications succeed in one direction but not the other - Status 84

pdvfs_lib_log: Connecting to webservice using SSL. pdvfs_lib_log: First CURL call (res: 0, default r_timeout: 120 ) pdvfs_lib_log: No events, returning cr_end.
TECH211825 | 2013-10-23
Technical Solutions | CMS-XML

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

14:22:34.764 [12439640] 2 vnet_sock_ready: vnet.c.507: max_time: 120 0x00000078 14:22:34.764 [12439640] 2 vnet_sock_ready: vnet.c.508: sock: 5 0x00000005
TECH129303 | 2013-10-24
Technical Solutions | CMS-XML

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

23:33:27.278 [16458] 2 set_job_details: Tfile (8768177): LOG 1332646232 4 bpbrm 7429 sending bpsched msg: CONNECTING TO CLIENT FOR myclient_1332646226 During that time, bptm child suffered a 120 second timeout because the client process did not connect to the remote end of the vnetd forwarding socket. The child returned status 25 to the parent and to bpbrm.
TECH185997 | 2012-07-02
Technical Solutions | CMS-XML

NetBackup Catalog Recovery fails with a status 2850.

13:04:54.665 [4720.2168] 2 start_indep_grp: (pid 114) start_mpx_group returned 254 13:04:54.665 [4720.2168] 2 wait_for_new_restore_msg: Wait up to 120 seconds for new restore msg The status 254 is then translated to a 2850:
TECH191623 | 2012-06-25
Technical Solutions | CMS-XML

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

12:28:53. 120 [19881] 4 rebuild_db: Exiting. rc = 77
TECH191598 | 2012-06-25
Technical Solutions | CMS-XML

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

Thus the file list will be received before the media/mpx socket is created and the socket will not have a chance to timeout. C) It may also be possible to review and alleviate the processing or network stack bottleneck on the master/mm server host that is causing it to take more than 120 seconds to pass the file list between processes on the same host. Keep in mind that if the file list grows longer over time, it will eventually exceed the timeout again.
TECH168191 | 2011-08-26
Technical Solutions | CMS-XML

A NetBackup Master/Media Server or NetBackup Media Server, running Microsoft Cluster Server (MSCS), freezes after displaying an error - “desktop heap exhausted”

20 backup jobs that includes 100+ clients. This translates to a maximum of 120 - 180 Netbackup processes running during peak backup activity. With the BMR option enabled in the backup policies, within hours the list of active processes goes beyond 1000 causing the server to either freeze or fail-over.
TECH145367 | 2011-08-15
Technical Solutions | CMS-XML

ACS(0) Unable to obtain Query Server sequence 0 acknowledge response, ACS status = 104, status_ni_failure

Jan 12 12:49:28 hostname acsd[2003]: ACS(0) unavailable: initialization failed: Unable to initialize robot Jan 12 12:51:38 hostname acsd[27271]: ACS(0) Unable to obtain Query Server sequence 120 acknowledge response, ACS status = 104, status_ni_failure Jan 12 12:51:38 hostname acsd[2003]: DecodeQuery() Actual status: Unable to initialize robot
TECH150014 | 2011-08-29
Technical Solutions | CMS-XML

BUG REPORT: The Netbackup process "NBPEM" intermittently hangs, all active operations fail and exit with status 50.

12/10/2010 02:45:13.525 [Debug] NB 51216 nbpem 116 PID:21688 TID:3 File ID:116 [No context] 4 [PemCORBACall::invokeCall] [+++ STATE fc17ed10 +++] (ID:c88568) NOS::NOSping at PemCORBACall.cpp( 120 )
TECH143915 | 2011-07-14
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?