Status 183 - Tar received an invalid archive
Hi,
I am getting status 183 error during restoration.
I checked the destination folder, It is having full perrmissions and Space also
07/09/2012 00:41:31 - begin Restore
07/09/2012 00:41:44 - number of images required: 1
07/09/2012 00:41:44 - media needed: STO381
07/09/2012 00:41:44 - media needed: STO382
07/09/2012 00:41:44 - media needed: STO756
07/09/2012 00:42:18 - restoring from image Timefinder_1340965643
07/09/2012 00:42:20 - Info bpbrm (pid=17763) cdcdrmisdb is the host to restore to
07/09/2012 00:42:20 - Info bpbrm (pid=17763) telling media manager to start restore on client
07/09/2012 00:42:20 - Info bpbrm (pid=17763) spawning a brm child process
07/09/2012 00:42:20 - Info bpbrm (pid=17763) child pid: 17773
07/09/2012 00:42:20 - connecting
07/09/2012 00:42:21 - Info bptm (pid=17768) Waiting for mount of media id STO756 (copy 1) on server bkpsvr.
07/09/2012 00:42:21 - started process bptm (pid=17768)
07/09/2012 00:42:21 - mounting STO756
07/09/2012 00:42:21 - Info bptm (pid=17768) INF - Waiting for mount of media id STO756 on server bkpsvr for reading.
07/09/2012 00:42:21 - Info bpbrm (pid=17773) start tar on client
07/09/2012 00:42:21 - Info tar (pid=0) Restore started.
07/09/2012 00:42:21 - connected; connect time: 0:00:00
07/09/2012 00:42:21 - requesting resource STO756
07/09/2012 00:42:21 - granted resource STO756
07/09/2012 00:42:21 - granted resource HP.ULTRIUM4-SCSI.002
07/09/2012 00:43:24 - mounted STO756; mount time: 0:01:03
07/09/2012 00:43:24 - Info bptm (pid=17768) STO756
07/09/2012 00:43:25 - Info bptm (pid=17768) INF - Waiting for positioning of media id STO756 on server bkpsvr for reading.
07/09/2012 00:43:25 - positioning STO756 to file 10
07/09/2012 00:44:22 - positioned STO756; position time: 0:00:57
07/09/2012 00:44:22 - begin reading
07/09/2012 00:44:23 - Info bpbrm (pid=17763) sending media manager msg: CONTINUE RESTORE
07/09/2012 01:01:19 - positioning STO756 to file 11
07/09/2012 01:01:19 - positioned STO756; position time: 0:00:00
07/09/2012 01:01:19 - Info bpbrm (pid=17763) sending media manager msg: CONTINUE RESTORE
07/09/2012 01:15:24 - positioning STO756 to file 12
07/09/2012 01:15:24 - positioned STO756; position time: 0:00:00
07/09/2012 01:15:24 - Info bpbrm (pid=17763) sending media manager msg: CONTINUE RESTORE
07/09/2012 01:23:10 - positioning STO756 to file 13
07/09/2012 01:23:10 - positioned STO756; position time: 0:00:00
07/09/2012 01:23:10 - Info bpbrm (pid=17763) sending media manager msg: CONTINUE RESTORE
07/09/2012 01:30:59 - positioning STO756 to file 14
07/09/2012 01:30:59 - positioned STO756; position time: 0:00:00
07/09/2012 01:30:59 - Info bpbrm (pid=17763) sending media manager msg: CONTINUE RESTORE
07/09/2012 01:53:59 - positioning STO756 to file 15
07/09/2012 01:53:59 - positioned STO756; position time: 0:00:00
07/09/2012 01:53:59 - Info bpbrm (pid=17763) sending media manager msg: CONTINUE RESTORE
07/09/2012 02:30:07 - positioning STO756 to file 16
07/09/2012 02:30:07 - positioned STO756; position time: 0:00:00
07/09/2012 02:30:07 - Info bpbrm (pid=17763) sending media manager msg: CONTINUE RESTORE
07/09/2012 03:09:28 - positioning STO756 to file 17
07/09/2012 03:09:28 - positioned STO756; position time: 0:00:00
07/09/2012 03:09:29 - Info bpbrm (pid=17763) sending media manager msg: CONTINUE RESTORE
07/09/2012 03:12:29 - Info tar (pid=0) done. status: 3
07/09/2012 03:12:29 - Info bpbrm (pid=17763) media manager for backup id Timefinder_1340965643 exited with status 0: the requested operation was successfully completed
07/09/2012 03:12:29 - end reading; read time: 2:28:07
07/09/2012 03:12:29 - Info tar (pid=0) done. status: 183 - tar received an invalid archive
07/09/2012 03:12:29 - restored from image Timefinder_1340965643; restore time: 2:30:11
07/09/2012 03:12:29 - Info bpbrm (pid=17763) sending media manager msg: TERMINATE
07/09/2012 03:12:30 - Warning bprd (pid=17731) Restore must be resumed prior to first image expiration on Wed Jun 26 15:57:23 2024
07/09/2012 03:12:31 - end Restore; elapsed time 2:31:00
Failed to get status code information (2826)
Kindly request your commnets on the same
Hi All,
Thanks for all.
Please find the issue closure.
Status 183 is becoz of invalid tar header found.The symantec engineer commented that the backup contains corrupted files.He suggested that the files belongs to oracle database and they have been backup using policy type "Standard". All Database files should backup through appropriate Netbackup Database Agent.
Please find the Tar log.
-----------------------------------------------------------------------------------------------------------------------------------
16:18:04 (12803.001) CKP - 12803.001 1343299684 1 10245323 41702722 13 0 0 54 /oraflash2_clone/app/oracle/oradata/MISBI/sysaux03.dbf
16:18:08 (12803.001) ERR - Invalid TAR header found:
16:18:08 (12803.001) INF - 0: M-B M-^? M-@
16:18:08 (12803.001) INF - 0: 00c2 0000 ffc0 0000 0000 0000 0000 0000
16:18:08 (12803.001) INF - 16: M-P M-7 @ ^C M-h z { | }
16:18:08 (12803.001) INF - 16: d0b7 0000 0000 4000 0003 e800 7a7b 7c7d
16:18:08 (12803.001) INF - 32: M-^A M-0
16:18:08 (12803.001) INF - 32: 0000 81b0 0000 0000 0000 0000 0000 0000
16:18:08 (12803.001) INF - 48:
16:18:08 (12803.001) INF - 48: 0000 0000 0000 0000 0000 0000 0000 0000
16:18:08 (12803.001) INF - 64:
16:18:08 (12803.001) INF - 64: 0000 0000 0000 0000 0000 0000 0000 0000
16:18:08 (12803.001) INF - 80:
16:18:08 (12803.001) INF - 80: 0000 0000 0000 0000 0000 0000 0000 0000-----------------------------------------------------------------------------------------------------------------------------------
