NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

Device management status code 33

Device management status code 33
HOWTO104662 | 2014-11-20
How To | CMS-XML

Device configuration status code 33

Device configuration status code 33
HOWTO104575 | 2014-11-20
How To | CMS-XML

NetBackup status code: 33

NetBackup status code : 33
HOWTO103963 | 2014-11-20
How To | CMS-XML

GENERAL ERROR: NetBackup for Microsoft SQL Server backups fail with Status code 2; client logs report error message: "unable to check if feature <33> is licensed".

16 bsa_checkfeatureid: unable to check if feature 33 is licensed
TECH43388 | 2010-01-15
Technical Solutions | CMS-XML

DOCUMENTATION: Explanation of bpclntcmd options and recommended troubleshooting when the commands return errors.

08: 33 :17.290 [1843254] 2 logconnections: BPRD ACCEPT FROM 192.168.0.30 3815 TO 192.168.0.1.13720 08:33:17.292 [1843254] 2 connected_peer: Connection from host client_01.domain.com
TECH50198 | 2013-10-08
Technical Solutions | CMS-XML

MSDP media write error (84)

optimized duplication failed, media write error (84). 2/12/2013 2: 33 :39 AM - Info msdp.symantecs.org(pid=25204) StorageServer=PureDisk:msdp.symantecs.org;
HOWTO89078 | 2013-10-01
How To | CMS-XML

GENERAL ERROR: How to troubleshoot robot communication issues in Windows

20041211 10:58:27 NetBackup TLD Control Daemon E13942 NA dci0050vms2 TLD(4) key = 0x2, asc = 0x4, ascq = 0x0, LOGICAL UNIT NOT READY, CAUSE NOT REPORTABLE 20041022 09: 33 :12 NetBackup TLD Control Daemon E13942 NA dci0050vms2 TLD(0) key = 0x4, asc = 0x40, ascq = 0x1, HARDWARE ERROR , GENERAL System log:
TECH38829 | 2010-09-07
Technical Solutions | CMS-XML

EventID 33 sidebyside error | Symantec Connect

EventID 33 sidebyside error
Connect Forums | HTML

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

07/11/2013 11:35:33 - Error bpduplicate (pid=23428) Status = no images were successfully processed. 07/11/2013 11:35: 33 - end Duplicate; elapsed time 0:10:05 no images were successfully processed (191)
TECH208798 | 2014-12-30
Technical Solutions | CMS-XML

VMware restore failing with "VMware policy restore error(2820)" due to timeout in bptm child pid "wait for child pid #### timeout"

11/25/2014 11:29:10 AM - Info tar32(pid=10124) INF - Transport Type = nbd 11/25/2014 11:29: 33 AM - Info tar32(pid=10124) INF - Transport Type = nbd 11/25/2014 11:50:03 AM - Info bptm(pid=7560) waited for empty buffer 9483 times, delayed 71284 times
TECH227068 | 2014-12-12
Technical Solutions | CMS-XML

NetBackup status code: 20

[15773] 4 bpmap_mm_get_devid: device_index -1 14:47:02.031 [15773] 16 bpmap_send_extend: ERR - can t obtain device id string EMC:SYMMETRIX:601092014000 14:47: 33 .167 [15773] 16 bpbkar Exit: ERR - bpbkar FATAL exit status = 227: no entity was found 14:47:33.167
HOWTO103950 | 2014-11-20
How To | CMS-XML

NetBackup status code: 12

09:55:33.941 [6092] 16 bpfsmap: ERR - open_snapdisk: NetBackup snapshot enable failed error 3 09:55:33.942 [6092] 32 bpfsmap: FTL - bpfsmap: can t open snapshot disk /dev/rdsk/c4t1d0s3 errno 0 09:55: 33 .950 [6092] 16 bpbkar Exit: ERR - bpbkar FATAL exit status = 12: file open failed 09:55:33.956
HOWTO103942 | 2014-11-20
How To | CMS-XML

Accelerator backup produces Status 1 due to: WIN32 13: The data is invalid

: G:\Data\userdocs\Document.DOC (WIN32 13: The data is invalid. 11/25/2014 9:01: 33 PM - Error bpbrm(pid=634) from client MyClient: ERR - failure reading file
TECH226852 | 2014-12-09
Technical Solutions | CMS-XML

BUG REPORT: Duplication job using SharedDisk receives a status code 800 error due to emmstatus=914 but activity monitor shows status code 0.

stays active waiting for further instructions until 17:20: 15:18: 33 .941 [15036] 2 read_brm_msg: additional delay to wait for bpbrm/bpduplicate message This continues until bptm
TECH70228 | 2014-11-06
Technical Solutions | CMS-XML

Restores or verification of a limited number of Exchange and Sharepoint images protected using NetBackup 7.1.0.x to PDDO/MSDP storage units fail with the error "invalid tar header encountered, attempting to continue"

10/23/2012 14:24:05 - begin reading 10/23/2012 15:12: 33 - end reading; read time: 0:48:28 10/23/2012 15:12:52 - begin reading
TECH200000 | 2014-11-04
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?