NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

NetBackup status code: 662

NetBackup status code : 662
HOWTO90856 | 2013-10-02
How To | CMS-XML

NetBackup status code: 662

NetBackup status code : 662
HOWTO51205 | 2012-11-19
How To | CMS-XML

NetBackup status code: 662

NetBackup status code : 662
HOWTO35315 | 2010-10-29
How To | CMS-XML

NBCC 7.5 fails with status code 13 (file read failed) during bpimagelist

Snippet of bpdbm log 10:23:14. 662 [14891] 4 db_error_add_to_file: Bad image header: backuppolicy_1300727630_full, error : file read failed (13) 10:23:14.663 [14891] 16 list_client_images: Bad image header: backuppolicy_1300727630_full, error: file read failed (13)
TECH192547 | 2012-09-06
Technical Solutions | CMS-XML

Full backups fail intermittently with status 40 when they run for several hours

21:25:30.652 [16826574] 4 bpbkar PrintFile: /mydir/mydir2/base/data1/myfile_00.dbf 21:25:30. 662 [16826574] 2 bpbkar SelectFile: INF - cwd = /mydir/mydir2/base/data1 21:25:30.663 [16826574] 2 bpbkar SelectFile: INF - path = lost+found
TECH176851 | 2011-12-13
Technical Solutions | CMS-XML

GENERAL ERROR: vStorage Snapshot fails with "vmcGetObjDetails failed with status 48"

14:12:46.646 [3844.3572] 2 onlfi_vfms_logf: INF - vmwareLogger: GetObjDetails: sym_vmc_error: failed_to_get_dshm_properties 14:12:46. 662 [3844.3572] 2 onlfi_vfms_logf: INF - find_vm_by_displayname: vmcGetObjDetails failed with status 48 SOLUTION/WORKAROUND
TECH124961 | 2011-12-29
Technical Solutions | CMS-XML

Backups intermittently fail with status 24 or 42 within a few seconds of the start of data transfer.

833 12:56:37.17026 3.3.3.3 - 2.2.2.2 TCP D= 662 S=13782 Ack=3625715306 Seq=3009467682 Len=1460 Win=49640
TECH143964 | 2010-11-11
Technical Solutions | CMS-XML

During Disk Staging Storage Unit (DSSU) relocation jobs, large images fail to be relocated due to random media read errors. This results in the job ending with a status 191.

19:07:14. 662 [6660.888] 32 bp_sts_read_image: sts_read_image failed: error 2060017
TECH56511 | 2010-01-25
Technical Solutions | CMS-XML

Backups of Novell OES Linux server fail with 'FFFDFFB1 An internal TSA error has occurred.'

The following can be seen in the BPCD log on the NetWare client that is being used to backup the OES Linux server: 4:07:18 PM: [295. 662 ] 2 tar_backup::backup_create: TAR - backup filename = /netware
TECH55415 | 2008-01-08
Technical Solutions | CMS-XML

File Read error on netbackup client 7.0 | Symantec Connect

07:17:46.661 [16646184] <4> bpbkar: INF - Estimate:-1 -1 07:17:46. 662 [16646184] <2> bpbkar add_to_filelist: starting sizeof(filelistrec) <128> 07:17:46.662 [16646184] <4> bpbkar: INF - Processing /
Connect Forums | HTML

NDMP bakup failing with status 99 | Symantec Connect

14:24:18. 662 [4665] <2> logconnections: BPDBM CONNECT FROM 10.78.194.163.49761 TO 10.78.194.163.1556 fd = 8
Connect Forums | HTML

Physical location of error database, catalog database | Symantec Connect

NBU Admin Guide for Windows, Volume I http://www.symantec.com/docs/DOC3653 See p. 662 : Parts of the NetBackup catalog Figure 18-1 on p. 663 shows the default files and directories in a NetBackup catalog.
Connect Forums | HTML

191 errors on Duplcation Jobs | Symantec Connect

18:32:33. 662 [1132.4312] <2> nbconf_create_authentication_domain_rec: ../../libvlibs/nbconf_private.c.261: AT Domain Name: agfhqrm30
Connect Forums | HTML

Status Code Chart

661 662 663
TECH58686 | 2014-02-18
Technical Solutions | CMS-XML

STATUS CODE 249: When performing a backup of a client with NetBackup, the backup job completes with Status 249.

In the example above, a quick search through the bpbkar log shows a list of 28, 662 socket special files . It takes bpbkar about 2 minutes to pass the list of files to bpbrm over the single established socket.
TECH49166 | 2010-01-17
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?