NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

A rare potential for data loss exists when using the NetBackup FlashBackup feature on a volume that has a very small cluster/block size, such as 512 bytes. Restores for Incremental backups performed by FlashBackup on this type of volume may result in the restoration of corrupt files, but the restore completes with a Status 0 (Successful).

A rare potential for data loss exists when using the NetBackup FlashBackup feature on a volume that has a very small cluster/block size, such as 512 bytes. Restores for Incremental backups performed by FlashBackup on this type of volume may result in the restoration of corrupt files, but the restore completes with a Status 0 (Successful).
TECH65738 | 2013-10-24
Technical Solutions | CMS-XML

NetBackup status code: 512

NetBackup status code : 512
HOWTO90782 | 2013-10-02
How To | CMS-XML

After upgrade to 7.1, catalog backups fail with a status code: 2 [ System call failed with status: 512 ]

25M -ch 500m -cl 25M \ /usr/openv/db/staging/NBDB.db\ -ds \ /usr/openv/db/staging\ 16:45:54.205 [7997] 16 NBDBsystem: System call failed with status : 512 16:45:54.205 [7997] 16 validate_database: Database validation failed for database NBDB
TECH175134 | 2012-12-17
Technical Solutions | CMS-XML

NetBackup status code: 512

NetBackup status code : 512
HOWTO51131 | 2012-11-19
How To | CMS-XML

NetBackup status code: 512

NetBackup status code : 512
HOWTO35241 | 2010-10-29
How To | CMS-XML

Redirected SQL database restore fails with status 5

10:07:58.123 [5201.4375] 16 readFromServer: ERR - recv() returned 0 while reading 512 bytes on 1164 socket
TECH148200 | 2013-10-24
Technical Solutions | CMS-XML

Troubleshooting error messages in the NetBackup Administration Console for UNIX

Messages with status codes 511 and 512 may or may not begin with Unable to login, status : Note: A status code does not always accompany the error message.
HOWTO91519 | 2013-10-02
How To | CMS-XML

Troubleshooting error messages in the NetBackup Administration Console for UNIX

Messages with status codes 511 and 512 may or may not begin with Unable to login, status : Note: A status code does not always accompany the error message.
HOWTO72875 | 2012-11-19
How To | CMS-XML

Troubleshooting error messages in the NetBackup Administration Console for UNIX

Messages with status codes 511 and 512 may or may not begin with Unable to login, status : Note: A status code does not always accompany the error message.
HOWTO33271 | 2011-03-10
How To | CMS-XML

DOCUMENTATION: How to troubleshoot and correct the error "Fatal error: disk write failure /usr/openv/db/data/NBDB.log"

setting is 2097151 in this example. Multiplying the block size ( 512 ) by the file(blocks) size (2097151) would yield the maximum byte count a file can grow to.
TECH75308 | 2009-01-07
Technical Solutions | CMS-XML

VMware policy is failing with status 6 and 23.

10/21/2013 11:18:28 - Info bptm (pid=14932) setting receive network buffer to 1048576 bytes 10/21/2013 11:18:28 - Info bptm (pid=14932) using 512 data buffers 10/21/2013 11:18:29 - Info bptm (pid=14932) start backup
TECH211280 | 2014-08-18
Technical Solutions | CMS-XML

Incremental VMware Backups or Duplications of Linux VMs are failing with Status 84 intermittently to deduplication storage

130603_8_pdplugin.log:06/03/13 23:55:40 [19629:bptm] [19629] [DEBUG] PDSTS: vxms_transadr: bmw=0xffffffff, map_part=0, part_index=32390, pix=32390 130603_8_pdplugin.log:06/03/13 23:55:40 [19629:bptm] [19629] [DEBUG] PDSTS: fbu_fill_bitmap: (1562) stream_offset=159927296, file_offset=0, length= 512 , fsize=303
TECH208047 | 2014-05-01
Technical Solutions | CMS-XML

MSDP backups fail with status 84

19c5 131072 65536 512 1 3628957165
TECH216358 | 2014-05-12
Technical Solutions | CMS-XML

file read failed:Status 13 on all VMs using SAN transfer type - " VixDiskLib: No transport modes availble to access disks"

1:46:16.606 PM: [2628.3088] 2 WinMain: DAT - lpCmdLine = -r 1209600 -ru root -dt 0 -to 0 -clnt CLIENTNAME -class vmdisplayname_san_localdisk -sched Full -st FULL -bpstart_to 300 -bpend_to 300 -read_to 300 -blks_per_buffer 512 -use_otm -fso -ifr -pid 6040 -mediasvr mediaservername -bt 1308084376 -t 0 -b clientname_1308084376 -kl 28 -fi -S mastersevername -fim NONE -ct 29 -shm
TECH165311 | 2014-04-23
Technical Solutions | CMS-XML

NDMP restores fail with media error EXIT STATUS 85

11:35:47.282 [4712.6328] 2 read_backup: using 32 data buffers 11:36:09.872 [4712.6328] 2 read_data: read short block, 312 bytes, sending to socket 11:36:10.059 [4712.6328] 2 bp_sts_read_image_non_512: adjusting offset or length to a 512 byte boundry
TECH214057 | 2014-02-24
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?