NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

Seeing error "Tar returned 127." when installing Netbackup 6.5.6 client patch on Redhat

cannot Tar returned 127 . No client binaries in /net/server/gsmo_software/gsmo_software.grp/INSTALLS/symantec/nbu_6.5/nbu_6.5.6_linux/vrtsnb_clt_6.5.6.Linux.tar.Z.
TECH189943 | 2014-01-09
Technical Solutions | CMS-XML

Media Manager status code 127

Media Manager status code 127
HOWTO90990 | 2013-10-02
How To | CMS-XML

NetBackup status code: 127

NetBackup status code : 127
HOWTO90548 | 2013-10-02
How To | CMS-XML

Media Manager status code 127

Media Manager status code 127
HOWTO51339 | 2012-11-19
How To | CMS-XML

NetBackup status code: 127

NetBackup status code : 127
HOWTO50896 | 2012-11-19
How To | CMS-XML

GENERAL ERROR: The Problems report shows the error "<16> compress_dbfile: system() returned 32512 (127)".

16 compress_dbfile: system() returned 32512 ( 127 )
TECH43400 | 2011-09-22
Technical Solutions | CMS-XML

NetBackup status code: 127

NetBackup status code : 127
HOWTO35006 | 2010-10-29
How To | CMS-XML

Media Manager status code: 127

Media Manager status code : 127
HOWTO35449 | 2010-10-29
How To | CMS-XML

error while loading shared libraries: /usr/openv/lib/libvxpbxcommonst.so: cannot restore segment prot after reloc: permission denied 127

/usr/openv/netbackup/bin/admincmd/bpminlicense: error while loading shared libraries: /usr/openv/lib/libvxPBXCommonST.so: cannot restore segment prot after reloc: Permission denied ( 127 ) Troubleshooting:
TECH76134 | 2009-01-25
Technical Solutions | CMS-XML

NetBackup status code 127: specified media or path does not contain a valid NB database backup header

127
TECH58614 | 2009-01-12
Technical Solutions | CMS-XML

Exit Status 127 when running bpbackupdb on Red Hat Linux ES 3.0 and VERITAS NetBackup (tm) 5.0

Exit Status 127 when running bpbackupdb on Red Hat Linux ES 3.0 and VERITAS NetBackup (tm) 5.0
TECH33260 | 2005-01-14
Technical Solutions | CMS-XML

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

17:50:14.939 [2172.4736] 2 vnet_async_connect: ... 0: connect: async CONNECT FROM 127 .0.0.1.57288 TO 127.0.0.1.57287 fd = 396
TECH162303 | 2014-04-09
Technical Solutions | CMS-XML

VMware Intelligent Policy Test Query operation is failing with "error parsing discovered XML data(1)"

Raw nbsl log: 0,51216,309,132,1453,1395775593654,53436,139780432148224,0:, 127 :xml parser fatalerror: invalid byte � at position 1 of a 1-byte sequence at line: 1 column: 81921 (../XmlInterface.cpp:607),32:XmlDocumentInterface::fatalerror,1
TECH216148 | 2014-04-14
Technical Solutions | CMS-XML

VMware for Replication Director snapshot are failing with "status: 4201" when the NetApp NFS is configured using a private name/network

15:16:59.709 [7294] 32 onlfi_fim_split: FTL - snapshot services: snapshot selection failed: provider-private error. NBUPlugin.log: 2013/11/06 15:16:59: ERROR : 127 .0.0.1: Claim Volume: Failed to find short name of filer private ip or name here
TECH212314 | 2014-02-03
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".

SOLUTION: The problem was resolved after the following entry was added to the local /etc/hosts file on the new media server and then NetBackup and Private Branch Exchange (PBX) service were restarted: 127 .0.0.1 localhost
TECH66433 | 2014-01-20
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?