NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

NetBackup status code: 5788

NetBackup status code : 5788
HOWTO91894 | 2013-10-02
How To | CMS-XML

NetBackup status code: 5788

NetBackup status code : 5788
HOWTO105366 | 2014-11-19
How To | CMS-XML

Backup of "Shadow Copy Components" completes with Status Code 1 for a Windows Server 2008 R2 system. The bpbkar log show an error fs_skip_object returned for BEDS for object 'Shadow Copy Components'

Symantec Internal link: http://svlvault.veritas.com/cgi-bin/patch_central?archive= 5788 External / Public link
TECH144975 | 2014-02-18
Technical Solutions | CMS-XML

Backup of 'Shadow Copy Compnents' fails with error: WRN - can't open file: System State:\

Symantec Internal link: http://svlvault.veritas.com/cgi-bin/patch_central?archive= 5788 External / Public link
TECH137514 | 2013-09-06
Technical Solutions | CMS-XML

Alternate path restore of a Windows client fails with status 12: Couldn't open /usr/openv/netbackup/.rename.xxx on client MyClient, status: 2

06:45:51.301 [6792. 5788 ] 16 process_requests: couldn t open file C:\Program Files\VERITAS\NetBackup\Logs\ALTPATH\.rename.446522 for write. errno = 2: No such file or directory
TECH174179 | 2013-09-03
Technical Solutions | CMS-XML

Status Code Chart

5787 5788 5789
TECH58686 | 2014-02-18
Technical Solutions | CMS-XML

NetBackup messages

debug logging has not been set up for Logging Assistant record See NetBackup status code : 5788 density is incorrect for the media id
HOWTO90266 | 2013-10-02
How To | CMS-XML

NetBackup messages

debug logging has not been set up for Logging Assistant record See NetBackup status code : 5788 density is incorrect for the media id
HOWTO103773 | 2014-11-19
How To | CMS-XML

Netbackup work with EMC NAS | Symantec Connect

2/11/2011 4:01:19 PM - Error bpbrm(pid=5788) removing rename file C:\Program Files\Veritas\NetBackup\.rename.5788 on client testing1_netbk FAILED, status = -2 2/11/2011 4:01:24 PM - Error bpbrm(pid= 5788 ) client restore EXIT STATUS 12: file open failed Riaan.Badenhorst Partner
Connect Forums | HTML

Exchange DAG backups fails with "client backup failed to read the file list (67)" due to poor network configuration

bpbkar: 11:01:47.577 AM: [ 5788 .11308] 2 tar_backup_tfi::setupFileDirectives: TAR - Processing filename list 11:02:47.609 AM: [5788.11308] 4 bpio::bread: INF - read timeout
TECH214138 | 2014-01-20
Technical Solutions | CMS-XML

NetBackup Services | Symantec Connect

12:28:26.476 [5556. 5788 ] <2> logconnections: BPRD ACCEPT FROM 10.1.9.195.49793 TO 10.1.9.195.13724
Connect Forums | HTML

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?