Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SCO vxrestore

Status
Not open for further replies.

terrywashington

Technical User
Jun 28, 2001
185
US
I am attempting to restore data from a tape that was archived using the vxdump command in SCO version
4.2MP 2.1.3 i386. I am using vxrestore -r and receive the below messages. I simply want to restore everything from the tape. Is there an easy way to do this?

saluk1:root:#vxrestore -r
open: No such file or directory
cannot open symbol table file ./restoresymtable
abort? [yn] n
stat: Bad file number
cannot stat symbol table file ./restoresymtable
abort? [yn] n
read: Bad file number
cannot read symbol table file ./restoresymtable
abort? [yn] n
Incremental tape too low


 
Are you restoring it onto a mounted vxfs filesystem?

man vxrestore
....
-r Read the tape and load into the current directory. -r should be used only after careful consideration, and only to restore a complete dump tape onto a clear file system or to restore an incremental dump tape after a full-level zero restore. Thus,

mkfs -F vxfs /dev/vx/dsk/vol1 80m
mount -F vxfs /dev/vx/dsk/vol1 /mnt
cd /mnt
vxrestore -r


is a typical sequence to restore a complete dump. Another vxrestore can then be performed to restore an incremental dump on top of this. Note that vxrestore leaves a file restoresymtab in the root directory of the file system to pass information between incremental vxrestore passes. This file should be removed when the last incremental tape has been restored.


....
 
The fileysystem was not vxfs when the tape was created via vxdump. Would I still need to restore to a vxfs filesystem as you specified above. Here is a copy of the filesystem structure.

saluk1:root:#df -k
filesystem kbytes used avail capacity mounted on
/dev/root 1477980 985452 492528 67% /
/dev/dsk/c0b0t0d0sa 16065 4268 11796 27% /stand
/dev/fd 0 0 0 0% /dev/fd
/proc 0 0 0 0% /proc
/dev/dsk/c0b0t0d0s4 2097152 576912 1520240 28% /home
/processorfs 0 0 0 0% /system/processor
/tmp 512000 384 511616 1% /tmp
/dev/dsk/c0b0t3d0s2 2097152 1340448 756704 64% /home/pawsdist
/dev/dsk/c0b0t3d0s1 2097152 843568 1253584 41% /home/pawsadm/db
/dev/dsk/c0b0t5d0s1 2097152 1731200 365952 83% /home/pawsdata
/dev/dsk/c0b0t5d0s2 2095104 414152 1680952 20% /home4
/dev/dsk/c0b0t1d0s1 512000 0 512000 0% /var/tmp
 
ok based on the man pages i would say no it doesn't have to be. They say that vxdump and vxrestore are compatable with dump and restore and can read each others tapes as long as the dumper is an older version than the restorer.

Now since it looks like you are trying to restore it on a linux system how compatable is the version of vxrestore that you are using. (i say a linux system because of the /proc and /dev/dsk nodes)
 
Thanks for the info Stan. The system is actually running SCO 4.2MP 2.1.3 i386. It does resemble a Linux filesystem. Anyway I restored the data by running vxrestore -i, entered the "extract" command with no arguments and all of the data was restored recursively to the directory that I was in.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top