NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

Media Manager status code 163

Media Manager status code 163
HOWTO91018 | 2013-10-02
How To | CMS-XML

NetBackup status code: 163

Status code 163 is an informational message. It indicates that the media block size was changed before a backup job from the last checkpoint resumed. Since the media block size must be consistent, the job was restarted from the beginning.
HOWTO90581 | 2013-10-02
How To | CMS-XML

Media Manager status code 163

Media Manager status code 163
HOWTO51367 | 2012-11-19
How To | CMS-XML

NetBackup status code: 163

Status code 163 is an informational message. It indicates that the media block size was changed before a backup job from the last checkpoint resumed. Since the media block size must be consistent, the job was restarted from the beginning.
HOWTO50929 | 2012-11-19
How To | CMS-XML

Media Manager status code: 163

Media Manager status code : 163
HOWTO35477 | 2010-10-29
How To | CMS-XML

NetBackup status code: 163

Status code 163 is an informational message. It indicates that the media block size was changed before a backup job from the last checkpoint resumed. Since the media block size must be consistent, the job was restarted from the beginning.
HOWTO35039 | 2010-10-29
How To | CMS-XML

STATUS CODE 163: nbpushdata -add will fail to complete if errors are encountered during the upgrade to Veritas NetBackup (tm) 6.0.

16 check_for_mappings_file: Verify that external_types.txt has been loaded into the EMM database. 16 main: check_for_mappings_file failed: 163
TECH45001 | 2010-01-25
Technical Solutions | CMS-XML

Incremental backup using client direct fail with status 14

13:48:14. 163 : [1556.5604] 16 dtcp_write: TCP - failure: send socket (424) (TCP 10053: Software caused connection abort)
TECH185860 | 2013-11-12
Technical Solutions | CMS-XML

nbfdrv64 dies on new FT media servers, erroring with "InitPipe returned 983081"

pciex1077,2532.1077.162 pciex1077,2532.1077. 163 pciex1077,2532.1077.164
TECH144936 | 2013-10-16
Technical Solutions | CMS-XML

A large Oracle RMAN restore transfers the data but fails with status 5 and status 52: Timed out waiting for the media to be mounted and positioned

...snip... 14:47:29. 163 [27002] 2 send_brm_msg: ERROR 82 14:47:29.163 [27002] 2 catch_signal: EXITING with status 82
TECH58821 | 2013-10-24
Technical Solutions | CMS-XML

Catalog backup fails with STATUS CODE: 35

bpbdm log shows: 13:26:03. 163 [13971] 2 exec_catalog_dr_protection: classname= catalog_backup_policy_name , fqDRImagePath=/usr/openv/netbackup/db/images/ master_server_name /1340000000/ catalog_backup_policy_name _1340180966_full, status =0 13:26:03.165 [13971] 2 exec_catalog_dr_protection: Writing DR image
TECH191339 | 2013-04-25
Technical Solutions | CMS-XML

Application backups fails with status 6 or status 42 when extjob.exe inherits NetBackup sockets

Len= 163 Win=64231 (4054606377) 48: fae7 0ac4 0000 4649 4c20 2d20 3738 3634
TECH189853 | 2013-03-27
Technical Solutions | CMS-XML

Full backups fail intermittently with status 40 when they run for several hours

21:25:37. 163 [15581340] 2 media_siginfo_print: 0: delay 1 signo SIGHUP:1 code 0 pid 16154734
TECH176851 | 2011-12-13
Technical Solutions | CMS-XML

ltid and vmd services are not running on all Windows media servers - receive error "Failed to validate this host with the EMM"

11:48:33.841 [5588.5432] 16 vmd: terminating - the operation requested has failed ( 163 )
TECH136104 | 2011-08-17
Technical Solutions | CMS-XML

nbproxy BPCDConnectionHolder: NB API: bpcr_connect_and_verify() failed with status:25. Special Error Code: 0

masterserver1 Command did not complete successfully. ----------------------------- EXIT STATUS = 163 ----------------------------
TECH163805 | 2011-08-15
Technical Solutions | CMS-XML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?