vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Hello, i tried to restore one file from a backup created with fbackup. ( so i was told) I checked with frecover -V and -I that it IS a fbackup tape and the needed file should be on the tape. Magic Field:FBACKUP_LABEL Machine Identification:9000/800 System Identification:HP-UX Release Identification:B.11.00 Node Identification:quali-hp User Identification:root Record Size:16384 Time:Mo., 14. Juli 2003, 19:00:02 Media Use:83 Volume Number:1 Checkpoint Frequency:256 Fast Search Mark Frequency:200 Index Size:20255278 12649 Backup Identification Tag:12649 1058202002 Language:de_DE.iso885915@euro 42576 1 /home/hage/ha-varsich But the restore runs now since 15 hours: root 22823 20942 1 17:45:21 pts/0 10:28 frecover -x -i /home/hage/ha-varsich -f /dev/rmt/0m I truss the process: ioctl(4, MTIOCTOP, 0x7f7f0a54) = 0 read(4, 0x40018458, 16384) = 0 read(4, 0x40018458, 16384) [running] read(4, " 1 2 3 3 1 7 \0 ".., 16384) = 128 read(4, "# # \nf i ".., 16384) = 16384 ioctl(4, MTIOCTOP, 0x7f7f0a54) = 0 read(4, 0x40018458, 16384) = 0 read(4, 0x40018458, 16384) [running] read(4, " 1 2 3 3 1 7 \0 ".., 16384) = 128 read(4, "# # \nf i ".., 16384) = 16384 ioctl(4, MTIOCTOP, 0x7f7f0a54) = 0 read(4, 0x40018458, 16384) = 0 read(4, 0x40018458, 16384) [running] read(4, " 1 2 3 3 1 7 \0 ".., 16384) = 128 read(4, "# # \nf i ".., 16384) = 16384 ioctl(4, MTIOCTOP, 0x7f7f0a54) = 0 read(4, 0x40018458, 16384) = 0 read(4, 0x40018458, 16384) [running] read(4, " 1 2 3 3 1 7 \0 ".., 16384) = 128 read(4, "# # \nf i ".., 16384) = 16384 ioctl(4, MTIOCTOP, 0x7f7f0a54) = 0 read(4, 0x40018458, 16384) = 0 Is the syntax incorrect ? S.Marquardt |
| |||
| > But the restore runs now since 15 hours: > root 22823 20942 1 17:45:21 pts/0 10:28 frecover -x -i > /home/hage/ha-varsich -f /dev/rmt/0m I have not the man page near me but try to read (verify) entirely your tape. -V and -I read only tape'header. May be there is a read error and the drive try endless to correct it. Alain. |
| ||||
| On Thu, 24 Jul 2003 14:22:17 GMT, Frank Slootweg <this@ddress.is.invalid> wrote: > As Alain (implicitly) points out, the on-tape index is unreliable >because it is at the beginning of the tape and hence can never know in >advance if the file made it (i.e. active, unreadable, deleted, tape >error, tape full, etc.) to the tape or not. Only the on-disk index, made >with the "-I" option of f*backup* is reliable, see the fbackup(1M) >manual page for details (browse it using "index" as a keyword). > > As mentioned by Melvyn, you may want to use the "-m" option (report >Fast Search Marks) of frecover to see if frecover makes any progress. > > To get a reliable index from the tape, do a pseudo-restore ("-N") with >the "-v" option ("-N" will do everything *except* the actual restore): > >/usr/sbin/frecover -r[m]vN -f /dev/rmt/... 2>/tmp/filelist > > Out of interest: What kind of device and tape is this, i.e. including >the tape type/length? > DLT C5141F Stefan |
| Thread Tools | |
| Display Modes | |
|
|