What type of drives? 
We had a similar problem with Super DLT
drives.  We initially received media read
errors and after two weeks of working on
the problem with Veritas discovered that
we had a typo in the st.conf file.  After
fixing that problem we suddenly started
getting this error "image not in tar format"
when trying to restore images written before
implementing the fix.

The problem seemed to be enhanced by 
changing the SIZE/NUMBER_DATA_BUFFERS.
Veritas says we are now SOL trying to read
a month's worth of backups.

Ken Sibley
Sr. Unix Administrator
Accor Economy Lodging
ksibley AT accorel DOT com
469-737-3370

> -----Original Message-----
> From: Adam Levin [mailto:alevin AT audible DOT com]
> Sent: Friday, February 01, 2002 8:30 AM
> To: veritas-bu AT mailman.eng.auburn DOT edu
> Subject: [Veritas-bu] failure of restore
> 
> 
> 
> Netbackup 3.4.1, Solaris 8, Spectra Gator 64000 AIT2 library.
> 
> We had a server's root disk fail miserably yesterday.  I 
> re-jumpstarted,
> but I need to get some configuration information from the old machine.
> So, I figured I'd restore the most recent full backup.  I 
> decided to throw
> the restore directly onto the media server, since it'd be 
> fast, there's
> plenty of disk space, and I could pick and choose what I wanted to
> restore from the resulting list of files.
> 
> However, I'm getting this in the restore log:
> 09:26:51 (2477.008) Restoring from image created Sun Jan 27 
> 00:32:11 2002
> 09:26:55 (2477.008) INF - Waiting for mount of media id 
> 000167 on server
> johnson.hq.audible.com.
> 09:27:41 (2477.007) INF - Waiting for positioning of media id 
> 000189 on
> server johnson.hq.audible.com.
> 09:28:49 (2477.007) INF - Beginning restore from server
> johnson.hq.audible.com to client johnson.hq.audible.com.
> 09:28:51 (2477.007) backup id 
> lincoln.audio.audible.com_1011504714 is not
> a tar formatted image
> 
> Then, I get a bunch of "file ... not restored", and then this:
> 09:28:51 (2477.007) more than 10 files were not restored, logging is
> supended
> 09:28:51 (2477.007) INF - TAR EXITING WITH STATUS = 92
> 09:28:51 (2477.007) INF - TAR RESTORED 0 OF 0 FILES SUCCESSFULLY
> 09:28:51 (2477.007) INF - TAR KEPT 0 EXISTING FILES
> 09:28:51 (2477.007) INF - TAR PARTIALLY RESTORED 0 FILES
> 
> Now, Netbackup *created* these backups, so how in the world 
> could they not
> be tar formatted?
> 
> Is it possible that for whatever reason, Netbackup's "User backup and
> restore" is picking up a different version of tar from my 
> path?  That's
> the only thing that comes to mind, but I really can't 
> understand why that
> would happen.
> 
> Thanks,
> -Adam
> 
> Adam Levin, Senior Unix Systems Administrator | 
> http://www.audible.com/
> Audible, Inc.     
> Wayne, NJ, 07470        I don't think my mind has *ever* been
> 973-837-2797                                  pink and happy.
> 
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>