NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

Robotic status code 250

Robotic status code 250
HOWTO104750 | 2014-11-20
How To | CMS-XML

NetBackup status code: 250

NetBackup status code : 250
HOWTO104164 | 2014-11-20
How To | CMS-XML

Phase 2 import failes with error 250 on NDMP image | Symantec Connect

Phase 2 import failes with error 250 on NDMP image
Connect Forums | HTML

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

[root@server volmgr]# sysctl -a | grep kernel.sem kernel.sem = 250 32000 32 128 Which can be adjusted using the following command:
TECH213131 | 2014-12-18
Technical Solutions | CMS-XML

VMware backup with "File Level Recovery" fails with Status 636 due to disconnect between Master and Media Server

bpbrm: 12:10:23.472 [3644.4264] 2 bpbrm main: ADDED FILES TO DB FOR vmclient_1396281339 250 v4recovery 19:24:46.066 [3644.4264] 2 put_strlen_str: cannot write data to network: An existing connection was forcibly closed by the remote host.
TECH216670 | 2014-04-14
Technical Solutions | CMS-XML

Lotus point-in-time restore via SAN client fails with status 5 without restoring logs

13:40:52.157 PID:3352 TID:7204 3 [RestoreThread] 7204: Pipe ID = 1 All buffers are full at seq 161477; waiting on client 7304 13:40:52. 250 PID:3352 TID:7204 5 [ErrorDecoder] ILI: residue 50688 is less than bytes requested 65024 Thread 7204 Cdb[0] 0x3c Mode 2 Pipe ID 1 Seq 161506 Length 65024
TECH160320 | 2013-10-24
Technical Solutions | CMS-XML

GENERAL ERROR: Certain reports in Veritas NetBackup (tm) Advanced Reporter cause out of memory errors

75 MB of memory supported approximately 2200 rows in a report. 200 MB of memory handled approximately 4000 rows. 250 MB supported approximately 7000 rows.
TECH27726 | 2013-10-23
Technical Solutions | CMS-XML

Exchange 2010 GRT restore fails with status 5: Faulting application bpresolver.exe

08:58:01.399 [6368.5704] 4 make_bpresolver_call: TRV - BPRESOLVER has executed on server ( exchange-server-name ) == HERE there is no log for 10. 250 minutes
TECH160404 | 2013-10-24
Technical Solutions | CMS-XML

Oracle backup fails with status 27 after bptm receives a fault from libstspiDataDomainmt.so

f84e7f94 stspi_open_server (f851d400, ffbff498, ffbff090, ffbfee8c, ffbfed44, f84e7e90) + 104 fe556ce4 opensvh (68f340, 0, ffbff498, ffbff090, ffbfee8c, 6d3438) + 250 fe558188 open_server (0, ffbff498, ffbff090, ffbfee8c, 0, 0) + a8
TECH68762 | 2013-10-24
Technical Solutions | CMS-XML

GENERAL ERROR: ltid hangs on media server. Many oprd processes found running on media server.

19:55:04.110 [15163] 4 QueueMsg: Data.Pid=4239, Type=101, param1=-65, param2=-3504, LongParam=1 19:55:04. 250 [15163] 4 QueueMsg: Data.Pid=4255, Type=101, param1=-65, param2=-3504, LongParam=1
TECH56642 | 2013-08-29
Technical Solutions | CMS-XML

On Windows Media servers, occassional error 1117, drive I/O errors are seen in the problems report and in the job details in the Activity Monitor.

and name it as BusyRetryCount and the value should be set to 250 decimal 5. Exit regedit.
TECH204686 | 2013-04-15
Technical Solutions | CMS-XML

GENERAL ERROR: Getting Status 191, 800, 150, 50 while trying to duplicate images

06:23:34.234 [1476.8080] 2 init_tape: \\.\tape0 (SCSI coordinates {3,0,4,0}) configured with blocksize 0 06:23:34. 250 [1476.8080] 2 init_tape: \\.\tape0 (SCSI coordinates {3,0,4,0}) has compression enabled 06:23:34.265 [1476.8080] 2 io_open: SCSI RESERVE
TECH146711 | 2011-03-28
Technical Solutions | CMS-XML

BUG REPORT: DSSU duplications fail after upgrading a Windows master server to 7.0.1. Image Cleanup completes (Status 0) but is not expiring images.

169.254. 250 .221.58786 TO 169.254.250.221.1556 fd = 844
TECH138266 | 2011-03-15
Technical Solutions | CMS-XML

Getting exit status 252 and error message "NBEMM returned an extended error status: invalid error number (4005006)" on client backups.

6.0 Troubleshooting Guide , Page 250 : NetBackup Status Code: 252
TECH56312 | 2008-01-21
Technical Solutions | CMS-XML

BUG REPORT: Mixing full, differential, or incremental and Vault schedules in the "hot_catalog" backup policy can result in Status 227

05:22:16.125 [3704.1436] 2 new_image: setup_image_relationship() failed (227) 05:22:16. 250 [3704.1436] 2 bpdbm: request complete: exit status 227 no entity was found Workaround
TECH48895 | 2007-01-01
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?