home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!wupost!usc!elroy.jpl.nasa.gov!nntp-server.caltech.edu!SOL1.GPS.CALTECH.EDU!CARL
- From: carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick)
- Newsgroups: comp.os.vms
- Subject: Re: File format change by BACKUP?
- Date: 12 Nov 1992 12:54:50 GMT
- Organization: HST Wide Field/Planetary Camera
- Lines: 27
- Distribution: world
- Message-ID: <1dtk6rINNenk@gap.caltech.edu>
- References: <1992Nov12.122046.484@hhcs.gov.au>
- Reply-To: carl@SOL1.GPS.CALTECH.EDU
- NNTP-Posting-Host: sol1.gps.caltech.edu
-
- In article <1992Nov12.122046.484@hhcs.gov.au>, sharmp@hhcs.gov.au writes:
- =We have just had a situation where the backup command has done a funny on us.
- =The situation was a backup to tape was being done of a number of indexed RMS
- =files. The operator was prompted for another tape, and had to abort due to
- =problems with the tape mount.
- =
- =When the files are recovered from tape, the last file on the tape prior to the
- =operator abort is in sequential format. I was fairly sure that backup restored
- =files in the same format as they were put on tape. Is it possible for the file
- =to be still opened when the operator aborted and for this to result in a
- =different file format? The recovery command used was just
- = backup/log/select=(filenames)
-
- This is just a guess, but: The fastest way to restore a file to disk is to
- simply copy the contents in block mode then fiddle with the file header after
- you've copied all the data. I suspect that this is the technique that BACKUP
- uses. Now, when you say "the last file on the tape prior to the operator
- abort," are you *SURE* that the entire file was on the tape? Or could it be
- that BACKUP hadn't finished processing that file?
- --------------------------------------------------------------------------------
- Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL
-
- Disclaimer: Hey, I understand VAXen and VMS. That's what I get paid for. My
- understanding of astronomy is purely at the amateur level (or below). So
- unless what I'm saying is directly related to VAX/VMS, don't hold me or my
- organization responsible for it. If it IS related to VAX/VMS, you can try to
- hold me responsible for it, but my organization had nothing to do with it.
-