NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

Media Manager status code 49

Media Manager status code 49
HOWTO104430 | 2014-11-20
How To | CMS-XML

Device management status code 49

Device management status code 49
HOWTO104675 | 2014-11-20
How To | CMS-XML

Device configuration status code 49

Device configuration status code 49
HOWTO104587 | 2014-11-20
How To | CMS-XML

NetBackup status code: 49

NetBackup status code : 49
HOWTO103979 | 2014-11-20
How To | CMS-XML

Client with encryption policy attribute is failing the backup with status 49. Job details show status 11: system call failed

Client with encryption policy attribute is failing the backup with status 49 . Job details show status 11: system call failed
TECH215265 | 2014-02-22
Technical Solutions | CMS-XML

STATUS CODE: 49 Restore of Oracle Proxy Copy backup fails with status 49, client did not start.

STATUS CODE : 49 Restore of Oracle Proxy Copy backup fails with status 49 , client did not start.
TECH43416 | 2013-10-23
Technical Solutions | CMS-XML

STATUS CODE: 5, 49 A restore fails with a Status 5 in the GUI and a Status 49 "Client did not start" is received in the logs.

STATUS CODE : 5, 49 A restore fails with a Status 5 in the GUI and a Status 49 "Client did not start" is received in the logs.
TECH32332 | 2013-10-23
Technical Solutions | CMS-XML

After upgrade of client to Netbackup 7.0.1 some backups getting an error 49

Standard backups failing with status 49 (client did not start) after upgrade from NB 7.0 to 7.0.1
TECH153875 | 2012-03-05
Technical Solutions | CMS-XML

Status Code 49 on Mac OS X clients

49
TECH66723 | 2011-08-24
Technical Solutions | CMS-XML

Status 49 when trying multi-stream backups

When trying multi-stream backups they fail with status 49 errors . Single stream backups run without any errors.
TECH145623 | 2010-12-18
Technical Solutions | CMS-XML

Backup jobs for hp-ux clients fail with status 49 after applying phss_33946 or phss_38140.

Backup jobs for hp-ux clients fail with status 49 after applying phss_33946 or phss_38140.
TECH64711 | 2009-01-24
Technical Solutions | CMS-XML

STATUS CODE 49: Backup attempts will fail reporting status 49 if the bpbkar binary does not exist on the client.

STATUS CODE 49 : Backup attempts will fail reporting status 49 if the bpbkar binary does not exist on the client.
TECH52636 | 2009-01-12
Technical Solutions | CMS-XML

client fails on very first selection- error status 49 - client did not start

client fails on very first selection- error status 49 - client did not start
TECH66868 | 2009-01-04
Technical Solutions | CMS-XML

STATUS CODE 49: When using Veritas NetBackup (tm) 5.x, the backup job fails with the error message "Client did not start (49)", but all the services/daemons are running fine, and it can communicate with other NetBackup systems without any issues.

Client did not start ( 49 ) Filesize limit exceeded (core dumped)
TECH37845 | 2007-01-02
Technical Solutions | CMS-XML

BUG REPORT: Duplication jobs fail with status code 50 (Client process aborted) reported

... 07:01: 49 .448 [6092.6824] 4 read_backup: successfully read (duplicate) backup id server1_1199761207, copy 1, fragment 1, 1026450 Kbytes at 42656,776 Kbytes/sec ...
TECH56753 | 2010-09-07
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?