NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

Robot Error status code 17

Robot Error status code 17
HOWTO104778 | 2014-11-20
How To | CMS-XML

Device management status code 17

Device management status code 17
HOWTO104649 | 2014-11-20
How To | CMS-XML

Device configuration status code 17

Device configuration status code 17
HOWTO104563 | 2014-11-20
How To | CMS-XML

NetBackup status code: 17

Recommended Action: Save all error information and call customer support. Click here
HOWTO103947 | 2014-11-20
How To | CMS-XML

Advanced Success Rate report fails with opscenter-10808 error when spanning 2/17/2013 and certain time zones are selected

4.) Click the Save button to save the change 5.) re-run the Advanced Success Rate report with a date range that spans 2/ 17 /2013 and verify that it now completes successfully. ETA of Fix:
TECH206623 | 2013-11-14
Technical Solutions | CMS-XML

Unable to create object for restore - rai error = 17 Server status 2810 Exchange GRT (Granular Recovery Technology)

A Restore of Exchange GRT fails with ms-exchange policy restore error (2810) Status 2810
TECH193280 | 2013-10-30
Technical Solutions | CMS-XML

BUG REPORT: NetBackup SAN Client restore fails with Error 17: pipe open failed

BUG REPORT: NetBackup SAN Client restore fails with Error 17 : pipe open failed
TECH87699 | 2010-01-15
Technical Solutions | CMS-XML

DOCUMENTATION: Explanation of bpclntcmd options and recommended troubleshooting when the commands return errors.

08:33: 17 .290 [1843254] 2 logconnections: BPRD ACCEPT FROM 192.168.0.30 3815 TO 192.168.0.1.13720 08:33:17.292 [1843254] 2 connected_peer: Connection from host client_01.domain.com
TECH50198 | 2013-10-08
Technical Solutions | CMS-XML

hp-ux 11.31 Itanium backups fail with BPTM Error "External event caused rewind during write"

00039391: file 16: eof after 8 records: 1579008 bytes 00039392: file 17 : record 1: size 1024: NBU EMPTY header (file 16) 00039393: file 17: eof after 1 records: 1024 bytes
TECH155113 | 2011-12-09
Technical Solutions | CMS-XML

Exchange Backup using VMware Application Protection option fails with status 1

Status 1 20/11/2014 12:00:57 PM - end Application State Capture, Application State Capture; elapsed time: 0:01: 17 Status 1
TECH226480 | 2015-03-02
Technical Solutions | CMS-XML

Duplications using Quantum DXi NDMP DirectCopy may intermittently fail with a status 85

12: 17 :36.951 [11544] 2 bptm: INITIATING (VERBOSE = 5): -copy -cmd -nosig -everything -cn 1 -c ab_master -b ab_master_1350946816 -ipc /tmp/vnet-11534351099056104609000000000-o_awhw NULL medsvr1 -jobid 2438931 -priority 0 -v -p @aaaat -mediasvr medsvr1 -ndmp_dc -nh dxi1102b -nu backup -np 886a57176403113f9f102855626b3cf9484319e7fd37847fa45a78bf0fcec978451bc1210db1888fb71e65ace7f00a81a3e8c83f7386e10596f2a084ae6f1103 -nk 2d27576827124c22 -dpath @aaaat
TECH200976 | 2015-02-20
Technical Solutions | CMS-XML

NDMP backup fails with status 99 when port 10000 is also open

02/25/2014 12:28:26 - end writing; write time: 0:01: 17 NDMP backup failure (99)
TECH215719 | 2015-02-19
Technical Solutions | CMS-XML

NDMP restores failing with the error "ndmp_mover_listen failed, status = -1 (-1)", followed by NDMP policy restore error (2813)

From Activity Monitor Jobs Detailed Status : 07/14/2014 09:10: 17 Error ndmpagent (pid=6092) ndmp_mover_listen failed, status = -1 (-1) 07/14/2014 09:10:17 Error ndmpagent (pid=6092) NDMP restore failed from path ...
TECH222958 | 2015-02-19
Technical Solutions | CMS-XML

Occasionally MSEO backups report a status 85 during import or restore with backups taken while the touch file disable_immediate_weof was not present.

15:23:01.590 [6693] 2 io_ioctl: command (1)MTFSF 1 0x0 from (tmisc.c.1442) on drive index 0 15:23: 17 .573 [6693] 2 io_read_back_header: drive index 0, reading backup header 15:23:17.702 [6693] 8 io_read_block: read error on media id a00001, drive index 0 reading header block, Not enough space
TECH224038 | 2015-02-09
Technical Solutions | CMS-XML

GENERAL ERROR: Unable to start ltid and vmd on the master server; an error message is returned, stating "another ltid daemon is already running".

-rw-rw-rw- 1 root other 0 Oct 7 15:31 .ltisymlinks -rw------- 1 root other 0 May 9 17 :55 lmfcd.lock -rw-rw-rw- 1 root root 3603 Aug 22 17:52 ltitables
TECH15895 | 2015-02-06
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?