NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

NetBackup status code: 1556

NetBackup status code : 1556
HOWTO91720 | 2013-10-02
How To | CMS-XML

NetBackup status code: 1556

NetBackup status code : 1556
HOWTO73045 | 2012-11-19
How To | CMS-XML

OpsCenter Error Messages

Make sure NetBackup host is reachable from OpsCenter and vice-a-versa via ping command. Also check if NBSL service on NetBackup Master is running. And if firewall is configured, check TCP port 1556 is opened on OpsCenter and NetBackup machine.
HOWTO88035 | 2013-09-30
How To | CMS-XML

OpsCenter Error Messages added in 7.5

Make sure NetBackup host is reachable from OpsCenter and vice-a-versa via ping command. Also check if NBSL service on NetBackup Master is running. And if firewall is configured, check TCP port 1556 is opened on OpsCenter and NetBackup machine.
HOWTO71918 | 2012-02-08
How To | CMS-XML

DOCUMENTATION: How to troubleshoot and correct problems with media servers when the status changes in the Media Servers area of the NetBackup Administration GUI.

13:29:10.179 [14608.19392] 4 ValidateConnectionID: (-) Created new Connection ID 0 13:29:10.179 [14608.19392] 2 emmlib_initializeex: (-) Connecting to the Server mastclust Port 1556 The connect back was made to the sending IP address, which is the IP associated with mastnode2
TECH69625 | 2009-01-15
Technical Solutions | CMS-XML

Restore of a large VMware virtual machine may fail with status 5/2817/2820 due to VM creation timing out after 2 hours

02:42:46.843 [5900.1860] 2 logconnections: BPCD CONNECT FROM 10.185.10.145.2898 TO 10.185.10.146. 1556 fd = 1344
TECH171837 | 2014-10-07
Technical Solutions | CMS-XML

Oracle RMAN restore fails with status 2801 when starting Client Direct job from the GUI

3.3.3.3.29432 TO 1.1.1.1. 1556 fd = 13
TECH225059 | 2014-09-29
Technical Solutions | CMS-XML

Accessing Vault Management via Java Console after upgrading NetBackup to version 7.6.0.2 or 7.6.0.3 generates error message “Access Denied. You do not have permission to perform this operation or access this resource.”

An error message similar to the following may appear Java GUI log located in install_path Veritas\NetBackup\logs\user_ops\nbjlogs [03-07-2014 16:34:05:499] pbxiop:INFO: createSocket - Trying to connect to nbmaster: 1556 :nbvault [03-07-2014 16:34:05:499] pbxiop:INFO: Connected to exchange at:nbmaster:1556:nbvault
TECH218104 | 2014-09-11
Technical Solutions | CMS-XML

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

Opening the PBX port ( 1556 ) through the firewall - bidirectional - between all NetBackup hosts will avoid the 10 second delay waiting for the initial connection to PBX to timeout. Having the PBX port open is the long term direction of NetBackup and is required to use many of the new features such as SAN Client, Oracle Cloning, etc. Other possible workarounds include:
TECH162303 | 2014-04-09
Technical Solutions | CMS-XML

Job fails with status 232 after going active on RHEL media server using NIS/YP

...snip... 03:30:38.827 [43776] 2 logconnections: BPCD CONNECT FROM 2.2.2.2.53385 TO 3.3.3.3. 1556 fd = 6 ...snip...
TECH145022 | 2014-03-24
Technical Solutions | CMS-XML

Any backups using a newly installed media server fail with Status Code: 12 : File open Failed

The firewall configuration must allow connection from the media server to the master server on port 1556 . Additionally if any clients are configured to use Client side Deduplication the firewall must allow connection from the client to the master server on port 1556.
TECH145797 | 2014-01-26
Technical Solutions | CMS-XML

EMM connection failure on new media server. The command "nbemmcmd -getemmserver" on a new UNIX based NetBackup 6.5 media server produces the error: "Failed to initialize EMM connection".

command on the new media server confirmed the master server was able to resolve the new media server s hostname and ip address correctly. 4. telnet to master server s PBX port, 1556 , also OK 5. The following errors were reported in admin
TECH66433 | 2014-01-20
Technical Solutions | CMS-XML

ms-sql restores fail with status code 2850

14:31:41.226 [3132.3152] 2 logconnections: BPRD CONNECT FROM XXX.XXX.XXX.XXX.50149 TO XXX.XX.XXX.XX. 1556 fd = 836
TECH211497 | 2014-01-28
Technical Solutions | CMS-XML

Duplications of Granular (GRT) Backups from disk to tape gives error 191

admin log: 11:25:39.105 [23428] 2 logconnections: BPDBM CONNECT FROM 168.192.1.2.52139 TO 168.192.1.2. 1556 fd = 5 11:25:39.130 [23428] 2 db_end: Need to collect reply
TECH208798 | 2014-01-20
Technical Solutions | CMS-XML

After jobs hanging and failing with error 252, all new jobs remain queued

.. 08:57:55.052 [11264146] 2 logconnections: BPDBM CONNECT FROM 10.244.145.13.42546 TO 10.244.145.71. 1556 fd = 0 08:57:55.052 [11264146] 2 vnet_check_vxss_client_magic_with_info: ../../libvlibs/vnet_vxss_helper.c.871:0: Ignoring VxSS authentication: 2 0x00000002
TECH211569 | 2014-01-09
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?