NetBackup Enterprise Server Search Results

Knowledge Base Search         Search Tips


Symantec Suggests


NetBackup status code: 1000

command before you submit the manual job. Click here to view technical notes and other information in the Symantec Knowledge Base about this status code .
HOWTO104939 | 2014-11-20
How To | CMS-XML

Netbackup Administration Console crashes with Application error 1000 and 1004

Netbackup Administration Console crashes with Application error 1000 and 1004
TECH144245 | 2013-11-15
Technical Solutions | CMS-XML

Active Directory GRT restore failing with status code 2808 and 5

10/8/2013 19:39:58.920 [RAIConsumer::_objectOpenAndWrite()] write() completed, status = 0 (../RAIConsumer.cpp: 1000 )
TECH211394 | 2015-01-21
Technical Solutions | CMS-XML

NetBackup status code: 41

Due to the files and directories it scans, it has not replied to the server within client_read_timeout or client_connect_timeout. This error occurs during backups when directories have thousands of unmodified files or during restores of the sparse files that have thousands of holes. For this case, try to add or modify the client_read_timeout value in the server s /usr/openv/netbackup/bp.conf
HOWTO103971 | 2015-01-20
How To | CMS-XML

Backup jobs fail with error: Failed to get status code information (2505)

bpdbm log: 15:31:14.460 [1480] 16 DbmOdbcConnect::initialize_odbc: Odbc connection failed ErrMsg [Sybase][ODBC Driver][SQL Anywhere]Connection error: An error occurred during the SharedMemory connection attempt, ErrC ode -1, Sqlstate 08001, ConnStr PROWS= 1000 ;PBUF=8m;CS=utf8;UID=dbm_main;PWD=******;LINKS=shmem,tcpip{PORT=13785};ENG=nb_server;DBN=NBDB;CON=dbm_1480_1
TECH213131 | 2014-12-18
Technical Solutions | CMS-XML

NDMP backup of EqualLogic fs7500 filer fails with status 13

15:12:42.133 [Debug] ndmpagent 134 [ConnectionToBrm::SendFileHistory] FH TO BRM: Nev - 0 0 0 0 156 0 0 10 33060 root root 1000 878720000 878720000 878720000 /TYPE=dump ...snip...
TECH192541 | 2014-12-01
Technical Solutions | CMS-XML

NetBackup status code: 1

For NetBackup Snapshot Client, the maximum path name length is 1000 characters for snapshot backups, not 1023. When the snapshot is created, a new mount point is added to the beginning of the file path. If the new mount point plus the original file path exceeds 1023 characters, the backup fails with status code 1.
HOWTO103931 | 2014-11-20
How To | CMS-XML

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

23682/1: e c v b u f : s e t t i n g r e c e i v e n e t w o r k 23682/1: b u f f e r t o 2 6 2 1 4 4 b y t e s
TECH76201 | 2014-10-16
Technical Solutions | CMS-XML

MSDP backups are failing with "Storage Server Error: (Storage server: PureDisk:msdp07) MBPOAddList: Failed to complete PO addlist webservice ((unknown)) v-454-36"

If you see thousands of entries, then perform some cleanup in the events table. For example remove garbage collection messages.
TECH208793 | 2014-08-05
Technical Solutions | CMS-XML

BUG REPORT: Unable to restore from the Java GUI. "invalid date specified" error returned - Java is truncating the path.

TO[0]: -T -H -S -D fairway -C fairway -X -s 1371747906 -e 1383004817 -R /usr/openv/netbackup/logs/user_ops/user_name/logs/jbp-string.chg - K -t 0 -M - k -
TECH217485 | 2014-06-08
Technical Solutions | CMS-XML

MSDP disk pool goes offline causing backups to fail with status 2074

In the spoold and storaged logs: July 11 06:34:18 ERR [000000002399cf60]: 25017: FileCopyA: could not open destination file k :\pdbackup\data/journal/delstat_0.log July 11 06:34:18 ERR [000000002399cf60]: 25017: FileMoveA: copy failed
TECH192770 | 2014-02-18
Technical Solutions | CMS-XML

Shadow Copy Components Backup fails with status 13 due to error "Could not allocate memory for Metadata Stream"

bpbkar log shows thousands of certificates in C:\Documents and Settings\All Users\Application Data\Microsoft\Crypto\RSA\MachineKeys\ In this case over 300,000 eg:
TECH176570 | 2014-02-06
Technical Solutions | CMS-XML

NDMP restore job failing with "ERROR 174 from media manager"

09/24/2012 12:36:04 - Error bpbrm (pid=291) Couldn t write to file /usr/openv/netbackup/.rename.291 on client media-server1, status: 28 09/24/2012 12:36:05 - Error bpbrm (pid=291) cannot put rename file on media-server1 df - k output on affected media server media-server1 confirmed /usr file system encountered disk full condition
TECH197274 | 2014-01-26
Technical Solutions | CMS-XML

NetBackup install fails with pkgadd error "WARNING: unable to commit contents database update" on Solaris

24292/1: 18.2635 write(2, \n I n s t a l l i n g , 12) = 12 24292/1: 18.2637 write(2, N e t B a c k u p a n .., 27) = 27 24292/1: 18.2639 write(2, a s , 5) = 5
TECH164161 | 2014-01-09
Technical Solutions | CMS-XML

bpdbm fails to connect to database with a connection error: Found server but communication error occurred

21:13:33.622 [544996] 16 DbmOdbcConnect::initialize_odbc: Odbc connection failed ErrMsg [Sybase][ODBC Driver][SQL Anywhere]Connection error : Found server but communication error occurred, ErrCode -1, Sqlstate 08001, ConnStr PROWS= 1000 ;PBUF=8m;CS=utf8;UID=dbm_main;PWD=******; LINKS=shmem,tcpip {PORT=13785};ENG=nb_bms-master;DBN=NBDB;CON=dbm_544996_1
TECH210207 | 2013-12-16
Technical Solutions | CMS-XML

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?