YATES@C.CHEM.UPENN.EDU ("Yates, John H.") (09/12/90)
I still have not yet been able to get vmsbackup to work on our 4D/320S
IRIX 3.3 . I re-supplied the code that was sent to me to a few interested
users, if anyone has gotten it to work please let me know. (if so please
let me know what level VMS the tape was written on, and what level IRIX
it was read on. This may be very important.) If anybody wants
it and has time to play with it, let me know and I will send it to you.
Review of problem I see: I made a short 1600 bpi backup tape on a VAX/VMS
machine VMS4.5 . vmsbackup builds with no errors or warnings, but when I:
vmsbackup -tvf /dev/rmt/xmt0d0nr.1600
I get:
Snark: Invalid header block size
Volume: TEX
Saveset name: TEX.BCK number: 1
It does have the save set name correct. Thanks, John
yates@c.chem.upenn.edu
P.S. SGI, are you listening? This could be a great tool for making sites with
dozens of VMS save set backups on the shelf totally independent
of VMS machines, without a major marathon tape media conversion effort.msc@ramoth.esd.sgi.com (Mark Callow) (09/13/90)
In article <9009112017.AA12162@remote.dccs.upenn.edu>, YATES@C.CHEM.UPENN.EDU ("Yates, John H.") writes: |> |> vmsbackup -tvf /dev/rmt/xmt0d0nr.1600 |> |> I get: |> |> Snark: Invalid header block size |> Volume: TEX |> Saveset name: TEX.BCK number: 1 My guess is that vmsbackup needs to do some byte swapping when running on an IRIS. Was it originally written to run on UNIX on a VAX? -- From the TARDIS of Mark Callow msc@ramoth.sgi.com, ...{ames,decwrl}!sgi!msc "There is much virtue in a window. It is to a human being as a frame is to a painting, as a proscenium to a play. It strongly defines its content."