NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

Robotic status code 256

Robotic status code 256
HOWTO104756 | 2014-11-20
How To | CMS-XML

NetBackup status code: 256

NetBackup status code : 256
HOWTO104169 | 2014-11-20
How To | CMS-XML

A potential for data loss has been discovered in NetBackup Server/Enterprise Server where Distributed File System Replication (DFSR) paths may be skipped on backup, yet report a Status 0. This has been observed in the unlikely case where the DFSR path exceeds 256 characters.

- The Shadow Copy method of backing up DFSR is used - One or more of the DFSR Shadow Copy paths exceed 256 characters - The DFSR data is later required for restore.
TECH76282 | 2012-06-01
Technical Solutions | CMS-XML

Receiving "System call failed with status: 256" when trying to do a new install on a RedHat 5.5 system

Receiving "System call failed with status : 256 " when trying to do a new install on a RedHat 5.5 system
TECH141173 | 2010-10-04
Technical Solutions | CMS-XML

GENERAL ERROR: Catalog image file uncompress is failing - the error "decompress_dbfile bpdbm system() returned 256 (1)" appears in bperror output

16 decompress_dbfile: system() returned 256 (1)
TECH57450 | 2009-01-13
Technical Solutions | CMS-XML

Status Code 85 (media read error) on NBU Hot Catalog restore job using media written with a 256 KB Block Size

It is possible that upgrading the Fiber Host Bus Adapter or its drivers can resolve this issue. Contact the hardware vendor for the Fiber HBA s for the vendor s recommendation on which HBA can support read/writes to tape using a 256 KB block size) then attempt the Hot Catalog restore from the current media that was written to with the 256 KB block size.
TECH84125 | 2009-01-15
Technical Solutions | CMS-XML

STATUS CODE 256: The message "Robot busy, multiple eject operation in progress" occurs when trying to eject media.

Robot busy, Multiple eject operation in progress ( 256 )
TECH46547 | 2006-01-29
Technical Solutions | CMS-XML

Media Manager status code 136

Recommended Action: Limit host names to 256 ASCII characters or less.
HOWTO104501 | 2014-11-20
How To | CMS-XML

NetBackup status code: 330

Recommended Action: Verify that the EMM database host name does not contain any space characters, and that the string size is a maximum of 256 characters long. Click here
HOWTO104242 | 2014-11-20
How To | CMS-XML

Drives marked as down due to Move Medium Error

Example as seen in robots log - only one move_medium is sent: 12:00:12.986 [14620] 5 tldcd:move_medium: TLD(0) initiating move_medium from addr 4136 to addr 256 12:00:30.304 [14620] 3 tldcd:log_scsi_error: TLD(0) key = 0x5, asc = 0x3b, ascq = 0xe, MEDIUM SOURCE ELEMENT EMPTY
TECH225696 | 2014-10-23
Technical Solutions | CMS-XML

After upgrading to 7.6.0.1/2.6.0.1, VMware backups via SAN may fail with Status 130 due to bpbkar core dump

The issue occurs after VDDK receives a SAN error during the backups: vdRead:VixInterface.cpp:559 TRACE : Read(9064624, 68476160, 256 ) g_vixinterfacelogger:libvix.cpp:1825 DEBUG : [vfm_esinfo] 2014-01-23t10:01:19.917Z [7eff73dbe700 info Libs ] fileioerrno2result: Unexpected errno=5, Input/output error
TECH214512 | 2014-08-12
Technical Solutions | CMS-XML

Subsequent backup or restore jobs with WAN resiliency, MSDP client direct, and accelerator enabled, fail with status code 40

8 and change the value to the number of threads required. The number of threads can be calculated by 256 *number of concurrent accelerator backup jobs.
TECH218268 | 2014-06-17
Technical Solutions | CMS-XML

GENERAL ERROR: On a NetBackup 6.x or 7.0 server, errors occur in the application event log stating "Application Error : The application failed to initialize properly (0xc0000142). Click on OK to terminate the application." This may occur for several different NetBackup processes.

5. Increase the third value by 256 or 512. For example, when the SharedSection equaled 1024,3072,512,512 in one case, changing it to 1024,3072,1024,512 resolved the issue.
TECH48099 | 2013-12-12
Technical Solutions | CMS-XML

NetBackup 5.1 BUG REPORT: Oracle RMAN backups using Advanced Client and Encryption options fail with status 25.

The workaround is to enable legacy encryption (40 or 56 bit) or to disable encryption for Oracle clients. Note: 128 and 256 bit encryption, now called Standard Encryption, is a new feature in NetBackup (tm) 5.1. Note: This problem may also affect database agents for DB2, Informix, ms-sql-server, SAP, and Sybase.
TECH38798 | 2013-10-23
Technical Solutions | CMS-XML

SQL RESTORE fails with Error 'RESTORE detected an error on page (10244:1799427905) in database "<DatabaseName>" as read from the backup set'

and buffer delays 16:13:17. 256 [19512.20960] 2 mpx_read_data: read short block, bytes = 32768, remainder = 0 16:13:17.272 [19512.20960] 2 mpx_read_data: ReadFile returned FALSE, A tape access reached a filemark.
TECH63983 | 2013-10-24
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?