NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

Device configuration status code 28

Device configuration status code 28
HOWTO104571 | 2014-11-20
How To | CMS-XML

Device management status code 28

Message: Error in MsgGet Explanation:
HOWTO104659 | 2014-11-20
How To | CMS-XML

Media Manager status code 28

encountered a record that was smaller than expected while reading an EMM database record. Examine command output, debug logs, and system logs for a more detailed message on the error . See Setting debug logging to a higher level in the Troubleshooting Guide
HOWTO104414 | 2014-11-20
How To | CMS-XML

NetBackup status code: 28

Check the NetBackup All Log Entries report for clues on where and why the failure occurred. For detailed troubleshooting information, create debug log directories for the processes that think may have returned this status code . Then, retry the operation and check the resulting debug logs.
HOWTO103958 | 2014-11-20
How To | CMS-XML

NetBackup status code 28: failed trying to fork a process

: Check the NetBackup All Log Entries report for clues on where and why the failure occurred. For detailed troubleshooting information, create debug log directories for the processes that think may have returned this status code . Then, retry the operation and check the resulting debug logs.
TECH57815 | 2009-01-28
Technical Solutions | CMS-XML

3RD PARTY: Backups fail with status 28 errors (failed trying to fork a process) in NetBackup 6.x running on hp-ux 11iv3 HP Integrity (ia-64) servers.

3RD PARTY: Backups fail with status 28 errors (failed trying to fork a process) in NetBackup 6.x running on hp-ux 11iv3 HP Integrity (ia-64) servers.
TECH61849 | 2009-01-13
Technical Solutions | CMS-XML

Status code 28 (failed trying to fork a process) NBU 6.5.1 on hp-ux 11.31 | Symantec Connect

Status code 28 (failed trying to fork a process) NBU 6.5.1 on hp-ux 11.31 Created: 28 Mar 2008 • Updated: 23 May 2010 | 13 comments
Connect Forums | HTML

Backup fails with status 24 after the network stops delivering data to the media server.

01:23:26.254 [23681] 2 bpbrm kill_child_process: start 01:23: 28 .426 [23681] 2 bpbrm wait_for_child: child exit_status = 82 signal_status = 0 ...snip...
TECH76201 | 2014-10-16
Technical Solutions | CMS-XML

DOCUMENTATION: How to troubleshoot and correct the error "ld.so.1: bpdbm: fatal: relocation error: file /usr/openv/lib/libvbp.so: symbol slp_errmsgstr: referenced symbol not found" when applying the NetBackup patch 6.5.4

-rwxr-xr-x 1 root bin 17474 Apr 24 2010 vrtsnb_6.5.6.preuninstall -rwxr-xr-x 1 root bin 20249 Apr 28 2010 vrtsnb_clt_6.5.6.postinstall -rwxr-xr-x 1 root bin 20249 Apr 28 2010 vrtsnb_clt_6.5.6.postuninstall
TECH74064 | 2011-01-25
Technical Solutions | CMS-XML

BUG REPORT: Duplication jobs fail with status code 50 (Client process aborted) reported

07:00: 28 .052 [6796.3912] 2 bptm: INITIATING (VERBOSE = 5): -dup -cmd -nosig -v -L D:\VERITAS\NetBackup\vault\sessions\V1\sid382\duplicate.log.2 -en -ru root -rclnt server1 -jobid 299454 -mediasvr server1 -c server1 -b server1_1199761207 -cl
TECH56753 | 2010-09-07
Technical Solutions | CMS-XML

GENERAL ERROR: The message "tar_base::v_vtarmsgw: TRV - object not found for file system backup:" occurs in the client's bpbkar log.

does. 8:48: 28 .111 AM: [388.2748] 2 tar_backup::backup_create: TAR - backup filename = D:\Backup\steve.sjc 8:48:28.111 AM: [388.2748] 2 tar_backup::backup_create: TAR - backup filename = D:\Backup\steve.doc
TECH39188 | 2014-12-15
Technical Solutions | CMS-XML

Backup to Windows master server fails with status code 12 when using long client or policy names

Job Details show that bpbrm detected a premature exit by the client process and that bpbkar exited with status 12. 1/21/2014 6:44: 28 AM - Critical bpbrm(pid=2516) unexpected termination of client image-level-small-linux-01%20(e38ebe5e-8176-4270-ab37-95126a56d7f7)
TECH214234 | 2014-11-06
Technical Solutions | CMS-XML

GENERAL ERROR: A NetBackup client restore fails with Status Code 52/2850: Message: timed out waiting for media manager to mount volume.

9/29/2008 9:45:41 AM - Warning bprd(pid=3388) Restore must be resumed prior to first image expiration on 10/10/2008 11:22:34 AM 9/29/2008 9:45:42 AM - end Restore; elapsed time: 00:05: 28 the restore failed to recover the requested files(5)
TECH63671 | 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

Drives marked as down due to Move Medium Error

Running strace on tldcd process showed that at the OS level x2 scsi move_medium commands were sent (a5 = scsi CDB for move medium) 14620 12:00:13 ioctl(17, sg_io, { S , sg_dxfer_from_dev, cmd[12]=[a5, 00, 00,00, 10, 28 , 01, 00, 00, 00, 00, 00], mx_sb_len=32, iovec_count=0 snip
TECH225696 | 2014-10-23
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?