NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

NetBackup status code: 300

NetBackup status code : 300
HOWTO90709 | 2013-10-02
How To | CMS-XML

NetBackup status code: 300

NetBackup status code : 300
HOWTO51057 | 2012-11-19
How To | CMS-XML

NetBackup status code: 300

NetBackup status code : 300
HOWTO35168 | 2010-10-29
How To | CMS-XML

STATUS CODE 6: SAP backup fails with a Veritas NetBackup (tm) Status Code 6: the backup failed to backup the requested files, and the logs contain the error: "SAP sap_lock_backint_file: ERR - (300) sec timeout waiting for lock file" and "bpbkar expand_wildcards: ERR - SAP end alter table space failed".

16 SAP sap_lock_backint_file: ERR - ( 300 ) sec timeout waiting for lock file: /usr/.../sap/.backint.lock.1140746845.3031252 16 SAP sap_alter_tablespace: ERR - in setting lock file
TECH47883 | 2007-01-13
Technical Solutions | CMS-XML

NetBackup SAP HANA backup jobs fail with error 41 and 25

is 300 seconds. For tape backups, change the Client connect timeout
HOWTO88624 | 2013-09-30
How To | CMS-XML

Live browse errors for snapshots

The file browse timeout specifies how long the NetBackup Master Server can wait for a response from the NetBackup Client while it lists the files. The default timeout is 300 seconds. The Master Server waits only for that period of time and file read error is displayed as that period is insufficient to list files when there are more than equal to 20 LUNs.
HOWTO69623 | 2012-02-07
How To | CMS-XML

Backups may fail with status 25 for Windows clients if Taiwan/Chinese Traditional locale is used

05:37:30.609 [4676.456] 2 process_requests: fork cmd = bpbrm -backup ... -L /C/Program\ 300 \240 Files/Veritas/NetBackup/Logs/user_ops/dbext/logs/2236.0.1400881046 ... The bpbrm debug log
TECH218254 | 2014-09-16
Technical Solutions | CMS-XML

vStorage snapshots are orphaned due to "Unable to access file since it is locked" error during snapshot deletion

Notes this adds a 10 second delay in bpfis delete operations. For Linux/Appliance this value must be HEX. For example dword:12c is 300 seconds.
TECH181118 | 2014-06-27
Technical Solutions | CMS-XML

BUG REPORT: Incorrect backup Status for Oracle on Windows platforms, when there is no script present.

The Following will be observed in the Install Path /netbackup/logs/bphdb/date.log 11:05:35.050 [7748.7928] 2 logparams: -sb -rdbms oracle -S Master -to 300 -c oracle -s FULL -clnt clnt -FULL -kl 28 -b e012967_1401786334 -jobid 679 -shm
TECH222203 | 2014-06-22
Technical Solutions | CMS-XML

Clients failing backups with status code 24 errors

Valid Range: 1-0xffffffff Default: 7,200,000 (two hours) Recommendation: 300 ,000
TECH145234 | 2014-05-18
Technical Solutions | CMS-XML

13: Some of the clients behind the firewall are failing with a Status 13 file read failure / 131 - Connection reset by peer

Extend the 300 second firewall idle session timeout to 7500 seconds or greater Another option is to change the TCP keepalive setting on the master and media server operating systems to a frequency that is less than the current firewall idle port timeout setting.
TECH178712 | 2014-05-07
Technical Solutions | CMS-XML

MS SQL and other XBSA Backups fail with status code 239 reported after applying the NetBackup 7.5.0.7 maintenance release.

is 300 seconds. Backup started Tue Feb 18 18:39:38 2014 nbpem
TECH215866 | 2014-04-28
Technical Solutions | CMS-XML

file read failed:Status 13 on all VMs using SAN transfer type - " VixDiskLib: No transport modes availble to access disks"

1:46:16.606 PM: [2628.3088] 2 WinMain: DAT - lpCmdLine = -r 1209600 -ru root -dt 0 -to 0 -clnt CLIENTNAME -class vmdisplayname_san_localdisk -sched Full -st FULL -bpstart_to 300 -bpend_to 300 -read_to 300 -blks_per_buffer 512 -use_otm -fso -ifr -pid 6040 -mediasvr mediaservername -bt 1308084376 -t 0 -b clientname_1308084376 -kl 28 -fi -S mastersevername -fim NONE -ct 29 -shm
TECH165311 | 2014-04-23
Technical Solutions | CMS-XML

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

[root@server volmgr]# sysctl -w kernel.sem= 300 32000 32 1024
TECH213131 | 2014-04-09
Technical Solutions | CMS-XML

Incremental backup failed for db2 database with status code 13 on unix client.

Default timeout values can be too short for big database. Default timeout value: client_read_timeout = 300
TECH215027 | 2014-03-26
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?