NetBackup Enterprise Server Search Results


Knowledge Base Search         Search Tips


   

Symantec Suggests

  Next 

NetBackup status code: 183

NetBackup status code : 183
HOWTO104103 | 2014-11-20
How To | CMS-XML

NetBackup status code 183: tar received an invalid archive

183
TECH58657 | 2009-01-12
Technical Solutions | CMS-XML

STATUS CODE 92 and 183: An error will occur when restoring or verifying data backed up on Windows clients using the Veritas NetBackup (tm) Encryption Option.

A verify of the image will fail with a Status 183 (tar received an invalid archive). The following messages will appear in the install_path \VERITAS\NetBackup\logs\bpbrm\ date .LOG
TECH44803 | 2007-01-14
Technical Solutions | CMS-XML

Status 183 - Tar received an invalid archive | Symantec Connect

Status 183 - Tar received an invalid archive
Connect Forums | HTML

Restores or verification of a limited number of Exchange and Sharepoint images protected using NetBackup 7.1.0.x to PDDO/MSDP storage units fail with the error "invalid tar header encountered, attempting to continue"

10/23/2012 21:07:44 - Info tar (pid=9150) done. status : 183 : tar received an invalid archive
TECH200000 | 2014-11-04
Technical Solutions | CMS-XML

A potential for skipped duplications has been discovered in NetBackup 6.5.4 when using Vault, or in NetBackup versions 6.5.1 - 6.5.3 if a specific vltrun binary has been applied. Vault may end with status code 0, 306 or 308 if duplication rules are configured. If a Status 0 occurs due to this issue, duplications are skipped without indication.

10:20:46.182 [1588] 4 vltrun@LogDuplicationBatches^1434: DupRule for MS=ms2 #Batches=4 10:20:46. 183 [1588] 4 vltrun@LogDuplicationBatches^1434: DupRule for MS=ms3 #Batches=0 10:20:46.183 [1588] 4 vltrun@LogDuplicationBatches^1434: DupRule for MS=ms4 #Batches=2
TECH72483 | 2013-10-24
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

14:47:29.183 [26886] 2 bpbrm signal_media_manager: got ERROR 82 from media manager 14:47:29. 183 [26886] 2 bpbrm Exit: ERROR 52 sent to parent process The bptm log
TECH58821 | 2013-10-24
Technical Solutions | CMS-XML

Backup fails with status 13 after bpbrm reports; socket read failed: errno = 62 - Timer expired

This will cause bpbrm to terminate bptm. 09:00:20. 183 [7249] 2 write_file_names: successfully wrote buffer to comm_sock 09:00:20.183 [7249] 2 bpbrm write_filelist: wrote CONTINUE on comm_sock
TECH71821 | 2013-10-11
Technical Solutions | CMS-XML

Auto Image Replication duplications are failing with Status 84, bpdm failing with "wait failed: error 2060014"

Disable the tracking of incoming webservice calls by removing the above 2 lines from /opt/pdweb/etc/apache2.conf as it may fill up the space really fast. Review the /Storage/log/incoming_connections.log for the following line - 10.146.251.128 - - [25/Jan/2012:11:43:45 -0600] GET /spa/ws/ws_job.php?action=getJobStatus id=2348 login=root passwd= password HTTP/1.1 200 183
TECH180353 | 2013-05-24
Technical Solutions | CMS-XML

Many small jobs in a large MPX group may result in slow performance and status 13 or status 6

12:46:37.019 [22497] 4 write_backup: successfully wrote backup id myclient_1249908170, copy 1, 1058 Kbytes 12:47:02. 183 [22497] 4 write_backup: successfully wrote backup id myclient_1249908125, copy 1, 1058 Kbytes 12:47:51.960 [22497] 4 write_backup: successfully wrote backup id myclient_1249907325, copy 1, 1699 Kbytes
TECH135606 | 2011-04-26
Technical Solutions | CMS-XML

client server failing with status 21 errors

10.128.181. 183 .41307 TO 10.128.180.10.13724
TECH146731 | 2011-01-27
Technical Solutions | CMS-XML

BUG REPORT: Vault catalog backups may fail with status code 294 reported in the Activity Monitor.

The vault log shows the start of the backup: 12:45:47. 183 [16622] 2 db_execvaultcatalogbackup:
TECH55690 | 2007-01-27
Technical Solutions | CMS-XML

Getting error “FILE WRITE READ” CODE 59 | Symantec Connect

Getting error “FILE WRITE READ” CODE 59 host s00asr07.xxx.xx.xxx: s00asr07.xxx.xx.xxx at 127.x.x.xxx host s00asr07.xxx.xx.xxx: s00asr07.xxx.xx.xxx at 11.45. 183 .176 aliases: s00asr07.xxx.xx.xxx 2002:7e06:664::7e06:664 127.x.x.xxx
Connect Forums | HTML

Linux FS restore failure - "Standard Policy restore error 2800" | Symantec Connect

Linux FS restore failure - "Standard Policy restore error 2800" 11/3/2012 11:53:03 AM - Info tar32(pid=5954) done. status : 183
Connect Forums | HTML

Restore complete with "invalid error number(2826)" | Symantec Connect

<2> bpbrm write_msg_to_progress_file: (9019.001) (9019.001) WRN - can't create directory: \\?\UNC\svlfiler2\Groups (WIN32 183 : Cannot create a file when that file already exists.
Connect Forums | HTML
  Next 

Please Sign In

Login using SymAccount.

Search Feedback

Are we answering your questions?