I think this is what happened, I saw truncated file messages from
Netbackup mail.  I'll retry the restore and see if it can restore
them fully.  Thanks for that.

--
Dan

Mark.Donaldson AT cexp DOT com wrote:

> The last step in the restore is the changing of the mtime from the
> restoration time to the timestamps stored in the image database.  If
> something interrupts the restore operation, you can end up with this
> symptom.   
> 
> The files with the incorrect timestamp may be incomplete.  I'd restore them
> again to be sure.  If you want to test, do an alternate-name restore, then
> compare checksums for the two files.
> 
> 
> 
> -----Original Message-----
> From: veritas-bu-admin AT mailman.eng.auburn DOT edu
> [mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu]On Behalf Of Dan 
> Logcher
> Sent: Tuesday, October 26, 2004 11:47 AM
> Cc: Veritas-bu AT mailman.eng.auburn DOT edu
> Subject: Re: [Veritas-bu] Restored files have current time?
> 
> 
> Darren Dunham wrote:
> 
> 
>>>We recently restored a bunch of Oracle logs as a test and found
>>>that some had the current time of the restore as opposed to their
>>>creation date.  Is this normal?
>>>
>>>
>>What OS/filesystem do you mean, and which timestamp are you talking
>>about?
>>
>>UNIX systems generally have 3 timestamps, none of which are are a
>>creation date, each of which are viewable by 'ls' with appropriate
>>options.
>>
>>My understanding is that Oracle in general ignores timestamps.  It has
>>it's own serialized counters within the files for consistency.  If the
>>timestamps don't cause problems for your own procedures, I don't think
>>oracle will mind.
>>
> 
> Sorry,
> It's Tru64 5.1B UNIX.  The timestamp I'm referring to is lats modified
> time.  I restored the logs, most of which restore with the last modified
> time of 9am or so.  Some of them restored with 6pm time.. the time of
> the restore.
> 
>